Phil Haack

A bio that defines me (he/him) in terms of my work and my relationships and leaves you no closer to understanding who I am.

[Phil Haack @haacked]

This tweet is pinned to my profile as a representative example of the types of tweets I tweet.

[Phil Haack @haacked]

We thought we were fast when we got our feature flag latency spikes under control and our p99 steadily under 100ms. https://t.co/IBeXggjP1t
Turns out that was child’s play.

[Phil Haack @haacked]

Airport lounge bar didn’t have yellow chartreuse for a Naked and Famous so we went with St Germain and it’s pretty good! I call it:

Naked and Infamous

¾ oz mezcal
¾ oz Aperol
½ oz St-Germain
¾ oz lime juice

[Phil Haack @haacked]

@lucasmeijer @conductor_build Thanks! It’s more barebones, but I like that it’s not trying to intercept Claude so it just works!

[Phil Haack @haacked]

I’ve really been enjoying @conductor_build but it’s really buggy for me. Anyone have alternatives they really like?

[Phil Haack @haacked]

Great post by my colleague about the work we did to reduce latency spikes in our feature flags service built with rust, Tokyo, and rayon: https://t.co/IBeXggjP1t

[Phil Haack @haacked]

Resolving gnarly merge conflicts can be a real tedious chore, until now. Grab a structural semantic merge tool, sprinkle a little AI on it, and you're going to have a lot less headaches.
https://t.co/kB9OtLBMQA

[Phil Haack @haacked]

My son is doing a school project about Buy Nothing and sustainability. https://t.co/aA1DsYLKyV

Drop a comment if you want to help out

[Phil Haack @haacked]

@sebastienros @github Yeah, I'm thinking about this for my own org. I like to use the GitHub PR tools to iterate on a PR without creating noise for others. I just do it as a public draft PR now.

[Phil Haack @haacked]

Hey @github, have you considered private draft PRs? I would like to be able to create a draft PR only I can see that runs CI, copilot, etc. Lets me iterate, before I mark it ready for review to the public.

[Phil Haack @haacked]

@tigkindel @github Ha! Exactly! Also, the multiple CI runs it takes to get everything in proper shape.

[Phil Haack @haacked]

@sebastienros @github What do you mean?

[Phil Haack @haacked]

Credit where credit is due, the new Slack AI bot has been a game changer for finding old slack conversations. I was skeptical, but it actually works for me.

[Phil Haack @haacked]

My colleague @dmarticus wrote a great piece challenging the “AI wipes out white-collar jobs in 18 months” narrative.

Software development isn’t typing code. It’s ambiguity, constraints, and coordination. That makes it much harder to fully automate:

https://t.co/oA8Zz9OGww

[Phil Haack @haacked]

An amazing rum with a hint of peat!

[Phil Haack @haacked]

My shirt keeps telling me that I’m absolutely right.

[Phil Haack @haacked]

Wow, ChatGPT suggested I go to https://t.co/tUS2FTaM5F for a travel issue with a AAA booked reservation. That appears to be a phishing site.

[Phil Haack @haacked]

@headinthebox Ha! Yeah, worktrees are a little confusing to use. I tried to streamline them with my tree-me shell script: https://t.co/wi2XwDpXG5

[Phil Haack @haacked]

Blogged: One year at PostHog https://t.co/W7f6dKbCpu

[Phil Haack @haacked]

I know it's just a stochastic parrot, but sometimes it can be wryly dismissive:

[Phil Haack @haacked]

Blogged: Don't sleep on git worktrees like I did. But using them can be a bit of a chore. But here's a script that makes using git worktrees a breeze:

https://t.co/wi2XwDpXG5