Felix Geisendörfer
@felixge.de
Working at Datadog on Go Profiling, Performance, OpenTelemetry and more.
Before:
- Manufacturing Observability at Apple
- Co-founder at Transloadit
- Node.js Core Dev
Before:
- Manufacturing Observability at Apple
- Co-founder at Transloadit
- Node.js Core Dev
actually, almost the same, the trunk parent is missing, but that’s okay if x is a descendant of trunk I guess?
October 28, 2025 at 8:15 PM
actually, almost the same, the trunk parent is missing, but that’s okay if x is a descendant of trunk I guess?
You can do that in one step if you run:
jj parallelize x::w
same as
jj parallelize x::w
jj new trunk x n p w
jj parallelize x::w
same as
jj parallelize x::w
jj new trunk x n p w
October 28, 2025 at 8:12 PM
You can do that in one step if you run:
jj parallelize x::w
same as
jj parallelize x::w
jj new trunk x n p w
jj parallelize x::w
same as
jj parallelize x::w
jj new trunk x n p w
Thank you for all your great work on this ❤️
October 24, 2025 at 5:42 AM
Thank you for all your great work on this ❤️
I'd love to join one of these again soon, but I'm playing beach volleyball during that time. But usually I play Fridays, so it should work next time.
September 30, 2025 at 9:36 AM
I'd love to join one of these again soon, but I'm playing beach volleyball during that time. But usually I play Fridays, so it should work next time.
What’s the market rate for corporate emoji smuggling? 🤣
a man in a green plaid shirt is standing next to another man in a black coat
ALT: a man in a green plaid shirt is standing next to another man in a black coat
media.tenor.com
September 24, 2025 at 9:07 AM
What’s the market rate for corporate emoji smuggling? 🤣
Initial prompt + follow-up conversation from cursor: gist.github.com/felixge/b317...
cursor_investigating_goroutine_state_tr.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
September 17, 2025 at 11:26 AM
Initial prompt + follow-up conversation from cursor: gist.github.com/felixge/b317...
Two amazing time savings here:
a) Tracing the call paths of a bunch of runtime functions to a function I know exists, but don't know the name of ("does network wakeup").
b) Writing the final analysis with code snippets and links to the Go code (permalinks at the right Go version).
This is fun.
a) Tracing the call paths of a bunch of runtime functions to a function I know exists, but don't know the name of ("does network wakeup").
b) Writing the final analysis with code snippets and links to the Go code (permalinks at the right Go version).
This is fun.
September 17, 2025 at 11:25 AM
Two amazing time savings here:
a) Tracing the call paths of a bunch of runtime functions to a function I know exists, but don't know the name of ("does network wakeup").
b) Writing the final analysis with code snippets and links to the Go code (permalinks at the right Go version).
This is fun.
a) Tracing the call paths of a bunch of runtime functions to a function I know exists, but don't know the name of ("does network wakeup").
b) Writing the final analysis with code snippets and links to the Go code (permalinks at the right Go version).
This is fun.
(This doesn't mean I'm not behind on an incredible backlog of other things ... but one step at a time 😅)
September 11, 2025 at 5:34 AM
(This doesn't mean I'm not behind on an incredible backlog of other things ... but one step at a time 😅)
s/way/day/ didn‘t have my coffee yet 😅
September 11, 2025 at 4:12 AM
s/way/day/ didn‘t have my coffee yet 😅
Even if the solution hadn't come to me, leaving the test case without a fix is a fantastic way to start the way. It gives absolute clarity of focus in the morning.
IIRC @thorstenball.com has been talking about this in the past as well.
IIRC @thorstenball.com has been talking about this in the past as well.
September 11, 2025 at 3:45 AM
Even if the solution hadn't come to me, leaving the test case without a fix is a fantastic way to start the way. It gives absolute clarity of focus in the morning.
IIRC @thorstenball.com has been talking about this in the past as well.
IIRC @thorstenball.com has been talking about this in the past as well.
Your call ovbviously. But I don’t think showing a full use case would overload things.
Everything is a funnel, and every step loses a fraction of users. Clicking into pkg docs for a full example will lose a decent % of potential users IMO.
Everything is a funnel, and every step loses a fraction of users. Clicking into pkg docs for a full example will lose a decent % of potential users IMO.
September 6, 2025 at 3:44 PM
Your call ovbviously. But I don’t think showing a full use case would overload things.
Everything is a funnel, and every step loses a fraction of users. Clicking into pkg docs for a full example will lose a decent % of potential users IMO.
Everything is a funnel, and every step loses a fraction of users. Clicking into pkg docs for a full example will lose a decent % of potential users IMO.