gfysfm

6 ms·

1.
Don't build tools for AI agents(seangoedecke.com)
4 points by gfysfm 1d ago|2 comments
2.
Slow developer experience will bottleneck fast models(seangoedecke.com)
2 points by gfysfm 4d ago|1 comments
3.
Notes on Incidents(seangoedecke.com)
2 points by gfysfm 12d ago|0 comments
4.
"Radical responsibility" means treating people like tools(seangoedecke.com)
4 points by gfysfm 12d ago|1 comments
5.
Readers can't identify watermarked AI text(seangoedecke.com)
2 points by gfysfm 14d ago|0 comments
6.
How to Keep Thinking(seangoedecke.com)
3 points by gfysfm 20d ago|0 comments
7.
Guess which of these LLM outputs is watermarked(sgoedecke.github.io)
72 points by gfysfm 29d ago|85 comments
8.
Good writing is obvious, not original(seangoedecke.com)
3 points by gfysfm 29d ago|1 comments
9.
Help Peer(seangoedecke.com)
4 points by gfysfm 1mo ago|0 comments
10.
Blog about things you don't understand yet(seangoedecke.com)
169 points by gfysfm 1mo ago|49 comments
11.
Text AI watermarks will always be trivial to remove(seangoedecke.com)
4 points by gfysfm 1mo ago|1 comments
12.
What's so hard about continuous learning?(seangoedecke.com)
3 points by gfysfm 1mo ago|0 comments
13.
Anti-AI nostalgia and the cult of the past(seangoedecke.com)
3 points by gfysfm 2mo ago|0 comments
14.
Screwing Up(seangoedecke.com)
1 points by gfysfm 2mo ago|0 comments
15.
Blood in the Datacenter(seangoedecke.com)
8 points by gfysfm 2mo ago|0 comments
16.
I don't like the "staff engineer archetypes"(seangoedecke.com)
4 points by gfysfm 2mo ago|0 comments
17.
Screwing Up(seangoedecke.com)
4 points by gfysfm 4mo ago|0 comments
18.
SkiFreedle, a daily game version of SkiFree (1991)(skifreedle.com)
3 points by gfysfm 4mo ago|1 comments
19.
What's so hard about continuous learning?(seangoedecke.com)
3 points by gfysfm 7mo ago|0 comments
20.
We are in the "gentleman scientist" era of AI research(seangoedecke.com)
3 points by gfysfm 7mo ago|0 comments
21.
How does AI impact skill formation?(seangoedecke.com)
1 points by gfysfm 8mo ago|0 comments
22.
by gfysfm 9mo ago
This is really cool! It's interesting that you can "cheat" by knowing the historical situation in advance. But I guess there's no way around that - if the situations involved were hypothetical, it would be unsatisfying w
23.
Grok is enabling mass sexual harassment on Twitter(seangoedecke.com)
20 points by gfysfm 9mo ago|1 comments
24.
How good engineers write bad code at big companies(seangoedecke.com)
407 points by gfysfm 10mo ago|320 comments
25.
It's not surprising that 95% of AI enterprise projects fail(seangoedecke.com)
2 points by gfysfm 10mo ago|0 comments
26.
Solving the inference problem for open source AI projects with GitHub Models(github.blog)
1 points by gfysfm 1y ago|0 comments
27.
Scan and resolve fixed GitHub issues and PRs with AI(github.com)
1 points by gfysfm 1y ago|0 comments
28.
Show HN: OpenAI Codex for Free with GitHub Models(gist.github.com)
7 points by gfysfm 1y ago|0 comments
29.
The Illusion of "The Illusion of Thinking"(seangoedecke.com)
6 points by gfysfm 1y ago|1 comments
30.
by gfysfm 1y ago
Hi, I wrote the post! Also not a ML researcher, just an interested engineer, so I'm sure I got some things wrong. > MoE should be the better tradeoff for the local/single-user scenario since the downside of batching being harde

More ›