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.
"I have a tendency to go down rabbit holes when faced with problems - give me a minor inconvenience and I’ll happily spend weeks building something far more elaborate than the situation warrants."
You don't know how happy I was to read this... I thought I had a serious problem with getting distracted with my "projects" but it seems this is much more normal than I thought ;-)
I find it absolutely mindblowing to witness the rate at which Anthropic can ship new features. Only a year ago I couldn't wait to see some sort of Github integration and then it appeared only a week later. Seriously impressive stuff.
I think to the extent they are making a speed v quality tradeoff, I think they are making the right call. 10x speed over quality any day for me. Reminds me of:
"If brute force doesn't work, you aren't using enough of it." - Isaac Arthur
Everyone is
making this tradeoff now. Surely nothing bad could come from it.
In the meantime I can’t even continue a Claude Code session I started on desktop on my phone. What’s the point of shipping a billion features of they are all half baked?
Everyone is NOT making that tradeoff. Maybe we will be forced into it someday, but my team is leveraging AI to increase the quality of code far beyond what we would have done without it. Some of us are using it to engineer better solutions.
Example: we are putting a lot of energy into removing technical debt, reorganizing the code to remove unneeded abstraction and complexity, and creating missing tests and automation. We're not just burping out new untested and poorly reviewed functionality.
It’s a phase, for sure things will turn around in the future once the hype of “oh we can now ship fast” is gone.
fwiw I’ve had this open source browser ui that sits on top of your claude code, gemini and codex and picks up/starts your sessions from any device https://github.com/siteboon/claudecodeui
The Claude Code TUI app is pretty solid. I use it heavily and I get great results from it. But with the mobile app, Claude Code remote is basically unusable (weird disconnect bugs) and Claude Code cloud has issues as well (UI hides approval confirmations; must reconnect to see them). So yeah, I imagine what you're saying is true. There are at least some major gaps in their QA process. It's ironically a pretty convincing case to keep humans in the loop. It's honestly shocking to me that those features were actually shipped in their current state. You run into the problems immediately.
I have a very different experience. Claude code tui is the worst tui I have ever used. How is it possible that an inactive tui regularly eats 8gb of ram, has freezing issues and rendering issues?
If I wasn’t forced to use it I wouldn’t as there are better options available.
I agree with you about the Claude Code TUI. I switched to it weeks after it was released. The browser interface is great for quick chats and talking through ideas/concepts, but not for coding. What I love about the TUI is that it can see all your repos as once so it has the full picture all the time. You can't get that with the web version.
I don't find criticism like this particularly compelling. Most products (written by humans) have the same failings. The few that aren't are exceptions to the rule or develop very very slowly and carefully.
They also pay... insane salaries, like double industry average. That coupled with an IPO on the horizon means they probably have their pick of engineers.
They clearly vibe code a lot (most? all?) of their stuff, and it shows. Elementary features are broken regularly and while I appreciate them trying new features, I'd appreciate it more if existing ones were reliable and promptly fixed if broken.
Trouble is, vibe coding refinements and bug fixes works well but probably isn't a good track to promotions at Anthropic (or virtually any other company.)
Meanwhile, you still can't Sign in with Apple on the website.
But you can Sign in with Google.
If you signed up with your Apple on the iOS Claude app, to access your account on the computer, you have to open the passwords app and copy your random email address and paste it into the Claude website login.
Also if you try to copy-paste a prompt from Notes etc into the Claude chat, it gets added as an attachment, so you can't edit the prompt. If you do the four-finger shortcut to paste it as text, it mangles newlines etc.
Why are they so dumb about such basic UX for so long?
> you still can't Sign in with Apple on the website.
Apple forces developers to offer Sign in with Apple on iOS devices if any other sign in service is used. Apple can't force them to do it on non-Apple platforms.
> If you signed up with your Apple on the iOS Claude app, to access your account on the computer, you have to open the passwords app and copy your random email address and paste it into the Claude website login.
Isn't this basically Apple's fault? When you signed up, Apple provided a fake email address in leu of your real one. This is great for privacy but means the service has the wrong email.
I'm sure they didn't want to provide an Apple sign in option at all, but it's required by App Store rules.
They could also just implement sign in with apple on their website, they have the ability to sign in with google so not supporting Apple is still a weird choice they are making.
Apple should not have had to require developers to have options other than Google for authentication, but clearly some companies have to be dragged kicking and screaming.
So clearly they support it, and there is no reason it should not work on the web also.
There are a lot of websites that only support third party login, so that is not always an option.
They don't have to bend for another, but they made a choice to put an app on iOS. They added support for apple signin, and then for some reason did not put it on their website.
You can criticize Apple for requiring that all you want, but they clearly have support for it and are choosing to not put it on their website which is causing a worse user experience.
IF apple did not support website loggin than sure, but they do. So the ability to fix this is on Anthropic (and many other websites).
If you are already going to support third party login you should not limit it to only Google accounts and there is no reason to support Apple on iOS and not the web.
Also for the record, Apple only requires sign in with apple if you already support third party authentication. So if you are already going to support that, giving the user more choice (and making it so we are all a bit less dependent on google) is a good thing.
No criticism from me towards apple or Anthropic. Both parties made their choice. Apple was late to the identity business and the other ships had already sailed.
Third party logins are an extension and a massive risk to any website that doesn't include email hosting.
We have see identity providers dissapear, and people may change their mind.
Easiest way is to register you rown domain and use it with an identity provider of your choice and be able to move it anywhere.
Otherwise we are a faceless citizen of a corporation that can handle access to our identity and everything attached to it without recourse or access to anyone.
Are you seriously trying to justify offering Sign in with Google but not ALSO offer Sign in with Apple because of some contorted principle, the method which HELPS users maintain their privacy? What the actual f.
Antrhopic's UX is just trash, the worst of all the major AI products.
They have this "I'm special" syndrome where they think they can get away with doing shit weirdly and not offer basic features that everyone else does, and the reason why I never purchased any of their services again after the first month, and had to replace my payment info with a throwaway card because they wouldn't let me remove it, again unlike everyone else.
I don't think it's hard to understand why a service would want to support Google as an identity provider but not Apple. Google is probably the most commonly used provider out there, at least outside of the enterprise space.
Apple's identity service is not as common, and newer than the ones that were established before.
It's ok that Anthropic wasn't a fit for your prompting preference, it doesn't have to work for everyone, and it doesn't mean it wont' work for others. LLMs in general have proven that trying it once a few months ago can be a great way to miss changes. There's something out there for everyone.
Not really. It's the user's fault. Apple provides an option to hide your email, it's not required. It's an option that shows up when you're prompted to create an account.
My original thinking was that Apple makes it too easy for a general audience to hide their email without considering the implications (the service won't know your email). But of course there's a tension here, since you also want the option to be easy and accessible.
The party I do not consider at fault in this case is Anthropic.
> I'm sure they didn't want to provide an Apple sign in option at all
But they wanted to provide a Google Sign In? wth?
> This is great for privacy but means the service has the wrong email.
So harm the users to benefit the service? wtf?
I don't want to give my real email or anything to random services, specially not one like Claude where they don't even let you remove your payment info.
> I don't want to give my real email or anything to random services, specially not one like Claude where they don't even let you remove your payment info.
The original complaint was:
>> If you signed up with your Apple on the iOS Claude app, to access your account on the computer, you have to open the passwords app and copy your random email address and paste it into the Claude website login.
Either you use your original email or you use a per-service email. Apple helps you do the latter, but this does come with UX tradeoffs.
Using a per-service email, then complaining that the service does not have your real email, strikes me as misguided.
Add to the list backtick handling. If you start a backtick block on the claude web chat, you cannot leave it with the keyboard. You are now stuck between the backticks. It is as if they wanted to reproduce Slack misery.
reply