6 ms·
I quit a job when I felt burnout developing. The cause? Pair programming. I just cannot that close to someone for the majority of the workday without feeling co
by ams6110 10y ago
I quit a job when I felt burnout developing. The cause? Pair programming. I just cannot that close to someone for the majority of the workday without feeling constant low-level stress and annoyance, and I can't focus and think about problems in that setting.
When you have to sit in your car for 15 minutes every morning just to summon the resolve to get out and go into the office, something's wrong with your work environment.
- city41 10y agoI also left a job due to pair programming. That company pair programmed 100% of the time. It concerns me that might become a norm. I wrote a blog post on why I think that's a bad idea: http://www.mattgreer.org/articles/pair-programming-is-not-a-panacea/ http://www.mattgreer.org/articles/pair-programming-is-not-a-...
- dasmoth 10y agoThanks for writing this. I particularly like the suggested desk arrangement -- although I'm not sure I can see it catching on given that pairing is often coupled with long tables in open-plan offices. Once upon a time, I thought programming was an introvert-friendly career. That seems to be changing fast.
- ape4 10y agoI guess they want to get rid of the deep-thinking reflective introverts.
- nikanj 10y agoTheir idea of a great hacker comes from movies such as Swordfish
- HarryHirsch 10y agoYou ask yourself if Agile, pair programming, open plan office and all the other fads of the day may have to do with the economic environment. Back in the day, when the economy wasn't excessively financialized, a company had to develop a product and compete successfully in the market. So management did what it took and treated its developers well. But nowadays, it's all about raising yet another round of funding and selling to an investor, consequently, management subscribes to every idiotic management fad in fashion because that's what investors look out for and what helps the company to stick around for yet a year more. No product development required.
- billmalarky 10y ago>It concerns me that might become a norm. I wouldn't worry too much about this. Most companies see pair programming as paying 2X for the same amount of programming output.
- s_kilk 10y agoI wonder if these kinds of teams are lead by extroverts, who appreciate having a captive audience for their peopley, extroverted shenaniagns. Having a stable of people who are contractually obligated to put up with their outgoing personalities.
- crmd 10y agoIt's not nice to belittle individuals whose brains work differently than your own.
- brokenmachine 10y agoThat's true, but the problem is that those outgoing types interfere with the introverts brains from working when they interrupt them constantly. I would like more segregation! Enjoy your riotous atmosphere over there (far away) please!
- ewjordan 10y agoI've mostly seen it pushed (as a hard 100% policy, at least) by well meaning but naive people that have done it a few times before, got obsessed with it, and decided it's this week's cure for everything. The reality is, it will make the team produce fewer bugs. It will also help in knowledge sharing, and in some cases result in tidier designs. But you'll basically have half the manpower. So unless you actually have serious problems with bugs, knowledge sharing, or code design, it's not going to be worth it. There are other ways to achieve quality, and most senior people can do that very well without someone pairing with them.
- pyb 10y agoPair programming is great, but that can only happen between willing and compatible participants. As you say, it should never be imposed from 'above' to any arbitrary pair of colleagues!
- JoeAltmaier 10y agoAgreed. I 'pair program' with my consulting partner. That is, we sit in the same lab and do our own thing, coming up for air to discuss an approach or algorithm, or even to review code. But 99% of the time is spent at our own tasks. This kind of 'pair programming' works best for us.
- trevyn 10y agoThat sounds like a nice, collaborative work environment, but I would not file it under any definition of "pair programming". Edit: 99%? So you spend less than five minutes collaborating per 8-hour workday?
- wott 10y ago> 99%? So you spend less than five minutes collaborating per 8-hour workday? It sounds reasonable: 0 minute on a day, 10 mn on the next one. You can double it because the "99%" figure was dropped randomly, but that seems fair.
- zeveb 10y agoNow that's a great article — so good I think that it should stand on its own. Submitted as https://news.ycombinator.com/item?id=12291080 https://news.ycombinator.com/item?id=12291080
- hacker_9 10y agoI had a similar experience that made me quit my last job, but for me it was being in an open plan office. I just found that I felt constantly under someones gaze, and I couldn't look around without looking someone in the eye. It was a low level stress like yours, and was really uncomfortable when trying to work through problems. For example I find closing my eyes helps me visualise a process in my head, but then someone sat nearby would see that and use it as a cue to talk to me 'oh are you stuck on something?.. yada yada yada'.
- freddyc 10y agoI had a very similar experience where I actually dreaded going into the office because I knew my productivity would fall off a cliff. I slowly found myself accepting the day would be a loss with pointless meetings and other distractions, and got into the habit of doing my "head-down" work later once I got home. My wife pointed out how stupid that was (and frankly, unsustainable) so I pretty quickly jumped ship to a different company with a much better office design/remote work policy where I felt a lot more comfortable.
- learning___ 10y agoI have the same questions for you as I asked the parent poster, as I mentioned in that post I feel like I am going through something similar to you both right now due to an open office. I also feel like it is hard and rare to get the real "head-down" work done while at work due to constant interruptions. How long at the job did it take you to realize that it caused a constant low level stress? How long did you end up staying there before leaving? Did you reveal the real reason for leaving when you left?
- freddyc 10y agoI would say it wasn't until after the honeymoon phase of being new and excited wore off and I was given meaningful work to complete. It was a while ago now, but I think it was around the 6-8 week mark that I begun to really notice my workdays were a waste. Being a male I suppressed my feelings :) and the stress slowly built up over the next 6 months until my wife finally pointed out that it wasn't healthy and was impacting my relationship with her and others in my life. I'm somewhat rare in the sense that I just quit vs lining up a new job first as we had a decent financial buffer, although if I'm being honest I suspect it was a case of jumping before being pushed as the stress was starting to impact my workplace relationships as well (especially with the CEO who was a chronic time-waster that loved pointless meetings). I've said this elsewhere, but I think it's healthy to mix things up every few years - leaving this company ultimately worked out well for me as I quickly found a new opportunity that opened up doors I had never considered before. I don't know your exact circumstances, but if you have a significant other I think it's worth having a candid conversation with them and work out what the two of you need to live a balanced and fulfilled life. If the workplace stress is leaking into the rest of your life and you find work consuming an unreasonbale amount of your time, it's probably a good sign that it might be worth exploring other opportunities (in my experience, it's much harder to change an organization than it is to just move on). I realize this is different to the "roll-up-your-sleeves" advice elsewhere in this thread, but I view my career as a 40+ year marathon so I embrace the odd twist in the road every now and again.
- a3n 10y agoI may be wrong, but my unresearched feeling is that extroverts promote these kinds of things, and introverts (like myself) are made to look bad for not liking and thriving in these imposed environments. Not team players. One size doesn't fit all.
- wott 10y ago> Not team players. For that kind of team, and that kind of play. But if you're like me, you can deal with workmates, it is just that a small amount of interaction with a small number of people is enough to be productive and yet not waste people's time.
- jMyles 10y agoThis phenomenon is one of the distinct situations where I have found that the effects of cannabis are helpful. Smoke a bit with your partner, go for a walk, maybe apologize or retract some things if necessary. Maybe stop being such a perfectionist and just merge what does work now.
- dasmoth 10y agoI have no objection to canabis or those who choose to enjoy it, but the idea that I might need psychoactives to handle the work environment -- even when I'm doing something I'm widely considered to be pretty decent at -- is repellant.
- wott 10y agoWell, most people build up their own ritual while getting to the work place and starting their work day. It is not much different as a psychoactive mean, it is just one step further, with a substance (this being said, most people already include tea or coffee in their ceremonial). It is just that a good part of them don't even notice what they do and why they do it.
- jMyles 10y ago> the idea that I might need psychoactives to handle the work environment It occurs to me that many people, perhaps even a majority, perceive a need for coffee in order to have the energy and focus they need. My assertion is that cannabis sometimes has a similarly useful effect, and that one distinct example is in how it affects teamwork.
- a-saleh 10y agoIt seems weird to me that some workplace would mandate physical(?) pair-programming as a default. And I actually like pair-programming, some of my best code was written with somebody sitting besides me and we have solved some really tricky bugs like this. But we tend to do this only rarely. Most of my day is spent organizing stuff and reading emails anyway :-)
- aantix 10y agoI'm pretty sure Pivotal and Carbon Five, two high end Rails consulting firms in SF require pair programming. I'm pretty sure that you can't hire Pivotal without contracting two of their engineering, strictly for pair programming. Some of my best code has been written with pair programming but I can see the flip-side. There's no day-dreaming, there's no zoning out, complete engagement all day long. It's the same mental overhead as with taking care of toddlers; you have to be constantly aware otherwise suffer the consequences.. :)
- shostack 10y agoAny idea how much of that is to juice margins by billing two people minimum? Surely the work is not completed twice as quickly.
- twic 10y agoI work at Pivotal, although in London. We do indeed insist on doing all programming paired. I honestly don't think that's because of margins, though - it's that everyone buys into the XP idea that it's the best way to program. I don't think it does much for margins, because you have to spend twice as much on developers to get that double revenue, so the margin is the same. Our normal thing is to form joint teams of Pivotal and client developers, and in that situation, pairing is also a really good way to teach the clients our way of doing things.
- BurningFrog 10y agoI love pair programming teams, and would not want to work anywhere else. Of course, a team like that needs to only hire people who are up for that lifestyle.
- watashiwa 10y agoI don't consider myself particularly extroverted or introverted, and I've personally had both bad and good experiences pair programming. I think it depends entirely who you're programming with and in what context. My bad experience was with a large international consulting company. The consultant members colluded to extend their contract and push their own design, architecture, and tools. The time spent pair programming with them was simply a method of advancing their agenda. It was a horrible experience and I felt burnout just like you described. It was a waste of time and money for the client. My last consulting project was the exact opposite, it was absolutely wonderful. I spent the day pair programming and it involved creative problem solving and an intellectual exchange. It was a great experience, I grew professionally, wrote better code, and can see legitimate a case that it was worth the client's money.
- trentmb 10y ago> Pair programming. I haven't had to work in an environment that requires it, and just looking at the wiki page makes it seem miserable. Do you really just sit at one workstation, with another person watching over your shoulder haggling over each line of code? I think I'm just not a quick enough thinker for this approach to work.
- ldjb 10y agoI suppose you could describe it that way. Pair programming certainly isn't for everyone, but under the right conditions, it can be very effective. It can be a good means to share ideas and keep up the motivation. That said, it ultimately comes down to whether or not the pair work well together — sometimes you 'click' and everything's great; other times you don't. A related technique that's quite interesting is mob programming, where an entire team is huddled around a workstation. There's less pressure on each team member as individuals, and the person typing the code is mostly following directions from the others. Really, the approach to development needs to be appropriate for the dynamics of the team. It might be a good idea to at least try out pair or mob programming to see how effective it is. But you can't just be doing it just because it's the 'hip' thing these days. Also, pair and mob programming can be quite draining, so you may not want to be doing it all day. You could do it for part(s) of the day, and work on your own at your own pace at other times.
- douche 10y agoThere was a time-lapse video of mob programming I saw on here recently (unfortunately can't find it). At least half of the group that was clustered around the one machine was completely checked out, and you could see that they were so incredibly bored that they were about to drive pencils into their eyes. Also, one guy came in during the lunch break, and got more done than the mob did in the other eight hours...
- HerpDerpLerp 10y agoThis? https://www.youtube.com/watch?v=p_pvslS4gEI https://www.youtube.com/watch?v=p_pvslS4gEI This looks more functional. https://www.youtube.com/watch?v=dVqUcNKVbYg https://www.youtube.com/watch?v=dVqUcNKVbYg I am not against the idea... but yeh I can see it has issues!