![]() ![]() I find this entirely toxic and incredibly risky. There is a dangerous notion of team members being 'heroic' when individuals pile into problems and crunch like crazy to fix them. And how much more frequent are bugs in code that's written at 10pm, versus work done in the normal working day? Similarly, eating pizza while 'working late' usually means you're not really working - you're just sat around the office ordering and eating often middling-quality food while not achieving much at all. Come in, work your day, go home, live your life. We flex 30 mins earlier if it helps with school or travel, but that's it. That's why at Wish we operated a standard 9am to 5.30pm working day, with an hour for lunch that we encourage people to take (and to get out of the office, or at least sit in the kitchen, to get away from their screens). You also need to be honest with your team - it might seem cool having people start at 10am or later, but that leads to leaving at 6.30pm or later. ![]() "There is a dangerous notion of team members being 'heroic' when individuals pile into problems and crunch like crazy to fix them" Casper Field I think that the decision-making related to feature-planning grows more confused and less logical as accumulated exhaustion kicks in. Is it really worth staying late to implement a 'cool' feature that 95% of users will barely notice? What are the knock-ons of that feature on other parts of the development team? I would argue it's a waste of time, or even worse, outright risky for the entire project. The solution is to plan sensibly, to trim specifications, to hire enough people, and to learn that it's okay to say no to external forces now and then.Įqually, you cannot lean on just one of those solutions - it has to be a mix. To be fair, if used very sparingly, for a day or two, I think that additional hours can help if something is in crisis, but over the long-term they are never the answer. The myth arises that working late will fix the problem. It's usually a fatal combination of those factors.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |