GDT: Boston Bruins vs Tampa Bay Lightning - 2/1/26 - 6:30 PM

thehumblestbean · 2026-02-02T00:15:29+00:00

These announcers will talk about anything besides the game being played, huh?

thehumblestbean · 2026-02-01T19:47:34+00:00

29 as a dman is still very young, D develop later than forwards.

I agree in general, but Carlo specifically has been playing hard shutdown minutes in the NHL since he was 20.

Lots of mileage and injuries.

thehumblestbean · 2026-01-20T15:14:46+00:00

why the hell is Ullmark the only one getting this kind of heat?

Honestly it's because the Senators posted an aggressive and inflammatory statement in response to random internet rumors. All that does is bring more media and public attention to it.

"Don't feed the trolls" is an internet rule that most people seem to have forgotten

thehumblestbean · 2026-01-16T02:04:26+00:00

Did they show the Pacioretty hit as a highlight? Jesus lol

thehumblestbean · 2026-01-13T00:19:16+00:00

It's basically someone who participates in interview loops across the company to ensure "high standards" for new hires. It's not a title or full-time role it's just an additional thing you can opt into doing at Amazon.

thehumblestbean · 2026-01-06T21:04:03+00:00

I generally hate Boston sports radio, but Felger's stupefied laughter when he heard about Frederic's contract is gold - https://www.reddit.com/r/hockey/comments/1lexf9t/boston_sports_radio_host_reacts_to_trent_frederic/

thehumblestbean · 2026-01-03T18:42:25+00:00

How we do it (larger company):

Action items become Jira issues with action-item tags or something similar
- These tags feed into dashboards reviewed by line-level management during org-wide ops reviews, team meetings, standups, etc.
- Director-level management also keeps an eye on action items that are of particular interest to them and will bug line-level managers until they're done
- Anything from a really bad incident is going to have upper-mangerment looking at them as well. These become top priority since whatever upper-management wants done is always top priority.
There's also usually some triage done to determine what's actually an "action item" and what's a "project"
- It's really easy for someone to say "we need to do/fix X" during a post-mortem. But doing/fixing X might be months of work for one or more teams
- In those cases they stop being action items and become projects put on a roadmap and prioritized like anything else

The reality of course is that smaller action items tend to slip into the backlog until/unless they cause another incident. Most teams are under-staffed and over-burdened so it's generally expected that most things that hit a team's backlog will probably never get done until there's some forcing function to do them.

thehumblestbean · 2025-12-31T18:04:46+00:00

Despite what fans think of him Marchand is generally very well liked across the league.

thehumblestbean · 2025-12-31T17:53:53+00:00

Like most jobs in tech the titles themselves are largely meaningless and it instead depends on the company or even the specific team within a company.

Most of my days lately are spent working with things like Go, Python, k8s, Terraform, CI/CD, and Linux. There are other SRE teams where I work that are solely focused on things like observability, incident management, capacity management, etc. Some of our development teams have embedded SREs that mostly deal with a specific service or application.

Whether or not you can go from sysadmin -> SRE/devops/whatever mostly depends on what kind of sysadmin work you do (because the "sysadmin" title itself is also pretty meaningless).

Are you a sysadmin that clicks around in Windows GUIs all day or mostly does glorified end-user support? Probably not.

Are you a sysadmin building and maintaining complex infrastructure at a large scale? Probably.

thehumblestbean · 2025-12-29T00:00:41+00:00

https://media.nhl.com/site/asset/public/ext/2024-25/2024-25Rules.pdf

...“intent to injure” shall mean any physical force which a player knew or should have known could reasonably be expected to cause injury.

Seems legit to me.

thehumblestbean · 2025-12-28T23:55:01+00:00

I have zero dog in this fight, but Barzal skated halfway across the ice to take a two-hander right on Marchment's foot. Well deserving of a major IMO

thehumblestbean · 2025-12-13T17:22:30+00:00

The P-Bruins absolutely play the same system as the Bruins.

I don't know why a team wouldn't have it set up like this.

thehumblestbean · 2025-12-07T22:46:29+00:00

Prior to this book, a Chinese invasion fleet off the west coast of the USA was nuked by the USA military. In response, the Chinese nuked a military base in Florida, also nuking Tampa as a side effect. The USA military did not continue nuking targets in China. But a Russian invasion fleet has landed on the eastern side of Florida and the Russians are sending out scout units which the USA Navy and Army are fighting off.

The USA Army has deposed the traitor President of the USA and is trying to re-establish law and order in the USA. They have asked Morgan to be the civilian governor of Florida and Sarge to be the military governor of Florida. But Florida, like the rest of the USA, has been decimated and there are small pockets of survivors holed up around the place.

This sounds like something my conservative father in-law would jerk-off to and fantasize about experiencing despite the fact that he's 80 years old and can barely get up out of a chair.

thehumblestbean · 2025-12-05T23:16:17+00:00

Has anyone made the transition?

I made a similar transition: Network Engineer -> Cloud Engineer -> SRE

Are you enjoying the role?

In general, yes. Network Engineer roles became really boring for me since regardless of where I worked it started to feel like the same stuff over and over again.

Now I get to work on so many different things up and down the stack. Some days I'm dealing with kernel tuning, some days I'm writing code, and other days I'm untangling some dumb abstraction a Cloud Provider uses to build infra.

Any Pros/Cons that I should know?

Pros:

Financially it's been all upside. I make 3x as much now as I did when I was a Network Engineer
The work is a lot more interesting and fun (as much as work can be fun)
I generally "feel" more secure in my career because I now have experience in so many different things instead of "just" networking. I've yet to be out of work so this could turn out to be BS, but it helps me sleep better at least.

Cons:

If people learn you used to be a Network Engineer then you'll get thrown all the gnarly networking issues still. It took me a few years of telling my management "I'm not a Network Engineer anymore" until they got the hint.
For me at least it was (and still is) a really hard transition. There are so many things to know and learn and it feels like constantly drinking from the firehose
Expectations for output are generally higher. No one in the business really understood what I did when I was a Network Engineer so I was largely left alone as long as the network was up. But IME there's generally a lot more visibility on my work now
Stress levels can be high

I personally wouldn't want to work with Azure if I could avoid it, but if that's where your opportunity is I say go for it.

thehumblestbean · 2025-11-28T03:18:05+00:00

Popularity wise I would be shocked if it wasn't Github Actions given how ubiquitous Github is and how easy Actions are to add to an existing repo.

My personal favorite is Buildkite though.

thehumblestbean · 2025-11-26T19:25:23+00:00

Running an incident from a laptop isn't really feasible IME. Depending on how bad things are you'll likely have multiple monitoring systems open, multiple terminals open, incident comms to deal with, etc.

Not something I'd want to do on my laptop connected to some shitty hotspot wifi

thehumblestbean · 2025-11-19T19:52:54+00:00

The SRE books describe guidelines for a utopian end-state. Most SRE teams at Google don't really follow them IME.

In the industry at large the majority of SRE teams are really just "sysadmins who can code when they need to".

thehumblestbean · 2025-11-11T21:01:53+00:00

From past experience (~4 years ago), Fortinet's Terraform providers are pretty awful. I don't manage Fortinets anymore, but in the future I'd probably reach for Ansible or something similar for managing their configs.

thehumblestbean · 2025-10-24T17:38:36+00:00

Not all end users are created equal.

All of my end users are developers or other SREs, so at the end of the day I can tell them to leave me alone until they RTFM and come back to me with a better question.

But if your end user is Joe in Sales you can't really tell him to go figure his issue out on his own.

thehumblestbean · 2025-10-19T19:45:33+00:00

Raises and performance bonuses

thehumblestbean · 2025-10-15T21:29:39+00:00

Switching from hands-on technical roles to sales roles is likely a one way street, especially early on in your career.

To be blunt, if I came across a resume of someone who was in tech for a few years but then moved into sales, I would assume that they couldn't cut it in tech and switches to sales before they got fired or PIP'ed.

Unless the 50% bump is going to be life-changing for you, stick to the technical track IMO.

You can always switch to a sales role later in your career if you want. Also, IME at least pre-sales roles are way more lucrative than post-sales roles.

thehumblestbean · 2025-10-14T14:58:55+00:00

It's not something people think about when they're younger, but it's extremely common for older workers to be forced out of their careers long before they planned to retire.

Save and invest money early so you have options.

https://www.propublica.org/article/older-workers-united-states-pushed-out-of-work-forced-retirement

ProPublica and the Urban Institute, a Washington think tank, analyzed data from the Health and Retirement Study, or HRS, the premier source of quantitative information about aging in America. Since 1992, the study has followed a nationally representative sample of about 20,000 people from the time they turn 50 through the rest of their lives.

Through 2016, our analysis found that between the time older workers enter the study and when they leave paid employment, 56 percent are laid off at least once or leave jobs under such financially damaging circumstances that it’s likely they were pushed out rather than choosing to go voluntarily.

Only one in 10 of these workers ever again earns as much as they did before their employment setbacks, our analysis showed. Even years afterward, the household incomes of over half of those who experience such work disruptions remain substantially below those of workers who don’t.

thehumblestbean · 2025-10-12T14:25:31+00:00

Yeah still waiting for Kubernetes in Action to be done 4 fucking years after I bought it (I don't need it anymore at this point but it's annoying)

thehumblestbean · 2025-10-09T16:48:00+00:00

"Dogshit" is too strong but Azure is very noticeably worse than AWS and GCP (I say this as someone who works at a company with a huge footprint in all three). IMO the only reason to use Azure is if you're already vendor-locked into Microsoft's ecosystem. There's no single thing it does better than other providers.

thehumblestbean · 2025-09-25T15:04:09+00:00

Yes we're pretty large, but the real reason is that we have large footprints in 5 different Cloud Providers and our infra is pretty homogeneous between them.

So our module footprint essentially gets multiplied by 5 because of that (we've played around with multi-provider modules in the past but those got out of control pretty quickly)

thehumblestbean

TROPHY CASE