If I'm starting a company:
- No Outlook or Word.
- No one will be in meetings more than 50% of their time, even the execs.
- Day job will take half of your time, the other will be inventing things.
- No heavy planning, we will instead build prototypes and write one-pagers.
- Maintenance is harder than launching new products.
- Reliability and security are the #1 job.
- It's ok to specialize in operations.
- You're empowered to initiate instead of being stuck in an approval queue for years.
- It's ok to fail, we can only succeed once in a while.
- Freedom to move across teams.
- Freedom to move across ladders based on work.
- People are the real asset. The company's capabilities are only a representation of its people.
- Leaders' job is to protect individuals from internal and external distractions.
- At least, 1:1 ratio between engineering and senior management. Each manager is matched with at least 1 engineer at their level, including the VPs.
- Execs get technical advisors each.
- Engineers are the final arbiters unless the dispute is purely a business decision.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
OpenTelemetry metrics instrumentation library concepts may be leaking to standard libraries, but these abstractions are often too abstract from what developers want to code against.
There are various ideas in OpenTelemetry that are powerful, but not necessarily interests developers. Simple is always harder than complex.
I'm thinking how anything like dumping events with numeric values to set aggregations out of the process and export metrics works okish until you are a mega large tech corp.
When I was a child, I had no idea speed of the light will be a daily matter for me personally. I never thought speed of the light will be one of the biggest limitations I will daily have to think about.
And here is the other part... I had no clue that I'd find the speed of the light to be actually very slow even for earthbound problems. There are times I'm thinking an advanced civilization can't survive with such a limitation.
When we are envisioning about the existence of type II/III civilizations, given the inherit latency, something doesn't really add up. With such a limitation, civilizations should more likely to distributed, branch out and evolve differently.
People don't understand that it's NOT in the evolution path in the majority of the tech companies to become tech unicorns. Think about Netflix. You need a substantially senior engineering staff to do what they are doing. Even if you can hire, your org structure may fail.
In the last 5 years, by working at two public clouds, I constantly felt like going backwards in time in terms of "the edginess" of the projects I'm working on. We want to meet the majority of tech where they are.
We have many opportunities to go beyond where we are but it doesn't produce results and causes a type of burnout due to lack of mass adoption & existential crisis. It's a sometimes a challenge to balance to keep inventing and ensure what we invent is not alienating the industry.
I have the scars of being a person who carried herself from place to place while still trying to be fruitful and contribute to the society. If you are going to be offended by my voice, I don't know how I can help you.
When I was watching a 9/11 documentary, something got stuck with me. One of the survivors said the trauma they went through will never heal, it's now a part of their identity. That's when I realized that a scar can become a part of your identity rather than a part of your past.
I will never understand people who think mocking disabilities is criticism and I should welcome it.
You have to draw a line or you normalize the behavior. My job is not to make awful people happy. My job is to protect my community from them.
And my humble attempt in protecting my community is why I decided to turn off my mentions. I read tens of notifications every day where people I know are being subject to awful comments from strangers.
Hello 👋 I work on distributed for a living. I worked for the biggest distributed tracing systems. Some of the distributed tracing you see and use could be my work. You don't have to explain me basics of distributed tracing.
Distributed tracing is a nuanced topic. I don't expect people to have consensus on very nuanced subjects but please do your due diligence before engaging people online and see where they are coming from.
Fun fact: When I was working on messaging systems that involved a large number of services, debugging was tough. One night I saw myself in a dream as one of the messages taking notes about its path. I wanted to build a collection system similar to distributed tracing backends.