Tuesday, March 19, 2019
As engineers, there are several ways to grow our skills. The most common ones are on-the-job experience and training, meaning learning by doing and executing on new tasks, learning from interactions with others, and formal education such as courses and training.
In our experience, job experience and training have the most impact on developing your people. In this post, I would like to share with you three methodologies I have used to maximize and deepen the learning achieved from day-to-day tasks.
Thursday, April 18, 2019
Technical debt is a term that reflects the:
"implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer" [Definition of the term "technical debt" (plus, some background information and an "explanation"). Techopedia. Retrieved August 11, 2016.]
I would like to present a different approach or point of view on "technical debt":
There is no such thing as "technical debt".
At every stage, we (development managers, leads and developers) decide (or should decide!) what and how to develop based on return-on-investment (ROI) considerations. I would even go further and say it is reckless and not professional if we decide to "overdevelop" when not needed.
Following that, I would change the question:
"How do we deal with technical debt?"
"How do we make the right decision on what to develop?"