←back to thread

174 points Philpax | 3 comments | | HN request time: 0s | source
Show context
codingwagie ◴[] 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 ◴[] 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 ◴[] 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. csto12 ◴[] No.43721779[source]
I was pointing out that if you spent 2 weeks trying to find the solution but AI solved it within a day (you don’t specify how long the final solution by AI took), it sounds like those two weeks were not spent very well.

I would be interested in knowing what in those two weeks you couldn’t figure out, but AI could.

replies(1): >>43721952 #
2. codingwagie ◴[] No.43721952[source]
it was two weeks tossing around ideas in my head
replies(1): >>43722276 #
3. financypants ◴[] No.43722276[source]
idk why people here are laser focusing on "wow 2 weeks", I totally understand lightly thinking about an idea, motivations, feasibility, implementation, for a week or two