You’re a software developer. What are the most common mistakes you make?

-Overengineering solutions: Focusing on complex solutions when simpler approaches might suffice. -Underestimating task complexity: Not fully grasping the scope of a task, leading to missed deadlines.

Pressure to meet deadlines often leads engineers to prioritize coding over testing, risking the omission of critical testing phases. Engineers may assume their code is error-free or that bugs will be caught later in the development process or by end-users. This assumption, coupled with limited test coverage, increases the likelihood of defects slipping through undetected. Moreover, as software systems grow in complexity, it becomes more challenging to devise comprehensive test cases, contributing to insufficient testing efforts. To mitigate this issue, engineers must prioritize testing, allocate ample time and resources, strive for comprehensive test coverage, and continually improve testing practices to deliver higher-quality software.

Not reading the official documentation. No I am not asking young developers to read and by heart 25000 pages of a framework. For example, APEX is a programming language used in salesforce. Like anyone else, even I used to be tempted to search for the the answers in stack overflow. Which is now changed. I always start with the official documentation first because, 1. Salesforce created APEX, they know it better than anyone else in stack overflow/ any other tech blogs. 2. It keeps me up to date with release updates. Some functions may retire with newer API versions and tech blogs may miss it. 3. You know that the documentation is going to be there whenever you need it. (Tech blogs may be retired)

In the rush to meet deadlines or to implement new features, many developers overlook the importance of thorough testing. Skipping or insufficiently performing testing can lead to undetected bugs or flaws in the code, which may only manifest themselves later, potentially causing significant issues for users or clients. Additionally, inadequate testing can result in increased maintenance efforts down the line, as bugs that could have been caught earlier are now more costly to fix. Therefore, it's important to prioritize testing throughout the development process to ensure the reliability, stability, and quality of the software product.

Alguna vez he cometido el error de infravalorar una tarea y puntuarla con menos puntos de la que debiera. Lo importante es hacer previamente un refinamiento técnico, para ver tener una imagen mental a nivel técnico de cómo podemos afrontar dicha tarea, con esa imagen, ya podemos puntuar correctamente la tarea (no sin olvidarnos del testing y pruebas, que aproximadamente se lleva un 40-50% del tiempo)

Neglecting to document the purpose, functionality, and rationale behind specific sections of code can lead to confusion not only for yourself but also for other developers who may need to work with or maintain the code in the future. Insufficient commenting makes it challenging to understand the intent behind certain algorithms, methods, or complex logic, potentially resulting in errors, inefficient debugging processes, and slower development cycles. Therefore, I continuously strive to improve in this aspect by adopting a proactive approach to documenting my code, ensuring that it remains comprehensible, maintainable, and conducive to collaboration throughout its lifecycle.

One of the most common mistake developers make is not following established standards. This can encompass a variety of areas within the development process, including coding conventions, documentation practices, and architectural guidelines. When you deviate from these standards, it often leads to inconsistencies in the codebase, making it harder to maintain and understand for both yourself and other team members. So, it's crucial to recognize the importance of standards and actively strive to adhere to them throughout the development lifecycle.

Being humble is important in software development. Technology is changing rapidly, and you can learn something from everyone. A senior engineer that has 20 years of experience may not understand the latest frontend framework like a person right out of a bootcamp. Remember there is always someone that is better than you at something. This ensures you continue to learn as well as be a better person to work with. Asking for help vs. grinding away at a problem yourself is a difficult balance. On one end, you want to learn and be able to solve problems on your own. On the other end, banging your head against your desk for a week when a single question could solve your problem is not effective either. I still have not perfected this balance.