41–47 of 47 posts
A big one is keeping iteration times fast.. If you have to wait more than a few minutes to run through your test suite or deploy to a dev environment it really kills the momentum. It starts easy but as you add complexity, dependencies, slow or flakey tests, it is slowly gets eroded.
It probably costs 30+ minutes of productivity every time I run them
Solutions: #1 get a private office
I really hate every article from this site when they get posted. The advice is never really useful, and the authors strike me as the worst kind of micromanaging, ineffective leader to work under.
A big one is keeping iteration times fast.. If you have to wait more than a few minutes to run through your test suite or deploy to a dev environment it really kills the momentum. It starts easy but as you add complexity, dependencies, slow or flakey tests, it is slowly gets eroded.
A trick from my PhD days: start the day with one to two hours of concentrated work. Don't look at your email or news or anything until you've done that. This worked fabulously for me because it allowed me to "swap in" my work enough that I could avoid distractions. And yes, I have ADHD.
Seems simple but it works.
A trick from my PhD days: start the day with one to two hours of concentrated work. Don't look at your email or news or anything until you've done that. This worked fabulously for me because it allowed me to "swap in" my work enough that I could avoid distractions. And yes, I have ADHD.
A therapist suggested this idea to me. Figure out when is your most productive time of the day (usually). Just two or 3 hours. OK, those are now your sacred hours. No procrastination or distractions allowed. Seems simple but it works.