what to talk about in 1:1s (permalink: wizardzines.com/comics/1-1s/)

I’d love to read a book called “It Depends” which details a dozen or so big historic decisions, taking a variety of contexts into account, discussing viable alternatives that were on the table, and then why the final decision was made the way it was.

launching things is scary but letting ideas live in your head rent-free is scarier

What problem did your current or former team solve in-house that you wish had been outsourced to a third-party solution instead? e.g.: you manage file upload and storage and wish you'd used S3

John Cutler A smaller company I as working with introduced a design system based on atomic and I took the chance to encourage designers to pair up with engineers armed with a A4 whiteboard in hand. Design cycle time went from 7 days to a few minutes.

What’s the next ‘Agile’? If I look at the long historical arc of people who care about making work better for all parties, it’s The Maintainers and their Maintainer Movement. It’s a smart take on #lean with a rapidly growing community around software, infrastructure & workforce

Seven incredibly non-intuitive things about growing your career, a thread 👇

George Bernard Shaw said: “The single biggest problem with communication is the illusion that it has taken place” Possibly the most important communication lesson, ever.

Pull Requests has to be the most misguided engineering practice I’ve seen in my career. It produces the worst engineering process with horrible incentives.

Your ability to ship swiftly and reliably is maybe 20% a function of your personal knowledge of algorithms and data structures, 80% an inheritance from the sociotechnical systems around you.

1/ The first 18 months of a startup: After starting my 2nd company in 2019, I decided I would write down useful lessons I learned or re-learned along the way. Some were hard-earned & others required steady focus. A thread that I hope may help other founders starting out 👇

people really do leave their jobs over build times. i am not making this up. the impact your deploy pipeline has on developer productivity and happiness is HARDCORE.

One of the (many) great things from the Marqeta S-1, is the visibility into transaction economics 🥰 80bp for the issuer (e.g. Square, DoorDash) 25bp for the card network 20bp for Marqeta 3bp for the partner bank 😂 Tells you all you need to know :)

I'm back from a week at my mom's house and now I'm getting ads for her toothpaste brand, the brand I've been putting in my mouth for a week. We never talked about this brand or googled it or anything like that. As a privacy tech worker, let me explain why this is happening. 🧵

Three ways to have a startup idea: something you want, something you’ve directly experienced others needing, something you’ve invented through analytic thought. They are listed in order of increasing risk.

Thinking of starting a venture fund called Emergency Scaling Team. Once you product hits an inflection point/goes viral, we come in for 2 weeks & eliminate existential risk: rearchitect your servers, audit your security, craft PR messaging, identify immediate legal risks, etc.

"In general, you should aim to maximize collaboration within teams, and minimize collaboration between teams." 🎯bingo🎯 rubick.com/how-to-build-s…

My peoples, the time has come for a MEGATHREAD. In 40 tweets I will explain another 40 concepts you should know. Strap in. Here we go:

I see product teams (esp. Scrum) build product when their feedback loop is the same size as their sprint. As a result, they only find out whether they delivered value at the start of the next sprint. And if they didn't, now they're one sprint behind the roadmap. Oops! 1/4