3 ms·

Remember when I was young C programmer out of varsity - immature really. Wasted a year to port some software over to a new embedded platform but eventually it

Remember when I was young C programmer out of varsity - immature really. Wasted a year to port some software over to a new embedded platform but eventually it became a new OS (GOS - named after me obviously) , network stack (RS485 based) with queues , new debugger but it was all so buggy that is crashed more than it ran. I was so overwhelmed as I kept working on new stuff without fixing existing stuff that eventually a veteran saw me struggling and took me aside and helped me to do a quick and dirty port minus all the crud. I learned a valuable lesson - yes write good code - but good enough - and know when to STOP and SHIP it.

john567 4y ago
Very valuable lesson. Put some effort into defining scope and prevent yourself from improving your design as you go. (There may be time for that next time) Know your platform! If you know exactly how well the different things you need are going to behave you are free to take every shortcut out there. If you're experienced you'll carve out a space for you to return to if you need. i.e. you make things modular where needed. The first iteration should be working code and unless there's time to make improvements you don't. You move on to the next thing.