arrjayh

~20 engineers, ~3 people managers. From what I recall the team had high attrition and shuffled through a number of people managers. When I joined 1 manager was new hire, 1 manager was new-ish hire, 1 manager was fairly seasoned at Riot and had a "good reputation". Was still a total mess.

> My experience at big corporate is that (edit: unmanageable) tech debt is caused by undisciplined and unorganized scrum team.

Yeah, this is 100% correct. I comically left Riot after ~6 months for this exact reason. Obviously it's a large company with many different flavors of teams, and it sounds like this team maybe has gotten it together, but by in large most haven't.

While I was there I was working on some of their core games tooling and felt uneasy about my day-to-day. My teams tech debt was quite literally owning them. Constantly missing sprint scopes, spending countless hours arguing and debating about trivial stuff, it was all a mess. They ended up laying off a number of people from that team in a pretty shifty manner so maybe things have gotten better since then.

Yes, you should absolutely care.

What in the actual, 6.2 GHz!? The power draw must be insane.

Do they really? that seems difficult to navigate

Probably because they couldn't hire effectively?

This is brilliant. I'm a mid-level engineer with decent C/C++/Rust background. Have yet to find a team like this. I'm inspired by your story to keep searching!

This is awesome! I've become preconditioned to seeing slow buggy demos. This is snappy and a great representation of HTMX. Good work!

I'm working through this exact situation right now, I really appreciate this insight!

Can't add much more than what's already been said here but I'm glad to see more presence of this on the internet. Grew up in IL, this was largely unspoken + alcohol and drug abuse.

I nominate SDL2 and DPDK. Spent a lot of time combing through these code bases, found them to be excellent.