davideberdin

I’m working on Alaska, a serverless compute platform I built entirely from scratch — no Kubernetes, no existing orchestration layers. It can spin up dozens of containers in parallel in just a few seconds. The platform is designed around a fast feedback loop — you write code locally, test instantly, and run it remotely with minimal friction. There’s a Python SDK that uses decorators to define what runs on the platform, so your local functions become distributed services without extra boilerplate. I also built a custom filesystem using FUSE to handle code, data, and runtime synchronization cleanly across nodes. It started as a personal exploration of distributed systems, but it’s grown into something that feels genuinely exciting! It's created by a developer for developers. Planning to open it up for beta testing soon.

I'm always impressed by the quality of the blog posts coming out from clickhouse.com! Super well written!

Redis I would say, by Salvatore Sanfilippo (https://github.com/antirez)

Thanks for sharing the link and your advices. I've never thought about squads as they are explained in the website.

Makes sense -- Knowledge Base is something I should definitely tackle. Thanks :)

Thanks for the tips! I appreciate them :)

I've been noodling for a while regarding Kanban. Where do you see the main advantages in using it?

Thanks for the tips. I do appreciate them :)

`Don't let them get bogged down or pinged constantly. Try to make that request flow async.` - This is very true yet so hard. Slack is not helping at all with this issue. I will check with the team about office hours or maybe a triaging system to minimize the Support effort.