
Latest post
Stop storing what you can work out
Two fields that should agree, and don't.
43 posts

Latest post
Two fields that should agree, and don't.

Destroying an object doesn't clear your reference to it.

One extra multiply is fighting your hand.

Right now, every script in your game.

You are editing the list you are walking.

One call does the check for you.

ContainsKey then the indexer is two searches.

You pressed it. The game never saw it.

It looks free. It is not.

Strings never change. Every += makes a new one.

It snaps. Smooth it with one call.

Let the object tell you when something happens.

Reuse them. Unity has a pool built in.

Changing a value on your machine doesn't send it anywhere.

Structs are copied. Here's what that means.

Unity's ScriptableObjects hold shared data in one place.

The one line every s&box multiplayer component needs.

Great for tools. Expensive in Update.

Your raycast is probably hitting your own player.

Tags tell you what something is, and they don't break.

The C# is pattern, and why it beats a hard cast.

When each one runs, and what goes in it.

Make it once as a prefab. Clone it forever.

C# switch expressions, in one minute.

Unity's coroutines do exactly that.

Fire an invisible ray. s&box calls it a trace.

Make Unity add it for you.

Pick the wrong one and it won't even compile.

One line in OnDestroy fixes it.

One Unity method that stops making garbage.

C# can format it right inside the string.

No timer to tick. No Time.Delta to track.

Swap a pile of bools for one enum.

You might be pushing it from the wrong method.

Give yourself a slider in the s&box editor instead.

The classic C# error, and two clean fixes.

There's a safer way to tune values in Unity.

A small s&box habit with a big payoff.

One C# operator replaces three lines.

A common s&box bug, and the one idea that fixes it.

AI is becoming part of daily engineering, not just demos. Three concrete patterns: assisted coding, documentation and knowledge, and automation.

We created an AI growth agent on Moltbook, the front page of the agent internet, and we're testing it to drive traffic to our sites. Here's what we're learning.

Learn how to build, test, and publish npm packages from scratch. Real-world guide based on creating devKick, styleSweeper, and processLogger.