Home/ Questions/Q 5954581
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T17:59:29+00:00

I’ve been working for years on my personal project, an operating system made from

  • 0

I’ve been working for years on my personal project, an operating system made from scratch. As you may imagine it’s quite complicated stuff. The problem is that I’ve been working this from scratch many times. Meaning that at some point (quite advanced too, I had hard disk read/write and some basic networking), things were too confused and I decided to throw it all by the window and try again.
In the years I’ve learnt how to make the code look nicer, I read “Clean Code – A Handbook of Agile Software Craftsmanship” by Robert Martin and it helped a lot. I learnt to make functions smaller, organize things in classes (I used C, now C++) and namespaces, appropriate error handling with exceptions and testing.
This new approach however got me stuck at the point that I spend most of the time to check that everything is going well, that the code reads well, that is easy, well commented and tested. Basically I’m not making any relevant step from months. When I see my well-written code, it’s difficult to add a new functionality and think “where should I put this? Have I already used this piece of code? What would be the best way to do this?” and too often I postpone the work.

So, here’s the problem. Do you know any code writing strategy that makes you write working, tested, nice code without spending 90% of time at thinking how to make it working, tested and nice?

Thanks in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Do you know any code writing strategy that makes you write working, tested, nice code without spending 90% of time at thinking how to make it working, tested and nice?

    Yes, here.

    Seriously, no. It is not possible to write good code without thinking.

    When I see my well-written code, it’s difficult to add a new functionality and think “where should I put this? Have I already used this piece of code? What would be the best way to do this?” and too often I postpone the work.

    This is called “analysis paralysis”. You might be interested in reading the “Good Enough Software” section of The Pragmatic Programmer. Your code doesn’t have to be perfect.

    • 0