crusty0gphr
@crusty0gphr.bsky.social
🥲 ▮▮▮▮▮▮▯▯▯ 🫠 | Go🪐 | Beer-Driven-Development 🍺 | Yet Another Golang Developer
💡 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
😎 Back then: google it, for sure someone else had the same problem.
🤪 Now: ask GPT, it knows how
October 29, 2025 at 11:00 AM
💡 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
😎 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
Your answer to “What's the best tech stack?" is automatically “It depends."
#programming #softwareengineering
October 21, 2025 at 5:55 PM
The sign you've hit senior engineer status:
Your answer to “What's the best tech stack?" is automatically “It depends."
#programming #softwareengineering
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
#Programming
October 20, 2025 at 3:30 PM
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
#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
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
October 20, 2025 at 5:37 AM
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
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
pkg.go.dev/sync@master#...
#go #golang
August 20, 2025 at 2:16 PM
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
pkg.go.dev/sync@master#...
#go #golang
July 17, 2025 at 5:25 PM
✨ 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
- 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
July 4, 2025 at 6:58 AM
Reposted by crusty0gphr
A nice article about "Finding performance problems by diffing two Go profiles"
#golang
www.dolthub.com/blog/2025-0...
#golang
www.dolthub.com/blog/2025-0...
June 21, 2025 at 5:54 AM
A nice article about "Finding performance problems by diffing two Go profiles"
#golang
www.dolthub.com/blog/2025-0...
#golang
www.dolthub.com/blog/2025-0...
🍵 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
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
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...
github.com
June 20, 2025 at 5:38 PM
🍵 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
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
Reposted by crusty0gphr
After hearing this a lot: "no debugger = no Zed"—we’re excited to share that Zed's Debugger has finally launched! 🎉
zed.dev/debugger
zed.dev/debugger
June 18, 2025 at 5:56 PM
After hearing this a lot: "no debugger = no Zed"—we’re excited to share that Zed's Debugger has finally launched! 🎉
zed.dev/debugger
zed.dev/debugger
On stage: "Imagine that everyone is naked"
On code review: "Imagine the code was vibed"
#ai #Developers #SoftwareDevelopment
On code review: "Imagine the code was vibed"
#ai #Developers #SoftwareDevelopment
June 5, 2025 at 3:12 PM
On stage: "Imagine that everyone is naked"
On code review: "Imagine the code was vibed"
#ai #Developers #SoftwareDevelopment
On code review: "Imagine the code was vibed"
#ai #Developers #SoftwareDevelopment
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
go.dev/blog/error-s...
#golang #go #SoftwareDevelopment #Programming
[ On | No ] syntactic support for error handling - The Go Programming Language
Go team plans around error handling support
go.dev
June 5, 2025 at 2:20 PM
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
go.dev/blog/error-s...
#golang #go #SoftwareDevelopment #Programming
I'm thinking about de-Appleing myself.
SPOILERS: I'm not sure yet 🤪
#developers #foss #thoughts #rightToRepair
SPOILERS: I'm not sure yet 🤪
#developers #foss #thoughts #rightToRepair
June 2, 2025 at 10:41 AM
I'm thinking about de-Appleing myself.
SPOILERS: I'm not sure yet 🤪
#developers #foss #thoughts #rightToRepair
SPOILERS: I'm not sure yet 🤪
#developers #foss #thoughts #rightToRepair
May 27, 2025 at 4:26 AM
Go's simple imperative loops make data transformations verbose & error-prone, but Rust's .map(), .filter(), & .fold() offer better composability, leading to more maintainable code. See screenshots comparing both languages.
#go #golang #rust #programming #debate
#go #golang #rust #programming #debate
May 25, 2025 at 6:23 PM
Go's simple imperative loops make data transformations verbose & error-prone, but Rust's .map(), .filter(), & .fold() offer better composability, leading to more maintainable code. See screenshots comparing both languages.
#go #golang #rust #programming #debate
#go #golang #rust #programming #debate
In addition to the direct memory manipulations in Go, here's how to manually allocate memory for a struct using the unsafe package without relying on high-level built-in allocation functions like new() or make().
Ugly, but doable 😉
#go #golang #tip #programmin
Ugly, but doable 😉
#go #golang #tip #programmin
May 22, 2025 at 1:08 PM
In addition to the direct memory manipulations in Go, here's how to manually allocate memory for a struct using the unsafe package without relying on high-level built-in allocation functions like new() or make().
Ugly, but doable 😉
#go #golang #tip #programmin
Ugly, but doable 😉
#go #golang #tip #programmin
I got bored 😎
I tried to manipulate array elements directly by accessing them via pointers.
Not a thing that you'll ever do in Go, but still interesting to try out.
#go #golang #pointers #programming
I tried to manipulate array elements directly by accessing them via pointers.
Not a thing that you'll ever do in Go, but still interesting to try out.
#go #golang #pointers #programming
May 16, 2025 at 3:05 PM
I got bored 😎
I tried to manipulate array elements directly by accessing them via pointers.
Not a thing that you'll ever do in Go, but still interesting to try out.
#go #golang #pointers #programming
I tried to manipulate array elements directly by accessing them via pointers.
Not a thing that you'll ever do in Go, but still interesting to try out.
#go #golang #pointers #programming