Using Technical Debt in Your Favor

Re:Using Technical Debt in Your Favor by cryptonector on Thursday March 22, 2018 @12:26PM (#16650099)

Some changes can be extraordinarily difficult, so if you can foresee that you'll need, say, to make some code into a library, or thread-safe, or async, then it's best to make it that way from the get-go.

Obviously there's a bit of YAGNI in tension here.

But if you have the experience to write it correctly from the get-go at low additional cost, then it's worth doing that instead of risking a massive rewrite later.

[ Parent | on HN ]

Re:Using Technical Debt in Your Favor by marcosdumay on Thursday March 22, 2018 @02:16PM (#16651124)

> to make some code into a library

I have never had any problem with putting some code into a library after the software is done. It is almost always a 1-4 hours exercise, and when it's not, it's a 2 days task at most.

Async code is also something that I have never seen it being a huge problem. Mostly because only a small part of your code needs to be async, most of it can stay synchronous, scheduled by the small async part.

Thread safety is a real problem. One can indeed trade some of it for some development speed, and this can become a huge bottleneck later/soon.

[ Parent | on HN ]