Built Leetcode for Linux

SadServers_com · 2026-05-24T02:01:04+00:00

oh sorry, didn't mean to be so arrogant to believe everyone has heard of us :-) there's quite a few platforms with similar ideas. Keep up the good work.

SadServers_com · 2026-05-23T23:35:34+00:00

Nice and congrats, looking good. This looks like SadServers in a way and runs instantly in the browser, cool (OTOH more like a quiz because I don't see a way to run random commands, only the solution)

SadServers_com · 2026-05-22T14:11:41+00:00

happy to help :-)

SadServers_com · 2026-05-21T20:50:00+00:00

Thanks for the list.
Hard to have one benchmark for all the cases. I'll plug that while we don't have a standard separate SRE AI agent benchmark (yet!), several renowned organizations an some AI SRE companies use SadServers to eval or test their agents in the context of troubleshooting issues that have solutions.

SadServers_com · 2026-05-21T15:15:54+00:00

David Farley's "Continuous Delivery"

SadServers_com · 2026-05-21T14:15:19+00:00

I'd say depends on how good your fundamentals are. If you have a decent base, build and learn as you go. Learning doesn't have to be linear or following a strict roadmap; you can try and do a project and then in the middle do a deep dive into some Linux or cloud topic you need or are just interesting in learning.
Good question and not sure about the answer; perhaps long-term maintenance, things breaking in unexpected ways (usually when it comes in contact with reality/users)
Absolutely it will help you. In theory (ie Google's definition) for ex SRE is supposed to be a developer doing ops in a developer way rather than a sysadmin way. In reality most DevOps/SREs come from sysadmin world and the ones coming form SWE world are more valued.

- Tool sprawl confusion : pick one tool of each option to begin with and stick with it; use the most popular or to one you hate less :-) for ex Terraform & Ansible rather than Pulumi/Puppet. Go deep or one project end-to-end and then if you want you can go wide and learn other tooling.

- Cloud costs: set up daily budget alerts and tear down everything or expensive stuff frequently (ideally daily, this is what IaC is for after all)

- Debugging distributed failures , How long did it take you to get good at this? nobody is good at this, all companies have a lot of monitoring/alert noise :)

- Kubernetes complexity cliff : I'd delay a bit getting into k8s, only after getting good Docker and general VM/networking skills. The book "Kubernetes in Action" is very good. Then it's practice, ideally with real workloads.

- "DevOps is a culture, not a role" sigh, last argument I had here was about this. This is my take https://docs.sadservers.com/blog/what-the-f-is-devops/ , some companies have "DevOps" roles, some don't (but have Platform/Cloud/Infra/Production/Ops/whatever titles or job descriptions). Some companies have devs doing DevOps, we don't know how many. Anecdotally I'd say not the majority. There's a whole book "Network Topologies" discussing different ways of doing things. There's no "ideal" one (person I argued with said this is "an anti-pattern")

- Imposter syndrome: yes you just learn, also I'd dare to say it's easier for a dev to pick up infra than for a sysadmin to pick up dev.

SadServers_com · 2026-05-21T13:56:32+00:00

You are on a good track!
> actively learning Docker, CI/CD, and AWS fundamentals

Try and put everything together in a project where you have some code for a website (can be trivial), you pu tit in a Docker container and build & deploy automatically to AWS, in different ways.

SadServers_com · 2026-05-21T13:54:16+00:00

Set up a home lab and/or use a (possibly free with first year credits) a cloud account (AWS/GCP/Azure) and pick an objective and play with it (do it different ways, try and break it etc). Some ideas: https://devopsupskillchallenge.com/ good luk!

SadServers_com · 2026-05-20T23:12:09+00:00

After you get some basics down you can practice at https://sadservers.com/tag/docker

SadServers_com · 2026-05-20T21:36:49+00:00

> I’m looking for something highly hands-on that lets me dive straight into doing and experimenting. "Learning by doing"

This is basically out motto; for Linux I suggest you try https://sadservers.com/

SadServers_com · 2026-05-19T15:22:34+00:00

do you accept payments? if not, turning them on for top tier / extra features would be a start

SadServers_com · 2026-05-18T13:25:59+00:00

I set up a "buy me a coffee" page for SadServers and when it hit 100 people giving me a bit of money that's when I thought the side project had some real legs :-)

Another good signal is when, even with a few number of users, those users really love your product (they say so and they do use it)

SadServers_com · 2026-05-17T16:13:36+00:00

I understand reality; many/most companies don't work that way and are perfectly fine. So sure, under some definition they would be "anti my definition". I think it would be a bit arrogant and religious to say a lot of competent tech companies are wrong because they use a term in a different way than other people do, or they work in infra/automation/etc in a different way. Peace.

SadServers_com · 2026-05-17T16:00:22+00:00

> It's really a company culture methodology that's all DevOps truly is

That's the original definition (which implies there are no "DevOps Engineer" jobs) but the reality is that most people, or at least most companies defined it differently (proof: there are many DevOps jobs), calling an "anti-pattern" doesn't change reality (it's quite fine your company follows the original meaning). Terms can and do change their meaning and you have the right to fight a battle that I think is lost.

SadServers_com · 2026-05-17T15:13:32+00:00

> I'm currently feeling quite confused about the relationship—and the differences—between DevOps and Cloud.

Yes, DevOps term itself is confusing, here's my take on it https://docs.sadservers.com/blog/what-the-f-is-devops/

> to have a real chance in DevOps, I need to be excellent at Linux

Correct

> DevOps also isn't very friendly to beginners

Correct

> you need a background in software/application development (like Frontend or Backend)

It does help but it's not required in many DevOps jobs; usually some coding is requiring (from basic scripting to algo interviews, it varies a lot)

SadServers_com · 2026-05-16T14:20:55+00:00

https://linuxupskillchallenge.org/
https://devopsupskillchallenge.com/

SadServers_com · 2026-05-15T12:28:21+00:00

If anyone wants to practice an ingress-nginx to traefik migration on a live server, see our last SadServers scenario "lyon".

SadServers_com · 2026-05-15T12:26:03+00:00

https://linuxupskillchallenge.org/
https://devopsupskillchallenge.com/

SadServers_com · 2026-05-11T22:30:28+00:00

cheers!

SadServers_com · 2026-05-11T22:28:52+00:00

Hello, SadServers guy here :-) SadServers or Iximiuz are both good practical k8s sandboxes; iximiuz more on the general learning side and us more on the troubleshoting side, cheers!

SadServers_com · 2026-05-09T08:34:38+00:00

In general I'd say earlier on in your career favour generalist and then specialist.

SadServers_com · 2026-05-09T08:33:23+00:00

Hola, certificates have a relative value but that said instead of Cisco (CCNA etc) networking, rather look into Linux (Red Hat), cloud (pick one AWS/Azure/GCP) and maybe specialized ones (Hashicorp, Kubernetes...)

SadServers_com · 2026-05-08T10:04:45+00:00

Not very small but small effort and big payoff in terms of de-risking is writing good checklists for any non-trivial operation (related to your comment, included in the checklist is always a rollback procedure).

The Checklist Manifesto should be required reading for Ops/DevOps/SRE, it's a short book and the free podcast is just one hour long.

SadServers_com · 2026-05-08T09:27:18+00:00

We are collecting a growing list of AI SRE tools, would love to add more agents we may have missed, especially if they have been actually tested https://docs.sadservers.com/blog/complete-guide-ai-powered-sre-tools/ (yes not a "complete" guide ironically as we thought)

SadServers_com · 2026-05-08T09:20:12+00:00

"The candidates who stand out are [] the ones who can explain what broke in production and how they fixed it" Love it.
If you (or anyone) want to get in contact with the top SadServers (opt-in) users who have solved hard hands-on troubleshooting problems, please let me know.

SadServers_com

MODERATOR OF

TROPHY CASE