The conversation

Lessons learnedExperience excerpt · English

I am one of those people - an academic type that likes to over-engineer, and at least partially …

I am one of those people - an academic type that likes to over-engineer, and at least partially work on embedded systems. What I've learned after two decades of experience is that it's best to apply most of that sophistication to tooling and supporting software - test suites, fuzzing, benchmarking, quality evalution, code and data generation, prototyping environments, automated reports, etc etc. All while keeping the actual shipped software as simple as possible.

Original discussionAsk HN: Strategies for working with engineers that are too smart?474 source comments · at import
2

What was this responding to?

Parent context · original excerpt

TH

There are a couple of engineers on my current team that I can only describe as being a little too smart for their own good, and I'm struggling a bit with how to work with them. I've worked with this sort of engineer on previous teams as well, and they all share a few traits: - They're brilliant, I mean very smart people (in an almost academic way?) - They have a big appetite for adding complexity to systems - They also have a big appetite for adding work to their own plates - Their code has no consistent style I work in embedded systems, so I'm generally writing C for resource-constrained systems. This sort of environment is rife with footguns, and I spend most of my time just trying to avoid those. A big part of that is keeping the things that my team controls as simple as possible, and while we are resource constrained, it's a balance. The tension comes when someone's more than happy t…

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

JO

I can also see this turning sour, though. A problem with the mindset being discussed is that it makes it hard for people to collaborate, since everything gets complex and muddled. If you just move that problem from the shipped code to the tooling around the code, you haven't really gotten rid of it. There is still a big barrier to entry to contributing to the project, since people don't understand your infrastructure.

Full original
MR

"If you were that smart you wouldn't be working here with me" A line I used a few dozen times in my career

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.