Having a big tech job is: - Being up to date on what’s the latest recommended path - Being up to date on what’s coming next - Being up to date on what’s going to get deprecated - Being up to date on how to slowly migrate between all these states without breaking anyone - Being up

for those of you interested in business positioning stuff here's how we think about things at sst: we are in the game of venture scale and to be in this game you need to be making asymmetric bets your positioning has to be counter to the market, so that if you are right, you

I talked to a ton of people lately about burnout. One shared experience stood out… People often mentioned signing up to do the impossible at a personal cost, then not being recongized by their leadership for delivering even though the earlier situation.

Burnout happens when there is no progress. Burnout also happens when you have no visibility into how dots will connect in the future. Burnout is about not being able to close the loop after putting a ton of effort and not seeing enough results.

the person that gets hyped on something, tries it everywhere, eventually concludes it's maybe not so great vs the person who said it's not so great at the beginning replay person 1 over the years and they crush person 2

I don’t know if leadership at tech companies understands how clean and well structured code attracts the best engineers, and a lack of it makes you lose anyone who is good regardless of the potential of the product.

LLMs attracted way too people who don't understand the basics of building systems with non-deterministic components to machine learning.

there’s been an entire class of companies that have destroyed the reputation of certain technologies by selling the idea “you don’t need to learn anything to ship” saw it happen with nosql happening with serverless now

Trying to convert a high performing software engineer into a manager against their personal wish so that they can grow faster must be the biggest crime.

there is no escape from software complexity, you just get to choose the place where it happens anyone that tells you otherwise is trying to sell you something

Talked with a founder who shared a low during their career: when they were a TML with 20 reports, expected to produce the output of a senior engineer (plus lead the team) at the same time. This doesn't get old:

This is the flowchart of how slack decides to send a notification. It is an excellent example of why a simple feature may take much longer. This might also explain why people don’t get notifications or clear the red dots sometimes. Img source: slack eng blog

We really pulled off something awesome yesterday.

Packed room for Stefan’s talk! #BBDescape2022

Picking up on Kelsey Hightower's idea to minimize your digital footprint. Try: docker run soxoj/maigret:latest <your-nickname> Thank me later.

Scheduling your team at 100% capacity is a great way to ensure that nothing will be delivered on time.

Testing microservice-based systems is hard 😢 With that said, software testing in general is challenging, but to paraphrase the late great B.I.G.: "mo' services, mo' problems" 💰 Here are some key references and thinking points 🧵 👇

the key to becoming a senior engineer in two years is to compress 10 years of failure into 2 years without getting fired

Where did you Go? What did you C? How did you React? Did Java good time?

Why did we stop napping after kindergarten? What a terrible lapse in societal judgment.