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.

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 <dev> 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.

All the electronics inside are very much capable of combustion.

Your power supply inside the printer body for example can very much fail and burst into flames.

And tbh it’s not that uncommon for that to happen with 3d printers. They’re often made with very cheap parts and prone to cheap work on the inside bits.

Add on how much of a high wattage load they meed to handle for extended periods of time and yeah, sometimes the inner wiring bursts into flames and the whole thing goes up.

I always recommend keeping a cheap lil smoke alarm directly overhead any 3d printer, seriously. Those fuckers can very much spontaneously burst into flames lol

None of this stops the risk of fire.

Once a fire starts, the printer turning off won’t magically stop the fire from continuing to grow.

Printers can fail in all manner of ways.

Also, you should have a venting solution of printing ASA.

It’s pretty cheap to get a proper fire resistant heat cover for a printer.

Just get an emergency “space blanket”, they’re often only a couple bucks and quite good, but very fire resistant.

Sometimes its a physical issue in your setup.

Double check your cable, double check the carriage, and double check the rails, look for potential obstructions.

I had one print that kept failing in the exact same place each time, couldn’t figure it out, then I watched it live and the dang ribbon itself was physically catching on a specific part of the geometry mid print and then the print would twist a bit, lol.

Something to consider, I’d recommend visually watching that specific layer when it’s coming up to see if you see something happen.

I find it weird how much people give a shit about what consenting adults do for pleasure in the comfort of their own homes, and to their own bodies.

If they are an adult, it’s their body and their choice.

And if their choice is to cosplay as a child and bang an older person because that’s what gets their rocks off, I really don’t care.

It’s honestly not even the most outlandish of fetishes I’ve seen. We got people out there that orgasm from popping balloons, eating shit, and getting kicked in the crotch.

This is already to some degree an existing dilemma. There are already individuals out there who, due to genetic lottery, happen to have an adult body that through some efforts of clothing, makeup, hairstyle, etc, can very much present themselves as substantially younger looking than their actual age.

Lord knows certain popular niches in the porn industry make this apparant… >_>;

And from what I have heard on social media, sometimes these individuals couple up with another person who… doesnt look substantially younger.

And often, these couples face quite a bit of controversy and social stigma, despite everything they are doing and into being 100% legal and, from am objective standpoint, ethically fine (they are two consenting adults after all)

But I agree that future tech with things like gene editing and whatnot this dilemma will certainly become substantially more pronounced and I think it will likely be yet another group being attacked for daring to live their lives.

Lasse is the original maintainer of XZ, they have been placed back in their position as sole maintainer.

“Jia Tan” was the person who slipped the backdoor into XZ and is now banned.

Lasse has already fixed abd removed the backdoor.

XZ itself is critical software everyone uses (its one of the main compression/decompression programs used on linux)

but the best way to avoid getting them is still to just avoiding stupid shit.

This is fine and dandy on a personal pc, but in a work environment you are now being actively targeted by malicious actors if your company is a good target.

Constantly.

So once you are in that zone you do need some fast acting reactive tools that keep watch for viruses.

Nowadays it’s less of an issue with docker and whatnot.

Just set the image to refresh every night at midnight and if they tried to make manual changes it’ll just revert back to its original state at midnight.

Customers don’t really get direct access to deployed code now, it’s buried under like 4 layers of abstraction on most CDNs now.

Simply deploying to azure already smears multiple layers of access control and RBAC overtop that it’s hard enough for me, the dev, to answer the question if “what is actually deployed atm?”, let alone for the customer to get in their and meddle.

There aren’t standardized screens for smartphones, as the inside of the screens typically has a bespoke aluminum chassis they are adhered to as part of their construction.

And since every single phone model has different insides, every screen is bespoke to its model.

You have to look on ebay for your phones screen model.

If you look for ones with a couple dead pixels they are pretty affordable though.

For casual users I typically recommend using Cinnamon Desktop, it’s the most Windows-esque UI and will be the easiest for them to pick up and use.

I roll with Cinnamon on Ubuntu and it’s been extremely painless, very simple to get stuff do and shit just works.

This one is really interesting. Primarily speaking ants a good example of where this type of genetic expression is taken to its logical extreme.

It’s basically the “aunt” and “uncle” survival trait that shows up in communal creatures. Homosexuality shows up in creatures that both need to raise their young and stay together in herds. So humans of course very much satisfy this condition.

So how’s this relate to ants (and bees and termites too)?

In a colony, technically speaking everyone is the queens offspring, so everyone are siblings.

The queens aletes (prince and princess ants if you will) are only the queens offspring, all the drones dont sexually reproduce.

Yet, the drones all care for the offspring as if they are their own, that’s kinda weird from a survival standpoint right?

Well it’s simple, the drones are clones of the queen, so they also heavily share genetics with the offspring. From a genetic standpoint there’s no difference.

So if the drones take care of the offspring like their own, and the offspring go on to mate, then the drones genetics also propagate. They have a evolutionary pressure to raise the babies despite not having any of their own.

The same occurs for homosexuality. Human babies are a lot of work to take care of, and if you have a sibling you share a lot of genetics, then you have an evolutionary pressure to take care of your nephews and neices. It’s the “next best” option to propagating your own children. The genetic difference isn’t much worse.

So what ends up happening is you have an evolutionary benefit if a percent of your population is born homosexual, as they will help with raising their nieces and nephews, and it turns out this combo has a net higher survival rate than just everyone being hetero.

So over thousands of years we get this gradual pressure to settle on a sweet spot of some % of us being gay.

This is also a solid explanation for the “fifth brother” thing, where every son a mother has is exponentially more likely to be gay. We haven’t fully isolated what causes it (its prolly hormones) but it’s a well known occurring phenomina that the more older brothers you have, the more likely you are to be gay.

Based on the above supposition, it’d 100% make sense from an evolution standpoint for mothers to produce homosexual offspring if they have multiple healthy children, as after a certain point it makes sense strategy wise to have a couple gay uncles/aunts that naturally help their older siblings with childcare.

It’s just way way better for survival in nature if not everyone is pumping out babies, and a handful just aren’t into that but still take care of their family.

Basically it’s quality over quantity!

Mature women is straightforward, older = more knowledge and capable.

Pretty much everything else you listed is about trust, so I’d say that trust is a very big thing you value in a partner, and due to humans very long time they spend dependant on parents and our community survival strategy, trust is very much a trait that is selected for.

People that are untrustworthy are unattractive, a lot of kinks primarily build on top of publicly shameful acts in private, which is effectively the ultimate trust fall exercise.

Feeling like you can trust a partner with such acts is very very positively reinforced genetically, so it becomes sexually attractive.

In short: because humans live together and make complex communities, trust is important, which means getting kinky is very sexy as it signals deep rooted trust.

I feel like this is more “how we feel we get perceived by others” moreso.

I try and perceive all the members of my team as, well, my team. I heavily appreciate everyone busting their assess off and contributions.

However, there are folks on each layer that do actually treat others like this and I think we can all agree those people suuuuck.

“Small” breasts typically are still large compared to a man’s chest.

There are other factors than size anyways, for any feature. For breasts as an example, symmetry, skin clarity, and firmness will also signal a healthy prospective mate.

“Small” breasts usually actually means “not sagging due to age”, as naturally speaking breasts, cheeks, and the neck of humans are common areas where sagging due to collagen levels can be witnessed in older age, so these are common cited areas of sexyal attraction.

So “small” breasts really just means “not old”, which is fairly normal to signal the health of a potentional sexual partner.

To activate monkey neurons, it has to be an indicator of health.

As an example, large breasts indicate health, as malnourishment during adolescence tends to result in smaller breasts later on.

Muscles indicate health as well, so they tend to be considered attractive.

For non health related features, like a symmetrical face, those ones are the non sexual dimorphic characteristics, as those ones you care about transferring regardless of sex. Both men and women want a symmetrical face, basically.

So a large Adam’s apple is both a dimorphic feature and a non indicator of health, so its ignored.

There’s not really a nice way to frame “your post sounds like it was written by an extremely cringe teenager trying to cosplay as their idea of what constitutes a professional dev, demonstrated by the classic combination of ignoring everything prior written, attempting to represent a ball of mud as a badge of honor, and unironically trying to use lines of code count as a metric to measure by”

Literally checked off all the “lol sure bud” boxes in a single statement, and then if you aren’t picking up on the nuance, let me explain what I wrote after:

I hope you understand later how incredibly cringe what you wrote is, because the day you do is the day you have likely matured enough in knowledge and skill to call yourself a professional unironically, which is a good thing.

Until that day, stop prostrating shit like what you just wrote above if you ever want any developer worth their salt to take you even remotely seriously, otherwise you will likely find yourself the laughing stock very quickly of any serious circle.

Best of luck out there, and finally:

Next time someone is giving extremely useful advice, just write it down, don’t shit talk. That’s without a doubt the #1 divergence that separates the path between long term failure vs success.