5 ms·
The thing that struck me is "anyone who is fascinated by computers and spends all their free time playing with them can be a developer." Back before developers
by ChuckMcM 10y ago
The thing that struck me is "anyone who is fascinated by computers and spends all their free time playing with them can be a developer."
Back before developers were perceived as 'rich' and 'pampered' there were people who were fascinated by computers and spent all their time playing with them and were called 'nerds.' Then it became "cool" to be a developer or "you can get rich as a developer at a startup!" and then you get people who don't care at all about computers and really never have, working as developers.
My litmus test is often to ask someone when they show me a solution, "what other solutions did you consider?" If they have wandered around looking at different ways to attack the problem they are more typically 'nerd' type developers, if their response is "none, this works so I went with it, moving on." they are often just working a day job. Watching the two types of people from the late 90's to today, the people in it for the money burn out much more frequently.
- ArkyBeagle 10y agoBeing a programmer meant not making all that much money. This was true as late as in the 1980s. Before Gates, nobody rich was also a programmer. People like Ross Perot were not programmers. Whatevs about it "being cool". I can certainly understand being interested in computers, but ... it's hardly what the cool kids do, what with they Camaros and 6x9 speakers and 8-track tape :)
- kirse 10y agothey are often just working a day job. I used to be snooty about this too until I had a member join one of my teams who is exactly this type of person... Treats it like a day job, and absolutely rips through well-defined coding tasks as long as I do the general solution-finding and lay the architectural groundwork ahead of time. They don't burn out either, because it's just work to them and they take regular vacations. They're not my go-to for solving architectural-type problems (solution-finding as you call it), but I'm OK with that because their strengths lie elsewhere in terms of discipline, focus, training JR team members in coding practices, knowledge of SW project process, etc. Every team needs its brick-layers who can work hard and follow blueprints really well, and not all of those brick-layers are going to be architects. One of my biggest work-related lessons out of 2016 really.
- cosinetau 10y agoSolid lesson. Thank you for sharing this.
- joatmon-snoo 10y agoOut of curiosity, how did you get this person on your team, since it doesn't sound like you were open to the idea until after the fact.
- kirse 10y agoThey were passed to me as a "here, I've got this person who needs work." It's not so much that I wasn't open to it as I generally just assumed finding semi-clones of myself (passionate about all-things computing, spends time outside of work on projects, etc) was the right way to build a team. The more teams I lead the more I realize how wrong that is, it's like trying to build a human body out of all eyes or hands.
- JBlue42 10y agoThat's a great insight. Thanks for sharing.
- throwaway99187 10y agoI've never seen a good architecture that wasn't largely by the single individual who started and initially wrote a project.
- jressey 10y agoOne man writes a novel. One man writes a symphony. It is essential that one man make a film. -Kubrick I often use this argument in situations where people are discussing system architecture.
- taman999 10y agoWhat's with the vacation shaming?
- mablap 10y agothen you get people who don't care at all about computers and really never have, working as developers You can say this about any profession though. Just look at the medical field. Some MDs have "true passion" but a lot have chosen this path because it pays well and comes with high status. At least that's what my personal experience suggests.
- davedx 10y agoHa I am both, it is situational for me and depends on the project impact, engineering challenge, deadlines, how tired I am... if I have to build yet another landing page in Angular then I just want to get it done. Sometimes knocking the less interesting stuff on the head in the most boring and productive way means you leave on time, have a nice night with your family, and are rested and ready for that cool or interesting bit of work you've been looking forward to working on. I also think having worked as a freelancer made me appreciate the business side a lot more, which made me consider when to be pragmatic and when innovation or more creative thinking might be worth it. My inner nerd is as strong as ever but I don't like to waste time.
- epalmer 10y ago> My inner nerd is as strong as ever but I don't like to waste time. Love the inner nerd phrase. I'm 63 and love wasting time now because when I do my brain works on the problem(s) at had and I write better code or create a better architecture when I get to it. Less is more. Slow down to speed up.
- otalp 10y agoI think that's true for everyone to an extent. Nobody like every single facet of technology, especially if it's the same repetitive job or a badly designed language.
- fillskills 10y agoAbsolutely dig this question - "what other solutions did you consider?". Will add to my interview flow.
- Jemmeh 10y agoEhhh, it depends. If you're being a perfectionist and constantly trying to find the "best" solution, that'll make you burn out too. Certainly do your work in the design phase rather than code phase as it saves you time overall, but don't obsess over unreachable "perfect code". And sometimes you just have to shut up and ship.