3 ms·

So fired from 3 startups, was a CTO in each, but doing senior developer and devops work with a common theme that the author didn't document the infrastructure a

So fired from 3 startups, was a CTO in each, but doing senior developer and devops work with a common theme that the author didn't document the infrastructure and built it on unstable foundations that required rework by the new teams. Did I summarise that correctly?

andomiazzz662 3y ago
To be fair, if he was really by himself doing all of that and as overworked as he says, then of course he didn't have time for documentation. If I saw a lack of documentation that severe from the person architecting a critical-to-the buisness project, I would take the time out to sit with them and find out what's going on and how to help. I've definitely had times back when I was doing work on one or two man teams where documentation was essentially impossible. Now, it sounds like he was a cofounder of sorts. That makes you a business partner and so he should have found out they weren't going to hire help much sooner than launch. The project should never have gotten anywhere close to launch really. Now that's a year or two of his life's work flushed down the toilet in a sense. With the experience I have now, I would not allow myself to end up in a similar situation, but when I was younger I was much more naive and would buy into a lot of junk from early stage startups that were obvious red flags looking back.
GianFabien 3y ago
When working for abusive idiots, there is no time to document nor to do proper design and evaluation. Basically what passes for a proof-of-concept or MVP or prototype ends up being put into production. Gotta start minting money fast.
znpy 3y ago
No. You just took the parts that fit your narrative. The guy was effectively doing multiple jobs, which is borderline acceptable when you’re an early stage startup, but as soon as you get either vc money or profits you should start scaling stuff, beginning with your team. The guy could just have been hit by a bus, and those companies would have crumbled anyway.

andomiazzz662 3y ago

To be fair, if he was really by himself doing all of that and as overworked as he says, then of course he didn't have time for documentation. If I saw a lack of documentation that severe from the person architecting a critical-to-the buisness project, I would take the time out to sit with them and find out what's going on and how to help. I've definitely had times back when I was doing work on one or two man teams where documentation was essentially impossible. Now, it sounds like he was a cofounder of sorts. That makes you a business partner and so he should have found out they weren't going to hire help much sooner than launch. The project should never have gotten anywhere close to launch really. Now that's a year or two of his life's work flushed down the toilet in a sense. With the experience I have now, I would not allow myself to end up in a similar situation, but when I was younger I was much more naive and would buy into a lot of junk from early stage startups that were obvious red flags looking back.

GianFabien 3y ago

When working for abusive idiots, there is no time to document nor to do proper design and evaluation. Basically what passes for a proof-of-concept or MVP or prototype ends up being put into production. Gotta start minting money fast.

znpy 3y ago

No. You just took the parts that fit your narrative. The guy was effectively doing multiple jobs, which is borderline acceptable when you’re an early stage startup, but as soon as you get either vc money or profits you should start scaling stuff, beginning with your team. The guy could just have been hit by a bus, and those companies would have crumbled anyway.