People easily forgot how they laughed at wizards in Harry Potter series who said "You-Know-Who" instead of "Voldemort". Now they are doing exactly the same thing.

At this point it's easier to just write the code. If my prompt is to be longer than the code produced, why bother with explaining that to LLM?

The delta between "make a small requirement that you can check and verify" vs "create the code yourself" is pretty big. A well crafted sentence can sometimes still be hours of work.

Sounds very depressing.

I used to code at night with a kerosene lamp sitting on my desk. I love the light spectrum of a live fire.

"Portable" (they couldn't even fit in a pocket) CD players were the worst thing imho. Too sensitive to even small shocks, which was particularly annoying while taking longer walks, and draining batteries like crazy. I switched from cassette players to MP3 players, almost completely skipping the era of CD players. I've tried it once or twice because my sister had it, and never again.

What other social interactions are needed more than: "One flat white to go, please", and "Thank you"? Asking genuinely, because I don't know what else I can say.

I usually make coffee at home, but the baristas are remarkably stable in my area. When I do go to a coffee shop (there are 2-3 that I might go to) there’s a good chance I’ll recognize the barista and that they’ll also remember me. In one such case I’ve been seeing the same one for close to a decade, and we always chat for a bit.

I think most baristas who do it for more than a year or two learn to not primarily be a coffee factory but first to make a positive impact on the people they see. The coffee is something that can be made consistent (and in a way, boring) through practice, but personal connection, especially when it is genuine, has a real draw.

Lots of things. “Could I have some sugar, please; two frappy mochachos? one with almond milk; can you explain what all these options are, please; what the hell is mushroom powder?” In today’s coffee shops this can lead to hours of complex social interaction at the counter, enriching our lives and ultimately extending our lifespans. — sorry, couldn’t resist. In seriousness, I actually find this conversation interesting. Some coffee shops do have quite a social culture around them, though I think they’re outliers on whole. Here in Spain it’s a mix, but in some it is like everyone’s friends with the barista.

> whatever ultimately gets you to where you want to be

Money.

> classifying people is utter BS, and assigning labels is very hurtful

Is saying "you have cardiovascular issues" labeling or diagnosis? Where would you draw the line? We have a definition of a healthy heart, likewise we have a definition of a healthy brain. If I suffered a stroke, it's not because my body is unique, it's because of a disease.

Ironically, we chose a work style that requires maintaining prolonged focus, which sucks without meds (especially when dealing with boring tasks).

I really enjoy doing the dishes now that the dishwasher does ~100% percent of the work.

Maintaining a switch for all possible TIFF tags doesn't sound like a good programming practice, though.

I kind of have to disagree. I have really learned to love the explicitness of a big ole' switch statement. Its fast, no misdirection, all available in one place, and its easily readable where you need it. All of the "clean code" options for something like this I have seen that used more abstraction ultimately just split up the fact you have to keep a list of 100 something hex code values and some value there.

Can't tell what would be the best case (pun intended) for you, depends on the language you use. Yes, it will eventually end up as some sort of look-up table, though switch statement is the last option I'd use (assuming you gonna have more than 20 cases or so).

The good thing of programming without generative assistants is that it makes you think how to make the algorithm and the code better to avoid too much manual work. Laziness of engineers is crucial for automation and optimisation.

So... Mindless coding is it? The best part of coding is doing research and learning. Coding, for the pure sake of finishing the project as soon as possible with the least involvement, sounds like doing unpleasant chores.

Far from mindless, just at a different abstraction level. What should the software do, what capabilities and features, how to slice it into small increments (product management work)? What user journeys, what should the screens look like (UX work)? What architecture and components, which libraries, what communication protocols, what layering, what kind of tests, what kind of data structure and data persistence (Architect/tech lead work)? For example, for the DSL syntax i'll have claude code suggest different options, and detail out one of the proposal i like best.

Nice, but what does it mean? Are you gonna replace a group of specialists in their fields with prompts to LLM?

I have a background in coding (including assembly), worked on UX projects, as a technical architect, a product owner, and now a product manager in the last 30 years, so yes.

Some people love the act, which is fine. A good many other people just want the result.

Something something quarter-inch hole.

I agree. Vibe coding eventually just becomes repetitively QA testing the work of a bad engineer.

You can have AI write automated tests before writing the code, so it can QA itself.

You can try. What happens is it cheats you at every turn and finally admits it wasn’t testing anything when you ask why it’s still broken.

Yes, this actually happens.