Over the years I’ve been learning, designing, implementing and supporting solutions backed by the knowledge shared by various technology enthusiasts, professionals and hobbyists.
Pair that w/ my hands on experiences backed by more frequent than I’d like to admit brute forcing
/ head banging
🤘 and on the job work I feel that
I’ve acquired a decent share of knowledge/workflows that I’d like to give back to the communities that have fostered my own learning.
With that effort in mind I decided to finally take the dive into public knowledge sharing & blogging, starting here!
My first goal was to create a consistent format that ammends frustrations I’ve seen w/ other blogs and articles, tailoring this to preferences I see as helping foster
more effecient knowledge soaking
if you will since everyone has different learning styles.
Some like to read and follow line by line while others learn better by reverse engineering the code or solution itself.
Naturally there are others who are somewhere in between, so the format I’ve created below is what I’ll be following in an attempt to meet the needs of all 3 scenarios.
I’m always open to suggestions/improvements/criticism so if anyone has ideas for positive improvements I’m all ears, here goes the first step on this journey!
I’ve recently been thinking about starting on xyz or I stumbled upon xyz or had to solve for xyz recently so I decided to dive in, here’s my journey if you want to follow along
1
2
3
4
if [ $? -ne 0 ]; then
echo "The command was not successful.";
#do the needful / exit
fi;
I’ve found that doing
xyz
or following the guide posted at Helpful Guide makes this easier
Something to keep in mind,
xyz
is affected byabc
in file /opt/service/assets/config.yml
Doing this without first adding line
sed -i /foo/bar/
to file/opt/foo/bar/foobar.sh
will result in a failure