3 ms·

Mind elaborating on this? This is a fresh take for me. Are you saying a 10x dev writes code optimized for their own velocity, at the expense of accessibility/te

by sdwr 4y ago

Mind elaborating on this? This is a fresh take for me. Are you saying a 10x dev writes code optimized for their own velocity, at the expense of accessibility/teamwork?

hsbauauvhabzb 4y ago
I consider myself above average and a key distinction is not wanting to build complexity. Microservices, k8s, fancy languages, or integration into things like Dynamica CRM are all generally mistakes unless you have a very good reason for doing so. I also spent a lot of time optimising my workflow, which leverages build/test on change and large volumes of automations. Unit tests are also key.
- yupper32 4y ago
  I've had people on my team with these views and often their expectations need to be re-calibrated. They want to spend their time rewriting the codebase their way instead of being actually productive. Those people are not 10x engineers, despite them sometimes thinking they are. (Not saying that's you, I don't know you).
  - hsbauauvhabzb 4y ago
    I think that re-engineering code based needs to be a calculated decisions, but i also think that there’s a large amount of resume driven development too. There are places where there’s a need for k8s and similar, but largely that’s when you’re at google level scale. For the rest of us plebs, maybe leveraging simpler paas solutions or traditional mechanisms are more effective. Except CRM. If you’re building in CRM you’re just making a mess, no matter what the rationale is.
- IncRnd 4y ago
  You seem to be describing anything but the lowest common demoninator as unwanted complexity.
  - hsbauauvhabzb 4y ago
    Yes. Complexity is the root cause of many systemic issues in many projects I see. I see probably 2-3 medium applications every month. Either things are totally engineered or under-engineered (e.g., traditional php/aspx applications).
turtlebits 4y ago
Anyone can be a 10x engineer, if you don't write any specs or go through planning, ignore architecture/deployment/monitoring best practices. And uses a language / framework/ tech stack that only they are familiar with. Of course you'll royally screw over the rest of the company/team that has to productionalize, maintain your code + spaghetti of services after you leave.
- EduardoRT 4y ago
  That doesn't sound like a 10x developer at all, sounds like a bad developer that prioritizes dumping code, 10x developer would write docs, spend time planning the architecture and removing complexity from systems.
- mbrodersen 4y ago
  What you are describing is not a 10x developer.

by sdwr 4y ago

Mind elaborating on this? This is a fresh take for me. Are you saying a 10x dev writes code optimized for their own velocity, at the expense of accessibility/teamwork?

hsbauauvhabzb 4y ago

I consider myself above average and a key distinction is not wanting to build complexity. Microservices, k8s, fancy languages, or integration into things like Dynamica CRM are all generally mistakes unless you have a very good reason for doing so. I also spent a lot of time optimising my workflow, which leverages build/test on change and large volumes of automations. Unit tests are also key.

yupper32 4y ago
I've had people on my team with these views and often their expectations need to be re-calibrated. They want to spend their time rewriting the codebase their way instead of being actually productive. Those people are not 10x engineers, despite them sometimes thinking they are. (Not saying that's you, I don't know you).
- hsbauauvhabzb 4y ago
  I think that re-engineering code based needs to be a calculated decisions, but i also think that there’s a large amount of resume driven development too. There are places where there’s a need for k8s and similar, but largely that’s when you’re at google level scale. For the rest of us plebs, maybe leveraging simpler paas solutions or traditional mechanisms are more effective. Except CRM. If you’re building in CRM you’re just making a mess, no matter what the rationale is.
IncRnd 4y ago
You seem to be describing anything but the lowest common demoninator as unwanted complexity.
- hsbauauvhabzb 4y ago
  Yes. Complexity is the root cause of many systemic issues in many projects I see. I see probably 2-3 medium applications every month. Either things are totally engineered or under-engineered (e.g., traditional php/aspx applications).

turtlebits 4y ago

Anyone can be a 10x engineer, if you don't write any specs or go through planning, ignore architecture/deployment/monitoring best practices. And uses a language / framework/ tech stack that only they are familiar with. Of course you'll royally screw over the rest of the company/team that has to productionalize, maintain your code + spaghetti of services after you leave.

EduardoRT 4y ago
That doesn't sound like a 10x developer at all, sounds like a bad developer that prioritizes dumping code, 10x developer would write docs, spend time planning the architecture and removing complexity from systems.
mbrodersen 4y ago
What you are describing is not a 10x developer.