|
|
|
|
|
|
by lostdog
1884 days ago
|
|
|
Nobody cares about what materials you used in your bridge! https://www.courthousenews.com/34m-settlement-reached-for-de... But seriously, they call it "tech debt" for a reason. It's not a problem until suddenly you're no longer able to add needed features to your project, because every little bit of development takes hours and weeks and months. There are so many posts about how "Engineers Need To Learn About The Business," and yeah, it's helpful sometimes, but really there are different types of jobs. Some jobs require the engineers to understand the product and business rules, and other jobs need engineers with deep technical engineering abilities. There's nothing inherently better or worse about either! What's bad is if the job is one type and you are the other type. (Similarly, you think you want to be one type, but really you want to be the other type). So go ahead! Fiddle with an esoteric language or framework, because there are plenty of open positions that need you. |
|
|
"The metaphor of debt is sometimes used to justify neglecting internal quality... Teams who do this end up maxing out all their credit cards, but still delivering later than they would have done had they put the effort into higher internal quality."[1]
"the whole debt metaphor, let's say, the ability to pay back debt, and make the debt metaphor work for your advantage depends upon your writing code that is clean enough to be able to refactor as you come to understand your problem"[2]
"write the best code possible given a partial understanding of the problem so later when you do understand it better you improve the solution"[3]
1. https://martinfowler.com/bliki/TechnicalDebt.html
2. http://wiki.c2.com/?WardExplainsDebtMetaphor
3. https://www.youtube.com/watch?v=pqeJFYwnkjE