Week 3: Bash Scripting & CTF Challenges
This week was meant to be a contained week with Bash scripting and Docker fundamentals. Instead, it turned into a week where I learned that knowing Linux commands and writing a script are not the same skill, and then I got an unplanned 48-hour technical assessment on top of it.
Here's what I did.
What I Did
The original plan for this week was Bash scripting and starting Docker. I'm glad to say I got the scripting done, but I had to push Docker because of time constraints, and some other activities came my way.
I started the week with the hope of writing 3 scripts, but on my first attempt, I realized writing a script is way beyond just knowing Linux commands, so I had to go back and start with the smallest possible script (a script echoing "Hello World!"), and then slowly add concepts, variables, and conditionals so I could get a grasp of what I could do next. Thankfully, I came across a 7-day Bash scripting challenge on GitHub, and that gave me a concrete framework to work with. I didn't do all 7 days or 7 challenges; I only did 3, with the hope of completing the other 4 as I grow in my expertise.
From the challenge, I wrote three scripts:
A basic test script
A directory exploration script
A disk management script
Outside of the plan, I got an email on Monday morning informing me about a technical assessment for an AI red-teaming role I applied for, and that I had 48 hours to complete it and submit a report. It was a CTF-style challenge covering both web and network vectors. I reproduced the exploits, documented the steps for reproduction, and assessed the impact and severity for each one.
What I Learned
For the scripting, it was a good way to fully understand how variables, conditions, and the general syntax work.
Starting small removed all the intimidation, and it gave me a way to break it to break writing a script down.
The CTF was a different one on its own, definitely my best experience with CTFs. It was its own kind of learning, less "new concept," more confirmation that reproducing and documenting an exploit under a bit of time pressure is a different skill than reading about one.
What Didn't Go to Plan
I couldn't go ahead with Docker as planned for the week, but Week 4 is already "Docker deep dive," so I can simply merge into that instead of creating a real gap.
What's Next
Docker, for real this time: images vs. containers, container lifecycle, volumes, and building my first Dockerfile, adding Week 3's deferred Docker intro into Week 4's planned deep dive.
