The perf is meh, but tbh if you look at the kind of code we, regular developers write for work, it's probably still vastly better.
459 karma · joined August 13, 2020
The perf is meh, but tbh if you look at the kind of code we, regular developers write for work, it's probably still vastly better.
Of course then there's the maintenance - updating operators, Kubernetes, whatever else you have, but you don't have to do it and if you want to do keep up with recent versions then it's just as much work as on Ubuntu or any other distro. The upside with k8s is that you can definitely roll back (I'm just assuming you're using GitOps).
Besides, you'll probably want to add all of that Kubernetes functionality at some point anyway - eg you may just at first deploy your server/app via ClickOps, have some issue, decide GitOps is the way to go, then decide that you really need to have automatic certs, then decide that DB backups would be good to have. With Kubernetes you just keep extending it and never really have to "rethink" the approach cos it's really difficult to shoot yourself in the foot unless you really want to and have a shred of understanding (and to clarify I'm speaking about small deployments), and of course because you're using it yourself your knowledge grows meaning that your expertise grows.
But I found funny that the OP summarized to use Kubernetes when CTO is no longer the only dev.
This time - I'm so close! I probably need few more weeks to somewhat polish the game and fix the rendering quirks and I'll be ready to put it online for easy access when I'm bored lol.
I’m NOT the creator.
I have zero experience building computers - where would I even start? I mean, aside from the things already well documented and mentioned in the blog post.
The simplest way to start probably would just be to create a custom Helm chart and define what you want in `values.yaml`.
- Go - backend + CLIs
- TypeScript - fronted, occasionally zx for more complex scripts
- Nushell as my scripting language (I’ve been relentlessly using it everywhere I can instead of bash/zsh and man it is such an improvement)
I heard so much good stuff about both Zig and Rust and would love to eventually get to know one of them.
This SpaceX thing will make him 2 trillion guy, not the 1 trillion he’s promised to be.
What I don’t understand is why. There’s a natural churn at each company. Of course it’s not 40%, but probably 4-5% per year, but I doubt the company freezes hiring and they are not pressured to do this.
I’ve been recruiting people and had exposure to small sample of generalists as an interviewer, but also in a team. Not too long ago, I’ve been briefly exposed to „staff” level Go developers who, I kid you not, would not follow ANY known and widely accepted as best practice Go convention (that I could identify). Obviously these were Java, C#, Python developers bringing habits from their last language to that project and boy was it bad. I suppose that was an extreme end of the spectrum (they were also incredibly toxic), but not once before were I in a team where new code was that bad. Of course, best practices are there to serve you and not the other way around, but each time I’d ask, they couldn’t explain why in a coherent way.
I suppose once you know programming it’s kinda easy to change the syntax, but imo code is just significantly better if people know what they are doing.
Now, imagine that I don’t ask for a number nor share my expectations. With 3-4 rounds of interviews, even if we assume 1/10 is in my range, I’d have to SUCCESSFULLY do maybe 30-40 interviews on average to find a job that matches my expectations. Another thing is that benefits in Poland are pretty standard almost nearly everywhere: private medical care, gym card, 20 vacation days, 10 sick days… unless you’re willing to work in the big few companies that just have unlimited money.
(If someone in Poland has different experience, please share - would love to hear more.)