Hacker News Reader

Comment by taeric | Hacker News Reader

My favorite trap in all of this, is that this thinking will fail most tech interviews. It is incredibly frustrating.

Yep. Failed an interview because I used EJS (SSR) and Node to build a simple Twitter in 30mins. The interviewer saw that it was three files and did not seem impressed.

I guess they wanted me to use lots of little components in an SPA which I did in my day job, but it didn't seem nessisary for the task...

3 files? "Luxury!"

I could implement a Twitter in 1 Python or Go file, hosted on 1 machine

granted its concurrent user capacity and traffic load capacity would be insufficient for actual Twitter. but all the basics would work, in the small

You had a machine?

LUXURY!

I'm sure there are horrible kubernetes deploys out here that you can deploy with a good ol' curl | sudo

Trap or integrated win-win?

We use one of these "aggressively simple" architectures too. At this point, I would quit my job instantaneously if I had to even look at k8s or whatever the cool kids are using these days.

> look at k8s or whatever the cool kids are using these days.

I'm fine with complex architecture and would actually welcome someone choosing something complex but the issue is that we have perverse incentives at work to introduce stuff just to pad our resume.

Kubernetes was designed for companies deploying thousands of small APIs/applications where management is a burden. I've seen companies that deploy 3 APIs running Kubernetes and having issues...

Man, kubernetes is so much easier than the smattering of crap that you have to jungle together before it. Puppet and co? No thanks. Terraform? It's fine, but only a part of a CI/CD picture. If you think the alternatives are better, I really have to wonder how much of the trenches crap that people in your org deal with regularly that you're insulated from. That, or you're a release-quarterly kinda company?

We're using Nomad + Consul + a custom little cli and I would never go back to K8s from this.

Not a yaml document in sight.

Nomad is pretty great for a lot of things, especially self hosted. The only reason I prefer k8s is the ecosystem. Even though there are standardized specs like CSI, they were written with k8s in mind, so some drivers are completely broken on Nomad. Also, most cloud providers offer managed k8s, but very few offer managed Nomad.

> Puppet and co? No thanks.

Puppet? Luxury. I started my configuration management journey with cfengine. And the folks that I first heard CM about started with Makefiles:

* http://www.infrastructures.org/papers/bootstrap/bootstrap.ht...

* https://www.usenix.org/legacy/publications/library/proceedin...

We wrote our own tools for most things. Our build is a single dotnet publish command, followed by copying the output to an S3 bucket for final consumption.

That output is 100% of what you need to run our entire product stack on a blank vm.

Monolithic pays for itself in so many ways. Sqlite and other in-process database solutions are a major factor in our strategy.

I guess the only thing you can do is avoid those places. Last time I checked Wave were on a hiring spree.

I think that probably says more about the tech companies than anything else.

Reply on news.ycombinator.com