Do you face the same problem? How can you solve it? Please share.
Nice ... this is what we lack most ...The hardest part for me is to think as a user
That's one of the most difficult part. Different users don't mostly not expect the same.The hardest part for me is to think as a user.
Klaus you are not old fashioned. What you have done is a fantastic summary of the golden rules of every good programmer.Sorry, I am old fashioned !
People are followersWe are human
1000 hundred mens stare on shit on the midle ....
One comes around and decide to take a look
Then he becomes even courios and ask ...Why do you staring at this shit ?
It fun and every body does it can't you see that ?
Why not ..let's "subscribe"
No need to build complicated designs ..make it pleasant ...if there is a shit make first 100 men like it !
Enjoy !
You've surmised exactly where I go wrong in the first nine steps. I often start programming and then need to modify what I've already done because I didn't plan well enough from the start. I also find myself reiterating through my code because I hate writing repeated lines of code. If I write a few lines once and then a while later have to do it again I like to turn this into a function and reduce my code. But that means that I'm forever going back over my code thinking how can I reduce this more. I'm a little obsessive in this respectFor me, the most important things at the beginning, depending on the kind of program, are :
- Define as exactly as possible what the program is supposed to do.
- What data do I need for it.
- Where does the data come from and how.
- What is the user supposed to do, or better what is he allowed to do.
- Where and how to get the data.
- What data should be displayed and how.
- What can or is the user allowed to do with the results.
- Where and how to save them, if needed.
- Think about the user interfaces, make them as simple as possible with the minmum of operations. This is by far not simple.
- Only then begin with coding.
- Eventually write some small test programs.
- Begin with the skeleton and add the different functions.
- Then think about graphics, animation etc. for the user interface.
Sorry, I am old fashioned !
Error checking and fault finding is the part I enjoy the most, but then I'm not working to deadlines etc. I find its like pitting wits against the computer when something unexpected is happening or something doesn't work as you expected it too..... Once I can see results the boredom of programming goes away (until the tedium of error checking comes along later down the line).
I understand exactly where you're going from. For me too the challenge is to see if it can be done and how.I have so many ideas and I've started a lot of apps. Half way (when I got it to run) my motivation to finish decreases to zeroMostly I want to understand how this and that works and when I understand... well... that's it...
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?