
It's recently been a year since I started working on
my pet OS project, and I often end up looking backwards at what I have done, wondering what made things difficult in the beginning. One of my conclusions is that while there's a lot of documentation on OS development from a technical point of view, more should be written about the project management aspect of it. Namely, how to go from a blurry "I want to code an OS" vision to either a precise vision of what you want to achieve, or the decision to stop following this path before you hit a wall. This article series aims at putting those interested in hobby OS development on the right track, while keeping this aspect of things in mind.
Member since:
2011-01-28
"The first time code is written, the primary priority of a developer should not be speed, but cleanness, maintainability, and getting it to work."
I don't disagree with the order of priorities here. But I do believe efficiency should have a larger role up front than your suggesting.
Once the whole thing works, the "cement" has already begun to dry, so to speak.