https://almostintuitive.com/docs/technical/Recent content in Technical on Mark Aron SzulyovszkyHugo -- gohugo.ioen-UShttps://almostintuitive.com/docs/technical/reimagining-github-actions/Sat, 02 May 2026 00:00:00 +0000https://almostintuitive.com/docs/technical/reimagining-github-actions/Re-imagining Github/Gitlab Actions As with most of you, our small team’s velocity has increased a lot over the last 6 months. There is a “reimagining git(hub)” zeitgeist going on, and “actions” are a big part of that in terms of time and money spent for every productive team. They’re even more important now, right? I think a world where llms/agents write most of the code (they do on our side), there are a couple of tweaks that may be optimal for “actions”:https://almostintuitive.com/docs/technical/sync-endpoints/Sat, 04 Apr 2020 00:00:00 +0000https://almostintuitive.com/docs/technical/sync-endpoints/Sync APIs - git patch inspired non-blocking client-server communication pattern Three years ago, we were in a desperate need for a mental model: how to structure the highly asynchronous, non-blocking communication we have between our backend and mobile clients - where Read/Update are the only meaningful operations. The solution we ended up with was something different than the currently popular CRUD / REST APIs (but closer to GraphQL’s) - and rather close to the concept of git’s patches / diffs.