Programming

17506 readers

32 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

snowe

Ategon

[email protected]

108

i wanna have fun programming again (self.programming)

submitted 1 year ago* (last edited 1 year ago) by pugsnroses77 to c/programming

53 comments fedilink hide all child comments

after a grueling 4 years of school and a bit of time at a fintech company ive lost almost all the enjoyment i once had for computers in high school. what kind of projects or whatever can i do to have fun again without feeling stressed.

edit: thanks everyone for such creative suggestions!! anything else on the internets just like build a trivia game teehee but yall put real thought into this shit, thank you!!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

We focus a lot more on production than the average developer. It's our job to make sure whatever devs build is run quickly, efficiently, safely, and scalably.

You will work with a lot of kubernetes, Argo, terraform, Prometheus, grafana. You'll design build pipelines and software rollout strategies. You plan for zero downtime migrations and upgrades, database maintenance.. You'll have your hands in everything from capacity planning to security to cost optimization to developer support.. User permissions, infrastructure, networking, observability.. You will write RFCs and setup POCs for new tools. You define and track error budgets and figure out how to keep your org under those projections. When there is an outage you will be involved in writing post mortems.

The days are so varied and unpredictable that it keeps things interesting. The landscape changes so often you're never really stuck doing the same thing over and over.

I genuinely love it.

EDIT: The SRE Podcast from Google is actually really great for learning about this world. The first season talks about what you'll be doing and why (based around the SRE O'Riley book). The second season talks about what to expect in different stages of your career progression.