250 karma · joined October 7, 2023
Historically women couldn't vote, and black people were segregated and worse. I guess those things were "created and forced into the lexicon by political activists" terms back them I guess.
The core thing is that one term humanizes a group of people that contributes to communities, pay taxes, the other dehumanizes them and opens the gate to justifying well, criminalization and prosecuting. You decided to choose the later.
Criminals don't pay taxes, don't contribute to communities as far as I know. That's a quite positive outcome for the "illegal" immigration given the history of the US's destabilization of southern countries. You could advocate for a better country, yet you decide to punch down. That's quite telling, not much has changed in the United States compared to the 19th century.
Such broad categorization about that vast of a nation seems disparaging to me. Grouping an entire nation on a label, and marking it inferior to your own.
I'm curious and hear a lot about agentic programming, yet hear little about the cognitive load from it. Having more code generated doesn't make you more productive, in fact, I would argue the contrary is the case. There's more code to understand, more code to discard, an extra decision (which result do I pick? How do I split the workload through my agents), which is not at all how we operate (I. E context switching, limited by our cognitive energy, working task by task).
I really don't buy the whole agentic thing. The only reasonable use case I can see for it, is to scaffold multiple projects at the same time.
I think phones are the real issue. Even if you have unlimited access to whatever short form apps, eshopping, information on a computer, it's the ease of being able to immediately get a hit as you lie comfortably in your couch, or while you wait for something, that's the issue. No time to simmer in your thoughts, or to be able to put in some effort to get a reward. We are lazy by nature, smartphones exploit that to make profits, and as a consequence to that, we rewire our brains to prefer the seamlessly of just scrolling down ad infinitum.
In any REAL, workload, with good processes, code review makes speed of code generated a moot point. You still move as fast as you can review the code, and no, I won't debate that you can rely on LLMs, a deterministic language predictor, to determine the correctness of code; in the context of the business, and technical implications.
Kind of.... I don't know. To get placed such requirements from the top down and not fight back, just take it head on, not even maliciously, don't even oppose it on a technical basis, just be like "yeah, you've now gotta ship faster or you're left behind, so therefore LLMs must be the future!", no critical thought attached. Is this shit coming from experienced engineers?
Preposterous we're relying on "it's better because I feel like", "dudes who don't use it are falling behind at work", "they ask for it in job interviews".
Code review is specifically for code quality, more lower level stuff.
It circles back to the question, is this unimportant enough for me to delegate it to a LLM that might get it wrong? If the answer is yes, why even do it to begin with. If the answer is no, you have to do it manually.
I personally though, see value in this type of automation. Stuff like tag categorization, indexing, that otherwise would've been lost seems like a good fit for LLMs. Whether or not they're an ideal solution and something else like a search engine would've been a better fit, is a different question.