Yeah, my current software project at work was basically half a year of feature development and since then, we’ve purely tried to get it into the real world, which meant evaluating use-cases to see where it falls flat and what needs stabilizing, as well as figuring out people’s needs and how our software can assist with that, then setting up a demo and hoping they find money somewhere…
I always get upset when people write unclear lines.
I do a lot of code reviews, and it’s taking years to explain how to write code that makes sense. Some are better, some just write, or worse - copy, things that are ambiguous, or are made such by copying them with small changes.
It’s very difficult to specify bullet-proof rules for good code. And after every step devs find more ways to fuck it up.
It’s easy to overestimate how much of software engineering is about coding, when in truth it’s mostly about the code you don’t write.
Yeah, my current software project at work was basically half a year of feature development and since then, we’ve purely tried to get it into the real world, which meant evaluating use-cases to see where it falls flat and what needs stabilizing, as well as figuring out people’s needs and how our software can assist with that, then setting up a demo and hoping they find money somewhere…
I always get upset when people write unclear lines.
I do a lot of code reviews, and it’s taking years to explain how to write code that makes sense. Some are better, some just write, or worse - copy, things that are ambiguous, or are made such by copying them with small changes.
It’s very difficult to specify bullet-proof rules for good code. And after every step devs find more ways to fuck it up.