Jack Allen (@jackallenh) header
Jack Allen (@jackallenh) profile picture
Joined September 2013
Photo by Jack Allen (@jackallenh)Photo by Jack Allen (@jackallenh)Photo by Jack Allen (@jackallenh)Photo by Jack Allen (@jackallenh)Photo by Jack Allen (@jackallenh)Photo by Jack Allen (@jackallenh)Photo by Jack Allen (@jackallenh)Photo by Jack Allen (@jackallenh)Photo by Jack Allen (@jackallenh)Photo by Jack Allen (@jackallenh)
In recent weeks, when it came to tricky bugs (a memory leak, a routing issue, a sharding bug), Claude’s initial analysis was almost always 100% wrong. I had to give it multiple hypotheses, clues, ideas, suggestions for it to solve the bug. When asked “so, what did you learn?”
7
8
4
177
20,516
Jack Allen retweeted
i love pseudoscience aesthetics so much
5
8
1
106
11,590
This is quite the paper! It gave 25 AI agents motivations & memory, and put them in a simulated town. Not only did they engage in complex behavior (including throwing a Valentine’s Day party) but the actions were rated more human than humans roleplaying. arxiv.org/pdf/2304.03442.pdf
325
3,056
863
15,933
5,601,863
Just wrapped up a new chapter on how accidental complexity comes in two different shapes. The combination of these dimensions is what determines the relative ease of change when coding.
4
5
1
42
So now code review now means … system design? 😅 All that’s changed is a new ad ranker service is introduced into the mix. Wonder why he asked for screenshots of code for this lol. Would be interesting to read more scoops about what really happened in that room.
Just leaving Twitter HQ code review
11
10
1
148
Jack Allen retweeted
After nearly 25 years, I’m publishing the Distributed Computing Manifesto in its entirety, an internal document from the early days of Amazon that transformed the architecture of our e-commerce platform. allthingsdistributed.com/202…
55
936
79
3,807
The "Metastable Failures in the Wild" paper is still not out, but a good synopsis is up. https://nitter.gq/t.co/TWSQ8Yel9K Makes a complete joke of the concept of "root cause", because these are types of failures that persist after the "root cause" (initial trigger) has been removed!
OSDI program is up and it seems to get more and more ML/AI centric every year. ☹️ Still, some promising systems papers to look out for: 1. Metastable Failures in the Wild 2. Cancel Culture in Systems: An Empirical Study of Task Cancellation Patterns and Failures
1
13
1
65
Airbnb’s Journey To Post-Microservices (HINT: microservies didn't solve all the problems) medium.com/qe-unit/airbnbs-m…
12
502
43
2,675
How do you take a legacy system toward fast flow of change? @suksr takes us through an evolution using wholistic approaches including DDD, Wardley Mapping, and Team Topologies #QConLondon
3
9
3
42
Jack Allen retweeted
I'm doing some research on supporting Manager of Managers, hence forwards on #MoM Currently split into two different themes - 1) Similar, but moar (sic)! and 2) Very different
2
6
3
27
Here's a podcast with one of my favorite people, the very kind @suksr. We discuss Susanne's tools of choice: Warley Maps, #DDDesign, and @TeamTopologies. You'll also get a glimpse into her upcoming book! adddot.io/podcast/episode-8/
11
22
Jack Allen retweeted
Second recap post of 2021, work and some general musings on the engineering hierarchy of needs vickiboykis.com/2022/01/02/2…
Thinking about an idea I’m trying to tease out into a post, what needs to come together to make an engineering job enjoyable or fun. Anyone have links to pieces that talk about stuff like this?
2
3
17
I'm writing about credibility. If someone says, say, “root cause” or “100% reliability”, they instantly lose credibility with reliability people. What are the equivalents in other areas of software? What phrases make you assume someone doesn't know what they're talking about?
139
50
28
381
Jack Allen retweeted
Replying to @wgrosso @allenholub
There's no escape from the Queuing Theory. The longer the backlog, the longer the waiting time on average. To be honest with oneself and the customers, the organization must start to learn to say no slideshare.net/at2009qc/wast… thenewstack.io/mary-poppendi… via @mpoppendieck
1
8
1
25
Replying to @allenholub
@allenholub thought you would be interested reading piece 🙏🏻 newsletter.pragmaticengineer… value delivery > framework
1
4
21
Unfortunately there is still relatively little research on the antecedents of psychological safety. Here are a couple: Edmondson, A. (1999). Psychological safety and learning behavior in work teams.
1
3
25
Since time immemorial, when a CEO asks a PM at Product Review, “what do you need to 10X users/revenue?”, “what will make you go faster?”, etc the PM steadfastly responds “We need [N] more engineers”. The Eng Mgr nods approvingly. A story thread, with some hard truths to swallow:
147
1,073
427
5,614
There is a fallacy about how domain modelling works, and we need to talk about it. With software design, you're not just solving problems, you can reframe the problem itself. 🧵 /1
7
90
26
298
Avoid impactless work. When discussing required artifacts and outputs, don't be afraid to ask what they are for - you'll be surprised how often people will stop mid-sentence because they don't know what the purpose of the work is, beyond "we've always asked for X."
2
16
3
86