1406
Tests are code too (lemmy.world)
submitted 10 months ago by jroid8@lemmy.world to c/programmerhumor@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] organicmolecules@lemmy.ml 4 points 10 months ago

Depends. If I'm working in an existing system and I know what the shape of the thing I'm writing is, then I might write the test first and tdd it out as that process is usually a bit faster for me.

If I'm developing a new feature I'd probably spike out a solution and write an acceptance test to match it, then if I'm feeling pedantic I might throw away the spike code and tdd it back up from scratch but I haven't done that in a while now.

This all depends on the language and the abstraction layer I'm at.

this post was submitted on 02 Nov 2023
1406 points (98.5% liked)

Programmer Humor

32067 readers
830 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS