63 karma · joined October 25, 2015
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.
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.
https://www.youtube.com/watch?v=a_Vy6fgaBPE
Want more positive cases? Use a higher threshold. Want to scare the population into compliance? Use a higher threshold. Want to demonstrate that person X or policy Y was effective against stopping spread? Use a lower threshold.
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.
There is value is static typing, but there are many instances where that cost is not worth the reward.
[1] https://medium.com/@sigil66/dynamic-nginx-upstreams-from-con...
If we want to blame younger generations for not "thinking deeper" or "solving the hard problems", then we should shift our focus towards the economic drivers that are favoring quick/quantity over quality. I know how to develop software but if an employer is given the choice of fixing a buggy tool at the cost of maintaining a fork (GASP!) vs spending unbounded man-hours working around said buggy tool, my money's on that they will choose the latter since maintaining tool X is not a core competency. Meanwhile, tool X is hemoraging production data or producing buggy results and nobody flinches.
python3 -m pip install -t .pip ...
export PYTHONPATH=".pip:$PYTHONPATH"
Use whatever directory name you prefer instead of .pip. Mucking with PYTHONPATH is a bit dirty.Bash does leave a lot to be desired when it comes to data structures and error handling, but in some cases it makes the most sense. In those cases, better to have some semblance of sanity via a common lib like bash-infinity or bash-booster.
- data access / control
- availability & stability
- performance
- costhttps://www.americanprogress.org/issues/green/report/2016/05...
The optimist in me wants to believe that our dependence on foreign oil encouraged new domestic oil production via tax policy. I don't think that nudge is warranted any longer. I'm not a fan of governments interfering in markets, but in this case, better to incentivize alternative energy and not fossil fuel.