2 ms·
I've worked at both relatively large (thousands of employees) and small (less than 10) companies. When I transitioned from small back to large-ish about 10 year
by ghaff 4y ago
I've worked at both relatively large (thousands of employees) and small (less than 10) companies. When I transitioned from small back to large-ish about 10 years ago, a couple things struck me. (Really, I was reminded of because I had worked at a similar magnitude size company previously.) There was so much "machinery" to support me in various ways. But the internal communications to take advantage of that machinery (and to inform stakeholders, the field, etc.) was a huge ongoing effort.
- rsstack 4y agoNot all large companies have so much machinery! While people think of MAGMA, maybe Capital One, Clouflare, etc. - there are many huge companies that aren't tech-first that have the internal communication responsibilities but without better developer tooling than small startups. That _sucks_ if you're the kind of person who's used to high personal velocity.
- ghaff 4y agoI was using machinery in a more general sense given I don't do development. For me, it's things like lots of marketing program people, public relations, analyst relations, competitive analysts, designers, editors, etc. They can offload a lot of work (and, in many cases, can do that work better than I could). But it's a lot of people to keep informed and coordinated.
- rsstack 4y ago> marketing program people, public relations, analyst relations, competitive analysts, designers, editors I guess it depends on the role. I don't think startup developers do any of these (except maybe design) :)