Is it irrational to wonder how large swathes of the population will earn a living if their employable skills vanish in a couple of years, with little prospect for retraining into something else that AI hasn't replaced? Is it irrational to wonder what effect an influx of the AI-replaced will have on remaining AI-free fields? Is it irrational to wonder about the psychological impact of work where one simply operates the AI instead of thinking, creating, growing? Is it irrational to wonder if wealth inequality will spiral when these essentially-unobtainable resources are used by a select few to enact the above scenarios?
I can only assume you have easy answers for all of these questions given your casual dismissal of such concerns, likening them to being scared of a light switch.
Skill issue. It's the most popular VCS in the world by a huge margin, millions of devs use it every day just fine, countless forges have been built around it, and there's only one semi-compelling alternative frontend (jj). If you honestly find Git challenging, how are you coping with software engineering? Git is the easy part.
Millions of dev use it in the most rudimentary way, occasionally lose their stash, rm their local repo and start over, ask the office expert for help every time they need to figure out where-the-foxtrot that commit came from, don't even attempt to use reflog or bisect or interactive staging, etc.
Wouldn't put too much weight on HN comments boosting AI. Lots of brand new accounts, obvious LLM drivel ("it's not X, it's Y"). I just tried to reply to one to call out how overt it was and the comment was already killed, so they're definitely here.
The entire industry is moving towards integrating these new platforms, because they obviously work.
It's perfectly reasonable to find problems with AI use, perfectly reasonable to 'not actually want' to use it, but it's basically irresponsible to reject the notion outright.
Read somewhere once that trading firms use satellite imagery of shipping to inform trading strategy. Don't know any more about it unfortunately but it sounds interesting.
Seems like "shooting down ideas" here is just "criticism of my idea whose framing hurts my feelings". If you want to light a fire with wet wood and cry because someone points that out, you probably lack the grit to execute anyway. Nobody owes you a sugarcoated explanation of the ways your idea is shit. Grow up.
Yeah it does. If you're happy routing your personal data through software that lacks an author who fully understands what the software does, good for you. Suggesting that this doesn't matter in general is.. not an opinion I'd share publicly.
Meh, 2026 edition of "developers vs coders vs engineers". It wasn't interesting before, it isn't now. People will do development at varying depths and breadths depending on their interest, role, project, and skill. For some reason, some people seem obsessed with this topic. "Coders don't care about CS fundamentals!", "engineers apply rigor"! Snore
I can only assume you have easy answers for all of these questions given your casual dismissal of such concerns, likening them to being scared of a light switch.
reply