6 ms·
Where does it say that 501's are actually productive and produce good bug-free code? Being a little bit of a dick here, but programming is art and science and
by robomartin 15y ago
Where does it say that 501's are actually productive and produce good bug-free code?
Being a little bit of a dick here, but programming is art and science and there are aspects of it that require dedication beyond a 9 to 5 mentality. I, for one, prefer to hold reasonable hours and come home to the kids. At the same time, I am no stranger to 18 hour days, seven days a week. Sometimes inspiration and problem solving require you to stay on task longer in order to get things done.
And then there are those bug-hunting missions that sometimes never end. I once spent six months tracking down a software bug in a hardware design (Verilog, FPGA). High-speed digital designs can be notoriously difficult to troubleshoot. The problem was caused by a rounding error in an Excel spreadsheet used to calculate parameters plugged into the code months earlier. We used "ROUND()" instead of "ROUNDUP()". Though I digress, the point is that programming sometimes is about recognizing when you need to do a little (or a lot) more than watch a clock.
I'm not proposing that all programmers ought to work ridiculous hours. Whenever I've done 18 hour stints it took me out of the game for weeks. And that's OK so long as there was a point to exerting yourself to that extent.
The bottom of the manifesto says: "To us it is just a job, but we still do it well."
That, to me, is a guarantee to not being hired. That it is "just a job" means that they might as well be welding, at least to me. I don't want people like that in my team.
Having said that, I am the first one to tell someone to get the hell out of the office if they need to go see their kid perform at their school event at noon. Get the hell out and go enjoy the day with your family. Need to take a four day weekend when it isn't an official holiday? Do it! Send pictures. The point is that you build a team and everyone looks after everyone else while having one hell of a time creating a product. Respect, dedication and consideration. 5:01? How about not coming to work to go fly a kite with your kid? I like that.
- bmelton 15y agoI don't agree with everything you've said, but I do agree with the notion that "putting in time" doesn't necessarily equal work. It's important to me to maintain a good work life balance. To this end, I work from home 90+ percent of the time so that 'working late' doesn't mean having to miss out on family interactions, or becoming the proverbial stranger to my family. The flip side though, is that if there's a problem, or a challenge that needs to be solved, I generally go all out until it's solved. Not every bit of programming is amazingly fun -- CRUD operations or writing login forms for example are pretty mundane most of the time. But when I'm building out the logic for something that I don't know is possible, or if I'm attacking a problem I don't immediately know the answer to, I tend to spend a lot more time on it than 8 hours a day, and I seldom even notice until I'm done that I have. To me, it's not about watching the clock, it's about getting work done. If it takes me longer to get something done than I thought, that shouldn't necessarily mean that it's going into the queue for another day. Similarly, if I have dinner plans with my family, I'm not likely going to miss dinner because there's an unsolved problem. I don't have family plans or obligations every single day, so there really isn't a good reason for me to bolt at 5:01 every single day unless things are running smoothly.
- robomartin 15y agoWhat's interesting is that I agree with everything you said! My view of the job is that you should be passionate about what you are creating. That is not at the exclusion of personal or family life. Not at all. At times this dedication to the task will result in sacrifices. I am saying that, so long as these are justified this is OK. If working long hours is normal there might be something wrong with the process. My view was more about that case where "Hey, I am really into getting this state machine figured out. I should stay and get it done 'cause I'm in groove" or "we really have to ship this by Friday, let's get it done and take a few days off next week". In my view of the job the team is a team and everyone looks after everyones interests and well-being. I've let employees go out of town for a few days (fully paid) to go see a concert by a band they really liked. When asked, if nothing horribly pressing is happening I'll almost always say "yes". Why? Because I have those interests and passions outside of work too and it would not be fair to treat others differently. This is not a religious view, BTW, as I am most definitely not religious. When someone takes a few unscheduled days off to go do something they love the business does not loose money, you gain by fostering a stronger relationship as well as having someone come back from their trip re-infused with energy. Robotically clocking out at 5:01PM has never made sense for me, even when I was the employee. I don't think I have ever worked 9 to 5 in my life. Maybe I'm lucky 'cause I've had fun jobs that I wanted to keep doing.
- bmelton 15y agoThe only thing I really disagreed with was the notion that 501 developers aren't necessarily good developers. I've worked with some folks who belied that argument. Good, solid work, but no more than 8 hours of it. In all fairness, this usually (though not always) was the result of having been exploited. They were great developers working 18 hours a day, 6+ days a week, until they came in and quit. Realizing how necessary they were, the employers were able to strike a deal that kept them. Usually the only complaint were the work hours. Employers give them a gentler schedule and they stay, still producing good code. I get the motivations for the 501 guys, and will freely admit there were places I worked where I wasn't happy, and that unhappiness expressed itself as a nonchalant attitude toward the work. Of course, once I realized it, I made it a priority to get out; to get myself somewhere I could enjoy the work, and to get my employer the opportunity to get somebody in place of me that might enjoy the work they were doing. I didn't feel it was fair to either party for me to be that guy, and sadly, the work itself was exhilarating, it was a variety of factors within the team that made the job unenjoyable. I miss the work. :'(
- cmiles74 15y agoI don't understand why you wouldn't be interested in hiring someone who feels that software development "is just a job, but I do it well." And what is wrong with welding? What is it about programming that requires dedication beyond regular and predictable work hours? If the implication is that the 501'ers aren't thinking about what they do when they are not at work --they say they "...value personal creative projects over commercial products the world doesn't need." Certainly that is an abrasive way to phrase it, but it's clear that they are doing some level of development outside of their workday. This could cover keeping abreast of the state-of-the-art, certainly I feel that it is my responsibility to keep my skills competitive and up-to-date. You yourself prefer regular and predictable work hours, why shouldn't your software developers be able to enjoy these kinds of hours as well? The implication seems to be that people who work these kinds of schedules will be unwilling to work longer during a "crunch period." I don't see any reason to believe this is the case; I strive to work regular and predictable hours and I will put in extra time when warranted. I take full responsibility for my work and its effect on the company. I don't know what more any manager could ask of their employee and it's not clear where the 501'er is (in your estimation) falling short. Perhaps you believe that someone who strives for a regular and predictable schedule will be spending all of their time eyeballing the clock, perhaps even "gaming the system" to work as little as possible. For sure, such people exist, but I don't believe that there is any reason to assume a 501'er is one of these people. Again, I have to point out that you enjoy this kind of schedule yourself and you are clearly not spending all day "watching the clock." For that very reason, I find your objection to hiring a 501'er very puzzling. Lastly, as an aside, I wonder if the objection to the 501'er Manifesto boils down to this: the 501'er clearly values their personal life over their professional life. It seems to me much more difficult for a manager or business owner to baldly argue that their employees should value their work product more than their girlfriends, wives or families. Yet I can't help wondering if that isn't their true objection; that despite what they may say or do they are very much looking for people who are willing to live very unbalanced lives, lives that are unbalanced in favor of the workplace.
- ericd 15y agoCreative endeavors are not regular or predictable. Manual labor is. That's the difference, as writers and painters figured out a long time ago, but we seem to be struggling with. (For understandable reasons - it's often a team sport and not a solo one like those other two are)