• 4 Posts
  • 62 Comments
Joined 10 months ago
cake
Cake day: June 7th, 2024

help-circle
rss














  • We gave our oldest a basic feature flip-phone when he started Middle School, mainly so he could text and coordinate pickups. In 7th grade, we gave him a smartphone because he was going on a class trip to DC and the kids were encouraged to take pictures and share. At home, we made it a rule that the phone had to be plugged into charger in our bedroom to avoid bedtime disruption.

    That same year I created social media accounts for him on every service, mainly to reserve his username. But they were all blocked using parental controls, based on advice from school. We also had software/hardware from Circle (now Aura: https://meetcircle.com/) that blocked access on wifi and cell and capped usage.

    In high school, when he turned 16, as part of his birthday gift, we gave him an envelope with his own non-school email account, and all the links and passwords for social media accounts. We also took away all the filter blocks. Figured he was mature enough without feeling left out.

    It really worked out well. Later, he asked to put usage limits back on so he would be forced to put it down and go to sleep.







  • Wonder:

    • How do they handle someone who may not be performing as well as others?
    • What’s the process for conflict resolution? Both professional and inter-personal.
    • Not sure if they’ve been through a big global recession yet. That’s usually when companies and their policies get tested.

    Not to take away from their unique model. Just curious how the idealism handles the messy parts of human nature.



  • At one point in my life I was working on a massive Android AOSP fork that itself had lots of variants for different downstream devices. Custom drivers, specialty services, etc. Thousands of people were actively working on all parts of it, and it had been around for at least a decade.

    There was incredible tooling around onboarding, local dev, testing, PR management, CI/CD, and post-release telemetry. Almost everything was automated. All code was reviewed at least once, and sometimes more for critical components. It was an immediate rejection if there wasn’t sufficient test coverage. Big subsystems took months to architect, build, and deploy.

    Nobody got to cowboy things and just push to release. It was much slower than a solo or a few people at a startup. The whole point was consistency and predictability, and you could see why.