I say that knowing how often those words have been wrong throughout history.
Yup
Previous technology shifts were “learn the new thing, apply existing skills.” AI isn’t that. It’s not a new platform or a new language or a new paradigm. It’s a shift in what it means to be good at this.
A swing and a miss
Oh yeesh. Sounds like it’s got a good way to go before regular use becomes viable
Neither of those have working audio channels yet right?
Fatal Fury: City of the Wolves has Cristiano Ronaldo and Salvatore Ganacci in it. Having a goofy soccer character as a character is out of place in that game, I don’t want real people in fighting games at all, and to top it off, Rinaldo is a piece of shit anyway.
Open source maintainers don’t want to hear this, but this is the way people code now, and you need to do your part to prepare your repo for AI coding assistants.
Or they don’t like the character that they don’t have to pick.
Yeah I’m not playing a game when I’ll have to see a real life rapist in the character select screen
There was a time when I worked in an office where I had a door and a 15 minute commute. I preferred that over working at home for the social aspects, but longer commute eating into my free time and and the stress of trying to focus while working in open floor plans make WFH way better than the average office
I always wonder this as well… I will use tools to help me write some repetitive stuff periodically. Most often I’ll use a regex replace but occasionally I’ll write a little perl or sed or awk. I suspect the boilerplate these people talk about are either this it setting up projects, which I think there are also better tools for
Rules can be more specific than just “allowed to access any address”
Tells you and prompts you to make a rule when an application makes an outbound connection
For the future, it’s a pain in the ass but I think opensnitch is well worth the peace of mind
Then you’re just wrong. Clean Code directly tells you to make the mistakes the author of the article points out. The absurdity of the examples in the book should be evident enough.
The problem is that people recommend clean code to junior developers all the time. Clean Code is full of terrible advice and heuristics over critical thinking throughout, and is usually foisted on burgeoning juniors when they don’t know any better.
In other words, you’re correct that adherents of clean code are thinking like junior developers, because that’s what clean code tells you to do.
It seems that way, but they smell awful to me and at best taste neutral
Sir this is a Wendy’s/it is a screensaver from 1995
It definitely seems different than the rest of their “unappealing” list.
LLMs don’t add an abstraction layer. You can’t competently produce software without understanding what they’re outputting.