Hakan Lofcali (@hknlof) profile picture
Joined October 2026
DevX in Data is the worst experience in Software. Whether it is editing, rolling out or what not. It is just horrific how the tooling evolved.
3
Why does every podcast on YouTube start like a 90s HipHop Video?
2
Hakan Lofcali retweeted
A thousand years ago, I made a dent in dev envs with “Vagrant.” The most popular request always was “I want Vagrant for remote envs.” I’ve been asked this to this day!! I tried and failed many times. I made things that worked but didn’t work right. Well, Rex is done right. Rex is my answer, finally. It’s always lived in the back of my mind no matter what I did. I would come up with something and try it and it didn’t feel right. I got really close around 5 years ago to the point I setup a website branding etc (via HashiCorp). But at the last minute I pulled it. It still wasn’t right. I couldn’t explain why and didn’t have a better solution. I just knew it had to be binned. Well, Rex is it. This is the real deal. Rex is doing for remote development (and a lot more than just dev) what I think a proper solution should’ve done. It’s far more than just a dev tool but I think part of what I knew is once you reach into remote environments that line isn’t clear anymore. You have to solve both remote dev and remote prod. Here we go, back to the beginning.
95
64
14
2,722
118,751
Hakan Lofcali retweeted
As a big 'monitor the situation' guy, there are currently way too many situations to monitor.
176
5,719
161
52,173
657,769
Hakan Lofcali retweeted
I’m old enough to remember that email was supposed to be decentralised
72
226
15
2,897
47,287
Hakan Lofcali retweeted
We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work. First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs. Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue). Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main. Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown. The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in. Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way."). This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours. All of this works on mutual trust. It ONLY works with mutual trust. Everyone at all times has to trust that they've got each others back: 1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts). 2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer. 3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly). We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago. In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome.
179
196
71
4,630
299,666
why are we measuring data by bytes of storage and not bits of information?
3
Hakan Lofcali retweeted
a huge thank you to @OpenRouter for giving me a credits grant to continue research expanded further than just samsung TVs. it's already being put to good use. all common household devices will ameliorated before morale improves.
47
113
2
2,305
22,944
How are freelancer in engineering and design pairing up
4
what does your machine smell like
2
Simple to use, means lots and lots of detailed coherent decisions made.
2