←back to thread

768 points speckx | 1 comments | | HN request time: 0.001s | source
Show context
oceanplexian ◴[] No.45672984[source]
It's weird how the circle of life progresses for a developer or whatever.

- When I was a fresh engineer I used a pretty vanilla shell environment

- When I got a year or two of experience, I wrote tons of scripts and bash aliases and had a 1k+ line .bashrc the same as OP

- Now, as a more tenured engineer (15 years of experience), I basically just want a vanilla shell with zero distractions, aliases or scripts and use native UNIX implementations. If it's more complicated than that, I'll code it in Python or Go.

replies(21): >>45673276 #>>45673397 #>>45673416 #>>45673493 #>>45673595 #>>45673606 #>>45673685 #>>45673787 #>>45673894 #>>45674022 #>>45674094 #>>45674098 #>>45674837 #>>45675554 #>>45675916 #>>45675962 #>>45676837 #>>45676947 #>>45677013 #>>45678082 #>>45679080 #
1. nonethewiser ◴[] No.45673416[source]
On the other hand, the author seems to have a lot of experience as well.

Personally I tend to agree... there is a very small subset of things I find worth aliasing. I have a very small amount and probably only use half of them regularly. Frankly I wonder how my use case is so different.

edit: In the case of the author I guess he's probably wants to live in the terminal full time. And perhaps offline. there is a lot of static data he's stored like http status codes: https://codeberg.org/EvanHahn/dotfiles/src/commit/843b9ee13d...

In my case i'd start typing it in my browser then just click something i've visited 100 times before. There is something to be said about reducing that redundant network call but I dont think it makes much practical difference and the mental mapping/discoverability of aliases isnt nothing.