52
you are viewing a single comment's thread
view the rest of the comments
[-] fubarx@lemmy.world 10 points 2 weeks ago

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.

this post was submitted on 23 Mar 2025
52 points (96.4% liked)

Programming

19368 readers
207 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS