search

js-jslog / harpguru

A monorepo containing the component packages to run and build the harpguru application
0 stars 0 forks source link

Lessons learnt #4

Open js-jslog opened 4 years ago

js-jslog commented 4 years ago

A log of the lessons which I've learned having seen and invested thought in so many aspects of application development in one place.

js-jslog commented 4 years ago

Use techdebt. My experience of techdebt in industry has always been that it's incurred, then paid off in bugs later and never satisfactorily addressed.

This experience led me during a lot of early development to insist on resolutions to problems found in code review to be implemented within that pull request.

In retrospect a great deal of that effort was wasted since the project changed shape and rendered all finessing in a given area to have been a waste of time.

A strategy I've employed more recently is to identify certain issues in code review as being candidates for future enhancement. These are recorded as issues along with all the fresh thoughts which relate to them at the time. These issues and the record keeping within them may become useful later when those issues are felt to be starting to cause real tension, or they may become moot, in which case no effort was wasted fixing them.