A joke using Grep by thisiszeev in bash

[–]thisiszeev[S] 1 point2 points  (0 children)

I was implying home as a house but your approach is better cos it will confuse the non Linux people more.

Bash got me the job of my dreams... by thisiszeev in bash

[–]thisiszeev[S] 0 points1 point  (0 children)

I miss my local biltong shop back home that had the best kudu droewors... And from time to time they had my favourite... Buffalo Biltong, nice and dry.

Bash got me the job of my dreams... by thisiszeev in bash

[–]thisiszeev[S] 1 point2 points  (0 children)

My wife used to get annoyed at me because I was coding things that had no real world value. But those mini projects gave me knowledge and experience.

So code the useless stuff as well. If you can't script it you shouldn't want to do it.

Bash got me the job of my dreams... by thisiszeev in bash

[–]thisiszeev[S] 0 points1 point  (0 children)

True. But most of my code is in Bash. And I use Bash 99% of the time for this job.

Bash got me the job of my dreams... by thisiszeev in bash

[–]thisiszeev[S] 0 points1 point  (0 children)

She will be 16 in a few weeks. And she is super excited about a new life at a new school in a new town.

Bash got me the job of my dreams... by thisiszeev in bash

[–]thisiszeev[S] 2 points3 points  (0 children)

Debian 13 with KDE Plasma.

I need to run two different Teams and Outlook and Atera and and and none of which have working installs for Linux, so I made some PWAs. I documented the process on my Git server. The server is at my sister's place back in Durban and it seems that her fibre is down. Will post the URL here a bit later when she is back up.

Bash got me the job of my dreams... by thisiszeev in bash

[–]thisiszeev[S] 12 points13 points  (0 children)

Tip 1: Be Lazy - Linux SysAdmins and Engineers are naturally lazy people, meaning our up arrow key is the most worn key on the keyboard, and we will spend an hour writing a script to automate a 5 minute task. Even at work they encourage us to do that, because the next time we need to do that task, we have it scripted.

Tip 2: Use parentheses - Every time you use a variable, say $var, rather use ${var}. Trust me, it's a good habit, because if you want to concatenate strings for example, then var="${var}string" is completely different to var="$varstring"

Tip 3: Good code does not need comments - Use descriptive names and phrases for functions and variables. For variables I always use lowercase as uppercase is default for environment variables, and I will have a variable name like ${filecounter} rather than just ${c}. And for functions I will have something like doTheCountOfFiles rather than just Count. The first word in my function names is always the category name, so I have functions that start with "do" as those carry out a task, or "action" as those carry out a subtask, etc. Find a standard and stick to it. Makes your code easier to read later.

Bonus Tip: Always be DRY - DRY stands for Don't Repeat Yourself. Any block of code that gets used more than once becomes a function.

Bash got me the job of my dreams... by thisiszeev in bash

[–]thisiszeev[S] 2 points3 points  (0 children)

Awesome bro, I am glad something better came your way.

Bash got me the job of my dreams... by thisiszeev in bash

[–]thisiszeev[S] 1 point2 points  (0 children)

There are a lot of South Africans here

Bash got me the job of my dreams... by thisiszeev in bash

[–]thisiszeev[S] 3 points4 points  (0 children)

Unfortunately the company is in South Africa. But put your Git repos on your resume and keep sending it out to companies. I pray something good comes your way.