Kevin
15K posts

Kevin
@kvnify
Staff Software Engineer @Shopify and a Super Nice Guy™ https://t.co/VXGJINwK5b

@nummanali tmux grids are awesome, but i feel a need to have a proper "agent command center" IDE for teams of them, which I could maximize per monitor. E.g. I want to see/hide toggle them, see if any are idle, pop open related tools (e.g. terminal), stats (usage), etc.


We used to build big things in Canada, and we used to build quickly. It’s time to get back to it.

We @ShopifyEng just open-sourced Tophat, our one-click mobile app testing tool 🎉 🖱️ Install a build on a simulator or device with a single click 📷 Skip building branches locally by leveraging your existing CI infrastructure ✨ Easily integrate with GitHub and custom tooling.



Sunday rant. For software engineering, my sense is that the phrase “premature optimization is the root of all evil” has massively backfired. Its from a book on data structures and mainly tried to dissuade people from prematurely write things in assembler. But the point was to free you up to think harder about the data structures to use, not leave things comically inefficient. This context is always skipped when it’s uttered. Not all fast software is world-class, but all world-class software is fast. Performance is _the_ killer feature. If you are in engineering, here is a fantastic anecdote. I refer to this account often. It’s a bit subtile, but the implications are massive- It’s an account of how SQLite became 50% faster, not by doing one specific thing but hundreds of small ones. SQLite is everywhere today because of this work. sqlite-users.sqlite.narkive.com/CVRvSKBs/50-fa… We need the engineers in all companies fight for this more. Product leads are not the right owners of the end performance of the software. This needs to be encoded in the professional pride of the software engineering discipline. Leaders in companies need to encourage it and hold engineering accountable. It’s simply not ok to fritter away the performance of the products for random reasons. Every user of your products cares exactly as much about latency as engineers do when typing in their terminal. They just don’t have the words to describe what they don’t like about the experience and neither should they.















