3 ms·
It really irks me when a big company like Meta tries to describe a new project as a startup created by a "nimble team of engineers". In the blog post they link
by treesknees 3y ago
It really irks me when a big company like Meta tries to describe a new project as a startup created by a "nimble team of engineers". In the blog post they link to [1]
>Threads was developed in an environment more akin to a startup.
OK sure, a small group of people broke the model of development and did something new from the ground up?
>Threads scaled successfully to 100 million users without any major downtime thanks to Meta’s underlying infrastructure and engineering foundations, which were critical to the successful launch.
Ah, no. All of the underlying hard parts were done already for them. That's not a startup.
[1] https://engineering.fb.com/2023/09/07/culture/threads-inside-story-metas-newest-social-app/ https://engineering.fb.com/2023/09/07/culture/threads-inside...
- sangnoir 3y agoThey never claimed their stack was startup-like, just the process. They are likely contrasting it with their usual[0] engineering practices: no focus-grouping, applying for headcount from 3 directors and making a 4-year roadmap after a gaggle of project managers finally agree on what to build. Perhaps its just one decision-maker and bunch if empowered engineers and no red tape - which would be very much be closer to startups, without denying themselves access to humongous datacenters. 0. Exaggerating some of the bureaucracy I've seen in larger orgs
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]