LOL, it might not look like much, but to me, this is incredible. 9 people have already taken the time to download and play OVERCHARGE. That honestly means the world to me! Thank you to everyone checking it out. 💜📈 #gamedev #indiedev #solodev #pixelart

du -sh .zig-cache/ 226G .zig-cache/ (╯°□°)╯︵ ┻━┻ #Ziglang

I'm developing a hate for non garbage-collected runtimes. #Ziglang

I updated Learning Zig to work with 0.16 www.openmymind.net/learning_zig/ #Ziglang

I rather not know a metric than only knowing an average value.

Where are all these companies / developers writing well thought-out, clean, secure and maintainable code that I keep hearing AI is threatening?

For any hosted (i.e. not deployed on a desktop/mobile), #elixir is objectively better for anything you'd use ruby / node for. But Phoenix is so...ugh.

I dearly miss Elixir.

Blogged: On AI www.openmymind.net/On-AI/

About 3x a week now. Claude says I'm violating its AUP for benign things. Today I asked Claude what was up with the error and it said "false positive", probably because we use words like "bug", "corrupt" etc. So I asked Claude to phone home again, but avoid those words...and it worked.

A thread-safe pool of arena allocators, with different sized buckets (1K, 4K, 16K, 128K, 512K) is a good solution to many allocation problems.

For a large agent-driven refactor, I benefit a lot from two things: 1 - Co-driving the first ~25% of the work. Helping nail a scope and shape and catching any assumptions / miscommunications. 2 - Spinning off a separate session (or taking over directly) early on stuck build / test failing.

Coding agents are a tool, and, assuming they survive the bubble implosion, we're going to see (and already are seeing) effective individual / companies benefit from it, and incompetent individuals / companies suffer from it. 1/2

Modern stdlib's should have a parser combinator.

Let me enjoy this weekend by.... trying to get my networking heavy libraries to work with zig 0.16 half-baked networking i/o . . . on windows.

I'm willing to grant that maybe Claude is effective for me because I code in a well documented/spec'd/ domain. But, at 800K context, slugging through a complex but well scoped piece of code, which is specific to the implementation, it can do anything in there ~100x faster and at least 5x better.

if a $200/month tool is a significant productivity boost, that's going to be an issue for people living where $200 (USD) / month is a significant expense and, I would think, an issue for those countries as a whole.

I've always been too dumb to learn Rust (I've tried!). I'm 100% sure I could pick it up with an AI-sidekick.

There's 1 [software] management activity that trumps all others, and it isn't even close: reviewing pull requests.

At least 1/2 of my Zig projects end up with a discriminatory type like `Binary{value: []const u8}` to be able to map byte vs string data. I just added one to lightpanda.

Every C library should have 1 version that takes a null terminated string, and 1 that takes a ptr+len. It should be a law.

It's a bit concerning that Claude Code is asking me to enter something like "I confirm that this is a legitimate part of the project and not part of some malware program".

Zig 0.16's current state forced me to minimize the internal-use of std.Io that I added for 0.15. httpz is a bit of a mess now, but the 3/4 that reverted to the 0.14 way of doing things is _a lot_ neater and simpler.

Enough tests tests that I feel confident pushing to main. But also not enough tests that I'm not surprised when something fails.

In my old age, I prefer: (hasPending() == false) over: (!hasPending()). Fuck it, I said it.

It's so easy to inject code into, what seems like, a [large] rebase.

Said it before, I'll say it again. The reason #Ziglang should have a string type is purely so that code can discriminate between a string a binary data, which can be important in all types of cases usually involving things like interacting with other libraries or systems.

It's simple: posix is better to program with than std.Io #Ziglang

I'm starting to think unconditional WFH might not be right for most companies. For a well-managed company, it should probably be a per-employee policy. But for companies that can't deal with the drama that will cause, it should just default to hybrid.

The Zig compiler (0.15.2) has been SIGABRT'ing on me daily for trivial errors. It can hard to review the current changes & figure out the error. Thankfully, this almost always finds the issue and turns a near-dealbreaker into a chuckle: find . -name "*.zig" -exec zig ast-check {} \;

Engineering managers have 1 job right now: Find out which employees don't feel like coding agents are significantly increasing their productivity and figure out why.

A commit message should explain why, not what. The diff already has what. Don't say "moved this to an ordered map"...that's redundant. Say _why_: "We need to execute these in insertion order as per the spec (ideally: link to spec)"

That old joke, applied to tmux... How do you know if someone uses tmux? Don't worry...they'll tell you.

Container tabs is the only reason I stick with Firefox. Can't believe it still isn't available in Chromium.

I'm too dumb to know if the compiler will optimize my code, and too smart not to worry about it.

Sometimes the #ziglang compiler just fails with no meaningful error. Just this: test └─ run test └─ compile test Debug native failure error: the following command terminated unexpectedly:

There's virtually no code that I write now without an accompanying claude session. The $20/m plan suits my needs, but I could see myself doubling my usage (but not much more). I think comfort and success with it directly relates to your comfort and success with collaborative coding in general.

WIP PR is at +62,029 −31,380 (and it isn't some linter / formatting).

If I was building a web site/service today, I'd, if nothing else, at least consider Gleam.

TIL: // zig fmt: off

I find it fun. And there's probably a blog post or two in there. But the TL;DR would be - I've always found reading / reviewing code fun. It's the same, but a bit different.

Claude also didn't like the way pg.zig's pool handled connections in a fail-state, so it wrote this: github.com/karlseguin/p...

Claude didn't like my lame hash function. github.com/karlseguin/h...

Everyone should try and use Google Jules just to see that there's clearly something wrong at Google.

Spam on Fastmail is getting a bit bad.

Let's pay some bills.

Blogged: Is #zig's New Writer Unsafe? www.openmymind.net/Is-Zigs-New-... Please tell me I'm doing something stupid. #ziglang

Not the #zig post I thought I was writing, but this is what came out: Everything is a []u8 www.openmymind.net/Everything-I...

dev: my zig code is slower than Go. zig dev: have you tried ReleaseFast? dev: my zig code is less safe than Go. zig dev: have you tried ReleaseSafe? dev: my #zig binary is larger than with Go. zig dev: have you tried ReleaseSmall?

Blogged: I'm too dumb for Zig's new IO interface www.openmymind.net/Im-Too-Dumb-...