tonkkatonka

4 ms·

1.
Engineers grieve a job that no longer exists(leaddev.com)
3 points by tonkkatonka 29d ago|3 comments
2.
by tonkkatonka 29d ago
The best engineers don't want to be botsitters
3.
Engineers grieve a job that no longer exists(leaddev.com)
5 points by tonkkatonka 1mo ago|1 comments
4.
Every software company will become a dev tools company(thenewstack.io)
1 points by tonkkatonka 2mo ago|0 comments
5.
Shipping code without human verification(thenewstack.io)
1 points by tonkkatonka 2mo ago|2 comments
6.
by tonkkatonka 2mo ago
One approach could be the role of an automated verification engineer, a cross between a developer experience engineer and quality assurance.
7.
Do we even need a better GitHub?(aviator.co)
2 points by tonkkatonka 2mo ago|0 comments
8.
by tonkkatonka 2mo ago
Similar: https://www.aviator.co/blog/do-we-even-need-a-better-github/
9.
How do you go from junior to staff engineer when AI writes the code?(cio.com)
1 points by tonkkatonka 3mo ago|0 comments
10.
Enabling non-devs to contribute code at Slack(aviator.co)
1 points by tonkkatonka 3mo ago|0 comments
11.
How long before we stop reading the code?(thenewstack.io)
9 points by tonkkatonka 3mo ago|3 comments
12.
Do we even need a better GitHub?(aviator.co)
4 points by tonkkatonka 5mo ago|0 comments
13.
by tonkkatonka 5mo ago
Maybe. Humans just can't thoroughly review the amounts of code AI can produce. But the answer is not YOLO and just ship blindly whatever AI created. The answer is to move the human review/judgment upstream. You review specs. You r
14.
Tokenmaxxing and the search for AI metrics that matter(leaddev.com)
2 points by tonkkatonka 5mo ago|1 comments
15.
by tonkkatonka 5mo ago
Some engineering organizations are measuring AI output via tokens burned, some compare engineers to executive chefs, and some rely on self-reporting.
16.
I said code review was dead. Here's what I got wrong – and right(aviator.co)
1 points by tonkkatonka 6mo ago|1 comments
17.
by tonkkatonka 6mo ago
The response to my piece about killing the code review was loud. This is my attempt to address the comments.
18.
Stop throwing AI at developers and hoping for magic(leaddev.com)
3 points by tonkkatonka 7mo ago|0 comments
19.
What If Code Review Happened Before the Code Was Written?(aviator.co)
1 points by tonkkatonka 7mo ago|0 comments
20.
How to Kill the Code Review(latent.space)
19 points by tonkkatonka 7mo ago|5 comments
21.
by tonkkatonka 7mo ago
Human-written code died in 2025. Code reviews will die in 2026.
22.
To jump on the agent orchestration wagon or not?(aviator.co)
1 points by tonkkatonka 8mo ago|1 comments
23.
by tonkkatonka 8mo ago
What's working, what’s still vaporware, who should be paying attention, and what the real path forward looks like for teams that want to be ready when orchestration goes mainstream.
24.
AI and Developer Productivity: Insights from a 100k-Developer Stanford Study(youtube.com)
2 points by tonkkatonka 9mo ago|1 comments
25.
by tonkkatonka 9mo ago
Stanford researcher shares insights from large-scale studies on developer output, why early AI productivity claims were overstated, and what engineering leaders should (and shouldn’t) measure when rolling out AI across the software developm
26.
Why AI Coding Still Fails in Enterprise Teams(aviator.co)
1 points by tonkkatonka 9mo ago|1 comments
27.
by tonkkatonka 9mo ago
Four industry veterans — Kent Beck, Bryan Finster, Rahib Amin, and Punit Lad — shared their perspectives on how enterprises can adopt AI coding tools wisely.
28.
Throwing AI at Developers Won't Fix Their Problems(aviator.co)
2 points by tonkkatonka 1y ago|1 comments
29.
by tonkkatonka 1y ago
Systemic engineering bottlenecks won’t disappear by just throwing AI at them. You’ve got to fix the roadblocks to realize the full value of AI tools.
30.
AI Is Eating Developer Experience(aviator.co)
2 points by tonkkatonka 1y ago|3 comments

More ›