I’ve launched Small Hours 🌙 A calm HTML website template for creators selling ebooks, guides and digital products. Two homepage styles, responsive layouts and a setup guide. $19 one-time. Preview + details: whop.com/beyondlogic/small-h…

I want this too @elonmusk

Do you remember when you joined X? I do! #MyXAnniversary

Freelance devs: the site's done. The “small changes” keep coming. Turn those requests into paid monthly support—with clear limits. Short guide + templates. Birthday treat 🎂 First 20 buyers: 50% off. $19 → $9.50 with BIRTHDAY50 Take a look: beyondlogic.whop.site/from-o…

“Just a simple website” isn’t a scope. Before sending a quote, clarify: • Pages needed • What visitors should do • Who supplies the content • Required integrations • Delivery expectations Ten minutes of questions can prevent weeks of confusion.

Freelance website projects need less back-and-forth. I created the Client Website Project Kit to help web designers and developers scope work, collect content, prepare quotes and manage feedback. Five practical tools. One workflow. $49. beyondlogic.whop.site/

I built Ready to Quote for freelance web designers who get enquiries like “just a simple website.” Define the scope, use your own rates, then export a client quote. Offline browser app + 3 worked examples. $29 once. whop.com/beyondlogic/ready-t…

A cleaner’s website needs service areas. A photographer’s needs a feel for the work. A designer’s needs a clear process. That shaped Open Doors: three HTML templates I created. Which business should I design for next? beyondlogic.whop.site/open-d…

Freelance brand designers: give your finished work a clear handoff. I built All Yours to organise approved logos, colours, font references and file links into a client guide. Downloadable browser app. $15 USD, one time. beyondlogic.whop.site/all-yo…

I just launched BeyondLogic! 🎉 My first product: “What Do I Say?” — 30 ready-to-edit client replies for freelance graphic designers. For those “how do I respond to this?” moments. $5 once. PDF + copyable text. beyondlogic.whop.site

New on WADMASTER 🚀 You can now manage your inventory, track stock levels, cost prices, and see how much you actually make — all connected to your invoices. Try it out wadmaster.com/inventory-mana…

A few random notes from claude coding quite a bit last few weeks. Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent. IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits. Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased. Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion. Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage. Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building. Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it. Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements. Questions. A few of the questions on my mind: - What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*. - Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro). - What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music? - How much of society is bottlenecked by digital knowledge work? TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

If they're fine borrowing but suddenly uncomfortable when you mention Kehbar… that's your sign . Lend smart, protect your peace. Kehbar makes lending between friends and family clear and stress free. Join the waitlist👇 kehbar.com/ #Kehbar #Waitlist #BuildInPublic

Lending money to people you love shouldn't ruin things between you 😞 Kehbar keeps it clear on both sides. Join the waitlist 👇 kehbar.com/ #Kehbar #Waitlist

We've all been on one side of this situation and it is never comfortable. Kehbar exists so lending money to people you love doesn't end in silence, resentment or a public scene. Join the waitlist: kehbar.com/ #Kehbar #Waitlist #StartupJourney #BuildInPublic

Introducing GPT-5.5 A new class of intelligence for real work and powering agents, built to understand complex goals, use tools, check its work, and carry more tasks through to completion. It marks a new way of getting computer work done. Now available in ChatGPT and Codex.

When you the waitlist you also get access to premium features amongst others. Join NOW! kehbar.com/#waitlist

A friend that owes you money just posted “soft life 😌✨” What’s your next move? Be honest… no lies 😂 Join the waitlist via the link in the bio #kehbar #softlife #friends