Doing a (brief) presentation Monday on long term software development (>10 years). Things you regret in year 8. I'd love to hear things you found out and wished you'd done differently. Or conversely, what worked out really well. Will turn this into a public presentation & blog post. To kick it off: PLEASE KEEP YOUR CODE AS SIMPLE AS POSSIBLE.

@bert_hubert

So far, it looks like the top three tips are:

Simplicity
- minimize dependencies
- appropriate frameworks
for scale, etc. (?)
- ?

Continuity
- keep the team together
- train new members before
oldsters retire

Transparency
- Document, document, document
- instrumentation?

@lolcat plus a strong vote for doing cleanups because the cognitive load of dealing with bad APIs or unfortunate semantics adds up over time. I wonder if @arclight will weigh in btw!

@lolcat @arclight so the other thing we haven’t even mentioned is that modern system development is now more and more “cloud native”. Which means you now have runtime service dependencies. Try doing that for 10 years.

Follow

@bert_hubert
There's going to be a €€€ to something conversion scheme that's going to "solve" this ... as a service. 😅 Great money for the provider.
@lolcat @arclight

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.