I have to agree here. The amount of cyclists I see with full over the ear headphones on-- if these guys are blarning tunes, there is no way they'll every hear the traffic around them. Extremely dangerous.
What I really want to know is... as a software developer for 25+ years, when using these AI tools- it is still called "vibecoding"? Or is "vibecoding" reserved for people with no/little software development background that are building apps. Genuine question.
"Vibecoding" is about how you use AI tools, rather than who you are.
If you're asking the AI to generate large amounts of code that you don't really look at, you're definitely vibecoding. If you are mainly writing the code yourself with some assistance from AI tools, you are not vibecoding.
Naturally it's fuzzy in the middle. And for people without software development skills, vibecoding is the only option they have.
Steve Yegge has been a dev for several decades with lead spots at Amazon and Google, has completely converted to using AI, wrote a book about it using it effectively for large production-ready projects, and still calls it vibe coding.
I don't think I'll ever adopt this term, I'm not a fan of it at all. I find myself saying "I was working with AI" and just leave it at that. It is a collaboration afterall.
It can't do things with me like a human, it's not human, it's not intelligent, it's not thinking, it's not aware. It's an aide I use, not a tool I rely on.
I've got about ~15 repos for a project and I just start Claude Code in the parent directory of all of them, so it has clear visibility everything and cross-reference whatever it needs.... super handy.
This is the big one for me, I hate all that lag with bluetooth, signal interference, and constantly wondering which device my headphones have connected to. So much easier for so many reasons, with a wire!
100% agree with this, as much as I hate the term "game-changer"... it truly is, I'm working on projects that I've always wanted to do but never had the capacity (or money to pay a small team of devs to build something)-- all these things that you thought you'd never have a chance to do, are suddenly now real and completely possible. I know there's a lot of AI haters out there but I'm pretty sure in time, all devs will embrance it and truly enjoy working with it
"Can you believe that Dad actually used to have to go into an office and type code all day long, MAUALLY??! Line by line, with no advice from AI, he had to think all by himself!"
This was literally part of the premise of The Jetsons. George's job was to press a single button while the computer RUDI did all the work.
The difference is, Jetsons wasn't a dystopia (unlike the current timeline), so when Mr. Spacely fired George, RUDI would take his side and refuse to work until George was re-hired.
> "Can you believe that Dad actually used to have to go into an office and type code all day long, MAUALLY??! Line by line, with no advice from AI, he had to think all by himself!"
Grumpy old man: "That's exactly why our generation was so much smarter than today's whippersnappers: we were thinking from morning to night the whole long day."
I was thinking about that recently. Maybe decades from now people will look at things like the Linux kernel or Doom and be shocked that mere humans were able to program large codebases by hand.
I was being a little facetious, but there are things that most people would find tedious today that we would put up with in the past. Writing anything long by hand (letters, essays), doing accounting without a spreadsheet, writing a game in only assembly language, using punch cards, typesetting newspapers and books manually...
Why not just get a Linux phone running Ubuntu Touch or postmarketOS. You'd have full root access, sideloading etc and none of that corporate control, likely for half the price of an iPHone. Sure you'd lose all the Apple look/feel but at least you can do what you want with the phone.
reply