Share this page!

Enter URL or ID to Unroll

You can paste full URL like: https://x.com/threadreaderapp/status/1644127596119195649
or just the ID like: 1644127596119195649

How to get URL link on X (Twitter) App

  1. On the Twitter thread, click on or icon on the bottom
  2. Click again on or Share Via icon
  3. Click on Copy Link to Tweet
  4. Paste it above and click "Unroll Thread"!
  5. More info at Twitter Help
Charity Majors Profile picture
@mipsytipsy
Aug 11, 2019 • 3 tweets • 1 min read • Read on X
You must read this entire thread by @isotopp, where he describes the kind of real time explorability, testing and experimenting in prod you can do with a mature event driven stack (at booking.com).
Do you have a production system architecture that sounds like this? We are both interested in evangelizing it more widely, and actively looking for co-conspirators. DMs are open.
Given how powerful these event systems are, it seems odd that there aren't more of them. Getting to experiment non destructively in real time seems like it should be a key business differentiator for lots and lots of tech companies.

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with Charity Majors

Charity Majors Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @mipsytipsy

Charity Majors Profile picture
Jun 25
Well, I for one am not past this bullshit by now. ☺️ EMs who do some hands on engineering are better EMs.

Forbidding EMs from touching code at all is almost as silly and counterproductive as telling EMs that writing and shipping code is a core function of their role.
I say "almost" because if I had to choose one or the other, I would choose the clarity of "EMs responsible for team outcomes, SWEs responsible for technical outcomes" over the muddle of holding EMs responsible for everything and splitting their focus between people and code.
But I don't have to choose! EMs who keep a hand in the code are better EMs. They have more empathy and understanding for their team. They are better equipped to evaluate their engineers, they have more credibility and context. Everyone wins.
Read 5 tweets
Charity Majors Profile picture
Jun 10
I have a new piece up. It's a bit of a rant, even for me, so buckle in.

A lot of "thought leaders" have been making their mortgages lately off of bits on how AI is going to replace software engineers, particularly entry-level engineers.

stackoverflow.blog/2024/06/10/gen…
This is a dumb idea. It bespeaks a wealth of misunderstanding about what it means to be an engineer and write code, and what is valuable and hard about software systems.

But even really dumb, damaging ideas can weasel into people's heads if you repeat them blindly enough times.
Generative AI has made it easier than ever to generate lots of code. @kentquirk says it's "like a junior engineer who types really fast". 🤣

But writing code has always been the easiest part of software engineering -- *always*. And it's getting easier by the day.
Read 15 tweets
Charity Majors Profile picture
Apr 28
In 2023 we saw several rounds of quality conversation around engineering productivity, thanks to McKinsey, @GergelyOrosz and @KentBeck and others.

It moved the industry forwards. 🙌 But it also felt fairly inside baseball to me. Deeply technical, lots of metrics.
It felt, to me, like those participating were stepping very cautiously around a few of the third rails Jaana just tripped over. (💜)

"Work-life balance"
"Working hard vs working smart"
"Meritocracy"

The intersection of company tech cultures and expectations and performance.
These are hard, complicated topics, and there are some very good reasons for speaking carefully. People can pick up a sentence and run in the wrong direction with it, and do a lot of damage.

I have abandoned god only knows how many drafts on this topic, for that reason.
Read 26 tweets
Charity Majors Profile picture
Apr 22
The question is, how can you interview and screen for engineers who care about the business and want to help build it, engineers who respect sales, marketing and other functions as their peers and equals?

It's a great question!! I have ideas, but would love to hear from others.
I said "question", but there are actually two: 1) how to hire engineers who are motivated by solving business problems and 2) aren't engineering supremacists.

They are not *unrelated*, but they are different things.charity.wtf/2022/01/20/how…
Some things you can ask to tease out these attitudes are,

* when was the last time you paired with someone outside engineering? Outside R&D?

* what did you learn? How did it change your perspective or the way you do your job, or did it?
Read 12 tweets
Charity Majors Profile picture
Apr 11
Say you want to modernize your org and introduce progressive deploys, feature flags, switch o11y vendors, etc. You could:

* roll each change out, one at a time
* change all at once, Big Bang style, migrating one service at a time

Has the Big Bang style EVER worked? For anyone?
I can think of lots of examples of engineering orgs who *tried* the Big Bang style, but got wedged halfway through, or 20% of the way through.

I can think of lots of examples of orgs who are successfully bringing up *new* services on a new stack.
I can't think of any examples of folks who have successfully migrated *off* an old stack, tool chain, and workflow.

Surely they exist. How did they do it, and what do they credit their success to? I would love to hear from y'all!
Read 12 tweets
Charity Majors Profile picture
Mar 22
Ooooohhh boy, this is a terrific question. I have written two closely related pieces,

* for engineers interviewing at a new company, on how to sniff out bad management culture:

* how to tell if the co is rotten on the inside: charity.wtf/2021/02/19/que…
charity.wtf/2022/01/29/how…
But both of those were written from the perspective of the engineer/interviewee, not the interviewer. The dynamic is different, for sure. 🤔

I would probably start by asking them why they became a manager, why they enjoy the job (if they do). (Softballs)
* what was the most demoralizing week of your management career to date, and why? What would it take for you to give up management entirely?

* I would probe their familiarity with our tech stack, and ask what they do to stay sharp and up to date technically.
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

Send Email!

:(