folkrav

Really bigger updates obviously require a major version bump to signify to users that there is potential stability or breakage issues expected.

If your software is following semver, not necessarily. It only requires a major version bump if a change is breaking backwards compatibility. You can have very big minor releases and tiny major releases.

there was more time for people to run pre-release versions if they are adventurous and thus there is better testing

Again, by experience, this is assuming a lot.

From experience shipping releases, “bigger updates” and “more tested” are more or less antithetical. The testing surface area tends to grow exponentially with the amount of features you ship with a given release, to the point I tend to see small, regular releases, as a better sign of stability.

That’s not “self hosting” related tho lol

I too had those hour long snoozefests where 99% of what’s said doesn’t pertain to my work, and those useless meetings that could have been a message on a Slack channel. I still feel like the sentiment is a very broad generalization based on some assumptions that may or may not apply well to every work environment.

My most recent project has direct dependencies between 5 teams just on the developer side, and multiple internal and external clients. Figuring out if we need to reach out to the stakeholders or figuring out who can help them on a particular task isn’t necessarily always that straightforward, depending on scope.

Anecdotally, the devs on my team were losing a lot of their time doing all that stuff before I joined as a tech lead in August. I spend most of my non-dev time (about 50% of my time, lately) shielding the rest of the team from stakeholders, pushing back when needed, pushing back on various demands, enabling communication lines, all to protect them from context switching and let them code.

And honestly… Outside all that, agreeing with me or not, is 15 minutes of human interaction that terrible lol?

we don’t need managers we need people helping us getting the tools we need and trust that what we do

The word “manager” is extremely overloaded and barely says anything about what that person does for its team without knowing how the company operates. Where I work, the person you’re describing would be someone in technical management.

Interesting… I’ve yet to see a team that didn’t have regular touch bases not having the polar opposite issue, being communication happening in isolated silos and resolvable issues taking too long to bubble up. YMMV, I guess.

They were both pretty popular 10+ years ago, so you may have been old for a while. Or you just don’t watch Marvel stuff and/or other more recent fantasy TV lol

Deborah Ann Woll played in True Blood, then was cast into the Marvel universe through Daredevil, then Punisher. Bernthal played Punisher in the series of the same name, and in The Walking Dead before that.

Adding types on an untyped project is hell. Greenfield stuff is usually pretty smooth sailing as far as I’m concerned…

The practice of calling a product “FooBar X”, unless it’s literally your version 10 that you just happen to be marketing in Roman numerals, feels a bit like those businesses that named themselves “Plumbing 2000”, it’s a bit tacky and doesn’t tend to age well IMHO. But hey, it’s not like it’d be the first software with a slightly kitsch name I use either lol

He specifically said “unit tests” though, which aren’t black box tests by definition