Here's a topic for discussion. There was a recent twitter thread about the "10x
Engineer". Does that person exist? Would you want to work with them? Is there a time and place for such a
person?
Founders if you ever come across this rare breed of engineers, grab them. If you have a 10x engineer as part of
your first few engineers, you increase the odds of your startup success significantly.
OK, here is a tough question.
How do you spot a 10x engineer?
Here's some even tougher questions. Are they really that good? Do they make everyone better, or do they get things done
and leave a trail of barely working code and burned our engineers supporting their code behind them? Do you really want
someone like that on your team?
I mentioned Conway's law last week, and that got me to doing some semi-random
link following. I ran across a couple of articles on structuring the development of large systems so as to
create
bounded contexts and limit cognitive
load and organizational
refactoring to reducing organizational debt.
Learning from your mistakes is important and key to building stable efficient systems, As good as that is, learning from others mistakes is even better. With that in mind, here's a list of Kubernetes mistake stories we can all learn from.
Not to kick off a religious war, but I like vi/vim since it's what my fingers learned lo those many moons ago, but I ran across this list of vim tip and tricks and I learned something new. Enjoy/discuss at leisure.
Here's a topic for discussion. Conway's
Law says that organizations which design systems ... are constrained to
produce designs which are copies of the communication structures of these organizations.
There's lots of evidence, anecdotal and structured, that this is in fact the case. Knowing that, how might we
approach our infrastructure design, both the internal interfaces and the customer facing ones?
