jordz
That being said it’s much easier at the moment to continue to use the frontier providers for most general tasks, that is the argument I’ve heard.
For creating these types of fine tuned local models, on constrained hardware for inference, I do think this is the way to go for specific tasks too!
I use these models for coding, but also a lot of product, commercial, financial and architectural work where I’m trying to develop something half-formed. 4.6 was unusually good at understanding what I was trying to get at, playing it back cleanly, getting the nuance, and extending it without bastardising it as the conversation was drawn out.
It could make useful connections without constantly trying to manufacture an insight.
5.6 Sol is genuinely excellent at the creative part, and in some cases better than 4.6. My issue is convergence to get to a point, a final point. As you try to distil an idea, it often invents new terminology for concepts you’ve already established but its so subtle you have to really keep track of it. The vocabulary and idea tree keep expanding when what you actually want is to collapse everything down to the few things that matter.
Opus 5 has the same problem for me that barrkel said, the prose is often so elliptical and I just want it to tell me it and get to the point than making me dance around what its trying to tell me.
I don’t think 4.6 was necessarily the most capable model (compared to Fable) for long horizon task delivery, and Opus 5 is much more Fable like, it's fiercely determined to get through the task list .
4.6 just felt unusually well calibrated to my way of collaborating and its ability to understand, extend and then compress my thinking without constantly imposing some random walk.
There are several challenges with this, safety, thermal runaway, and life cycle of the asset which has a limited amount of cycles.
Also the architecture of the system for the AC inverters and the DC side can come from very different places in the supply chain and aren’t as vertically integrated leaving you in a position where you can’t actually make this work without compromising something in the supply chain. That being said we are talking about a LOT of energy in these systems and to dissipate that much heat you’d need a load bank.
Thank you for sharing!
Not to the end customer anyway. To organizations and developers building on top of the APIs...
Completely against this idea though its a shame its not... "Get paid for hosting a network using the devices you purchase from us"*
Lastly, it is a cost albeit negligible to the end user who installs the device (power, bandwidth, etc).
*I know it wouldn't amount to anything but its a interesting way to think about it.
Having said this, I don't know what this product does from the website.
We pay ~$80 a month for 2 users to a financial planning application that integrates with our accounts (Xero) and it works well. Our revenue is 7 digits annually.
As a start-up founder, I appreciate what you're trying to do with your model but I kind of like, you know, just knowing the fixed costs regardless of our revenue.
Edit: Or rather should I say it’s relative... (lol?)
Principles by Ray Dalio - I found this really motivating to ensure our business sticks to and has a set of principles that evolve based on mistakes made (sounds obvious).
Hard Thing About Hard Things by Ben Horowitz - I loved listening to this (audible) because being a CEO can be lonely and hearing other peoples thoughts and advice based on their experience (that you can relate to) is really uplifting.
2018 has been a great year for us and I do think these books have helped me get through the roller coaster that is building a technology startup.