-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathnewsletters_2026-03-12.json
More file actions
147 lines (147 loc) · 6.59 KB
/
newsletters_2026-03-12.json
File metadata and controls
147 lines (147 loc) · 6.59 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
{
"scraped_date": "2026-03-12",
"source": "newsletters",
"feeds_checked": [
"simon_willison",
"sean_goedecke",
"rachel_by_the_bay",
"mitchell_hashimoto",
"matklad",
"hillel_wayne",
"paul_graham",
"experimental_history",
"anil_dash",
"pragmatic_engineer",
"leaddev",
"staffeng",
"engineering_managers",
"software_lead_weekly",
"steve_blank"
],
"total_articles": 244,
"relevant_count": 7,
"articles": [
{
"feed_id": "sean_goedecke",
"feed_name": "Sean Goedecke",
"title": "I don't know if my job will still exist in ten years",
"summary": "In 2021, being a good software engineer felt great. The world was full of software, with more companies arriving every year who needed to employ engineers to write their code and run their systems. I knew I was good at it, and I knew I could keep doing it for as long as I wanted to. The work I loved would not run out. In 2026, I’m not sure the software engineering industry will survive another decade. If it does, I’m certain it’s going to change far more than it did in the last two decades. Mayb",
"link": "https://seangoedecke.com/will-my-job-still-exist/",
"published": "2026-03-06T00:00:00+00:00",
"matched_keywords": [
"staff engineer",
"leverage",
"fewer engineers"
],
"relevance_score": 5,
"feed_focus": [
"large tech orgs",
"career growth",
"engineering culture"
]
},
{
"feed_id": "leaddev",
"feed_name": "LeadDev",
"title": "The staff+ playbook for derisking big decisions",
"summary": "Staff+ engineers need a broad understanding of how organizations operate and evolve. The post The staff+ playbook for derisking big decisions appeared first on LeadDev.",
"link": "https://leaddev.com/leadership/derisking-the-big-decisions-a-playbook-for-staff-engineers?utm_source=leaddev&utm_medium=RSS",
"published": "2026-03-11T09:23:00+00:00",
"matched_keywords": [
"leadership"
],
"relevance_score": 3,
"feed_focus": [
"engineering management",
"org maturity",
"leadership"
]
},
{
"feed_id": "leaddev",
"feed_name": "LeadDev",
"title": "AI adoption has to be driven from the top",
"summary": "Not by mandate, but clear leadership and guidance over why AI is being adopted. The post AI adoption has to be driven from the top appeared first on LeadDev.",
"link": "https://leaddev.com/ai/ai-adoption-has-to-be-driven-from-the-top?utm_source=leaddev&utm_medium=RSS",
"published": "2026-03-09T06:59:00+00:00",
"matched_keywords": [
"leadership"
],
"relevance_score": 3,
"feed_focus": [
"engineering management",
"org maturity",
"leadership"
]
},
{
"feed_id": "simon_willison",
"feed_name": "Simon Willison's Weblog",
"title": "AI should help us produce better code",
"summary": "Agentic Engineering Patterns > Many developers worry that outsourcing their code to AI tools will result in a drop in quality, producing bad code that's churned out fast enough that decision makers are willing to overlook its flaws. If adopting coding agents demonstrably reduces the quality of the code and features you are producing, you should address that problem directly: figure out which aspects of your process are hurting the quality of your output and fix them. Shipping worse code with ",
"link": "https://simonwillison.net/guides/agentic-engineering-patterns/better-code/#atom-everything",
"published": "2026-03-10T22:25:09+00:00",
"matched_keywords": [
"technical debt",
"trade-offs"
],
"relevance_score": 2,
"feed_focus": [
"ai leverage",
"engineering strategy",
"platform thinking"
]
},
{
"feed_id": "simon_willison",
"feed_name": "Simon Willison's Weblog",
"title": "Quoting Ally Piechowski",
"summary": "Questions for developers: “What’s the one area you’re afraid to touch?” “When’s the last time you deployed on a Friday?” “What broke in production in the last 90 days that wasn’t caught by tests?” Questions for the CTO/EM: “What feature has been blocked for over a year?” “Do you have real-time error visibility right now?” “What was the last feature that took significantly longer than estimated?” Questions for business stakeholders: “Are there features that got quietly turned off and never came b",
"link": "https://simonwillison.net/2026/Mar/6/ally-piechowski/#atom-everything",
"published": "2026-03-06T21:58:33+00:00",
"matched_keywords": [
"visibility"
],
"relevance_score": 1,
"feed_focus": [
"ai leverage",
"engineering strategy",
"platform thinking"
]
},
{
"feed_id": "simon_willison",
"feed_name": "Simon Willison's Weblog",
"title": "Can coding agents relicense open source through a “clean room” implementation of code?",
"summary": "Over the past few months it's become clear that coding agents are extraordinarily good at building a weird version of a \"clean room\" implementation of code. The most famous version of this pattern is when Compaq created a clean-room clone of the IBM BIOS back in 1982. They had one team of engineers reverse engineer the BIOS to create a specification, then handed that specification to another team to build a new ground-up version. This process used to take multiple teams of engineers weeks or mon",
"link": "https://simonwillison.net/2026/Mar/5/chardet/#atom-everything",
"published": "2026-03-05T16:49:33+00:00",
"matched_keywords": [
"architecture"
],
"relevance_score": 1,
"feed_focus": [
"ai leverage",
"engineering strategy",
"platform thinking"
]
},
{
"feed_id": "pragmatic_engineer",
"feed_name": "The Pragmatic Engineer",
"title": "How Uber uses AI for development: inside look",
"summary": "How Uber built Minion, Shepherd, uReview, and other internal agentic AI tools. Also, new challenges in rolling out AI tools, like more platform investment and growing concern about token costs",
"link": "https://newsletter.pragmaticengineer.com/p/how-uber-uses-ai-for-development",
"published": "2026-03-10T19:23:06+00:00",
"matched_keywords": [
"platform"
],
"relevance_score": 1,
"feed_focus": [
"engineering leadership",
"career growth",
"org strategy"
]
}
]
}