• 1 Post
  • 153 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle

  • It’s heavily because you call out to your SO a lot, and their full name is a mouthful.

    Typically words like “babe”, “hun”, etc are the lowest effort pet name. The “b” percussive is one of the easiest to pronounce.

    Usually this is simply to make communication faster and easier, “hun” is way faster to say than whatever their full name is.

    This becomes do commonplace that after being together for many years, their full name is reserved for emergencies.

    Like if you cut yourself or are hurt or whatever, you instinctually use their full name to grab their attention and alert them. (People alert to their full name way easier and can hear it better)

    This results in producing an alarm “wtf?” response when you use it casually, it makes them whip their head up and their brain goes “is something wrong?”

    Then when they realize the situation is fine, it becomes a sort of “you spooked me for nothing! Don’t!” result.

    You effectively reserve the full name only when you are trying to get their attention.




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


  • 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”


  • 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



  • Unfortunately this is false. They’ve tested this and monkeys establish captilasm extremely fast when they come to understand currency as a concept.

    https://www.jstor.org/stable/10.1086/503550

    They would exchange the currency, steal it, gamble with it, purchase with it, and even do some prostitution for it.

    Edit: To people responding that this isnt capitalism, it actually is, in this case the privatized controller of wealth were the researchers distributing “payment” to the monkeys at a fixed rate, as well as having experiments where the monkeys had to pull levers before they would receive rewards either to themselves or later, altruistically to other monkeys.

    You would know that if you took the time to read up on the study before responding…


  • The one thing that sucks is this doesn’t cover gear stored in the extra mog… whatever it was called storage you could pay extra for.

    And you can’t pay just for that inventory, you have to pay for your account before you can pay to enable the storage.

    And finally, if you had important shit stored in those bonus inventories, you can’t access it til you pay for it

    Result: players that prior paid for and used the extra inventories basically can’t leverage the free login, they can login but can’t access their stuff unless they opt out of the free login and fully pay for the month + inventories…

    RIP


  • The fact that they prioritized Helluva Boss (which does follow that type of storyline), on their own YouTube (which they have control over), whereas Hazbin was put onto Amazon Prime with only 8 episodes honestly is what I think caused it.

    My gut instinct was to assume they had to agree to certain conditions to get onto Amazon Prime and the money from that is what got us Helluva Boss (which if you haven’t watched that, it’s so fuckin good)


  • It’s a musical, the songs are catchy.

    However I disliked how fast paced the writing was, and how even though it’s called “Hazbin Hotel” and the pilot framed it as a sort of slice of life “bunch weirdos” hanging out and getting redemption, instead that weirdly became the B plot?

    Somehow they took the whole story and shifted it over to the B plot and pulled this other big high stakes thing out as the A plot.

    That’s not really what I was wanting to watch, and it feels a bit like they hit swapped out the story on me, so I kinda got a bit turned off by that.

    I don’t give a shit about some high stakes angels vs demons war end game shit.

    I wanted to see interpersonal relationships of weirdos learning to co-exist.

    Tl;dr: I was expecting something closer to The Good Place, but instead that got side lined by some huge MCU style plot no one asked for.




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