Lack of imagination
Posted: Tue Jul 07, 2009 12:29 pm
Hello. Do you ever feel you want to code something but you just can't get any ideas or find that project that really motivates you?
The Place to Start for Operating System Developers
http://forum.osdev.org./
All. The. Time.Rui wrote:Hello. Do you ever feel you want to code something but you just can't get any ideas or find that project that really motivates you?
OSdev is a pretty reasonable cure for that - creating a whole OS from the ground up is a large enough task that you won't get bored for years.Rui wrote:Hello. Do you ever feel you want to code something but you just can't get any ideas or find that project that really motivates you?
Yes... except for an OS dev... Not bad though, atleast I don't run out of ideas for itRui wrote:Hello. Do you ever feel you want to code something but you just can't get any ideas or find that project that really motivates you?
I have the opposite problem. Too much motivation, not enough time!Rui wrote:Hello. Do you ever feel you want to code something but you just can't get any ideas or find that project that really motivates you?
I'll just leave a QFT here.MessiahAndrw wrote:I have the opposite problem. Too much motivation, not enough time!Rui wrote:Hello. Do you ever feel you want to code something but you just can't get any ideas or find that project that really motivates you?
When I have time, I lack motivation. When I don't have time, I have a rush of motivation. It's awfully frustratingToo much motivation, not enough time!
When you reach the point on a project where all the coding you need to do is bugfixing and stuff like that, it's easy to lose motivation, which makes debugging impossible. In times like these it's often nice to find motivation by succeeding in some other project (say, doing Project Euler problems) and then going back to your main project with that new-found motivation.Do you ever feel you want to code something but you just can't get any ideas or find that project that really motivates you?
same here! I often get ideas for projects in 2 at a time, and my projects I dream up are huge enough to take me a year to get a prototype going, so its very bad and probably why I can't finish anything.pcmattman wrote:When I have time, I lack motivation. When I don't have time, I have a rush of motivation. It's awfully frustratingToo much motivation, not enough time!
Proper build systems rather than Make are more portable and extensibleearlz wrote:Reason EPBP-C died: trying to find the perfect makefile that worked with BSD and GNU(and from there it gets worse, like me realizing it won't be any faster and what not)
Newlib is actually quite simple to port. It's the applications that're more complexbut I was stuck at the point where I was going to have to port or create a custom C library which is very complex..
That's why everyone suggests design first: you can find those flaws before you jump into the project, and figure out workarounds that don't involve rewriting existing code . IMHO, proper design fills the gaps in those times when you lose imagination.I also tend to get stuck starting a project and then discovering a design flaw and try to work out the flaw and suddenly I'm bored of the problem and start a new project..
I agree and I've always stressed that. With a proper design document laid out you should never be starting or mid-way through a project and be wondering "what's next?"pcmattman wrote:That's why everyone suggests design first: you can find those flaws before you jump into the project, and figure out workarounds that don't involve rewriting existing code . IMHO, proper design fills the gaps in those times when you lose imagination.