←back to thread

768 points speckx | 1 comments | | HN request time: 0.236s | 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 #
chis ◴[] No.45674098[source]
I think it's more likely to say that this comes from a place of laziness than some enlightened peak. (I say this as someone who does the same, and is lazy).

When I watch the work of coworkers or friends who have gone these rabbit holes of customization I always learn some interesting new tools to use - lately I've added atuin, fzf, and a few others to my linux install

replies(2): >>45674487 #>>45675898 #
heyitsguay ◴[] No.45674487[source]
I went through a similar cycle. Going back to simplicity wasn't about laziness for me, it was because i started working across a bunch more systems and didn't want to do my whole custom setup on all of them, especially ephemeral stuff like containers allocated on a cluster for a single job. So rather than using my fancy setup sometimes and fumbling through the defaults at other times, i just got used to operating more efficiently with the defaults.
replies(3): >>45674715 #>>45674779 #>>45676671 #
1. ◴[] No.45674715[source]