Before:
- Manufacturing Observability at Apple
- Co-founder at Transloadit
- Node.js Core Dev
newsletter.vickiboykis.com/archive/i-wa...
newsletter.vickiboykis.com/archive/i-wa...
www.youtube.com/watch?v=WWNh...
www.youtube.com/watch?v=WWNh...
The kind of stuff goroutines get up to behind the scenes can be truly fascinating.
The kind of stuff goroutines get up to behind the scenes can be truly fascinating.
Example: Asked opus to explain some runtime internals, and then turn the analysis into a nice human-readable markdown output that I can use to explain a code change I'm making to a colleague.
Example: Asked opus to explain some runtime internals, and then turn the analysis into a nice human-readable markdown output that I can use to explain a code change I'm making to a colleague.
#golang
#golang
Typically they align, but one answer is better than the other.
But it turns out no amount of AI can solve the "too many chefs in the kitchen" problem 😂.
Typically they align, but one answer is better than the other.
But it turns out no amount of AI can solve the "too many chefs in the kitchen" problem 😂.
And to top it off, Spotify just pulled an incredible "Discover Weekly" playlist out of the hat.
Good times 🎶
And to top it off, Spotify just pulled an incredible "Discover Weekly" playlist out of the hat.
Good times 🎶
Old me would have been excited and stayed up late trying to fix it.
These days I know this is the best time to go to sleep. And indeed, the solution came to me while falling asleep.
Wrote it up this morning - works 👍🏻
Old me would have been excited and stayed up late trying to fix it.
These days I know this is the best time to go to sleep. And indeed, the solution came to me while falling asleep.
Wrote it up this morning - works 👍🏻
repeatedly, whereas previously, running jj undo twice was previously a no-op (it only undid the last change).”
😮 It seems Christmas came early this year.
github.com/jj-vcs/jj/re...
repeatedly, whereas previously, running jj undo twice was previously a no-op (it only undid the last change).”
😮 It seems Christmas came early this year.
github.com/jj-vcs/jj/re...
What it allows me to do is split a lot of my work into independent PRs (CLs), but work on a local tree that reflects the state of the repo as if all of them had already been merged.
What it allows me to do is split a lot of my work into independent PRs (CLs), but work on a local tree that reflects the state of the repo as if all of them had already been merged.
The countdown is officially ON—#GopherCon is just around the corner!
Don’t wait until the last minute—lock in your pass now and get ready to join us in NYC for the biggest #golang celebration of the year!
👉 www.gophercon.com
#GopherConOrBust #GophersUnite
The countdown is officially ON—#GopherCon is just around the corner!
Don’t wait until the last minute—lock in your pass now and get ready to join us in NYC for the biggest #golang celebration of the year!
👉 www.gophercon.com
#GopherConOrBust #GophersUnite
How I think about it is as a way to deflake tests by simulating an infinitely fast processor (because time doesn’t move until all work is done), and then shorten them by compressing time (because time jumps once it moves).
📝 Release notes: https://go.dev/doc/go1.25
⬇️ Download: https://go.dev/dl/#go1.25.0
#golang
How I think about it is as a way to deflake tests by simulating an infinitely fast processor (because time doesn’t move until all work is done), and then shorten them by compressing time (because time jumps once it moves).
📝 Release notes: https://go.dev/doc/go1.25
⬇️ Download: https://go.dev/dl/#go1.25.0
#golang
📝 Release notes: https://go.dev/doc/go1.25
⬇️ Download: https://go.dev/dl/#go1.25.0
#golang
kohlschuetter.github.io/blog/posts/2...
kohlschuetter.github.io/blog/posts/2...
Join Go contributor @thepudds.bsky.social for a deep dive into escape analysis—the part of the compiler that decides whether your data stays on the stack or takes the more expensive trip to the heap.
🎟️ www.gophercon.com
Join Go contributor @thepudds.bsky.social for a deep dive into escape analysis—the part of the compiler that decides whether your data stays on the stack or takes the more expensive trip to the heap.
🎟️ www.gophercon.com
Join @felixge.de as he introduces a novel approach to analyzing Go request latency using critical path analysis—one that goes beyond traditional CPU profiling, logs, or traces.
🎟️ www.gophercon.com
#GopherConOrBust #golang
Join @felixge.de as he introduces a novel approach to analyzing Go request latency using critical path analysis—one that goes beyond traditional CPU profiling, logs, or traces.
🎟️ www.gophercon.com
#GopherConOrBust #golang