Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)J
Posts
0
Comments
329
Joined
2 yr. ago

  • Processor architectures maybe. They put Rust into Debian and it's so bad that now e.g. amd64 is ruined forever for any OS and won't see any new processors in the future. We'll have to move to a different architecture. I didn't watch the video since I treasure my brain cells too much but that's what I choose to read into it.

    (A more reasonable reading is that Debian now ships a kernel that includes Rust code and coincidentally has also dropped builds for several obscure architectures but I do not feel obliged to assume reason with a title and thumbnail like that.)

  • Pushing to prod without review and breaking the running application is a resume-generating event in many companies. In many others it's not even possible because of programmatically enforced policies.

    If your company's response is not to prevent or dissuade it but to have other people work overtime to fix the mess then that's a major management fail.

    Try to educate your boss about best practices. This incident should give your arguments some more weight.

    Deployment to prod should not be something a developer can do by themselves; a proper CI/CD system can be configured so that prod can only be deployed to by people with an appropriate role (product owners or lead devs if your company doesn't have POs).

    If you don't have such a system, make it an explicit policy: Only Steve the lead dev (or someone specifically appointed by him while he's absent) can push to prod; if anyone else does it they get invited to an uncomfortable meeting with Steve. If they do it again the meeting will be with HR.

    But seriously, you should lobby for a proper CI/CD system (if none is present) and for the system to be configured so that a) you can't merge to the main branch without a code review and b) deploying to prod only works from main and with explicit approval by a PO/lead dev. That should stop most of the shenanigans.

  • Deleted

    Permanently Deleted

    Jump
  • No. Firstly, no means of contraception is 100% effective; stacking them further reduces the likelihood of unwanted conception. Defense in depth is your friend.

    Also, sometimes people can catch something without being aware of it. He might have an infection he's not aware of. You might have one. The condom protects both of you. If you want to do it without, get yourselves tested.

    And all of that is under the assumption that everyone is honest and has the best of intentions, which... isn't always the case.

  • And exist in a system that can only support two parties, which means that the most effective strategy is not to convince voters that your pictures are superior but to convince them not to vote for the other party. Cue a race to the bottom.

  • Well, the content is the same and it works the same as far as I can tell. I'm not terribly attached to the old domain name when the (rebooted) radio works just fine.

  • As long as the penguins haven't discovered warp drive, that is.

  • Again, possibly sensible in a vacuum but not a great move when you need the ship to work properly right now. Changeovers like this incur temporary inefficiency as new schedules have to be drawn up and adapted to. Showing up out of nowhere, demanding that everyone execute the changeover (planning and all) within several hours doesn't sound like a very good idea to me at the best of times, much less when the ship is going to do double duty with delicate diplomacy work and backup for a covert ops mission.

    And that's not the only time he pisses people off with no explanation. He shows up in engineering and demands a two-day death march project to overhaul the warp drive for no reason other than he thinks it should be more efficient. Sure, Starfleet engineers routinely deal with such circumstances but it's usually for a well-known reason and not "because I say so" over the active objections of the department head. And overworking the engineers doesn't sound very efficient in anything but he short term.

    I maintain that Jellico may have a decent understanding on how to efficiently operate a starship but he's not very good at actually leading a crew.

  • Fair points. I think in the end, given only what we see, neither of them seemed to have shown particularly good judgment.

    Jellico was temporarily given command over the flagship of Starfleet, which had so far performed well. He immediately decided to implement his personally preferred policies across the ship, which would've been fine if he had been given a long-term posting under normal circumstances but wasn't when he was temporarily in command during a time when the crew needed to perform reliably. Heck, he even had the fish removed from Picard's office despite knowing full well that it was a temporary posting.

    Riker was rightfully concerned about all this but took far too much leeway in dealing with it. Honestly, Picard wouldn't have acted much differently than Jellico by the time Riker flatly refused to do his job. Jellico might've acted unwisely in a professional sense and inappropriately on a personal level but Riker wasn't acting like an officer at all.

    It's like the two of them were trying to make a case study on how many different kinds of dysfunction you can cram into just two officers aboard a single starship.

  • I'd argue that upending the duty roster in the middle of a crisis is a bad move. You want people to perform optimally and they probably won't immediately do that while adjusting to a new schedule.

    Jellico's changes might've been sensible in a vacuum but I think that he tried making them at an inappropriate time.

  • Deleted

    Permanently Deleted

    Jump
  • Remember: If you're not part of the solution you're part of the precipitate.

  • Deleted

    Permanently Deleted

    Jump
  • My girlfriend got herself a pair and taped them to corners of her desk. She doesn't want to turn on the light when she gets up at night but she also doesn't want to bump into the desk. Tritium vials fit that use case well.

    Could we have gone with dimmable lights or something homebrewed with low-power LEDs? Sure, but tritium vials are affordable and don't need a power supply, a remote, or much in the way of setup; they'll just keep doing their thing for about a decade before you have to even think about their light output.

    They're a solid choice if you have the specific use case of wanting something to be easily located in (near-)complete darkness but you don't want to use electricity for some reason.

  • Unless other situations where the established technology wins due to inertia, sodium ion batteries have two benefits that make them interesting regardless:

    Firstly, they are safer. A punctured sodium ion battery doesn't catch fire, which massively simplifies safety design. That makes them very attractive for certain scenarios, especially ones where density is a secondary concern. That in turn means they get further development money instead of withering on the vine.

    Secondly, they require fewer hard-to-obtain materials, which makes them attractive from a strategic perspective. This one should be less important than the safety factor but it's also relevant.

    I'm pretty sure we'll actually see wet sodium cells in the wild if they are actually practical. Sodium ion tech is already being commercialized and if this brings it within the same ballpark as lithium ion then it becomes a very interesting choice for vehicles due to instant crash safety gains.

  • It definitely depends on the use case. I could accept this being abstracted out to facilitate mocking, for instance (although I'd recommend mocking at a higher level). But in general this wouldn't pass review with me unless I get a good explanation for why it's necessary.

  • Then they could add their own function in later stages. YAGNI exists for a reason.

  • My high school had a few unusual traditions around graduation time.

    The first related to our director, a man who gave his 100% on official school business and then gave another 100% on all of his hobby projects around the school. It wasn't that we had something like an apiary or a pond biotope. We had an apiary and a pond biotope and a herd of goats and a tiny vineyard (in an area mostly unsuitable for wine) and a shelter for emotionally disturbed aras. In a public school. And all that besides him being a highly respected director and teacher who epitomized the definition of "strict but fair".

    So at some point the students started to express their gratitude by giving the school presents upon graduation, usually themed around the director. The gym sported a Jurassic Park sign, except with the name of the school and with the profile of the T-Rex replaced with that of the director. In another year someone had contacts with the roads office and got something that looked like an official city limits sign made, except that it identified the school along with "administrative region <director's name>". Very cool; he took that one with him when he retired.

    Another tradition is somewhat common in the region: The "chaos day", effectively a formalized graduation prank. At my school, it worked like this: The evening before, the students were given a copy of the keys to the school and free access to the school grounds to prepare. The next day they had to prevent the teachers from entering the building; if a teacher got in, school would resume as per normal. The teachers had a fairly good track record. Many graduating classes failed to account for the fact that the teachers had bolt cutters. One time they didn't account for an obscure window at the back of the school, which happened to be an emergency exit and had an external lock.

    My year didn't take any chances. I come from a fairly rural area so we had farmers in class and those farmers had forklifts and hay bales. By the time school was supposed to start, all entrances to the building had solid walls of hay in front of them. We also immediately cashiered any teacher who entered the school grounds and forced them into party activities. I have fond memories of hearing my class teacher horribly butcher Oh my darling, Clementine before wandering off to listen to the school band play Hurra, hurra, die Schule brennt.

  • Oh yeah, same here except with a self-hosted LLM. I had a log file with thousands of warnings and errors coming from several components. Major refactor of a codebase in the cleanup phase. I wanted to have those sorted by severity, component, and exception (if present). Nothing fancy.

    So, hoping I could get a quick solution, I passed it to the LLM. It returned an error. Turns out that a 14 megabyte text file exceeds the context size. That server with several datacenter GPUs sure looks like a great investment now.

    So I just threw together a script that applied a few regexes. That worked, no surprise.

  • NSFW Removed Deleted

    Permanently Deleted

    Jump
  • Dude somehow owns a smartwatch where the step count and sleep tracker need to be operated manually. He might be too busy fiddling with that thing to get anything done.

    I wonder if he has to manually blink the turn signal on his car.

  • Speaking as someone who is currently planning to move a community away from Discord to something self-hosted, it's not as easily said as done.

    Apart from the need to run your own infrastructure, competing software is typically finicky and comes with caveats. Plus you have to worry about discoverability if you want to attract new users.

    It's doable, sure, but it requires a lot of planning and work. Honestly, it's probably going to take us months to get our own service fully up and running.