markdown guide

breaking things down into manageable pieces and making sure you are only looking at the immediate needs at any given moment. "By the end of today, I need to get X done." And plan built in short cognitive breaks.


Don't rush. I know about working in a stressful environment with tight deadlines (I used to work in advertising, not anymore πŸ™ƒ), believe me, you don't want to rush. Reserve 1h or 2h to sit down and develop an action plan. Every detail you can foresight is a win.

Classic DEV Post from May 6

Thoughts on legacy code, diversity and inclusion

TLDR; If you're still dropping snarky commentaries about PHP on Twitter, just grow up already.

Nathan Englert profile image
Web developer by day, game developer by night.