I've come to use all these over time, as I gained more professional experience and had more and more hours using a terminal under my belt. I'm not sure on this, but I'd imagine that "effective"...
I've come to use all these over time, as I gained more professional experience and had more and more hours using a terminal under my belt.
I'm not sure on this, but I'd imagine that "effective" could be substituted with "experienced" here. Unless a developer gets stuck in 'Expert Beginner' phase, they should get a handle on this stuff.
There are helpers that help manage virtual environments, activate them, list them, delete them, etc. I reccomend using that as aliases is a fragile approach. I use virtualfish, for example. One...
$ alias pvenv
alias pvenv='/Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8 -m venv venv && source venv/bin/activate'
$ alias ae
alias ae='source venv/bin/activate'
[...]
There are helpers that help manage virtual environments, activate them, list them, delete them, etc. I reccomend using that as aliases is a fragile approach.
$ alias howdoi
alias howdoi='cd $HOME/code/howdoi && source venv/bin/activate && howdoi'
Again, aliases are very fragile, use pipx instead. It allows to keep python programs updated in their own virtualenvs while keeping symbolic links to ~/.local/bin, it even has a command to ensure that directory is in $PATH for a seamless integration with any shell interpreter.
Till somebody suggested ag (aka The Silver Searcher) and my dev life became so much better.
Although the name is horrible, fd is a much friendlier alternative to find. I also recommend ripgrep over ag, it's much faster.
The article suggests
ag. I have recently switched toripgrepand it works really well (and fast) too.I've come to use all these over time, as I gained more professional experience and had more and more hours using a terminal under my belt.
I'm not sure on this, but I'd imagine that "effective" could be substituted with "experienced" here. Unless a developer gets stuck in 'Expert Beginner' phase, they should get a handle on this stuff.
There are helpers that help manage virtual environments, activate them, list them, delete them, etc. I reccomend using that as aliases is a fragile approach.
I use virtualfish, for example. One that works on bash is pyenv-virtualenv
Again, aliases are very fragile, use pipx instead. It allows to keep python programs updated in their own virtualenvs while keeping symbolic links to
~/.local/bin, it even has a command to ensure that directory is in $PATH for a seamless integration with any shell interpreter.