wj
Joined 16 years ago
Joined 16 years ago
Once you are inserting models into non-creative (and software development is creative work) it is imperative to start creating your own small evals. Not just to check how different models perform in that equation, but to catch model drift over time.
I anticipate that the harness (and memory) will evolve far more outside of engineering. Muse/Dots are an example of that.
I've been writing about this thesis for the past year or so and here is a bit of a summary of where I think it is going: https://zero2data.substack.com/p/the-future-of-consumer-ai
Also, as tech companies grow, a significant portion of the dev body count is for internal tooling. I was always flabbergasted at Twitter's headcount growth back in the day when it seemed like the only innovation increasing the number of characters in a tweet.
Right now we are in a weird spot where a lot of people are flailing around inside corporate America trying to figure out how to leverage AI. Few have enough vision to see what the companies of the future will look like and work towards that.
1. There is one-time work (development, personal assistant) where the input and output are net new. There is also back office work (billing, FP&A, questions about data) that is quite repetitive--working within existing datasets.
2. Back office work exists within SaaS products all of which are including AI within their platforms. Those SaaS products are often integrated with each other.
3. Business logic needs to be transferred between systems in order for each SaaS AI to be accurate. (Asking a Salesforce AI and a Xero AI "What is our revenue?" may get you different answers if either system has custom logic that defines any input to that question differently.)
Based on this, I believe that the optimal path forward for back office work is:
1. Centralize agents (business logic) across an organization
2. Decouple agents from orchestration
Agents that exist at the end of an API call--which can be from a SaaS, Airflow, vibe-coded app, or model harness--are a better answer than platform specific AI. They provide a centralized repository for business logic while reducing vendor reliance (and lock in). Additionally, you get better observability and auditabilty.
Sleeper Service is the result of this thinking--an enterprise AI framework.
Larger write up of my thought process behind Sleeper Service here: https://zero2data.substack.com/p/agents-as-a-service
https://www.startuplevelup.com/corporations-as-an-api/
What I think is missing is the lineage of an agent's identity. A public key maybe?
When most people are consuming _their_ news (as opposed to _the_ news) in the form of a thumbnail in an algorithmic social media feed, those copy errors matter less.
Honest question. There is a line in the sand somewhere apparently.
Train ride videos on YouTube scratch some of the same itch.
I have the Smokey Mountain which is amazing at holding heat but a total PIA to clean. Have one of their gas grills as well on a built in line, and it is fairly high quality also.
Nothing tops the kettle though.
I am not anticipating people self identifying slop.
A feature I would like on LinkedIn would be a 100% verified human content flag for users. LinkedIn can then do the scans and flip that to false for any users it catches posting AI assisted content. Let me filter that out of the feed.
If we don’t do something to maintain some standard of discourse, we lose intellectually and as a piece of our humanity.
LinkedIn is the only social media I use and it is on thin ice.