I’m not a professional programmer with formal education or anything like that, but for me writing software is sort of like painting a picture; First I think of what I want the program to do and imagine how it should look like, a basic structure. Then I start hacking towards this goal, just to get it working. At that point I usually have a basic skeleton of a program that can at least do a bare minimum. After that I usually start doing things like thinking of adding more features. One feature at a time, step by step, keep things simple. I always found this to be the best way for me personally.
I’ve been working professionally for several years now and this is also my workflow. I sit down and think of what the requirements are, which tools I need to use, and sketch out a basic structure of what components I need and how they work together. Then I make a prototype where I just focus on building something that works and fulfills the requirements. Once I have a functional product, I take notes of what can be improved/optimized and start iterating. It does imply spending some time going over, rewriting and refactoring code, but I find that with each design iteration I gain a much deeper understanding of the problems the code needs to solve by actively working on it, putting it together and seeing it run than I could achieve by trying to think of everything in a void before I even start working.
I’m not a professional programmer with formal education or anything like that, but for me writing software is sort of like painting a picture; First I think of what I want the program to do and imagine how it should look like, a basic structure. Then I start hacking towards this goal, just to get it working. At that point I usually have a basic skeleton of a program that can at least do a bare minimum. After that I usually start doing things like thinking of adding more features. One feature at a time, step by step, keep things simple. I always found this to be the best way for me personally.
I’ve been working professionally for several years now and this is also my workflow. I sit down and think of what the requirements are, which tools I need to use, and sketch out a basic structure of what components I need and how they work together. Then I make a prototype where I just focus on building something that works and fulfills the requirements. Once I have a functional product, I take notes of what can be improved/optimized and start iterating. It does imply spending some time going over, rewriting and refactoring code, but I find that with each design iteration I gain a much deeper understanding of the problems the code needs to solve by actively working on it, putting it together and seeing it run than I could achieve by trying to think of everything in a void before I even start working.
deleted by creator