• 0 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: June 18th, 2023

help-circle














  • Been using pixel phones for that reason, since… Pixel XL, and six pixel phones since then. Used several different AOSP based OS-es, most recently CalyxOS on Pixel 4a, and then GrapheneOS on Pixel 6a and now the 8 Pro.

    Everything works, and you can choose how much of Google you invite back in. The best part is that the Google stuff doesn’t get any special treatment. Which means that the Pixel Camera app and Google Photos isn’t allowed access to Internet, because why should it?

    The only thing that is still fundamentally flawed, are remote push notifications. And I don’t mean that it’s flawed for GeapheneOS, they work fine. It’s flawed in the sense that information goes through Google or Apple. The privacy concerns there are significant. It’s not end-to-end encrypted. You cannot avoid the problem either by disabling them on your phone. Each application, be that a Ring Camera, or backend messaging system, etc, that sends the stuff to Google through notification apis, will do so regardless of how much you sandbox or disable those services on the phone-receiving end. Conveniently, there is no effort by Apple or Google to make this core functionality any less tied to Apple or Google. The “asynchronous” nature makes it a problem that needs to be solved for each and every backend service system, for remote notifications. Some privacy conscious apps/services might let you limit what is sent to Google so you only get “New message from Hubbie” instead of also “Hubbie: remember to buy the paint for the baby-room! I’m so excited”.

    Anyways… Not sure why I went on such a long tangent. I was done pooping a while ago.

    CalyxOS on a Pixel is as great as it currently gets. But stuff can get better.




  • Only losing a week on a major change is a good sign. I wish the people who started the project had that same attitude with regards to clarifying requirements. They also did the opposite of designing a flexible solution. No thought to the actual problem, picking a contrived problem to “tackle”. Full on blinders on event driven architecture, split a simple thing into multiple nano-services, yet tightly coupled by sharing the same model which is de/serialized at every step, and then throw in application level filtering on the events… no schemas, no semantic versioning.


  • waiting for solid requirements

    This is exactly the situation. Except that my team consisting of consultants just “started”, instead of trying to scope out the constraints and larger picture. I joined a month or so after.

    Six months, and the result so far of their exploration is a fairly uninteresting happy-path use of some technologies, barely related to the task that had unclear requirements. Turns out the work done is unsuited for it. Boggles the mind how much resources are wasted on such things.

    Feels extremely unrewarding to have worked, relatively hard, for half a year, and the fruits of my labour is… getting to the point where the actual problems are solved. Which one could have done from day one, if one had started in a team without wrong preconceptions, or, no team, for that matter.