Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
My most niche hobby is writing ungodly bash scripts, and sourcing them to one of my bash profiles -- mingw64 (windows), zshell (OSx), or normal (debian based).
I write in such a way that scripts are separated by concepts which overwhelmingly align with a certain technology or tool (e.g. git) and source whichever functionality I want into the proper profile.
The pain is separating corporate vs personal scripts, which I don't have a great solution for outside of actually separating the scripts and sourcing in the proper order so that corporate functionality can override personal functionality (i.e. my git commands in corporate environment are still the same but with properly overridden config, etc)
For example, I bought a steam deck and mainly use it as a laptop instead of a gaming device. I created a new bash script
steamosand source to my (new) steamos profile. All my setup is repeatable through scripts to the point I could factory reset, clone my profile repo, run a couple commands, and everything is back where it should be. I am not quite to that state with other environments, but that is my goal.Imagine starting a new job, being handed a laptop you don't get to choose (probably a Crapbook), and then simply clone and run config command to setup the OS for your personal prefs so you can hit the ground running on week one. This doesn't mean you clue people in on the fact you are running not walking, however, ESPECIALLY at a new job.
inb4 have you heard of Ansible
Haha, I love that kind of thing too - even if there's a "better" off the shelf alternative, it's fun to figure it all out and design it exactly the way you want. it feels like doing a sudoku or writing a story or something to me. I feel like I wouldn't be working in tech if I hadn't initially gotten into making my setup just right with scripts - before that point I just didn't have a lot of programming tasks that caught my interest, but I learned a lot that way and eventually branched into other stuff too.
I am a looooot more basic. But I see the fun in scripting. I make scripts when I need to do boring/monoton/repeating tasks like setting up a new win env after a new install, Set up test environments or getting info that my customers ask for that is something they will most likely not ask for again or if I need test data (especially files). I am a fullstack developer so that is why I am not doing anything fancy like the sys admins and I am too practical to create something for the sake of creating. But I do love creating things that is being used!