pixxelkick

A crew of people wearing clown makeup as an anti authoritarian crew of antiheros operating under the ultimate of anarchist clown boys in a dystopian cityscape sounds actually pretty familiar... where have I seen that before in popular media.... 🤔

My understanding is risk is low on this one as we already have a prepared and tested vaccine, and we have a known medicative treatment.

So it'd suck if it spreads but we at least have the tools to fight it on hand.

It's pretty likely they'll understand exactly what you mean, emotional manipulation tactics are timeless so they'll prolly be like "oh yeah there was this asshole my sister met who was like that, never liked him, pompous arsehole"

I go to a United Church up here in Canada, and it's similar. Giant rainbow painted on the sidewalk, fair number of LGBTQ+ members, affirming church, participates and supports the pride festivals every year, the loveliest most welcoming people I've ever met.

Might wanna read it again, it's right there :)

The best architectures, requirements, and designs emerge from self-organizing teams.

It's an incredibly critical part companies love to completely ignore.

If you assign devs to teams and lock em down, you've violated a core principle

And it's a key role in being able to achieve these two:

Agile processes promote sustainable development.

And

The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

This is talked about at length by the likes of Fowler, who talk about how locking devs down us a super fast way to kill sustainable development. It burns devs out fast as hell.

Note that it's careful not to say on the same project

That's actually a pretty important part of its original premise.

It's a big part of why scrum meetings were a thing, as the expectation was any curious dev could just join in to see what's up, if they like.

Not tying devs down to 1 specific thing is like the cornerstone of agile, and over many years of marketing and corporate bastardization, everyone had completely forgotten that was literally the point.

The whole point of the process was to address 2 things:

1. That client requirements can't easily be 100% covered day one (But you still need to get as many as you can!)

2. To avoid silo'ing and tying devs down to specific things, and running into the one bus rule ("how fucked would this project be if got hit by a bus?")

And the prime solution posited is to approach your internal projects the same way open source works. Keep it open and available to the whole company, any dev can check it out, chime in if they're familiar with a challenge, etc.

One big issue often noted in non-agile companies (aka almost all of them) is that a dev slent ages hacking away at an issue with little success, only to find out far too late someone else in the company already has solved that one before.

An actually agile approach should be way more open and free range. Devs should be constantly encouraged to cross pollinate info, tips, help each other, post about their issues, etc. There should be first class supported communication channels for asking for help and tips company wide.

If your company doesn't even have a "ask for help on (common topic)" channel for peeps to imfoshare, you are soooooooo far away from being agile yet.

I've literally never actually seen a self proclaimed "agile" company at all get agile right.

If your developers are on teams that are tied to and own specific projects, that's not agile.

If you involve the clients in the scrum meeting, that's not agile.

If your devs aren't often opening PRs on a variety of different projects all over the place, you very likely aren't agile.

If your devs can't open up a PR in git as the way to perform devops, you aren't agile.

Instead you have most of the time devs rotting away on the sane project forever and everyone on "teams" siloed away from each other with very little criss talk, devops is maintained by like 1-2 ppl by hand, and tonnes of ppl all the time keep getting stuck on specific chunks of domains because "they worked on it so they knpw how it works"

Shortly after the dev burns out because no one can keep working on the same 1 thing endlessly and not slowly come to fucking losthe their job.

Everyone forgets the first core principle if an agile workplace and literally its namesake us devs gotta be allowed to free roam.

Let them take a break and go work on another project or chunk of the domain. Let them go tinker with another problem. Let them pop in to help another group out with something.

A really helpful metric, to be honest, of agile "health" at your company is monitor how many distinct repos devs are opening PRs into per year on average.

A healthy company should often see many devs contributing to numerous projects all over the company per year, not just sitting and slowly be coming welded to the hull of ThatOneProject.

I feel like I often do 1 step above the farthest right, which is doing "guta", with the t very soft.

"I'mma "guta" go to te sto" is how it comes out when I say it quickly.

Not gonna lie very few teachers from my experience have the charisma in their teaching that an experienced Podcaster has on a topic.

I've had a couple for sure who I could listen for hours teach.

But many would just rattle off facts endlessly and wouldn't really engage.

It does mean something.

The skibidi toilet "creatures" are considered the antagonists, and the word is associated with their traits.

• creepy
• gross
• scary
• weird

Its an insult to and pretty much interchangeably with "creepy" with a splash of "cringe"

Often paired with "ohio" which means "bland" / " boring" / "mid"

Example:

"Yo he got that skibidi Ohio rizz"

Translation:

"This dude has zero game, in fact he is creepy and weird and has negative charisma, people find him repulsive and boring"

Are you implying they didn't have minivans in the 80s, lol?