As someone on the intersection of both (I've built a lot of vibe coded toy projects and lead a vibe coding initiative at work), they're both right and both wrong.
For a single dev team, vibe coding is great. Write specs, write plans, write code. I know what the project wants and needs because I'm the target market.
At work, I haven't written more than a few lines of code since December. But I work with other people vibe coding this same project. Lots of changing requirements and rapid iteration. Lots of mistakes were made by everyone involved. Lots of tech debt. Sure, we built something in 2 mos that would have otherwise taken us 6 mos, but now I'm fixing the mess that we caused.
I think the critical difference is the attitude towards our situation. My boss said to fix the AI harness so we can vibe code more confidently and freely. But other bosses might cut their losses and ban vibe coding. Who's right? I dunno. In both cases I'd just do what my boss wants me to do. But it's not that I don't want to be left behind. I don't want to lose my job. There's a difference.
Broadly speaking I agree. But the reality for many SWEs is that if they don't learn new AI tools they'll get let go. It's use AI or be replaced by AI (or, more accurately, be replaced by someone using Ai) for many folks.
I think it's a luxury to be able to ignore a trend like AI. crypto was fine to ignore because it didn't really replace anyone, but Ai is a different beast
I think they want to sell that perception, but the biggest thing the tech execs want in their SWEs is fear.
Fear that makes us stay in our jobs, even when raises and bonuses stagnate, because the market is scary with all the "AI layoffs" (which have largely been regular downsizing with the AI label slapped on).
Fear that makes us use the LLMs and then put in extra hours when we don't see the 10x productivity gains that they expect.
Fear that makes us erode our own skills and become dependent on these gatekeepers to maintain even a base level of productivity.
So much of the advertising and discussion around AI is based around fear. It's inevitable. It will take your job. Render you useless. It will render humanity useless. You better get in now, or you'll both lose your job and could end up in a virtual hell (https://en.wikipedia.org/wiki/Roko%27s_basilisk).
I think you're right that it is fear. But it's kind of a self fulfilling fear. Teams are requiring employees to use AI, probably because of this fear. Maybe it isn't directly taking my job, but it is necessary for me to use Ai to keep my job.
> I think I’ve reported this as a bug to Google a couple times, in a couple different apps… as they do it in their other apps too.
Alas, I don't think it's a bug. A PM or VP probably got a bonus for this.
> How about just giving the option to login with Google if so choose to login, and not spam it on every website just for visiting?
Yeah this is kinda weird. I don't know if it's browser specific though. I use Firefox on my main computer and I think I still see it. Which means that the website owner opted into this weird pattern. No other auth providers do this. Just Google.
I opt into it on my site it's just a login option you can ignore if you want to log in another way, but for those who use it it removes the friction of writing out a password and verifying the email
It can’t just be ignored, it covers content, and if someone accidentally clicks the wrong thing… poof, they now have that site linked to their Google account.
Thanks for sharing! It's not really easily ignored for some people (I ignore it the same way I ignored banner ads in the 00s). I'm curious if you have any metrics on bounce ratios with/without the option. The sentiment here on HN appears to be largely negative but HN does not represent the population at large. I find that many people don't mind or even like a lot of stuff that HN tends to hate.
I find myself babysitting agent-derived tests unless I specifically say what the in variants and edge cases are. Sometimes I'll ask it if I missed anything and it'll be helpful. But I have to be proactive.
I don't have data but I was always under the impression that consumer use of fossil fuels (ie gas) was a drop in the bucket compared to enterprise use of fossil fuels (shipping trucks/boats/planes, private jets, etc).
The whole "reduce your carbon footprint PSA" was just a ruse.
Ugh don't get me started on paper straws! At least EVs are a cool way to reduce reliance on fossil fuels, however ineffective it may be at scale. But nobody likes paper straws.
> But the companies have a large carbon foodprint to deliver a product or service for the consumer.
I agree that that's _why_ they have a large carbon footprint, no company is just burning fossil fuels for fun. But it doesn't change a) the fact that they do have a large carbon footprint, and b) entire cities could ban gas cars and everyone could take public transit and it still wouldn't make a dent in the global carbon footprint.
As I think you're alluding to over-consumerism as a cause of companies having a large carbon footprint, that's part of it. But unless everyone just stops consuming, it's not gonna change anything. If it were legislated that big companies needed to reduce their carbon footprint by X% by Y date I think that would be the most effective, short term at least.
> When I buy a large SUV / Truck, and never drive it, is that not counted negative towards my carbon foodprint?
I don't know why it'd be negative. Zero or neutral, at best, but not negative. Negative would entail you're somehow removing CO2 from the environment.
The article only talks about rent, not price of housing, which I think is an important data point.
Homeowners don't want housing prices to fall. Ever. They don't care about rent prices (at least, not directly). But renters care about both — obviously lower rent prices are good, but many want to be able to enter the housing market but it's prohibitively expensive.
Perhaps falling rent prices has a similar effect on home prices — the value of buying a home for the purposes of renting becomes less desirable due to lower rental revenue, so prices fall. Not sure, the macroeconomics of housing never made sense to me because it's never as simple as pure supply and demand.
As an example, my wife and I finally decided to buy a house in a fast-growing CA suburb (not in Bay Area). The house was constructed in 2021 and sold for $611k. Plenty of renovations have been done on the house, we'd estimate around $20k+ worth of renovations, and the neighborhood and surrounding area has only grown since then (more parks, housing, great schools, stores etc).
The house was listed for sale at $600k; even then we were able to underbid and get our offer accepted. Inspections turned out clean, just minor cosmetic issues.
I don't keep an eye on the rental market but we've lived at two different rental properties and both of those places went up in rent once each, so I can only assume that rent is going up everywhere in this area.
Point is, rent and real estate don't always go in lock step.
My sister is non-technical but loves Karaoke. I'd love to use this or similar software to build a small box attached to her TV where she can look up any song on YouTube and generate a karaoke version.
I don't expect this feature to be magically built though, so I'll have to research how everything works, and maybe I'll contribue :)
I've built so many fun projects that I've been meaning to build using AI, and my boss has as well.
I do agree that AI does make a whole category of projects feasible, but I disagree that AI does not also replace developers.
Should AI replace developers? I'd argue no, and the recent Amazon outage proves that.
But is AI replacing developers? Many companies seem to be doing so, whether or not it's a good idea.
I've also subscribed to the idea that even if AI doesn't replace me, I could be replaced by a developer using AI, so it's in my best interest to understand how to use it effectively (hence the projects!)
For a single dev team, vibe coding is great. Write specs, write plans, write code. I know what the project wants and needs because I'm the target market.
At work, I haven't written more than a few lines of code since December. But I work with other people vibe coding this same project. Lots of changing requirements and rapid iteration. Lots of mistakes were made by everyone involved. Lots of tech debt. Sure, we built something in 2 mos that would have otherwise taken us 6 mos, but now I'm fixing the mess that we caused.
I think the critical difference is the attitude towards our situation. My boss said to fix the AI harness so we can vibe code more confidently and freely. But other bosses might cut their losses and ban vibe coding. Who's right? I dunno. In both cases I'd just do what my boss wants me to do. But it's not that I don't want to be left behind. I don't want to lose my job. There's a difference.
reply