• 3 Posts
  • 561 Comments
Joined 1 year ago
cake
Cake day: July 4th, 2023

help-circle




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




  • I mean, that’s just how it has always worked, this isn’t actually special to AI.

    Tom Hanks does the voice for Woody in Toy Story movies, but, his brother Jim Hanks has a very similar voice, but since he isnt Tom Hanks he commands a lower salary.

    So many video games and whatnot use Jim’s voice for Woody instead to save a bunch of money, and/or because Tom is typically busy filming movies.

    This isn’t an abnormal situation, voice actors constantly have “sound alikes” that impersonate them and get paid literally because they sound similar.

    OpenAI clearly did this.

    It’s hilarious because normally fans are foaming at the mouth if a studio hires a new actor and they sound even a little bit different than the prior actor, and no one bats an eye at studios efforts to try really hard to find a new actor that sounds as close as possible.

    Scarlett declined the offer and now she’s malding that OpenAI went and found some other woman who sounds similar.

    Thems the breaks, that’s an incredibly common thing that happens in voice acting across the board in video games, tv shows, movies, you name it.

    OpenAI almost certainly would have won the court case if they were able to produce who they actually hired and said person could demo that their voice sounds the same as Gippity’s.

    If they did that, Scarlett wouldn’t have a leg to stand on in court, she cant sue someone for having a similar voice to her, lol.


  • There’s basically no reason to keep using windows.

    Debian or Linux Mint are both easy to install, work out of the box, and the only thing that might take a smidge of effort is the 3 commands you gotta run to install gpu drivers.

    Steam proton works incredibly well. I ran my entire steam library (most of which were “windows only” games) and even single one worked with proton as is without issues.

    I’ve been using steam link from my debian box for months now and it’s smooth as butter.


  • 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


  • Also even going with the flood theory, pretty sure Egypt comes after Noah even in the Bible itself >_>;

    The world did flood when humans were around (most cultures have great flood stories from ancient times), but that was way way before Egypt.

    Amusingly iirc the Nile nearby however is a great example of proof the earth once was covered in ice the melted and flood, as I believe it’s a giant striation or whatever the term is, huge gouge left behind by receding ice, no?

    That’s why it’s so big and runs so far, it’s ancient from countless years of erosion and meandering after being carved out during the ice age.


  • Well tbh Quests dont really bug you much about anything FB related. After you setup the account the only thing you deal with is the initial menu starts opened to the app store with suggestions based on what you already bought.

    But that initial menu let’s you also set quick access buttons for your favorite apps.

    So it’s only a single click to go from “put on headsst” to “open thing I want” usually.

    It’s not any different from steam starting you out in the store tbh, I can accept that level of advertising as it’s pretty transparent and half the time it has something of interest for me anyways.

    It’s about as big of a deal as a gift shop at a museum.



  • In terms of the erosion, doesn’t wind erosion on raised surfaces behave very similar to how water erosion on shores behaves?

    Since both are just fluids brushing up against surfaces, and the fact in the desert the wind will have a lot of silica dust in it, it stands to reason the wind currents around the pyramid would have very similar erosion patterns to water on a shore.

    Fluids are fluids, air doesn’t behave to dissimilar from the ocean, and wind is not to dissimilar from water currents in terms of the physics.

    Silica dust will kick up off the nearby dunes, carry in the wind, but due to its weight it’ll be less likely to erode higher elevations. So the tip top of the pyramid is high enough up sand in the wind won’t reach it as easily so it erodes way slower.

    Much akin to how waves crash on a coastline, water has weight so the higher an elevation is, the less and less sea spray it gets hit by, so it erodes slower.


  • Yeah its wild how people think that glyph depictions of legends on a wall (and people looking at that and going “Ah yeah, this is depicting a scene from their legends we have text versions of too”), somehow think we’re arguing giants were real.

    To that I just will say that it’s likely “giants” legends were just born through the simple fact way back in the day, people were a lot less homogenous and that people’s height had a lot more variation, due to how secular living was (instead of taking a plane to the other side of the world in a single sitting, you would take multiple days just to go 1 village over)

    As a result you had a lot less genetic “sameishness”, so you likely had some areas where people were a lot shorter, and then other areas where people were taller. In particular colder climates had shorter people, and hotter taller.

    Due to people’s nomadic natures, it’s pretty likely most legends of both “wee folk” and “giants” were just tall as fuck people from country A meeting up with short as fuck people from country B.

    We literally, right now, have humans who you can put em side by side and person A is over twice the height of person B.

    So yeah, it’s not hard to imagine if you had a whole family of tall ass people meet up with a family of short ass people, you’ll get through word of mouth (and a bit of story telling), you’ll get legends of “giant” folk.

    In particular the folk of europe, especially vikings who travelled quite far and wide, had some pretty fuckin huge populations in terms of height.

    And inversely we also had a fair number of fairly short and stout folk from other countries in the middle east.

    If one were to meet the other, I mean, it’s not hard to see where the legends would get spun from, lol