4 ms·
> You need to be really smart and have a scientific mindset. Most importantly you need to love learning new things. I'm not so sure that these are required. I
by ChrisMarshallNY 4y ago
> You need to be really smart and have a scientific mindset. Most importantly you need to love learning new things.
I'm not so sure that these are required. I think they are more akin to "commonly found characteristics."
Especially the "scientific mindset" part. I have a disciplined mindset, but I suspect most scientists would take issue with me, calling it a "scientific" mindset.
In my experience, being a good problem-solver is more important than just about anything. Being able to "divide and conquer" a problem, sniff out root causes, and not settle for symptomatic fixes, etc. Stubborn might be more important than smart.
We also don't all have to be Mensa members. Many programmers are probably not much smarter than their peers in other disciplines.
But "love learning new things" is, while maybe not "required," at least quite helpful. It certainly applies to almost any vocation; not just software development.
But the real gist of her essay was that it helps if programmers are good with people, as much as with machines, because they connect better to the end-users of their work.
Whether or not being "good with people" is required is debatable, but I think that it is important for everyone to keep an eye on the final deliverable, and its operation in the context of the end-user.
In my experience, many organizations go well out of their way, to ensure that engineers never hear directly from the user. That's Marketing's job, and Thou Shalt Have No Other God Before Me... etc. I've watched Marketing people throw huge tantrums at engineers that "dare" to suggest that they might envision the way their work would be perceived by the end user.
- tunesmith 4y agoI worked with someone who didn't have what I'd call a scientific mindset, and it can really be a limiting factor. They confused correlation with causation, in other words were quick to launch on to theoretical explanations without testing or proving their thinking. When solving a problem, they tried tons of different approaches until they empirically found one that worked, without always fully rationally understanding the cause of the symptom they were trying to remedy. They usually succeeded, but the cost was the time spent, and the complexity of code that resulted. There are a lot of ways to be a programmer, but that is not one of the better ways. The programmer was productive (prolific) enough, and the business was resource-constrained enough, that their work quality was not even close to consider firing or replacing, but I'm convinced it cost the team and the company a lot of productivity and effectiveness over time.
- ChrisMarshallNY 4y agoSounds like a bad problem-solver. Maybe a good problem-solver is "scientific." Dunno. I have never had "scientific" training, but I have had plenty of "problem-solving" training.
- inkblotuniverse 4y agoAll problem-solving methods should converge, given enough brainpower, so yes.
- GoblinSlayer 4y agoStubborn problem solving isn't always good. A problem can be solved in many ways, some of then can lie in the realm of program architecture or even product strategy. If your solution conflicts with them, it will be thought of as narrow sighted.
- ChrisMarshallNY 4y agoTrue. It’s also possible to go all “Captain Ahab” on a bug, and waste a huge amount of resources, trying to fix a minor problem, or refusing to use a perfectly acceptable workaround.