3 ms·
1. Decouple dev from analysis; work on only 1. 2. Analysis at night with pencil & paper. 3. Don't go to sleep without specific morning plan. 4. Dev sta
by edw519 11y ago
1. Decouple dev from analysis; work on only 1.
2. Analysis at night with pencil & paper.
3. Don't go to sleep without specific morning plan.
4. Dev starts first thing in the morning.
5. Always focus on WHAT to build, never HOW.
6. NO INTERNET in same room as dev computer.
7. Start with the data; the process will follow.
8. 3 3-hour dev sessions per day.
9. 1 2-hour analysis/review/refactor session at night.
10. It's a marathon, not a sprint.
11. Apparent failures are OK. May lead to something great.
12. Take care of myself (diet, exercise).
13. When I'm not working, I'm not working.
14. Never forget WHY I'm building something.
15. Weekly & monthly project plans, frequently revised.
16. Happy dance whenever something really cool works 1st time.
- rubiquity 11y ago> 8. 3 3-hour dev sessions per day. > 9. 1 2-hour analysis/review/refactor session at night. > 10. It's a marathon, not a sprint. Ummmm....
- Mikushi 11y agoNice recipe for burnout. 11h per day is not sustainable, not healthy and hurtful to whatever you are trying to do.
- electronvolt 11y agoI think that it's manageable, esp. if you are doing breaks for meals/exercise/etc. and getting enough sleep, even moreso if this is not an every day of the week plan (two days on, one or more off, for instance). Without any data on frequency or what this person is working on, you really can't make a blanket statement like that.
- wildpeaks 11y agoNO INTERNET in same room as dev computer. That one doesn't seem like a good idea, better work on impulse control if one can't stop himself from checking his facebook every 2 minutes than shooting yourself in the foot by cutting off an invaluable tool like internet. It's like turning off the heating to avoid sleep-deprived developers falling asleep: a short term solution that doesn't solve the root of the issue.
- papaf 11y agoI can relate to a "no easy internet" rule. It is possible to download a lot of important information (godoc, cppreference, perl man pages) so that internet interaction is minimised. It is possible to plan what needs to be looked up. If you have to move room to look things up that sounds about perfect to me.