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.
Running locally is great but I would already be happy if I could step through a CICD pipeline with a debugger. This includes stepping though the services the pipeline calls. Also include breakpoints.
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.
to be fair, even within the TypeScript world that can be a problem. If typescript versions don't line up, or if your various strict options are too strict, you can get into really weird situations. It -generally- works, but when it doesn't, it's hell.
If anyone is looking for a simple way to speedup TS compilation for a big project, we use incremental compilation [1]. It does work pretty well, with some caveats when changing between refactoring branches ;)
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!
This looks pretty interesting! If anyone is looking for a tool to build a full fledge Back Office I warmly recommend react-admin (https://github.com/marmelab/react-admin/). Been using it for a year now and we went from 0 back office to a feature full one in no time!
React Admin is awesome. Combine it with Hasura (automatic GraphQL on top of PostgreSQL) and you can build an entire back office admin suite (API endpoints and admin front end) in a matter of hours. You end up writing more SQL than react as react-admin is basically a CRUD form generator.
Some may even call this a disguised ad...