> Code reviews should not allow such commits to pass through.

Are you suggesting that your code review process has a stage for combing through commit messages? What does this look like? If the third commit message of 15 isn't up to par what happens?

You ask them to fix the commit message. Every git GUI should support that by now, so it should be a 1 minute fix, even for junior devs.

Neat!

https://thefitness.wiki/getting-started-with-fitness/ https://thefitness.wiki/routines/

amazon (no ref): https://www.amazon.com/dp/0143108271

in case anyone has the same issues I did finding it.

The Dude and the Zen Master

I wonder what take aways there are for personal finance.

I also wonder if real estate will drop with the market, and what impact that has on a HCOL pro-seller housing market.

A radio ad for the second season of the Duolingo podcast prompted me to check out the first season.

I appreciate the idea that the episodes are life stories instead of fake cafe scenes. The stories are interesting, and sometimes intense. The CEO / cofounder talks about a kidnapping in his family in the last episode of season one.

The small english summaries every few sentences helps provide context. That helps with context for the words I'm not familiar or strong with.

The language used is intermediate level. Personally I am below that level, but have gotten value from episodes.

I like the idea of publishing interesting text files like this automatically to a personal site.

When I develop locally using Docker, I live link my code directory into the container. I.E.

docker run -v "$PWD":/some/app/location ...

My editor doesn't know I'm using Docker. You can change your workflow when you want to deploy to a container registry, etc.

Aha!! So all code is executed in the container but all the code is stored locally so all my local tools see it normally. Yes on the surface that seems like the approach I need.

Consider vagrant.

How to scan your projects (from their directory, or their parent directory)

https://github.com/eslint/eslint-scope/issues/39#issuecommen...

You can easily modify the script to scan for the other vulnerable dependency as per

https://github.com/eslint/eslint/issues/10600

version: eslint-config-eslint 5.0.2