Live data from Hacker News

Infrastructure decisions I endorse or regret after 4 years at a startup (2024)

cep.dev

111–120 of 247 posts

Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)

#111

As a non infra guy I'll say this. I'm curious about Linear. At my own company I vibecoded my own project management app against the JIRA API because I can't stand our version of JIRA. It's too many clicks, too many things to remember and it's unintuitive.

Been incredibly happy with the speed, featureset, and pace of new (good) features in Linear. Our team has adopted it quite happily and it gets a ton of good use. Can fully recommend.

Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)

#112

> Not using Function as a Service(FaaS) more FaaS is almost certainly a mistake. I get the appeal from an accountant's perspective, but from a debugging and development perspective it's really fucking awful compared to using a traditional VM. Getting at logs in something like azure functions is a great example of this. I pushed really hard for FaaS until I had to support it. It's the worst kind of trap. I still get s…

What's the issue with logging? I would have expected stdout/stderr to get automatically transferred to the providers managed logging solution (e.g. cloudwatch). Though I never really understood the appeal of FaaS over something like Google-Cloud-Run.

[deleted]

Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)

#113
I feel so many of these. LOL @ GitHub endorse-ish, more -ish every day now. Overall though seems like a pretty good hit rate.

Surprised to see datadog as a regret - it is expensive but it's been enormously useful for us. Though we don't run kubernetes, so perhaps my baseline of expensive is wrong.

Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)

#115

> Not using Function as a Service(FaaS) more FaaS is almost certainly a mistake. I get the appeal from an accountant's perspective, but from a debugging and development perspective it's really fucking awful compared to using a traditional VM. Getting at logs in something like azure functions is a great example of this. I pushed really hard for FaaS until I had to support it. It's the worst kind of trap. I still get s…

What's the issue with logging? I would have expected stdout/stderr to get automatically transferred to the providers managed logging solution (e.g. cloudwatch). Though I never really understood the appeal of FaaS over something like Google-Cloud-Run.

As a developer who spent a couple months developing a microservice using aws lambda functions:

it SUCKS. There's no interactive debugging. Deploy for a minute or 5 depending on the changes, then trigger the lambda, wait another 5 minutes for all the logs to show up. Then proceed with printf/stack trace debugging.

For reasons that I forgot, locally running the lambda code on my dev box was not applicable. Locally deploying the cloud environment neither.

I wasn't around for the era but I imagine it's like working on an ancient mainframe with long compile times and a very slow printer.

Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)

#116
The part about account teams for AWS and GCP is very true in my experience. I could tell my AWS account team that I was hungry and they would offer to bring me a bagel in an hour. My GCP account team no-shows our cadence calls and somehow forgets the one question I ask them in the intervening time between our calls, which means each month I get to re-explain the issue as they pretend to escalate it again.

Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)

#118
post #21

> Picking Terraform over Cloudformation: Endorse I, too, prefer McDonald's cheeseburgers to ground glass mixed with rusty nails. It's not so much that I love Terraform (spelled OpenTofu) as that it's far and away the least bad tool I've used in the space.

Any opinion on Pulumi?

We used it at my last startup and I loved it but im a dev not devops guy

I loved reading code

Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)

#119

As a non infra guy I'll say this. I'm curious about Linear. At my own company I vibecoded my own project management app against the JIRA API because I can't stand our version of JIRA. It's too many clicks, too many things to remember and it's unintuitive.

Baffling piece of software. It's a task manager and every time I use it I flail around for ages trying to figure out how to mark a task completed. No idea why people like it.

Re: Infrastructure decisions I endorse or regret after 4 years at a startup (2024)

#120
post #88

Infra guys doing DBA is a nightmare in my experience (usually clueless and it gets loved less than more sexy parts of infra). Devs too Hire a DBA ASAP. They need to reign in also the laziness of all other developers when designing and interacting with the DB. The horrors a dev can create in the DB can take years to undo

As an infra person I couldn't agree more. Get an expert in there. DB's are their own universe of complexity and deserve dedicated attention.
Post reply on HN