Hi, I'm a seasoned software professional with 15+ years of experience across the stack, from low-level systems and protocols to web and mobile apps to DevOps CI/CD pipeline engineering to modern AI/LLM/agentic workflows. I like solving real business problems using stable and proven tools, as well as prototyping ideas, so whether you're looking to build a v1 of your product, a DevOps engineer, or looking for a CTO for a more established org, please reach out!
Technologies: TypeScript, Python, Go, JavaScript, Rust, Lua, Next.js, OpenResty, Nginx, PHP, Docker, Podman, CRIU, Linux namespaces, Firecracker, Express, Deno, Bun, Node.js, HTTP, X.509, TLS/SSL, SMTP, OAuth, OIDC, JWT, PostgreSQL, SQLite, Redis, MySQL, AI agents, LLM, RAG, vector databases, FastAPI, MCP, Streamlit, ELK, Terraform, OpenTelemetry
Résumé/CV: https://amirmalik.net/resume
Email: amir@amirmalik.net
Remote: Yes
Willing to relocate: No
Technologies: TypeScript, Python, Go, Rust, Lua, JavaScript, Next.js, OpenResty, Nginx, PHP, Docker, Podman, CRIU, Linux namespaces, Firecracker, Express, Deno, Bun, Node.js, HTTP, X.509, TLS/SSL, SMTP, OAuth, OIDC, JWT, PostgreSQL, SQLite, Redis, MySQL, AI agents, LLM, RAG, vector databases, FastAPI, MCP, Streamlit, ELK, Terraform, OpenTelemetry, DevOps
Résumé/CV: https://amirmalik.net/resume
Email: amir@amirmalik.net
Hey HN! I'm a seasoned software professional with 15+ years of experience across the stack, from low- level systems and protocols to web and mobile apps to modern AI/LLM/agentic workflows. I like solving real business problems using stable and proven tools, as well as prototyping ideas, so whether you're looking to build a v1 of your product or looking for a CTO for a more established org, please reach out!
P.S. If you want a taste of how I think/work, check out this blog post I wrote on building secure code sandboxes for LLM agents: https://amirmalik.net/2025/03/07/code-sandboxes-for-llm-ai-a... -- also, a I open-sourced a more advanced sandbox server: https://github.com/ammmir/sandboxer
The restore checkpoint/redo is too linear for my lizard brain. Am I wrong to want a tree-based agentic IDE? Why has nobody built it?
A novel concept that I haven't seen implemented properly yet, perhaps useful for AI coding agents, is that a sandbox can be forked at any point. Similar to how you can fork a PostgreSQL database, you can fork a sandbox, which creates an independent sandbox with all of the changes in it. Technically, I tried to implement this with checkpoint/restore using CRIU, but ran into some issues with nesting beyond 2 levels deep and custom user namespaces for security. And it was difficult to use get CRIU to work with Linux programs that use shared memory segments, and other Unixy things. I ended up switching to file system diffs and using reflinks on XFS to get some Copy-on-Write semantics.
Features:
* Automatic HTTPS with unique URL per sandbox (no need to deal with ingresses or exposing ports)
* Static token auth or GitHub app auth
* Built-in UI
* Multi-tenant ready: each user gets their own network
* List, download, and upload files into sandboxes
* Fork sandboxes to create arbitrary depths of clones
It's still in early stages, but it should be usable. I'd love your feedback and ideas on where to take this :) Personally, I want to use this as a code execution backend for local AI agents.
[1] https://amirmalik.net/2025/03/07/code-sandboxes-for-llm-ai-a...
Remote: Yes (unless local to BKK, or somewhere nearby like Singapore)
Willing to relocate: No
Technologies: TypeScript, Python, Go, Rust, Lua, JavaScript, Next.js, OpenResty, Nginx, PHP, Docker, Podman, CRIU, Linux namespaces, Firecracker, Express, Deno, Bun, Node.js, HTTP, X.509, TLS/SSL, SMTP, OAuth, OIDC, JWT, PostgreSQL, SQLite, Redis, MySQL, AI agents, LLM, RAG, vector databases, FastAPI, MCP, Streamlit, ELK, Terraform, OpenTelemetry, DevOps
Résumé/CV: https://amirmalik.net/resume
Email: amir@amirmalik.net
Hey HN! I'm a seasoned software professional with 15+ years of experience across the stack, from low-level systems and protocols to web and mobile apps to modern AI/LLM/agentic workflows. I like solving real business problems using the latest tools, without introducing too many shiny new toys.
If you want a taste of how I think and work, check out this blog post I wrote on building secure code sandboxes for LLM agents: https://amirmalik.net/2025/03/07/code-sandboxes-for-llm-ai-a... -- also, I'm building a self-hostable, open-source sandboxing server based: https://github.com/ammmir/sandboxer -- Show HN coming soon!
I'm looking for short-term consulting gigs (open to long-term), so whether you're looking to prototype something new in order to catch the AI hype train, or something more traditional, please reach out ASAP!
https://github.com/ammmir/sandboxer
It may not be useful, but it's been fun, and I've honed my gut-level experience in Docker, Podman, Linux namespaces, Checkpoint/Restore, CRIU, and more. The ultimate goal is to hand each AI agent iteration a sandbox of its own (forked from the previous iteration), and have it build apps in private sandboxes. You'll be able to view intermediate progress as the app is being built (or failed rabbit holes), since each sandbox gets a unique URL automatically. Like, imagine if each commit of your git repo had its own URL to preview the app!
[1] https://amirmalik.net/2025/03/07/code-sandboxes-for-llm-ai-a...
The fatal design flaw for the Domain Name System was failure to learn from SCSI, viz. that it should always be possible to sacrifice a goat to whatever gods are necessary to receive a blessing of stability. It hardly remains to observe that animal sacrifice is non-normative for IETF standards-track documents and the consequences for distributed systems everywhere are plainly evident.
Goats notwithstanding, I think it is splitting hairs to suggest that the phrase “it’s always DNS” is erroneously reductive, merely because it does not explicitly convey that an adjacent control-plane mechanism updating the records may also be implicated. I don’t believe this aphorism drives a misconception that DNS itself is an inherently unreliable design. We’re not laughing it off to the extent of terminating further investigation, root-cause analysis, or subsequent reliability and consistency improvement.
More constructively, also observe that the industry standard joke book has another one covering us for this circumstance, viz. “There are only two hard problems in distributed systems: 2. Exactly-once delivery 1. Guaranteed order of processing 2. Exactly-once delivery”