2 ms·
Ironically to me, the most apt application of "debt" to any source you do is not the hack or shortcut code, but the libraries you bring in. You are literally b
by taeric 8y ago
Ironically to me, the most apt application of "debt" to any source you do is not the hack or shortcut code, but the libraries you bring in. You are literally borrowing against the knowledge and expertise of someone else.
The vast majority of the time, this is the correct thing to do. But if you find yourself scaling to absurd levels, this is the code you will have to worry about. You will find that you almost certainly will start to care about all of the details of the network that you were able to ignore in the past. Connection and thread pools you were able to ignore, now need you to invest directly in.
The hacks? Just make sure you aren't worried about aesthetic changes. Keep people on point solving problems, but don't berate them for wanting things to look at certain way. Developer happiness is important. Often that rewrite of a module that you thought would take too long, can help morale so that folks are moving faster by the end of it. Just make sure to keep it goal oriented and for the love of all things good, don't let them get away without keeping feature parity for your customers.