Regardless to this I was always seen as the efficient guy who delivered work on time or early. My typical play to get ahead of the curve often resulted in stress due to the continuous change in requirements. However I then joined an industry where "business and system change" is typically embryonic, fuzzy or scope is unknown. Early in my career and through education I learnt to jump on new work early so I could gauge it's size and ultimately then end up ahead of the curve with less stress to hit deadlines. And lo and behold, that was the first post to have comments on it. That was the weekend I created the whole comment system on the site and then I woke up really early on Monday to actually write the article. □Īnother notable instance of this for me was a time when I was working with on a dev.to post that had to go out on Monday morning. Regimented strict homework time is hard for me and if I'm going to be productive, I need cleaning my room to count as productivity.įor example, this post is cleaning my room instead of doing my homework, because myself and a couple folks from the team are going to be conducting some workshops at DevFestNYC and I've been tasked to finish up some dev.to integrations we have planned for the event. It allows us to be honest about our humanity. A lot of our best code is written in "clean your room" time. It's not negative per se, because cleaning your room is really important. ![]() We have a metaphor on the team called "Cleaning your room instead of doing your homework" to describe when someone does a lot of productive work instead of their most important priority.
0 Comments
Leave a Reply. |