• 6 Posts
  • 51 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle
  • The base OS of Android is, but the widely dispersed version maintained by Google with the hardware drivers required for it to work with the actual hardware is not.

    That’s why projects like Graphene can’t work on every phone. They have to rely on either reverse engineering hardware drivers or the manufacturers providing the drivers. For many years, Google openly released the drivers for all the hardware in their Pixel line of phones, which allowed Graphene and other customized versions of Android to easily work on Pixel phones.

    Manufacturers usually don’t release drivers separately and instead they’re only available built into the manufacturers customized Android version. Android Open Source Project is the open source base, then Google builds their proprietary stuff on top as “Android”, then the various phone manufacturers build their own versions on top of Google’s “Android” with: manufacturer specific crud added, phone specific crud added, and often phone carrier specific crud added.













  • That was always my assumption of the end game. You have the system prompts, an advertising bias prompt layer over top, then the user prompts.

    “Naturally worded” advertising that doesn’t immediately appear to be advertising and searching using natural language always seemed to be the biggest use cases for LLMs to me, considering they can’t be relied on to output accurate info.



  • Rookie mistake. The password is what we write on a sticky note and tape to the edge of our screen.

    Birthright membership in the Domain Admins group is what keeps all our users from being pestered when they want to install that neat new tool they found. Then you don’t need to harden the built in admin account against attacks, you can just disable it!


  • It’s not always for lack of trying. I spent a year or so building the integration (from a box of scraps!) between the shiny new HR system and our IDP. This integration was supposed to be functional out of the box according to the HR system salesgoblin. It didn’t just need to be configured, it needed to be built from scratch because they didn’t actually support hybrid AD/Entra setups managed from the AD side. Which was only the unofficial standard for Windows based shops at the time.

    Anyway, I wanted to make it grant employees access to shit based off a combo of Job Title and Department. On a technical level, it’s basic baby stuff. Concatenate the Dept and Title into a string, use that as the key to a hashtable with the access they need listed. Bish bash bosh, bob’s your uncle.

    It would have been a cakewalk compared to all the shit I had to build for handling separations and all the data retention shit around those.

    But none of the department managers could actually tell us what the fuck their workers needed access to. Like maybe 3% had any idea at all. And I didn’t have the team or time to try and do data analytics across the access of everyone at the company just to get an unreliable best guess.

    So it just handles setting new hires up with the basic access everyone gets and separations. Still a savings of ~1 hour per employee.


    It’s been something like 7 years since I built that integration. They’re finally going to replace it with a true access management platform. It’s cost them multiple millions so far, has an entire new department dedicated to the thing, it has been “in-progress” for two years, and it still hasn’t replaced my shit yet.

    My favorite part is when they come to me months in to something they’re trying to get working, and I’m able to point them at where they made mistaken assunptions at the first step leading to the mess they’re currently in.

    I provided a ton of in-depth notes on our current standards, the weird gotchas/deviations, every single stumbling block and edge case I had found, all the seemingly logical and safe assumptions that don’t actually hold. I don’t think they read any of it. I keep asking them to reach out before they start working on a new piece of functionality. They don’t.

    So now I get to tell them things like “that assumption you built this piece of logic off of will bite you in the ass in this specific way”, they say they’ll take it under consideration, and I laugh knowing this whole project will probably implode under the weight of incorrect assumptions before it’s finished.