Threads for EvanMiller

  1. 12

    I feel like I can’t open a web browser these without reading about some conflict in the Great Demographic War between men in their 20s and everyone else (that is, some version of Luis versus the OP). I personally think it’s great that Luis is interested enough in his work that he wants to spend part of his weekend on the problem, and the dire admonitions to the contrary sound to me like people are afraid that the Luises of the world are out to make everyone else look like Skid Row bums and good-for-nothing layabouts.

    It’s amusing to me that the commenters on that post immediately feign concern over programmer burnout, as if poor Luis is going to stumble into work on Monday morning a haggard and broken man, requiring weeks of recovery before he is well enough to utter the one-word solution to the problem. I guess Luis just needs to learn that the local politics require that he pretend to discover the solution at exactly 9:15 AM on Monday morning, and then move on to the next bug.

    1. 40

      I don’t think people are afraid that Luis will make them look bad. I think they worry that the higher-ups, after seeing Luis put in a weekend here and there, will come to expect it and begin to feel that they are entitled to having him (and everyone else) work weekends whenever they want. In my experience, this fear is entirely justified at most companies.

      “If you give an inch, they’ll take a mile” has been the defining characteristic of labor-management relations at the majority of my employers, and has led to my being very careful, when I do get interested in a bug and poke at it on my own time, to make sure that nobody finds out.

      David Graeber, in his book on debt, talks about how gifts, when repeated, became obligations–debts–in feudal societies:

      But this introduces another complication to the problem of giving gifts to kings-or to any superior: there is always the danger that it will be treated as a precedent, added to the web of custom, and therefore considered obligatory thereafter. Xenophon claims that in the early days of the Persian Empire, each province vied to send the Great King gifts of its most unique and valuable products. This became the basis of the tribute system: each province was eventually expected to provide the same “gifts ” every year.

      He describes in more detail than I can summarize here how this is the consistent result of gifts between people in a hierarchical relationship (such as employer-employee).

      1. 10

        Part of it is about establishing a clean boundary for your employer. Once you’ve established that you’ll allow them to invade your personal time, you can expect it to be the norm from then on.

        1. 9

          I guess Luis just needs to learn that the local politics require that he pretend to discover the solution at exactly 9:15 AM on Monday morning, and then move on to the next bug.

          Oh, would that it worked like that.

          Instead, what happens is Luis’s co-workers arrive on Monday to find out that Luis, self-directed millennial autodidact that he is, hasn’t just discovered the solution, he landed it in production around 4am on Sunday. His co-workers, freshly rested and sipping coffee, slowly realize that Luis’s “solution” is actually a depth-first exploration of the problem space that bottoms out kind of near a solution, but if we’re honest—and Monday morning’s an excellent time to be honest—it’s a rolling clusterfuck. It has no tests, it has no separation of concerns, the code has some, uh, Luis-isms in it, it adds a number of unorthodox dependencies, it tightly couples a number of orthogonal services which results in overall SLA degradation, its sweeping changes have resulted in breakages of three feature branches other engineers had planned to merge this afternoon, and there isn’t a scrap of documentation to be found for the thing.

          Luis rolls into the office late on Monday to find his co-workers angrily planning how best to roll back his changes and is hurt and dismayed. He’s hurt because he spent all that time fixing the problem and he learned so much about the new library he found to implement some of that. He can’t understand why his co-workers are being so territorial. “I don’t get it,” he says, “why would we waste all this time tearing down my changes? I’ve already fixed the problem! Let’s move on to the next bug!”

          I, for one, am not worried about Luis burning out. I’m worried about his co-workers.

          1. 2

            I worked at a company where the CEO (and founder) would log on and do changes to production on Sunday afternoon, but without going via dev/staging so systems broke hard on the first regular deployment the following week…

          2. 8

            I agree with the OP. Most of us sell our time for money. Ideally we’re selling about 40 hours a week in return for X salary. However many companies find ways to “encourage” people to get 60-80 hours a week of work in return for X salary. Not only does this give poor results in terms of quality and productivity, but it effectively puts a pretty strong downward pressure on salary and upward pressure on hours worked per week.

            Commenters aren’t afraid of looking bad. They are here representing the interests of working programmers rather than the interests of employers.

            Also. I didn’t see a mention of age in the op. Probably not appropriate to bring that into the conversation. I know plenty of older programmers who burn the midnight oil (on billable hours).

            1. 17

              Also. I didn’t see a mention of age in the op. Probably not appropriate to bring that into the conversation.

              I wouldn’t discount that just yet. I think age intersects importantly here.

              Now, consider: the median age of a Google employee is 29. Is it any surprise that the Googolplex features three free meals at their cafeteria, on site haircuts, on site healthcare… literally any possible perk they can to throw at you? Including some targeted towards younger employees? Shouldn’t be: it’s in Google’s best interest to hire young programmers and keep them at work.

              This is also the reason companies that advertise “we hire based on your Github!” are actually saying “we hire based on your lack of external commitments.”

              Ageism in tech is a massive problem. I picked Google because they call their older employees “Greyglers” on their own damn diversity webpage! At one point they had a featured ‘Greygler’ who was 46. Google considers you “old and grey” at fucking 46.

              1. 1

                Meanwhile, at BMW:

                In 2007, the luxury automaker set up an experimental assembly line with older employees to see whether they could keep pace. The production line in Dingolfing, 50 miles northeast of BMW’s Munich base, features hoists to spare aging backs, adjustable-height work benches, and wooden floors instead of rubber to help hips swivel during repetitive tasks.

                The verdict: Not only could they keep up, the older workers did a better job than younger staffers on another line at the same factory. Today, many of the changes are being implemented at plants across the company.

                Via Bloomberg news.

            2. 3

              Agreed. This post seems to assume a lot about Luis' motivation and what causes burn out.

              Firstly, being interested in a problem and wanting an answer doesn’t mean you’ve fallen victim to the sunk cost fallacy. Sometimes you’re just interested. I don’t usually work extra hours myself, but once in a while, I get to work on a cool problem and my brain just wants more. Similarly for tricky bugs. Why deny it? It’s no biggie.

              As for burn out… I’ve experienced burn out and I’ve also sustained a pace that involves writing a lot of code for a long time without getting burn out. For me, the conditions that lead to burn out are extreme overwork on something that I don’t want to be doing. It just so happens that I really like building software, so it consumes a lot of my time, and there’s no risk of burnout because it’s something I want to do.

              1. 4

                I imagine the OP is looking back on experience and trying to do Luis a favor. But then, we all need to get our first speeding ticket sometime.

              1. 5

                For the curious, “since” keeps its state in a dedicated file, one of:

                • $SINCE
                • $HOME/.since
                • /tmp/since

                I think it’d be just a tiny bit cooler if instead it stored the access information in the extended attributes of each file (for file systems that supported it).

                1. 5

                  That would have issues with read-only files (given your permissions, multi-user systems where multiple people might use since, and it would take up some disk space here and there that you can’t readily free up at once.

                  I do wish more things would use extended attributes though.