The latest articles on DEV Community by Amir Taghanaki (@amirtghnki). https://dev.to/amirtghnki https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3869768%2Fc72ccc13-e748-4975-9704-ce5c94a40afd.png https://dev.to/amirtghnki en Amir Taghanaki Sun, 07 Jun 2026 14:20:35 +0000 https://dev.to/amirtghnki/-week-1-linux-fundamentals-functional-skills-full-time-work-what-i-learned-51fc https://dev.to/amirtghnki/-week-1-linux-fundamentals-functional-skills-full-time-work-what-i-learned-51fc <h2> What I studied </h2> <p>This week I started learning Linux through hands-on challenges while also studying for Functional Skills Level 2 English and Maths. Alongside this, I continued working full-time in a high-end cocktail bar in London.</p> <p>The biggest challenge wasn't the technical content itself. It was learning how to consistently make progress while balancing study, work, training, and everyday responsibilities.</p> <h2> Key concepts </h2> <ul> <li>Linux is a command-line operating system where most tasks are performed through terminal commands</li> <li>Commands such as ls, cd, cat, grep, mv, gzip, and tar each perform specific functions</li> <li>The Linux file system is organised in a logical hierarchy of files and directories</li> <li>Small mistakes in commands can produce very different outcomes, making attention to detail important</li> <li>Problem-solving is often more valuable than memorisation</li> </ul> <h2> What I didn’t understand at first </h2> <p>At first, Linux felt intimidating because there was no graphical interface guiding me through tasks. I was trying to memorise commands without understanding why they existed or how they related to each other.</p> <p>I also struggled to see how moving around directories and reading files connected to real-world Cloud and DevOps work.</p> <h2> What clicked </h2> <p>The biggest shift happened when I stopped viewing Linux commands as things to memorise and started seeing them as tools.</p> <p>Working in a high-end cocktail bar helped me understand this.</p> <p>Nobody memorises cocktail recipes for the sake of memorisation. You learn them because each recipe solves a specific problem and produces a specific result.</p> <p>Linux commands work the same way.</p> <p>A bartender uses different tools depending on the drink being made. A Linux user uses different commands depending on the task being completed.</p> <p>I also realised that both hospitality and technology rely heavily on systems, preparation, precision, and consistency.</p> <p>A successful service depends on organised stations, repeatable processes, and staying calm under pressure. Cloud and DevOps environments depend on exactly the same principles.</p> <p>Once I made that connection, Linux stopped feeling like a collection of random commands and started feeling like a practical toolkit.</p> <h2> What I’ll do next </h2> <p>Next, I’ll:</p> <ul> <li>Continue progressing through Linux challenges and labs</li> <li>Strengthen my understanding of the Linux file system</li> <li>Study consistently for Functional Skills Level 2 English and Maths</li> <li>Focus on understanding concepts rather than memorising answers</li> <li>Build a routine that balances work, study, fitness, and recovery</li> <li>Complete another week of learning while maintaining full-time employment</li> </ul> beginners devjournal learning linux