Technical Debt on Companies

Technical DebtDebt in any form is a redflag. A lot of startups start with a vision but no clear direction. We code as per the final requirements to make sure it works once we reach the million userbase. There is nothing wrong however changes happen all the times and it’s hard to predict the final product resulting in discarding lot of code. Even worse, if the code stays, it affects the entire infrastructure badly. It’s like carrying diesel in your car trunk while you are running on petrol. You have a useful fuel but it’s not just right to drive your company.

Best practices include the following

– Build a modular software by dividing project into as small parts as possible

– Every part ( module ) is independent

– Ship the software as soon as possible

– Try to clean up code periodically. Ideally once a month for a day or every quarter. If you are not doing it at least twice a year, you will have to pay high interest on it

– If you can afford, hire a hacker whose job is to cut the code into 50% to perform the same amount of work.

In terms of code, lesser the better.

2016-03-06T15:49:28+00:00February 11th, 2015|Categories: Startups|10 Comments

10 Comments

  1. Grantt May 23, 2015 at 5:23 am

    Woah! I’m really digging the template/theme of this blog.
    It’s simple, yet effective. A lot of times it’s challenging to get that “perfect balance” between user friendliness
    and visual appearance. I must say that you’ve done a superb job with this.
    Also, the blog loads super fast for me on Safari. Superb Blog!

  2. Jordan Kahn September 28, 2015 at 8:18 am

    Im grateful for the article post.Really thank you! Great. However whose responsibility is it ? Is it the Product guy , CTO or the coder it self ?

  3. Soby September 28, 2015 at 9:27 pm

    I just want to mention I am just new to blogging and actually liked your web-site. Very likely I’m likely to bookmark your blog post . You amazingly come with awesome stories. With thanks for sharing with us your website page. Never thought that technical debt would even be a concern for startups.

  4. Bryan October 6, 2015 at 11:26 am

    This web site is really a walk-through for all of the info you wanted about this and didn’t know who to ask. Glimpse here, and you’ll definitely discover it.

  5. Frances October 30, 2015 at 1:16 pm

    I think technical debt is over-rated at times. There is also effort required to remove technical debt. If that effort surpasses the development effort, then there is no point. As you mentioned no one can predict future product, there is a chance that even the debt-free code would be used in future. Only fix things if they break or have potential to break.

  6. Jeffrey Tom November 4, 2015 at 8:01 pm

    Hi, I think your site might be having browser compatibility issues. When I look at your website in Chrome, it looks fine but when opening in Internet Explorer, it has some overlapping. I just wanted to give you a quick heads up! Other then that, wonderful blog!

  7. Douglas W. Arner November 12, 2015 at 4:48 am

    I couldn’t refrain from commenting. Exceptionally well written!

  8. Kami November 21, 2015 at 6:11 pm

    As a developer, I can totally relate to it.

  9. James Lindsay November 30, 2015 at 2:44 pm

    I simply wished to appreciate you once again. I do not know what I might have undertaken in the absence of the actual hints documented by you on such a problem. Completely was a very frustrating case for me personally, but noticing the very professional strategy you managed the issue made me to leap over gladness. I will be grateful for this work and then expect you are aware of a powerful job you have been undertaking instructing the rest via your websites. Most probably you have never got to know all of us.

  10. Trinidad December 4, 2015 at 6:50 pm

    This really answered my drawback, thank you!

Comments are closed.