mweibel

interesting - I wasn't aware of that. Will read up on it, thanks!

yes, long fermentation reduces fodmaps in breads which in turn makes it better digestable (plus it just takes better).

Working on a bread recipe community where you can share and iterate on bread recipes. It's out of personal interest to be able to record my bread recipes and thought it might be interesting for others too.

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.

sourness is depending on quite a lot of factors - amount of water in starter, how long you proof, temperature etc.

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...

Helio 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

More details here: https://helio.exchange/jobs/senior-go-engineer

To apply, please email to [email protected]. 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.

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

More details here: https://helio.exchange/jobs/senior-cloud-engineer

To apply, please email to [email protected]. 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.

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?

you could use an `else` clause for the scope:

  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  
  }

it's in the second paragraph of the article:

    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.

Usually headless means that serving the content is done only through an API while creating content (and -types) is done using an admin interface.

If you look at the docs of Strapi you see that this is the case for Strapi as well.

also in Switzerland. It's a brand by Valora (Kiosk, Brezelkönig, Ditsch, ...)

maybe? I wouldn't know.

"strongly typed mainstream high level language" does not say anything about that, hence my question.

sure, there are pros/cons in all languages. My question was specificly to the sentence about "strongly typed mainstream high level language" - as there are many languages who fit that definition.

why not Go/Java/....? Honest question.

Only one finger needed

"we" doesn't necessarily include all.

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?

thanks for the interesting response and the link.

I hear about keto so often that it must be the best thing ever, however I have no idea what it even is and I got curious!

Do you have some links/articles which describe what it is and what positive/negative things can come out of it?