The salary ranges are very misleading, unfortunately. For example, posthog will only pay 120k gbp for a senior full stack in London, while they’ll pay 220k usd for the same role in Seattle. Ramp also doesn’t pay 200k+ for roles based in EU.
The point in the article was to prefer composition over inheritance, which is sort of like using OOP “the right way”.
It didn’t discourage OOP as a whole, nor do I think it should - making a game without objects would be a nightmare.
Whatever you do, don’t stop treatment. Follow the doctor’s advice, but at the same time use critical thinking, and seek a second opinion (from a doctor, not alternative medicine) when in doubt.
As for coping from her side - be understanding, encouraging and accepting. If she loses hair, or gets bad skin - don’t make it a big deal.
To add maybe one more point to this - it’s so much easier to run parts of the pipeline for devs who aren’t familiar with the environment. It can also serve as a documentation for what’s required to develop.
Won’t setting up a k8s cluster require writing resource definitions? I imagine you’d need to write a statefulset. How’s that better than writing a docker-compose?
I’m not sure how vscode does it, but it allows you to publish ports in real time as well.
I agree, the title of the article is a bit misleading. In general, you’d still need an IDE installed on the host machine, which can then connect to a runtime on the container. With VS Code and remote containers, it’s quite easy.
Alternatively, maybe it’d be possible to have the container expose an IDE over http (possibly vscode through the browser?).
Yep, I use it. There are two tricks to mitigate this:
1. Using a :delegated or :cached flag when using a bind mount can speed it up a bit
2. For folders that need a lot of RW, but don’t need to be shared with the host (think node_modules or sbt cache), I bind a docker volume managed by docker-compose. This makes it extremely fast. Here's an example: https://gist.github.com/kamac/3fbb0548339655d37f3d786de19ae6...