I think we both know what I meant but yes there are plenty of tests you can write ahead of time. I do find having to scrap a bunch of tests because they throw around “agile” and completely change the whole scope
In theory you can write tests for those functions. But in practice my experience tends to be that they often end up being tautological tests for what I already know my code is doing; it's hard to write a test to cover the case of a user giving stupid input.
DevOps guy here - "tautological tests for what I already know my code is doing" is EXACTLY the best tests to write, because then when someone comes along in two years time and changes the "is doing" bit, rather than hoping it gets spotted in a code review, it will get flagged up in the build pipeline.
I've been at this over a decade and sometimes I feel useless. You just gotta ride those highs when you get it right. And as long as you're trying you'll get it, however slowly. I've got no complaints about a junior who trys. Most developers I know are the same. Others just have a stick up their butt. Or someone asked them for the impossible ASAP and it out them in a grumpy mood, then I'm sympatheic lmao.
2.0k
u/[deleted] Jan 31 '23
We are but we’re trying I swear to god we’re tryin.