News for hackers. Stuff that matters.
Re:On over-engineering; finding the right balance by mgaunard on Wednesday September 11, 2024 @04:08AM (#41509167)
It's simple: understand what the goals of your team are for the current year. Write the code with supporting those goals in mind.
Re:On over-engineering; finding the right balance by cbanek on Wednesday September 11, 2024 @04:17AM (#41509235)
It's interesting you call out a year as a time span. I have no idea what the goals will be in a year, let alone how I'll code it. A year seems like a really long time, but also just short enough to justify adding extra work in early. My timeframe is more like a week to a month. Obviously different orgs will have different time windows for real reasons.
Re:On over-engineering; finding the right balance by mgaunard on Wednesday September 11, 2024 @04:39AM (#41509363)
Most companies have a revenue goal for the current year. From that revenue goal you can infer what software capabilities need to be obtained.