4 ms·
> In startups, its not uncommon to have engineers who have been handling various responsibilities, including security (especially early employees). You're righ
by Kalium 4y ago
> In startups, its not uncommon to have engineers who have been handling various responsibilities, including security (especially early employees).
You're right!
That said, by the time a company is large enough that 17% of it is more than 17 people the kind of startup organization you have wisely and correctly nodded to will have ceased to exist.
So while you are right in that such scenarios have, do, and will continue to happen there's perhaps cause to wonder if that's really the best way to characterize replacing a security organization with specialists with a bunch of engineers who are likely quarter-time security at best. It's akin to firing all your engineers because the sales people can do a little bit of coding each.
- unity1001 4y ago> That said, by the time a company is large enough that 17% of it is more than 17 people the kind of startup organization you have wisely and correctly nodded to will have ceased to exist. Not really. A lot of stuff having moved to services, a lot of stuff being handled in 'no code' manner have simplified organizations a lot these days. Today you can just offload a lot of things to SaaS vendors that can automatically handle those stuff. Instead of having to have entire teams dealing with it like how it was in the earlier decades. You just need a host of capable people to deal with those services on your side, by wearing various hats. So the 'startup format' seems to have become extended to larger organizations.