Mastodawn

I like to learn by teaching. It reveals the gaps in my knowledge and tests my understanding. Started writing a book for the #zig community and spent months writing the code, making sure each block of code builds and the language makes sense. In the midst of writing content for the second-half of the book, I paused. I started to ask myself about the meaning of it all in a post-AI world. I’m beginning to question the value of it to the community when the problem it solves is a prompt or two away.

definitepotato Mar 21

One of the most practical and useful books of my career has been the Thorsten Ball series of writing an interpret/compiler in #golang. I wanted to give to the #zig community so I've written a guide/book at https://www.definitepotato.dev/books/ called From Interpreter To Compiler in Zig.

It's essentially Thorsten Ball's structure but in Zig. I plan to maintain it as the zig compiler develops and I learn to do better.

Books

Online books by definitepotato

definitepotato

Show thread

definitepotato Feb 24

@dolanor I like that the discussions are happening and not being brushed off. It's a difficult subject to disect because each layer has it's own set of rules. Most of the code #AI yields is based on someone's work but the software that puts the pieces together is also adding some of it's own ingredients to the recipe.

So if I took someone's recipe for cheese cake and added salt, what's the right thing to do?

definitepotato Feb 23

" What should we do with CLs generated by #AI "?

A discussion on `golang-dev` begins when a #Golang dev noticed Claude as a co-author on a contribution. Responses from people other #Go devs include legal issues, licensing issues and extensive thoughts. Interesting post to read and follow:

https://groups.google.com/g/golang-dev/c/4Li4Ovd_ehE/m/UU87HnL5DgAJ?pli=1

What should we do with CLs generated by AI?

Show thread

definitepotato Feb 13

@__pity__ The official Go guidelines suggest method receivers be one or two letter names: https://go.dev/wiki/CodeReviewComments#receiver-names

Granted this doesn't extend to variables. I agree with you I prefer something more descriptive and explicit for the sake of clarity when reading code.

Go Wiki: Go Code Review Comments - The Go Programming Language

definitepotato Feb 13

Two new packages management features just added to #ziglang

- Fetched packages are now stored locally in the zig-pkg directory
- The zig build command gets a fork flag to override the entire dependency tree of a project given a path to the source

Devlog ⚡ Zig Programming Language

definitepotato Feb 11

#golang 1.26 is released https://go.dev/blog/go1.26

- new built-in function
- gc performance improvements
- go fix command has been rewritten
- experimental simd operations added
- experimental temporaries secret eraser added
- experimental goroutine leak detection added

Go 1.26 is released - The Go Programming Language

Go 1.26 adds a new garbage collector, cgo overhead reduction, experimental simd/archsimd package, experimental runtime/secret package, and more.

Show thread

definitepotato Jan 30

@rebelopsio #zig is great for learning systems programming. Keep going, keep learning. Happy to collab if you need a rubber duck, don't be afraid to reach out.

definitepotato Jan 30

AI could force popular #FOSS projects to close PR submissions from the public.

definitepotato Jan 24

Results from the latest #golang developer survey conducted in September2025.

https://go.dev/blog/survey2025

Results from the 2025 Go Developer Survey - The Go Programming Language

The 2025 Go Developer Survey results, focused on developer sentiment towards Go, use cases, challenges, and developer environments.

Github	https://github.com/definitepotato
Keyoxide	https://keyoxide.org/hkp/6e34f5a9bdc72011436b8c29807ee32a2f083c6d
Blog	https://www.definitepotato.dev