meadsteve

Reflections on the best time to discover bugs in software.

The excitement comes when security issues are discovered in no longer maintained code

Php 5 would not be boring and safe. You'd have some interesting challenges writing in an unsupported language version

If I was to rewrite my blogpost to fit your second sentence I would title it: "Please consider onboarding new staff as a need for your software". This is just another consideration when architecting. I absolutely will use cutting edge tools if they are needed. But we just need to think about it a little.

Agreed. Though not strictly a counterpoint. I do enjoy novelty (and benefit from it). I just want the right amount of it

Yeah I think this is why I liked "novelty budget" as a term. To me it implies a limit, but it also implies something which you should spend. Doing something a little bit different can be immensely valuable as you've highlighted. Also everything was new at one time.

This is a very good point. There are definitely "risky novel" choices that could make your company a success. But I've also seen many teams drowning in a soup of random tech choices.

I'd love to be able to write some more specific advice on this topic but mostly I just want people to be mindful of the impacts of their choices and actively choose risk rather than having it sneak up on them.