431–440 of 752 posts
Earlier quoted context omitted.
Yes, I didn't really doubt the developer could do it, the problems are: 1. That's not a great use of the developer's time, and 2. anything in-house increases our training and support costs
And both are completely different arguments then your original post.
Earlier quoted context omitted.
OTOH, I was hired by an enterprise that was many months into a giant backend rewrite. After wrapping my head around the many plans, I realized they were rewriting Django, badly. One weekend I prototyped the whole thing… in Django. It worked. It met the specs. It was a CRUD app with a REST API. I came in to work Monday morning, showed it off, and inadvertently triggered a firestorm. Later my boss told me not to do tha…
> Later my boss told me not to do that again because it caused havoc with schedules and such. Did you talk to anyone about your plans before you brought in the demo or let them know they were solved problems? Often these sorts of reactions come down to your boss not wanting their team to lose their jobs because of the perception that it can all be handled by one person who's happy to work weekends.
Again, and I can’t emphasize this enough, for a Django CRUD app. It was a 4 person-week project turned into a major ordeal. No one should have lost their job; they should have been put to work doing the thousand other more productive things they could’ve been doing instead.
Earlier quoted context omitted.
> Lots of people have really great ideas but very few actually commit to execution. This is true when you had to work hard for those ideas. Now you have LLMs. It means more people can sling a lot more crap at walls with fewer barriers to entry.
Good execution doesn't get easier with an LLM.
Earlier quoted context omitted.
If software already exists that does X, X is a solved problem. You didn't hire a developer to solve already-solved problems.
ya, i agree. but in your world, this company will fail https://glue.ai/ ?
The real story isn't that some enterprise mega corp is going to vibe-code their own Workday. The real story is that SOME startups made up of one person (or small number of engineers) will do it, and create pricing pressures against Workday, or DocuSign, or other B2B SaaS.
It's a tale as old as time that developers, particularly junior developers, are convinced they could "slap together something in one weekend" that would replace expensive SAAS software and "just do the parts of it we actually use". Unfortunately, the same arguments against those devs regular-coding a bespoke replacement apply to them vibe-coding a bespoke replacement: management simply doesn't want to be responsible…
It's a tale as old as time that developers, particularly junior developers, are convinced they could "slap together something in one weekend" that would replace expensive SAAS software and "just do the parts of it we actually use". Unfortunately, the same arguments against those devs regular-coding a bespoke replacement apply to them vibe-coding a bespoke replacement: management simply doesn't want to be responsible…