←back to thread

AGI Is Still 30 Years Away – Ege Erdil and Tamay Besiroglu

(www.dwarkesh.com)
174 points Philpax | 10 comments | 17 Apr 25 16:42 UTC | HN request time: 1.121s | source | bottom
Show context
codingwagie ◴[17 Apr 25 17:29 UTC] No.43719845[source]▶
I just used o3 to design a distributed scheduler that scales to 1M+ sxchedules a day. It was perfect, and did better than two weeks of thought around the best way to build this.
replies(8): >>43719906 #>>43720086 #>>43720092 #>>43721143 #>>43721297 #>>43722293 #>>43723047 #>>43727685 #
csto12 ◴[17 Apr 25 17:34 UTC] No.43719906[source]▶
You just asked it to design or implement?

If o3 can design it, that means it’s using open source schedulers as reference. Did you think about opening up a few open source projects to see how they were doing things in those two weeks you were designing?

replies(2): >>43720057 #>>43720965 #
codingwagie ◴[17 Apr 25 19:13 UTC] No.43720965[source]▶
why would I do that kind of research if it can identify the problem I am trying to solve, and spit out the exact solution. also, it was a rough implementation adapted to my exact tech stack
replies(5): >>43721294 #>>43721501 #>>43721779 #>>43721872 #>>43723076 #
1. margalabargala ◴[17 Apr 25 20:29 UTC] No.43721872[source]▶
Because as far as you know, the "rough implementation" only works in the happy path and there are really bad edge cases that you won't catch until they bite you, and then you won't even know where to look.

An open source project wouldn't have those issues (someone at least understands all the code, and most edge cases have likely been ironed out) plus then you get maintenance updates for free.

replies(1): >>43721946 #
2. codingwagie ◴[17 Apr 25 20:36 UTC] No.43721946[source]▶
ive got ten years at faang in distributed systems, I know a good solution when i see one. and o3 is bang on
replies(3): >>43722022 #>>43722522 #>>43722533 #
3. margalabargala ◴[17 Apr 25 20:42 UTC] No.43722022[source]▶
If you thought about it for two weeks beforehand and came up with nothing, I have trouble lending much credence to that.
replies(1): >>43723134 #
4. ◴[17 Apr 25 21:39 UTC] No.43722522[source]▶
5. lossolo ◴[17 Apr 25 21:40 UTC] No.43722533[source]▶
So 10 years at a FANG company, then it’s 15 years in backend at FANG, then 10 years in distributed systems, and then running interviews at some company for 5 years and rising capital as founder in NYC. Cool. Can you share that chat from o3?
replies(1): >>43722674 #
6. themanmaran ◴[17 Apr 25 21:58 UTC] No.43722674{3}[source]▶
How are those mutually exclusive statements? You can't imagine someone working on backend (focused on distributed systems) for 10-15 years at a FANG company. And also being in a position to interview new candidates?
replies(1): >>43722726 #
7. HAL3000 ◴[17 Apr 25 22:04 UTC] No.43722726{4}[source]▶
Who knows but have you read what OP wrote?

"I just used o3 to design a distributed scheduler that scales to 1M+ sxchedules a day. It was perfect, and did better than two weeks of thought around the best way to build this."

Anyone with 10 years in distributed systems at FAANG doesn’t need two weeks to design a distributed scheduler handling 1M+ schedules per day, that’s a solved problem in 2025 and basically a joke at that scale. That alone makes this person’s story questionable, and his comment history only adds to the doubt.

replies(1): >>43725426 #
8. qt31415926 ◴[17 Apr 25 23:01 UTC] No.43723134{3}[source]▶
the commenter never said they came up with nothing, they said o3 came up with something better.
9. thelambentonion ◴[18 Apr 25 05:59 UTC] No.43725426{5}[source]▶
> and his comment history only adds to the doubt

for others following along: the comment history is mostly talking about how software engineering is dead because AI is real this time with a few diversions to fixate on how overpriced university pedigrees are.

replies(1): >>43729098 #
10. codingwagie ◴[18 Apr 25 15:39 UTC] No.43729098{6}[source]▶
its not dead, its democratized