jakevoytko
Joined 17 years ago
Joined 17 years ago
The biggest pocket of skilled holdouts I've noticed are in more artisan spaces where the craft of coding is part of the art. Things like old-school indie game developers where they're still sweating the assembly output and clock cycles.
It just doesn’t provide an AI overview for me on a basic search.
I find it extremely unlikely that I'd be able to sell it since its two main competitors are (1) literally free to use and has been polished for 16 years, and (2) a best-in-class native application that has been the lingua franca of business writing for over 40 years
I've talked to a lawyer about how they handle this. They do indeed double-check everything, since it'd be embarrassing (or worse) to send hallucinated statements to opposing council or to the court. They still find the assembly a huge time saver
But based on stories in the news on the subject, not everyone has this same level of diligence
If you do something 100 times a day against a four-nines service, you can reasonably expect that everything will succeed.
If you do something 10,000 times a day against a two-nines service, you can expect to hit a substantial number of errors during that day, or even have long periods where your work cannot happen at all.
People aren't frustrated with Github because Github has 98% uptime or whatever the specific number is. They're frustrated because it regularly interferes with their ability to work. The 98% number is just a concise way to say it.
The last time I signed up for an Instagram account (2016) it got immediately flagged as a bot account. I think I was supposed to appeal it to have it reinstanted, but why bother if this is how badly they treat users?
Can you imagine going to work as Instagram's web developer, spending your day finding new ways that the app accidentally works and disabling them?
I used to work on the Google Docs team, so I basically did an 8-hour Q/A with Sol spanning like 400 questions. Did my best to reach back 10 years into my memories to see how things were implemented, and discussing architecture and tradeoffs. Then went through 5 ChatGPT resets implementing it on Astra to get a feel for the model.
I have a long way to go. But I'm writing my first post on it this week, and then I'll do a writeup of the editor project.
As a side project, I'm doing an experimental task now (having Astra implement my own personal Google Docs clone, OT and everything, for my blog), and it feels more capable than Fable but needs to be watched closer than Fable. It is obsessed with verification and evidence to the point that I've needed to make some absolute rules to stop it from repeatedly e.g. making unit tests with 10,000 test cases with 5+ hours of runtime
For well-defined coding tasks, I'd default to either Luna or Sonnet, or hell, just writing it by hand.
Unlike the vanilla read of the OpenAI press release, it is much more unfiltered and outlines some particularly aggressive behavior by specific OpenAI employees
Ex-Google, ex-Etsy
Writing: https://www.bitlog.com, https://www.clientserver.dev Email: [email protected] Twitter: @jakevoytko