> I watch videogame streamers play games. Millions of people do. There will be authors who livestream the entire book-writing-process (just typing that out makes me want to launch one today). No one person will watch the entire process, but enough people will tune in here and there, and it’ll on be on YouTube
Ironically, I finally caught up on an online web series (though it's been adapted to a published book as well as audiobooks) and discovered the author does live stream their writing of unreleased chapters.
They're a bit too prolific to actually dig into their overall process, but you can watch them type for hours straight. It's awfully boring tbh since there's no interaction and they're understandably focused on their work.
~70 FTE Engineering team. We are shipping more features, especially features that previously would not have survived the cut to make it on the roadmap. Even though we are shipping more, our total amount of escaped bugs has not increased, so our escape rate has actually lowered. On top of that we are able to triage and fix escaped bugs more quickly now. And then of course there has been an uptick in internal tooling that makes the rest of the company more efficient, and we have been able to address tech debt at a higher rate than before.
I don't think this would have been possible without having solid engineering culture and processes in place before bringing in ai coding tools.
And I don't want to sugarcoat it, this hasn't been easy, requires continued discipline, and took well over a year to get good at. And we still have to continuously learn, experiment and adapt our training, tooling, and processes.
> There was probably a reason it was on the backlog (because it didn't really have value).
There are definitely things in the backlog with low value. We don't work those items, even if we could now. The additional bandwidth we have now goes to valuable features that drive revenue and retention metrics. The reason they were on the backlog were because we just didn't have the bandwidth to execute on them well and they were just somewhat less valuable than the critical path items on the roadmap.
I prefer Dan Shapiro's 5 level analogy (based on car autonomy levels) because it makes for a cleaner maturity model when discussing with people who are not as deeply immersed in the current state of the art. But there are some good overall insights in this piece, and there are enough breadcrumbs to lead to further exploration, which I appreciate. I think levels 3 and 4 should be collapsed, and the real magic starts to happen after combining 5 and 6; maybe they should be merged as well.
Car levels autonomy is fake. Everything including Level 3 is not a real autonomy it is hard rules + some reaction to the world, and everything above 3 is autonomy with just s slightly human security guardrails to attempt the real autonomy.
At this moment where we have human who just sit there before verify enough 9 after comas of error rates, the entire level conversation is dead. It's almost a binary state. Autonomous or not.
Similar happened with software levels. Even Level 2 was sci-fi 2 years ago, 1 year away from now anything bellow level 5 will be a joke except very regulated or billion users systems scale software.
In response maybe we should design TCPAclaw. It is specialized in honeypotting all of the random cold call spam, tracks down the source of unsolicited contacts; including registration state, legal contacts, and registered agent(s). It then drafts and sends a TCPA letter and waits for one of two things to happen: Either a $500-$1500 check arriving in your mailbox, or the demand deadline elapses. In case of demand deadline elapse, TCPAclaw files a small claims suit in the appropriate court of jurisdiction.
That's... not a bad idea. The downside is the bot would be doing a lot of these and false-positives would be... embarrassing (like a real investor outreach).
