HackerTrans
TopNewTrendsCommentsPastAskShowJobs

tonkkatonka

344 karmajoined 3 jaar geleden

Submissions

Enabling non-devs to contribute code at Slack

aviator.co
1 points·by tonkkatonka·5 dagen geleden·0 comments

How long before we stop reading the code?

thenewstack.io
9 points·by tonkkatonka·18 dagen geleden·3 comments

Do we even need a better GitHub?

aviator.co
4 points·by tonkkatonka·2 maanden geleden·0 comments

Tokenmaxxing and the search for AI metrics that matter

leaddev.com
2 points·by tonkkatonka·3 maanden geleden·1 comments

I said code review was dead. Here's what I got wrong – and right

aviator.co
1 points·by tonkkatonka·4 maanden geleden·1 comments

Stop throwing AI at developers and hoping for magic

leaddev.com
3 points·by tonkkatonka·4 maanden geleden·0 comments

What If Code Review Happened Before the Code Was Written?

aviator.co
1 points·by tonkkatonka·4 maanden geleden·0 comments

How to Kill the Code Review

latent.space
19 points·by tonkkatonka·4 maanden geleden·5 comments

To jump on the agent orchestration wagon or not?

aviator.co
1 points·by tonkkatonka·5 maanden geleden·1 comments

AI and Developer Productivity: Insights from a 100k-Developer Stanford Study

youtube.com
2 points·by tonkkatonka·6 maanden geleden·1 comments

Why AI Coding Still Fails in Enterprise Teams

aviator.co
1 points·by tonkkatonka·6 maanden geleden·1 comments

comments

tonkkatonka
·2 maanden geleden·discuss
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 review the steps. You review the verification rules. You review the contract the code must fulfill.

https://www.latent.space/p/reviews-dead
tonkkatonka
·3 maanden geleden·discuss
Some engineering organizations are measuring AI output via tokens burned, some compare engineers to executive chefs, and some rely on self-reporting.
tonkkatonka
·4 maanden geleden·discuss
The response to my piece about killing the code review was loud. This is my attempt to address the comments.
tonkkatonka
·4 maanden geleden·discuss
[dead]
tonkkatonka
·4 maanden geleden·discuss
Human-written code died in 2025. Code reviews will die in 2026.
tonkkatonka
·5 maanden geleden·discuss
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.
tonkkatonka
·6 maanden geleden·discuss
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 development lifecycle.
tonkkatonka
·6 maanden geleden·discuss
Four industry veterans — Kent Beck, Bryan Finster, Rahib Amin, and Punit Lad — shared their perspectives on how enterprises can adopt AI coding tools wisely.