My career is driven by a passion for Cyber Security, particularly within cloud-based environments, where I aim to leverage my expertise to create innovative and high-impact solutions. I excel in dynamic, fast-paced settings that demand continuous learning and adaptability.

I have experience in automation, cloud infrastructure management, and secure software development, allowing me to effectively tackle technological challenges. By integrating security practices throughout the development life cycle, I ensure efficient and resilient systems. My expertise in secure coding, infrastructure as code (IaC), and automated security testing enables me to enhance system performance while collaborating with clients to refine requirements and deliver tailored, secure solutions.

As a First Class Computer Science Graduate, my education encompassed software engineering, cyber security, artificial intelligence, database management, and cloud computing. This diverse foundation has equipped me with the skills to solve complex problems efficiently and design scalable, secure systems.

I am committed to making meaningful contributions, whether through designing robust cloud infrastructure, developing secure applications, or enhancing system security. My focus on continuous improvement and embracing the latest technologies motivates me to push the boundaries of what’s possible in the rapidly evolving tech landscape.

• 👀 Interested in Cyber Security & Cloud.
• 🌱 Currently mastering AWS & Azure.
• 📌 Looking to collaborate on AWS & Azure projects.
• 💼 Interested in working together? Reach out to me via LinkedIn or Email.
• 💬 Got a question or just curious about something? Feel free to ask!

Not many developers like to write documentation, but I do. I believe that a well-documented codebase is as important as the code itself. It’s like a story, telling what the code can do and how it works. I always try to write clear, concise, and useful documentation.

Whenever I write documentation, I try to keep the following steps in mind to ensure the reader gets the most out of it:

1. What is this documentation about?
2. Why is this documentation important?
3. How can the reader use this documentation?
4. When should the reader use this documentation?
5. Who is this documentation for?