81–89 of 89 posts
Next is such a dumpster fire. So much wasted effort due to the Node ecosystem never developing a universal batteries included framework like Rails or Django.
Maybe they will rewrite everything with AI by then. /s
Earlier quoted context omitted.
I think the more specific description would be that "not writing tests allows shipping fast today, writing tests allows shipping fast tomorrow and afterwards". It wasn't too long ago that I wrote tests for something that was shipped years ago without any automated tests. Figured it was easier doing that than hoping we won't break it.
Yeah, but in my experience it really is a literal today vs tomorrow thing. Your tests pay for themselves the moment you want to ship a second feature without fear of breaking the first.
And that is the minimum level to aim at. If you can automate anything you do to test it right now you should.
Pearls. > I would NOT allow people to write tests > now [...] we started with tests from the ground up
Two different stages of the project, not necessarily contradictory. I'm not saying this is great, but tests make a whole lot more sense when you know what you're building.
It should be common sense to add common sense tests to critical components. Now they are doing TDD THEY STILL DON'T KNOW THE CRITICAL COMPONENTS. Nothing changed. They lack systems thinking.
My guess is that both are just vibecoded slop.
It's a big move. But I understand it. Sometimes your code is "just" a proof of concept, a way to test the idea. Very far from a decent product. That is the time you ditch the code, keep the ideas (both good and bad) and start over.
This. Depending on the project, especially if you're doing something really novel, you can end up going down dozens of dead-ends which, when removed, leave little scars all over the code base. It can be so refreshing making that decision to open the old code on one screen and a fresh project on the other and do it right from the start.
Who are you people? 4 pivots and still going with "no tests" -> "tests first" rewrites. I mean, people say tech jobs are on down trend, projects are drying. And then there is this. I just can't make sense.
I wouldn’t admit to this level of frankly incompetence. Wildly swinging dogmatism on how to do software development that’s so wrong you have to throw it all away - then repeating this failure loop multiple times. Doesn’t inspire any confidence in the person I wouldn’t get them to lead a project. Why would you be so loud and proud about all this.
"bugs were appearing everywhere out of the blue. The codebase was a huge mess of nulls, undefined behaviour, bad error handling. It was so bad that we actually lost a client over this." Especially wild considering their product is literally an automated bug finder lol.