ByteCaleb

Connect anything (even Nanobanana) to your Claude/ChatGPT/Slack with

[ByteCaleb @bytecaleb]

I THOUGHT IT WAS JUST ME

[Myk is Walking Backwards @mykola]

me, begging, crying, on my knees: "Please just use plain english, I don't understand what you're saying."

Claude: "The right fix, and the book's lesson applies: the tutorial rotted as a front door because a front door full of claims always rots. So the new root holds only what's timeless — the thesis and three doors — and every claim lives behind it in the thing that goes red when stale."

[ByteCaleb @bytecaleb]

@claudeai [insert something funny] because I'm early and want a lot of likes

[ByteCaleb @bytecaleb]

I'm building an AI video editor that lives in Telegram/Discord/iMessage/WhatsApp. Comment "BLOOM" and l'll give you free access

[ByteCaleb @bytecaleb]

Last week a Chinese AI model beat Claude Fable: "the AI model that was too dangerous to be released to the world" - but as users rush to use it, there is one graph everybody is sharing and another graph nobody seems to have seen.

Let me catch you up in case you have a clean feed and a healthy social life: Kimi-K3 is a new AI model released by a Chinese research lab called "Moonshot": and Kimi is the AI model that has some people asking if Anthropic's model - Claude Fable - has already been surpassed as the best AI model in the world. And this comes only DAYS after a massive splash from Anthropic's biggest rival releasing an AI model comparable to theirs.

Now that you're caught up, I'll get right to it. Kimi-K3 is expensive.

People typically associate Chinese research labs with cheap AI models but Kimi-K3 is the opposite. Artificial Analysis found it to be the third most expensive AI model in terms of cost per task (onIy beat by GPT-5.6 and Claude Fable itself). Don't get me wrong, it's still a massive saving from Fable, but this is still not the model you go to if you want to save money. Even if you go by API prices, Kimi-K3 is more expensive than well-known American frontier models like Gemini 3.5 Flash and Claude Sonnet 5.

While Kimi-K3 is clearly more capable than both the aforementioned models, I can guarantee that most tasks you need AI for do not require the capability jump. If you really do need it, now you know one trade off. If you don't need it and you see it later on, don't fall for the FOMO. Thoughtless adoption is the fastest way to lose money for no reason.

[ByteCaleb @bytecaleb]

If you're coding with AI (which is basically everybody these days), you need to know about Behavioural Matrices.

Behavioural Matrices answer the question: "How do I continue to understand the different behaviours of my system as I continuously modify it?"

& here is why this question is important. When you're building a fun sideproject, you don't tend to consider the long term evolution of your project. However, many systems that solve real-world problems solve a thousand sub-problems at once:
- What happens if a user's device is too slow?
- What happens if there's a network error while something is saving?
- What happens if there's no data to display in this area?

Over time, the behaviour of your system grows deeply interconnected to the point that a change in one area might affect how a totally different area operates, causing inconsistencies - or worse, break it entirely.

Historically, software engineers created flowcharts and state machine diagrams that were maintained to express how the system behaved in different states, but it's not so easy to represent flowcharts or state machine diagrams inside a terminal or coding IDE. And that is where Behavioural Matrices come in.

Behavioural Matrices attempt to be a tabular representation of flowcharts and state machine diagrams. It is super easy for an LLM to create a table in markdown and it is well-supported in almost all markdown renderers.

A Behavioural Matrix typically has 2 columns:

Old Behaviour / New Behaviour

And a row for how your system behaves in each case. When you are making a change to your system, your coding agent can give you an overview of not just the change it is about to make, but the predicted effect that the upcoming change will have on a subset of surrounding features.

This can warn you about potential bugs/regressions before you have to spend tokens fixing them, or even misalignment in the agent's interpretation of your instruction. I've found myself using behavioural matrices as the "flowchart of the markdown era" more and more so if you're coding with AI, you should definitely give it a try with this prompt the next time you're about to make a change:

"Before making this change, create a Behavioural Matrix with two columns (old behaviour / new behaviour) and rows by feature detailing the expected changes in this feature and any knock-on effects (or non-effects) to dependent features"

You might be surprised what you see.

[ByteCaleb @bytecaleb]

@rom1trs EDIT

[ByteCaleb @bytecaleb]

@borjafat Done

[ByteCaleb @bytecaleb]

@rom1trs VOX

[ByteCaleb @bytecaleb]

@TouchlineX Who's here after Brazil won?

[ByteCaleb @bytecaleb]

@TouchlineX At this rate Bruna Biancardi will deliver the 6th before Neymar

[ByteCaleb @bytecaleb]

@ThatG4m Parma

[ByteCaleb @bytecaleb]

A website where AI models predict the lineups and scores of football games, and get scored on how close they were to reality

[Google AI Studio @GoogleAIStudio]

What are you vibe coding this weekend?

[ByteCaleb @bytecaleb]

@UTDMael Brazil

[ByteCaleb @bytecaleb]

@Andyc1178 I wonder... does everyone understand?

[ByteCaleb @bytecaleb]

@FarzaTV This is what we thought Siri would be

[ByteCaleb @bytecaleb]

This is what we thought Siri would be

[Farza 🇵🇰🇺🇸 @FarzaTV]

Watch me control my computer with just my voice. This is the future of operating systems.

No hands.

GPT-Realtime 2.0 is very, very underrated.

Demo:

[ByteCaleb @bytecaleb]

I fell in love with software at 17.

My first office job, I watched my coworkers grinding through the same Excel spreadsheets every single day. Manual, repetitive, soul-crushing. So I wrote a couple formulas into a copy of their sheets.

You should have seen the look on their faces when they saw it for the first time. It was like I had discovered how to give them back their lost days. Things changed. People started going home earlier, dealing with the reports became quicker and we spent less time fixing inaccurate inputs.

Automation gets a bad rep now because a lot of people are afraid of AI automating their job, but there's genuinely a side of automation that people look forward to.

That's what I saw at 17. And it’s what I hear from people who use Chase Agents.

One of our Chase Agents customers works in a research department and they set up an automation to fill out a quote form on their behalf based on prices sourced from a costing matrix - a task that used to mean jumping between emails, folders, and tools just to give a client a quote. I had the pleasure of sitting in on a conversation where she discussed Chase Agents to her superior, saying:

“And here's the potent part [of Chase Agents]. It's if I’m not around, anyone else can do it based off that automation. And if anyone joins the department, they could easily figure it out.”

By her own account, this wasn't automation that reduced her professional value in any form, it is automation that freed up capacity and enabled collaboration and organisational resilience.

The AI industry's scare tactics will tell you that you should fear for your job (while charging premiums to your employer to replace you), but there's a good side of automation that I feel is being forgotten about. The kind of automation that genuinely allows you to scale your own capacity.

That’s what made me fall in love with software.

[ByteCaleb @bytecaleb]

@fin465 Send

[ByteCaleb @bytecaleb]

@Leisure4Me @filmlerz