this post was submitted on 20 Nov 2024
192 points (98.0% liked)

Programmer Humor

32532 readers
367 users here now

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

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 23 hours ago* (last edited 22 hours ago) (1 children)

If I actually did have that kind of job, the tests-first philosophy would sound very appealing. Actually, build the stack so you don't have a choice - the real code should just be an instantiation of plumbing on generic variables with certain expected statistical properties. You can do that when correctly processing unpredictable but repetitive stuff is the name of the game, and I expect someone does.

[–] [email protected] 2 points 19 hours ago (1 children)

Tests first is only good in theory.

Unit tests typically test rather fine grained, but coming up with the structure of the grain is 80% of the work. Often enough you end up with code that's structured differently than initially thought, because it turns out that this one class needs to be wrapped, and this annotation doesn't play nice with the other one when used on the same class, etc etc.

[–] [email protected] 1 points 17 hours ago* (last edited 17 hours ago) (1 children)

Can't you just add the wrapper to the test as well, if it's easy to do in the actual code?

[–] [email protected] 1 points 14 hours ago (1 children)

If you have to ask "can't you just" the answer is almost always no.

[–] [email protected] 1 points 12 hours ago (1 children)

Well, yeah, but I was kind of hoping you'd explain why.

[–] [email protected] 1 points 11 hours ago (1 children)

Because you don't know what you'll need that wrapper beforehand, that's my entire point.

Unless you're only doing trivial changes, the chances are very high that you won't be able to design the class structure. Or, you end up essentially writing the code to be able to write the tests, which kind of defeats the purpose.

[–] [email protected] 1 points 7 minutes ago

That's kind of the whole philosophy, though. The tests are the main way you understand what you're doing, the working code is just an addition on top of that. Presumably, there's a way to do that without repeating yourself - although I'm not turning up much on a quick look.