iamspoilt
Arguably, this workflow is more ergonomic than Docker for iterative dev work because the VM’s disk persists like a normal machine, so you just install things and move on without thinking about image layers, committing containers, or rebuilding to make changes stick.
GitHub-to-GitLab migration the easy way
https://www.mrafayaleem.com/blog/sandboxing-claude-cli-with-...
Sandboxing Claude CLI with Tart on Apple Silicon
U.S. declaration to exit USMCA to start a decade-long countdown for the pact
The copy-pasting of data from my markdowns to the tax software was the hardest path for me as well.
The intention of this is to reduce hallucination on information extraction, right?
Also, how do you convert your docs / information into JSON documents?
Improving personal tax filing with Claude CLI and Obsidian
I have used the kk8s MCP directly inside Github Copilot Chat in VSCode and restricted the write tools in the Configure Tools prompt. With a pseudo protocol established via this MCP and the IDE integration, I find it much safer to prompt the LLM into debugging a live K8s cluster vs. without having any such primitives.
So I don't see why MCPs are or should be dead.
Show HN: Orchestera – Managed Apache Spark on Kubernetes in Your Own AWS Account
I built Orchestera as a PaaS that allows you to orchestrate Apache Spark clusters in your own AWS account, with no additional markup on compute via EC2 instances.I built this because I was tired of the compute markup that products like AWS EMR and Databricks charge for the convenience of using Apache Spark via their platforms. One can argue that Databricks is a superior product with a lot of...
Humans will be needed to control the amount of entropy that AI agents will add
Currently implemented the following:
- Automated scale in / scale out of nodes for Spark executors and drivers via Karpenter
- Jupyter notebook integration that works as a Spark driver for quick iteration and prototyping
- A simple JSON based IAM permissions managementent via AWS Parameter Store
Work-in-progress this month:
- Jupyterhub based Spark notebook provisioning
- Spark History Server
- Spark History Server MCP support with chat interface to support Spark pipeline debugging and diagnostics
Open to feedback and connecting. Docs at https://docs.orchestera.com/
The platform I am building allows users to launch Spark on Kubernetes in their own AWS account without adding any markup costs to the CPU/Memory on EC2 instances. For example, AWS EMR offering adds a 25% markup cost on top of the EC2 instance pricing. Databricks markup is even higher ranging anywhere from 30% to 100% markup.
To learn more, check out the docs for the project at https://docs.orchestera.com/
A visual editor for the Cursor Browser
Agent OS
https://homeautomation.substack.com/p/setting-up-home-assist...