I remember when I was naive, young programmer, a side project would go something like this – I would set myself a goal to get a login and register screen that, as you guess, allowed a user to log in and register. This would take me about a day to do, maybe less. These were the days when the goal wasn’t for later use, because more likely than not, I won’t have to keep maintaining the code that I’ve written for longer than a few weeks at most, if at all.
Tag: General Programming
This year, I’ve decided to keep track of my thoughts, learnings and progress a bit more – I’ve decided to take note taking a bit more seriously. I feel that we lose a lot of knowledge over time, maybe not the big picture, but we definitely forget the important finer details.
Quite some time ago, I’ve come across a question in stackoverflow by Jon Skeet.
What’s your most controversial programming opinion?
As Developer’s, there comes a point in our life where we start questioning a bit more, and you realise – these things that these guides and principles that we’ve been taught doesn’t quite work for our problems – this is an awesome moment, this is the moment that you have become more pragmatic with your approach, you’ve formed your own opinions based on your experience, and you know that it works.
Everyone eventually rewrites either a small piece of code, an entire application or framework or refactor their work, and this process is in a constant cycle. You notice this everywhere, from small applications, libraries, frameworks and even Enterprise Software. Should we be concerned? Why is this such a common theme?
For Applications, one of the primary reasons for refactoring or rewriting is technical debt, so let’s have a look at some common reasons for technical debt, and I attempt to propose some solutions to each point.