12 "AI Programming 2.0" Case Study: The AI Can't Be Idle at Home Either. I started 3 tasks before leaving this morning; let's look at the results first. The first task ran from after 9:00 AM until 1:30 PM; the AI worked continuously for 4.5 hours on its own. Of course, I was at work during this time, but my AI was not idle at home. It worked all morning, without even taking a break for lunch. Looking at the commit frequency, it submitted 27 commits in 4.5 hours. The second task started around 10:00 AM and ran until 10:30 AM; at that time, I was in Beijing, just getting off the subway. The third task also started around 10:00
12 "AI Programming 2.0" Case Study: The AI Can't Be Idle at Home Either I started 3 tasks before leaving this morning; let's look at the results first. The first task ran from after 9:00 AM until 1:30 PM; the AI worked continuously for 4.5 hours on its own. Of course, I was at work during this time, but my AI was not idle at home. It worked all morning, without even taking a break for lunch. Looking at the commit frequency, it submitted 27 commits in 4.5 hours. The second task started around 10:00 AM and ran until 10:30 AM; at that time, I was in Beijing, just getting off the subway. The third task also started around 10:00 AM and ran until 10:30 AM; same as above. It successfully burned through my $60 quota. In fact, my AI at home finished spending it by 2:30 PM. In other words, for the first task, the AI actually worked from 9:00 AM to 2:30 PM, a total of 5.5 hours, and it only stopped because it ran out of toke...
No comments yet. Be the first to share your thoughts.