7 ms·
Pair programming, in this context, means two people sharing a workstation. No "single developer" code allowed, at least when it's taken to extremes. Agree wit
by dasmoth 10y ago
Pair programming, in this context, means two people sharing a workstation. No "single developer" code allowed, at least when it's taken to extremes.
Agree with much of what you say and...
>>> how do the introverts get on in such an environment?
...in my experience, not great.
Out of curiosity, what kind of area do you work in?
- ci5er 10y ago> Out of curiosity, what kind of area do you work in? I started out in semiconductor design (Motorola) in Tokyo (systems engineering - developing MCU firmware for consumer product customers. Sony and Canon were my main customers). This was a long (?) time ago - the mid-to-late 80s into the 90s. In the mid-to-late 90s, I did a startup developing software for electronics payments and banking on the Internet that sold its wares to the largest banks in various countries around the world (and sometimes the country's big telecom vendor if they were feeling feisty enough to take on their banking clients). In the early-to-mid 00's I tried (and often failed) to construct deals around aquaculture, mobile data telecom back-haul and coal-to-whatever conversion projects. This decade, in a addition to kick-starting software development teams for non-technical startup founders, I seem to be settling in around clinical informatics. I'm hankering to try and see if it is now possible to construct a "remote-first" company for enterprise software in healthcare IT. But I'm old and old fashioned. I tend to bring in people who have substantial development experience (there are always exceptions for brilliant young talent), and I've learned that people like to work like they like to work and to try to enable their productivity in their own style, not inculcate them in the "one true way" I want them to work. I'm guessing I said something really out-of-touch to trigger the question. What was it? :-)