As a software developer, you may be familiar with the concept of Test-Driven Development (TDD). This is a methodology that involves writing tests for a piece of code before the code itself ...
E25 - Neurodivergence and the tech industry
Audio only 🎧 Neurodiversity refers to the variance of neurological differences, behaviours and brain functions within the human population. The concept of neurodiversity has become contr...
E24 - Contracting as a Software Engineer
Audio only 🎧 This episode provides an in-depth look into the world of contracting and freelancing, and we share our background and experience in the field. Zac and I discuss why companie...
Great Pull Request Reviews #softwareengineering #coding #programming
Code reviews don’t have to be complicated and obscure. When reviewing a pull request, consider the following: The pull request description adequately documents the context of the change...
Stop adding more code! #softwareengineering
As software engineers, we often find ourselves overwhelmed with work and blaming our managers for not giving us enough resources. But have you ever stopped to think about how much of that w...
The Art of System Design: Practical guide & Lessons from the field
This video covers the essentials of system design. I’ll explain how to define the requirements and goals of your system, document the discovery process, and understand the motivations and c...
Why don't you speak in Arabic?
This is a short video in Arabic explaining to my Arabic speaking audience why my content is in English!
E23 - Software Testing is NOT what you’re familiar with!
Audio only 🎧 In this episode, Maaret Pyhäjärvi, a principal test engineer at Vaisala and respected speaker, author, and mentor, discusses the evolution of software testing & quality ...
A software architects leads by guiding and coaching #softwareengineering
A software architect is a key member of a software engineering team, responsible for the overall design and structure of a software system. They do not directly lead engineering teams, in...
A "Comprehensive" Review || Software Architect || Build a solid study plan
The software architect roadmap is important because it provides a structured approach to continuous learning and professional development. However, it can easily become overwhelming to figu...
Toxic work environments #softwareengineering #workplace
In my opinion, some signs that you might be better off working somewhere else include an unhealthy hierarchy, a lack of people who have been at the company for more than two years, a lack ...
E22 - What is Technical Debt & how can we deal with it?
Audio only 🎧 What’s technical debt? What is considered technical debt? How is technical debt measured? Who owns technical debt? How to pay-off tech debt? All these questions and more ar...
What is Elon Musk thinking?
Elon Musk has recently purchased Twitter and plans to do massive layoffs. Here are some thoughts on what might be going through his mind: Elon has stated that decision making from first pr...
Job titles in tech are meaningless #softwareengineering #coding
Job titles in tech are often meaningless and can be misleading. For example, you might ask for a promotion but only receive a new title without a pay bump. Job titles in tech are not regul...
The COMPLETE backend engineer roadmap reviewed | Build a study plan
Roadmaps are great to get a feel for the topics you should learn as a software engineer but they don’t help you build a study plan. In this video, I breakdown one of the most popular backen...
Getting promoted is not about hard work #softwareengineering
Getting promoted is not about how much effort you put into your work, but about visibility and impact. Here are some key points to keep in mind: Master your craft so that you can do di...
How many tech stacks should you learn? #softwareengineering #coding
As a software engineer, how many tech stacks should you know? It is not necessary to know all of them, but it is important to be “very good” at at least one tech stack. Early in your ...
What is tech debt?! #softwareengineering #coding
Technical debt is not the same as poorly written code. Technical debt refers to the shortcuts or compromises that are made in order to ship a product faster, but which may have negative co...