3 ms·

Anything you don't know about managing these systems can be learned asking chatgpt :P Whenever I see people doing something like this I remember I did the same

Anything you don't know about managing these systems can be learned asking chatgpt :P Whenever I see people doing something like this I remember I did the same when I was in 10 people startups and it required A LOT of work to keep all these things running (mostly because back then we didn't have all these cloud managed systems) and that time would have been better invested in the product instead of wasting time figuring out how these tools work. I see value in this kind of work if you're at the scale of something like Dropbox and moving from S3 will greatly improve your bottom line and you have a team that knows exactly what they're doing and will be assigned the maintenance of this work. If this is being done merely from a cost cutting perspective and you don't have the people that understand these systems, its a recipe for disaster and once shit is on fire the people that would be assigned to "fix" the problem will quickly disappear because the "on call schedule is insane".

deleted 2y ago
[deleted]
re-thc 2y ago
> and that time would have been better invested in the product instead of wasting time figuring out how these tools work It really depends on what you're doing. Back then a lot of non-VC startups worked better and the savings possibly helped. It also helps grow the team and have less reliance on the vendor. It's long term value. Is it really time wasted? People often go into resume building mode and do all kinds of wacky things regardless. Perhaps this just helps scratch that itch.
- mlinhares 2y ago
  Definitely fine from a personal perspective and resume building, it's just not in the best interest of the business because as soon as the person doing resume building is finished they'll jump ship. I've definitely done this myself. But i don't see this being good from a pure business perspective.
  - re-thc 2y ago
    > it's just not in the best interest of the business because as soon as the person doing resume building is finished they'll jump ship. I've definitely done this myself. I certainly hope not everyone does so. I've seen plenty of people lean choices based on resume / growth / interest than the pure good of the business but not to leave after doing so. > But i don't see this being good from a pure business perspective. And a business at the end of the day is operated by its people. Sure, there are a odd few that operate in good faith, but we're not robots or AI. I doubt every decision everywhere is 100% business optimal and if it's the only criteria.
Diederich 2y ago
> ... I remember I did the same when I was in 10 people startups and it required A LOT of work to keep all these things running... Honest question: how long ago was that? I stepped away from that ecosystem four or so years ago. Perhaps ease of use has substantially improved?
ljm 2y ago
I bailed out of one company because even though the stack seemed conceptually simple in terms of infra (there wasn't a great deal to it), the engineering more than compensated for it. The end result was the same: non-stop crisis management, non-stop firefighting, no capacity to work on anything new, just fixing old. All by design, really, because at that point you're not part of an engineering team you're a code monkey operating in service of growth metrics.

deleted 2y ago

[deleted]

re-thc 2y ago

> and that time would have been better invested in the product instead of wasting time figuring out how these tools work It really depends on what you're doing. Back then a lot of non-VC startups worked better and the savings possibly helped. It also helps grow the team and have less reliance on the vendor. It's long term value. Is it really time wasted? People often go into resume building mode and do all kinds of wacky things regardless. Perhaps this just helps scratch that itch.

mlinhares 2y ago
Definitely fine from a personal perspective and resume building, it's just not in the best interest of the business because as soon as the person doing resume building is finished they'll jump ship. I've definitely done this myself. But i don't see this being good from a pure business perspective.
- re-thc 2y ago
  > it's just not in the best interest of the business because as soon as the person doing resume building is finished they'll jump ship. I've definitely done this myself. I certainly hope not everyone does so. I've seen plenty of people lean choices based on resume / growth / interest than the pure good of the business but not to leave after doing so. > But i don't see this being good from a pure business perspective. And a business at the end of the day is operated by its people. Sure, there are a odd few that operate in good faith, but we're not robots or AI. I doubt every decision everywhere is 100% business optimal and if it's the only criteria.

Diederich 2y ago

> ... I remember I did the same when I was in 10 people startups and it required A LOT of work to keep all these things running... Honest question: how long ago was that? I stepped away from that ecosystem four or so years ago. Perhaps ease of use has substantially improved?

ljm 2y ago

I bailed out of one company because even though the stack seemed conceptually simple in terms of infra (there wasn't a great deal to it), the engineering more than compensated for it. The end result was the same: non-stop crisis management, non-stop firefighting, no capacity to work on anything new, just fixing old. All by design, really, because at that point you're not part of an engineering team you're a code monkey operating in service of growth metrics.