“If it’s your job to eat a frog, it’s best to do it first thing in the morning. And if it’s your job to eat two frogs, it’s best to eat the biggest one first.” - Mark Twain A useful software engineering practice is to work on the hardest part of a program first. If you can’t complete that piece then you’ll never be able to get the full system to work. For example, if a program has 10 components, and component #10 is the most challenging one, then coding up #1 through #9 first means that an engineer might waste a lot of time before figuring out that the entire project is impossible. It’s more sensible to start with #10 to understand if the project is viable in the first place. Tackling the easy stuff first is basically procrastination.
Tackle the Hard Stuff First
Tackle the Hard Stuff First
Tackle the Hard Stuff First
“If it’s your job to eat a frog, it’s best to do it first thing in the morning. And if it’s your job to eat two frogs, it’s best to eat the biggest one first.” - Mark Twain A useful software engineering practice is to work on the hardest part of a program first. If you can’t complete that piece then you’ll never be able to get the full system to work. For example, if a program has 10 components, and component #10 is the most challenging one, then coding up #1 through #9 first means that an engineer might waste a lot of time before figuring out that the entire project is impossible. It’s more sensible to start with #10 to understand if the project is viable in the first place. Tackling the easy stuff first is basically procrastination.