News for hackers. Stuff that matters.
Re:How my role as CTO has changed as we've grown from 1 to 1... by legohead on Thursday June 28, 2018 @06:09PM (#17420892)
I was an engineer #1 hired by a "CTO" and we grew to 50 engineers. His story/growth didn't really change much, however. He was a coding machine, a true "10x engineer", and programmed day and night. He even started up a second company while working on the first. He built both codebases from scratch, and even re-wrote the first company's core codebase at one point.

He did attend exec meetings and make all major technical decisions, but I never really felt he had to grow into anything.

When we got big enough to start worrying about compliance, security, and HR tools, we did it together and moved on to the next thing.

Re:How my role as CTO has changed as we've grown from 1 to 1... by justAnotherNET on Thursday June 28, 2018 @07:51PM (#17421408)
Are you me? We’re at 30 now and I know exactly what you mean.
Re:How my role as CTO has changed as we've grown from 1 to 1... by nine_k on Friday June 29, 2018 @02:49AM (#17422867)
Pretty sad that it sounds as if security was an afterthought in your design.
Re:How my role as CTO has changed as we've grown from 1 to 1... by lancefisher on Friday June 29, 2018 @03:30AM (#17423018)
There are a whole host of compliance and security issues that you don’t have to (and shouldn’t) worry about when you’re small. Employee background checks, documented disaster recovery plan, 3rd party pen testing, etc. Those are things you worry about once you have built something. It’s different than just application security which itself can always be improved over time even if it wasn’t an afterthought.
Re:How my role as CTO has changed as we've grown from 1 to 1... by dfsegoat on Friday June 29, 2018 @09:15AM (#17424277)
SarBox, GAMP, GAAP, cGMP, PCI-DSS... The devil hath many names.