Somehow I feel like this article was very unclear? The way it's written, the way it tells its story, I'm really not sure what happened. I wish there was just a link to the saas in question.
Like maybe it's that I just woke up, but all I really got out of this was that a vibe-coded app resulted in a company being downsized. But that's in the title. Any specifics beyond that? I really couldn't say despite having read the whole article.
They said that the team they work with is being replaced by a vibe coded SaaS product and that when they look at the product it only looks like it could replace the actual engineers from a very surface level.
> It's like someone took some screenshots of a competitor
This line stood out to me. I think it's something any of us who've tried to end to end vibe code something have experienced. The result is pretty (sometimes) but not functional.
> At the shallowest depth, I can see how a CEO got bamboozled. The happiest path is implemented. The second happiest path is rough. The third happiest path is unhinged.
If I'm understanding them, they're saying on the surface (the "happiest path") is correct, but everything underneath isn't. That the stuff underneath is harder. So only the easiest part was shown and the leadership was happy to move forward because they wanted to believe. It promised they could reduce costs by laying of expensive developers but the decision was unjustified considering the product didn't work as advertised.
not sure, but i'm getting the sense that they're annoyed that someone is expressing themself on their own personal blog and not being Professional enough
A part of me starts liking this kind of style because it feels more human... I'd rather wanna be bothered by some cringy writing than by those em dashes...
I had the same difficulty. i.e. what was the issue that caused a headcount reduction from a 1000 to 10 or less? It’s possible the organization had larger issues than generated code but again, difficult to draw conclusions without details.
It sounds like their employer is on the outs and in a bone-headed move to save on cost, is replacing the author's team and tech with some piece of crap vibe coded SaaS product.
They are expressing their (and their team's) bitterness over losing their jobs to something of such obvious poor quality.
I can empathize with this view. Seems like people's standards are a lot lower than they let on, and slop-ware is apparently A-OK at the right price point. Sad. But as the author points out, there will be legal consequences..
What is happening to this person sucks for sure. But one thing I have learned in this industry is the thing being replaced is always better than the thing replacing it when you talk to the team who built and run the thing being replaced.
There is enough to read between the lines. Dilbert manager has bought into a barely competent app (that they think replaces humans) in a panic because costs. They’ll learn more lessons over the next year, if they survive. The author might be a bit emotionally charged right now and is writing between some lines as they help migrate. Once they have some emotional distance they might write the fully clear article you’d like.
Like maybe it's that I just woke up, but all I really got out of this was that a vibe-coded app resulted in a company being downsized. But that's in the title. Any specifics beyond that? I really couldn't say despite having read the whole article.