crusty0gphr

It gets better when scales

Abstraction is a simplified view of an entity , which omits unimportant details. Abstraction is a part of simplification and a key to modularity.

Go generics are debatable. This was an entirely community-requested feature to remove some boilerplate from runtime code.

Go's json package, conceptually, has better design. It is a product of a design choice that values simplicity and high abstraction.

Rust & Zig (Bun): "We know everything about the data structure. Use that to generate perfect, specialized code possible."

Go: "We have no idea what data structure we'll get at runtime. We must be prepared to handle anything the user throws at us. We'll inspect the structure when we get it."

Well, there are a fundamental difference in concepts how Zig (Bun), Rust and Go work with json. Go's json package is reflection heavy. It is also bound by the GC.

💡 The most impacting change in software engineering industries:

😎 Back then: google it, for sure someone else had the same problem.

🤪 Now: ask GPT, it knows how

The sign you've hit senior engineer status:

Your answer to “What's the best tech stack?" is automatically “It depends."

#programming #softwareengineering

How legacy code always seems to end up as one big mess? It's a buildup of all those "temp" expedient shortcuts we take under pressure. Connections in the system get so twisted that no one can reason out the consequences of a change. That's when the fun stops and the headaches begin.

#Programming

TODO is a 𝗧otally 𝗢ptional, 𝗗elay 𝗢pportunity.

Every single TODO is a precious promise we made to our future selves that they'd be too busy fighting new fires to ever dig up that old code.

Honestly, we're not procrastinating, we're just spelling 𝗡𝗲𝘃𝗲𝗿𝗗𝗢 with a fewer letters.

#Programming #meme

Go 1.25 introduces a new method .Go() for the sync.WaitGroup type. With the introduction of the method the process finally has been simplified and made safer. It removes the manual management of the counter. Less code less bugs.

pkg.go.dev/sync@master#...

#go #golang

grep and awk

If you’re not sure about switching to Go, consider this 😎

#go #golang #funny

Anti-pattern: Overwriting return value inside defer Over the years, I have observed numerous examples of code overriding the return value within a defer...

Common anti-pattern that’s extremely dangerous

dev.to/crusty0gphr/...

#go #golang

This one actually will print "something went wrong".

The difference is how return value is declared and initialized to its zero value on the stack frame. This affects the defer closure.

This is a very dangerous concept. I lost a week of debugging a problem with a similar implementation.

Your answer is correct btw 🎉

Good catch, there was a trap 🪤

What about this one? 😈

✨ Quiz time!

- What will be printed? -
1. something went wrong
2. something else went wrong
3. nil
------------------------

Try your luck, let's start a comment war 😈

I plan to write an article about this next week and want to understand how many of you know how this behaves.

#go #golang #quiz

A nice article about "Finding performance problems by diffing two Go profiles"
#golang

www.dolthub.com/blog/2025-0...

runtime: green tea garbage collector · Issue #73581 · golang/go Green Tea 🍵 Garbage Collector Authors: Michael Knyszek, Austin Clements Updated: 2 May 2025 This issue tracks the design and implementation of the Green Tea garbage collector. As of the last update...

🍵 Green Tea is now a garbage collector.

Green Tea is experimental Span-based Scanning approach, instead of processing individual objects, the garbage collector now scans memory in "much larger, contiguous blocks" referred to as spans.

github.com/golang/go/is...

#go #golang #development

After hearing this a lot: "no debugger = no Zed"—we’re excited to share that Zed's Debugger has finally launched! 🎉

zed.dev/debugger

This is a thing I've noticed for myself. If I code the solution myself, I'm more aware of what I'm doing. When I generate tests, I feel disconnected from the project. After generating a few lines of code, bug fixing feels a bit quirky, like I've lost the context of what I'm doing.

Writing the code by hand provides a more complete theory of it than 'tabbing' AI generated results.

What do you think about this? Does all this vibe coding actually make you feel numb?

#ai #vibecode

Contexts: To Cancel or Not to Cancel In Go, the context package provides a mechanism to propagate cancellation signals, deadlines, and...

Goroutine chain shutdown with contexts on @dev.to

dev.to/crusty0gphr/...

#go #golang #contexts

On stage: "Imagine that everyone is naked"
On code review: "Imagine the code was vibed"

#ai #Developers #SoftwareDevelopment

[ On | No ] syntactic support for error handling - The Go Programming Language Go team plans around error handling support

Over the years, there were numerous proposals to add try/cache logic, error handling wrappers to minimize the bloat, but Go's team states that there won’t be syntactic language changes for error handling.

go.dev/blog/error-s...
#golang #go #SoftwareDevelopment #Programming

It’s more efficient than using map. You can have iota enums and assign values to them in a slice. Uses smaller memory footprint.

I’m talking about … operator 😂 I thought your post is about it, then I looked carefully what you mean

This actually is very useful. In scenarios where you have a static length array with constants, which might change over time by developers. You don’t have to manually count how many additional elements you have added and update the length. Case will be handled by the compiler.

Also, Nothing phone is another glass sandwich which I’m starting to hate. I want a durable phone made of good quality plastic.

I really like Fedora. I haven't used it for a while, but it's my favorite distro.

Honestly, I don't like the Nothing Phone. I've never used it, but its design makes me want to avoid it.