Thoughts about software engineering and life
Dependency Injection is a technique (Design Pattern = Which mean its a common solution to a common problem in software development design) that allow use to create a code It helps to create loosely coupled code, making it easier to manage, test, and maintain.
I used to believe that building everything from scratch was the mark of a good developer. However, I understand later that this mindset reflects a lack of experience and problem-solving skills. In the real world, developers often rely on prebuilt solutions rather than creating everything themselves. While we might not always understand the inner workings Continue reading “You can rely on existing solutions”
I often find myself back to the Laravel documentation whenever I need to create new factories and seeders for my projects, whether they’re learning exercises, hobby projects, or real-world applications (bored doing the same actions every time). To make this process easy, I’ve decided to create a guide that I can refer to whenever needed, Continue reading “A Quick Guide to Creating Laravel Factories and Seeders”
In JavaScript, a promise is like a promise someone made to bring you something. It works based on four main steps: creating a promise, waiting for the promise to happen, the promise being fulfilled (meaning they come with the thing you were waiting for), or the promise being broken (meaning they couldn’t come with that Continue reading “Promises in life is likes promises in JavaScript”
One of the most important things I’ve focused on recently is reading a lot of code written by others. Even if I don’t understand some large parts of the code blocks I’m reading, it’s a way to train my brain muscles, boosting both my imagination and logic. By reading others’ code, you gain new perspectives Continue reading “Code Reading is important!”
The best way to test if you are addicted to something is to try living one day without it. This way, you can observe your behavior. That’s exactly what I tried today. I used to be a heavy YouTube user, primarily for learning technical and Islamic topics. I believed I was using it positively, which Continue reading “One Day Without Using YouTube”
When you are part of a team, it’s not about being a “wow” person; it’s about truly being part of the team. This idea always motivates me to keep learning, so I can be an asset to the team. When you’re part of a team, strive to do just this: It’s about working as a Continue reading “It’s not about being “WOW”, it’s about be a part of the team.”
As a software developer throughout my career, I’ve learned many things from several mistakes, one of which is related to creating effective pull requests. Here are some steps to provide a well-structured pull request that simplifies the review process: 1. Break Down Large Tasks: If you’re dealing with a large task that requires extensive changes Continue reading “Create a good pull request”
When you encounter an error during your workday as a developer, don’t simply acknowledge the mistake and promise to avoid it next time. From my personal experience, that approach doesn’t work, and you’re likely to forget the error for sure. Instead, write down what you should avoid in the future. Place these notes somewhere you Continue reading “Document the Problems You Solve!”
In my pursuit of solidifying my backend knowledge, I want to share with you an overview of the OSI model as I understand it. This post serves as a reference for me to revisit and update later. The OSI Model, which stands for Open Systems Interconnection Model, is a conceptual framework that defines the transformation Continue reading “Backend Engineering Solidify: An Overview of the OSI Model”