Hey there! In my latest blog post, I dive into some fascinating reads I’ve come across. I explore whether AGI is more of a systems engineering problem than a model training one. I also question the infamous ’23 minutes and 15 seconds’ interruption myth, and share insights on building a coding agent in just 300 lines of code. Join me as I uncover these intriguing topics!
- [no title]:
- Away from Gmail | etcetera:
- The Management Skill Nobody Talks About:
- AGI is an Engineering Problem: LLM models are plateauing, but true AGI isn’t about scaling the next breakthrough model—it’s about engineering the right context, memory, and workflow systems. AGI is fundamentally a systems engineering problem, not a model training problem.
- Interruptions cost 23 minutes 15 seconds, right?: You’ve likely read lots of blog posts stating that it takes 23 minutes and 15 seconds to get back to work after an interruption, context switch, or meeting. Thus, “do you have five minutes” ends up not only costing those few minutes, but instead about half an hour. But where does that number come from?
- how to build a coding agent: free workshop: It’s not that hard to build a coding agent. 300 lines of code running in a loop with LLM tokens. You just keep throwing tokens at the loop, and then you’ve got yourself an agent.