1,463 karma · joined July 6, 2011
Go, Kubernetes, GitOps, ...
- https://mstdn.social/@mweibel - https://www.github.com/mweibel
However, I worked on it for the past ~5 years on and off (well, mostly off) and rewrote it too many times. Now finally close to releasing, bought a domain and setting up all the last remaining things.
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...
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
More details here: https://helio.exchange/jobs/senior-go-engineerTo 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.
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
More details here: https://helio.exchange/jobs/senior-cloud-engineerTo 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.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?
if foo, err := doThing(bar); err != nil {
// handle error
} else {
// handle foo
}
but most don't use that form and just do the call outside: foo, err := doThing(bar)
if err != nil {
// handle error
} The city council unanimously voted on Wednesday to ban
the use of the technology and prohibit any city
official from obtaining facial surveillance
by asking for it through third parties.If you look at the docs of Strapi you see that this is the case for Strapi as well.
"strongly typed mainstream high level language" does not say anything about that, hence my question.
Anyway, that's a bit sad IMHO. In my opinion, running what you build is great to discover ways to improve your software.
Regardless if you want to or don't want to touch ops: You still might want to talk to ops or vice-versa. Even if you have strict roles for devs and ops (and no mixed roles), you might be in a team where both are present and hopefully talk to each other.
OAM is essentially a YAML file.
It can be put in a service catalog
or marketplace and deployed from there.
But what’s maybe most important, says
Russinovich, is that the developer can hand
off the specification to the ops team and the
ops team can then deploy it without having to
talk to the developer.
This statement sounds very backwards to me. Isn't this increasing the separation between devs and ops which we want to get rid of?Do you have some links/articles which describe what it is and what positive/negative things can come out of it?
https://www.digitale-gesellschaft.ch/2019/03/23/demonstratio...
(german only, sorry)
It's all a bit different than in the EU because people may be able to vote against that at some point.. Whether that happens is another question entirely, though.
pretty safe bet ;) Love it.
To me that seems really an oversight on GitHub's part. Maybe it's intentional?
A small note: shared that in our internal slack and it just displays as a "preview" the domain, title and meta description of your page. I think Slack uses the `og` meta tags too, so adding a more elaborate description and an image would help :)
What's the reason for using macros instead of real functions? Is this an optimization because macros get inlined at compile time? Does this really bring a lot of value?