jorge-fundido

It's not a sampling problem, but more a gambling problem, as in the gambler's fallacy?

Tend to your personal relationships like a garden, especially when you're younger since it becomes much more difficult to establish meaningful relationships the older you get. It's only my experience, but that is my greatest regret. I think the less important things like career are more easily tackled with a solid foundation of personal relationships.

Also, I've found striving for perfection is fool's gold. Yeah, you may be "that person" that friends/family/colleagues will love name-dropping you every chance they get. The others will probably care little that you're an expert and may even resent you for it.

Middleware comes to mind (eg caches, proxies, api gateways).

Throwing this out there for criticism... I use `python3 -m pip install -t .pip -r requirements.txt` and add .pip to my PYTHONPATH. That works for me without having to use any of the python virtual env tooling, basically trying to get something more npm like.

I don't work on any significant python code bases, so I expect it has limitations when compared to the virtual env options like developing with specific (or multiple) python versions.

Killer keyboard feature for me is ~/Library/KeyBindinds/DefaultKeyBinding.dict - all text controls honor that. Very nice way to get basic emacs shortcuts defined. I've yet to find something half as simple & effective as that in linux desktop land, probably because of the variety of gui toolkits that isn't present in osx.

> If you're going to rely on a fancy shell anyway, why not just throw make out of the loop altogether?

I think can still add value in that scenario as the standard project entrypoint. Someone completely new to the project should be able to `make help`, `make install`, etc. Even if the make targets are simple wrappers to project specific tooling (npm, pip, sbt, etc). If the Makefile is kept simple, then users can treat it as a form of README and should be able to cherry-pick from it as they see fit.

But yeah, I share your sentiment about quirky, non-portable Makefiles potentially being anti-value.

Perhaps it's just a factual element. Or perhaps the intention is `s/python/pragmatic/`. Yeah, python sucks in many ways but is it really so horrible? I know! Let's ask the reader to get intimate with a static compiler. If they're "smart" enough to satisfy (or trick) the compiler, then they've earned the "reward" of being able to execute their program.

There is value is static typing, but there are many instances where that cost is not worth the reward.

My approach is to copy, paste, & tailor the programmable completion for a command that has similar interface to my mine. Can try browsing /usr/local/share/bash-completions/completions or `set` & search for _FOO. Hopefully the special variables like COMPREPLY will be self-explanatory. Also `help compgen`. I'm assuming bash, by the way.

Try `PYTHON -m MODULE` as in `python3 -m pip` if you want to make sure to use python3's pip, `python2 -m pip` for python2, `~/bin/python -m pip` for a personal python install, etc.

I interpreted that as not making his "intro to ocaml" REPL-centric, so that things like the build tooling gets covered.

VPN companies don't care too much about customers that are concerned about privacy - too small a percentage of their customer base. Catering to those trying access geo-blocked content is where the money's at.