Rowern

For anyone clicking on this for the title; please note that this blog post is pushing hard for the author coaching service.

Some may even call this a disguised ad...

Let's save someone a click: this is an empty shell of a blog post. Not really actionnable and only saying that's hard to secure Kubernetes clusters.

Be really careful with this kind of emailing flow. We were booted off 2 mains email provider because our B2B apps allowed people to send invitation to their colleagues... I'm thinking that big email providers (like Mailchimp) don't even try to understand your usage and largely prefer to ban any non-big players from their network.

I would expand your point to add that another missing key part of dev on big distributed platform is being able to run parts of the system locally. For some shop it is a lot harder than a simple docker-compose (think of envs with 10 or 100 of micro-services), any laptop cannot handle such load and it is critical for devs to work on the machine, otherwise you lose a lot of time with shared dev envs, SSH tunnels or rsync... I agree that CI pipelines are a pain in a distributed system but I heard more complains from devs not being able to test locally some new feature in serviceA that depends on 10 other services + DBs to work.

I won't try to do a TL;DR, but from reading the full article, it seems like he is doing kind of fine right now. He is still sick but he is currently writing a thesis. The article has a really positive vibe to it even though it is a really rare disease.

The issue here is that if you're running in the JS ecosystem you'll definitely want to use other people code (npm package or internal lib), if the subset breaks JS compatibility then you can break a significant amount of code without realising, if it is "only" a TS subset, then you need to make sure that each lib/package you import are compatible. Anyway this does not seem like a good solution.

Looks awesome, bravo to you/the team behind it!

Having worked with Terraform for 3 years, I totally agree!

Hashicorp should put more money into promoting "healthy" terraform tutorials based on real world usage (maybe split for small/medium/large orgs)

My first setup was split into 10-15 repos and it was an nightmare...

Now I have a mono-repo (and some GitlabCI magic to handle different projects) + terragrunt and it so much more stable than my first setup! As with everything, start simple, only change if you hit a wall!

So much this.

You should probably just say its a tutorial on how to install a PWA (i.e. how to click on the install button).

This issue is from 2016...

Traefik is really cool for most usage, I tried to used it in production and here are some of the shortcoming I found (the 2 first issues are on github):

- If you use DNS for a blue-green deployment, traefik does not honor DNS ttls (because it uses the DNS of go and go might do some caching) so when you do the switch you might still end on the "old" environment

- An error on one of the cool feature: serving error page when your backend returns some HTTP code

- Some configuration options are not documented (but easily found using github search)

I still love this software and I will keep looking at it.