Readit NewsHelio https://helio.exchange | Senior Go Engineer | Switzerland Zurich, On-Site Hybrid | Full Time (80-100%) | CHF 100-130k + equity and benefits
We are a Swiss startup based in Zurich and build the first carbon-aware cloud by increasing the utilization rates of data centers worldwide. We're focusing currently on the 3D render market (providing compute for rendering 3D animations) but will expand to further areas as we grow. We have a core product with scheduling and billing included where you'll mainly work on.
We're looking for a Senior Go Engineer and develop our core and render product further. We utilize various cloud providers and work with Kubernetes and Cluster API. You'll mainly develop Go code and deploy and monitor it on our production cluster (you build it you run it).
Tech Stack:
- Go
- gRPC
- NATS
- Kubernetes (including custom operators)
- Cluster-API, ArgoCD (GitOps), Argo Workflows
- Windows and Linux containers
- Prometheus (Cortex)
- PostgreSQL
- GitLab CI/CD, GitHub
To apply, please email to jobs@helio.exchange. Traditional CVs or Cover letters are unnecessary.
Interview process: We review your profile and reply with a small questionnaire, have a short 30min interview with the Founders, Connect with our team (getting to know them plus technical fit interview) and then join us with a flexible starting date.
Will you sponsor visa or work remotely from other country?
hi,
we have a couple of job offers which offer remote. The Senior Cloud Engineer role is on-site/hybrid at the moment though.
We're too small to sponsor visa or offer relocation, unfortunately.
Helio https://helio.exchange | Senior Cloud Engineer | Switzerland Zurich, On-Site Hybrid | Full Time (80-100%) | CHF 100-130k + equity and benefits
We are a Swiss startup based in Zurich and build the first carbon-aware cloud by increasing the utilization rates of data centers worldwide. We're focusing currently on the 3D render market (providing compute for rendering 3D animations) but will expand to further areas as we grow. We have a core product with scheduling and billing included where you'll mainly work on.
Join us as a Senior Cloud Engineer and develop our core and render product further. We utilize various cloud providers and work with Kubernetes and Cluster API. You'll mainly develop Go code and deploy and monitor it on our production cluster. You'll work closely with our Growth team and contribute to the ongoing success of our projects. We are a small team looking to expand to accelerate our growth.
Tech Stack:
- Go
- Kubernetes (including custom operators)
- Cluster-API, ArgoCD (GitOps), Argo Workflows
- Windows and Linux containers
- Prometheus (Cortex)
- PostgreSQL
To apply, please email to jobs@helio.exchange. Traditional CVs or Cover letters are unnecessary.
Interview process: We review your profile, have a short 30min interview with the Founders, Connect with our team (getting to know them plus technical fit interview) and then join us with a flexible starting date.
We're looking also for:
- Senior Fullstack Software Engineer (Remote)
- Windows Software Engineer 3D Tools (Remote)
- and others, check out https://helio.exchange/jobs for more.Deleted Comment
Deleted Comment
I never really had issues with lack of sleep until I became father 1.5 years ago. Child has issues with sleep since the start and while it recently got a bit better, in those 1.5 years I can count the number of times I got 8 hours uninterrupted sleep on one, maybe two hands.
On the worst days I could eat double my normal food intake and was still hungry. Working and concentration is quite hard, more coffee intake is the case. Complex thoughts are increasingly difficult (e.g. improving software architecture takes much more time than I was used to).
I do wonder what happens when sleep is back to normal. Are some effects staying or will eventually everything go back to how it used to be before?
mweibel commented on The ecosystem of the Go programming language henvic.dev/posts/go/... · Posted by u/henvic
I've been using Go for a personal project of mine recently. I had briefly used it at the tail end of my internship while getting my degree, but nothing particularly in-depth, and it was some pretty simple server code that never really challenged me.
There's definitely some nice stuff about it, but there's also some stuff that's a bit of a pain. For one thing, being straight up unable to compile a program if there's an unused variable, not even a debug compiler flag or anything to allow it while testing. There's a lot of cases where I just want to move one thing around, or I'm partway through writing a function and just want to see what state something is in at a point, so I want to throw a breakpoint on a line and run the program up to that point. But even though my code is technically all valid, because the variable I want to look at is unused, or I commented out a line that makes something else unused, I now can't compile at all. So there's a lot of times I'll have to throw in a random fmt.Print of a random property of index zero of an array or something, which might crash anyway if it's reached, but at least it'll compile. It maybe doesn't seem like it would be that big of a deal, but when you've got a train of thought going, and you're trying to iterate fast, it can really pull you out of the flow of things.
There's also a lot of weird situations where I find it hard to keep things clean. For instance, I like using this shorthand:
if err := doThing(bar); err != nil {
// handle error
}
if foo, err := doThing(bar); err != nil {
// handle error
}
var foo FooType
if foo, err := doThing(bar); err != nil {
// handle error
}
var foo FooType
var err Error
if foo, err = doThing(bar); err != nil {
// handle error
}
Perhaps there's some tricks I don't know about, but I tend to run into situations like this a lot, and I spend so much time trying to appease weird edge-cases of the compiler's strict rules that is really throws a wrench in my workflow.
you could use an `else` clause for the scope:
if foo, err := doThing(bar); err != nil {
// handle error
} else {
// handle foo
}
foo, err := doThing(bar)
if err != nil {
// handle error
}
I also prefer less sour breads and since I started using a stiff starter it's much better than more liquid ones. I still haven't found the perfect recipe yet but it is possible.
A good intro into the difference of starters is at the bread code: https://www.the-sourdough-framework.com/Sourdoughstartertype...