- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or # to comment.
I’ve never actually tried or got the point of this test stuff tbh. It didn’t exist when I started so I never really got the point of it. I tried reading up on it a bunch of times and it seemed like extra work for nothing 🤷
It seems popular though so maybe one day I’ll get around to it…
Isn’t test driven development also error driven development though?
Trauma driven developer
I’m a github issue driven developer, if it doesn’t get reported, I’m not fixing it, jk jk I love my 10+ users
Bug report driven development
(And I use app reviews as my bug tracker)
Karen incident in the customer service call center driven development.
If someone hasn’t yelled at a minimum wage phone rep over it, it doesn’t need to be fixed.
B: “I test in production.”
A: bows downVibe coding is error driven development.
Vibe coding is driving error development
Joke’s on you, I vibe coded my tests too! Now my development is driven by errors in my tests!
Hey that’s no fair, it’s still test driven development but the test just runs in production!
What movie is that guy from? I know I’ve seen it but I forget
Kingdom of Heaven, I believe
Oh yeah I like that one
This was me today. Had to push a small fix to our API server, which serves 10 apps. It didn’t go quite as planned; boy was Slack and Zabbix not happy. My phone got a good workout though from all of the notifications – which didn’t stop until about 5 minutes after the fix was fixed.
I wrote tests today and found an error in my code. What is that? Development driven test driven development?
