friend has been familiarizing himself with agentic workflows recently and was initially struggling. he figured out an instructive model that works for him, and generated a blog post about it. thought i'd show him some love, and share for others who might be feeling the same pain as him.
yeah our findings were similar. the issues we saw with iptables rules, especially at scale with ephemeral workloads, was starting to cause us a lot of operational toil. nftables ftw
Shame, I am not sure how others use actions but I like really small granular ones to make it easy to see what's wrong at a glance. E.g. formatting checks per language per project in my monorepo etc. Each check is like 10 seconds and I have like 70+, so the per minute is biting me ATM.
Come check out RWX :). We have per second billing but I think it won't even matter for your use case because most of those checks are going to take 0s on RWX. And our UI is optimized for showing you what is wrong at a glance without having to look at logs at all.
* Your per min billing is double blacksmith's
* RWX is a proprietary format? vs blacksmith's one line change.
* No fallback option, blacksmith goes down and I can revert back to GitHub temporarily.
yeah, like the others have said, the tradeoff isn't really worth it for us as a business. spot instances also generally come with low qos guarantees (since they tend to be interruptible). tbf there are on-demand alternatives with better guarantees though
another thing to note is that we bootstrap the hosts, and tune them a decent amount, to support certain high-performance features which takes time and makes control + fixed-term ownership desirable
I would probably hesitate but, if I had some financial safety, I would eventually decide to quit. Is there a lot of upside to staying in terms of career growth and/or compensation?
Yeah, web IDEs have made life a lot easier but I don't think the experience works well for a minimal note taking flow. one of the most important things for me when it comes to a note-taking app is to be able to write free form and without the need for too much process - obviously this is not quite possible in markdown or really most digital formats, but also just the fact that I know git is backing my notes store creates a maintenance burden in my mind that I'm not sure I care for. I used to use jupyter notebooks way back when which felt more flexible but even that began to feel too heavy a process.
Do you use git at all in terms of committing notes and looking through history, or are you only ever adding on top and treating a commit like a save in a notepad app? This is a bit peripheral but I've been considering investing in a remarkable tablet, but using it obviously requires me to carry an additional physical device around.
So for both use cases (Gitlab & Github) their web IDEs are leveraging Git (from the web GUI). So the cool aspect of all of this is that I could clone the repo locally and maybe even re-purpose for a Hugo site. But the core benefit of version control is there.
Oh yeah, I know. Let me rephrase - do you actually leverage the functionality that git (through Github/Gitlab) provides you in your note-taking? Do you go back in the history to see what you committed - do you bisect or look at meta, or commit in atomic ways so that things are more "organized" from a timeline perspective?
Yes! One nice aspect of version controlled notes: change management "trail". Meaning that I don't have to note what specific changes occurred to a requirement in a project but can just change the requirement. If I need to research why something took longer than expected one of the first ways to research that is via file history from git or from Gitlab / Github's History user experiences.
