Code

What Annoys a Programmer

What Annoys a Programmer

Free Python course ➞ Mini-course for beginners and experienced coders. 4 cool projects in the portfolio, live chat with the speaker. Click and find out what you can learn in the course.

Learn more

Niklas Millard

The author is an experienced specialist in his field, possessing deep knowledge and skills. His work is distinguished by its high quality and unique approach. The author actively shares his experience through articles and publications, striving to help readers understand complex issues and find optimal solutions. Thanks to his experience and professionalism, he has earned the trust and respect of colleagues and readers. Read his materials to learn more about the latest trends and practical recommendations in this field.

A technical writer from Denmark with experience in backend development on the .NET platform at a FinTech company. The author, whose materials have garnered almost a million views, shares his knowledge and experience in the technology field. Previously, he held the position of a leading technical consultant at one of the Big Four companies, which confirms his deep knowledge and professionalism in this field.

Poorly formatted code. Screenshot: Niklas Millard / Medium.com

Awakening the developer in you is actually quite simple. Those whose beliefs are absolutely fixed and unquestioned are especially vulnerable. In this context, teams of programmers, developers, and software engineers can be among the most toxic. This is because such teams often experience conflicts due to rigid views on coding and approaches to problem solving. Programmers who are unwilling to discuss and rethink their principles can create a tense atmosphere, which negatively affects productivity and collaboration within the team. It is important to develop flexible thinking and openness to new ideas to avoid toxicity and promote healthier working relationships.

The topic of self-identity in the programming field is the basis for active discussions. Who are we really? Are we simple developers, reminiscent of monkeys with a keyboard, or are we worthy programmers? Perhaps we are software engineers with high ambitions, or software architects with deep knowledge. Debates over titles and roles in the IT industry often lead to conflict; it's no coincidence that some software engineers become very emotional when referred to simply as "developers." This debate not only raises questions about professional identity but also reflects the diversity of roles and tasks in the tech world. Understanding one's role in this complex ecosystem can help every professional better navigate their career and find their place in the dynamically evolving world of IT.

FROM THE TRANSLATOR

Every translator faces unique challenges in their work. The importance of high-quality translation cannot be underestimated, as it impacts the perception of information and the understanding of cultural nuances. A translator does not simply transfer words from one language to another, but also adapts the content, taking into account the context and target audience. This requires in-depth knowledge not only of languages ​​but also of cultures, making the translation profession complex and multifaceted.

A professional translator must possess research skills to accurately convey the meaning and tone of the original text. It is important to monitor current linguistic trends and changes in the language to remain competitive in the field. High-quality translation can significantly improve the effectiveness of communication between people and organizations, promoting better understanding and collaboration.

Understanding the specifics of various fields, such as legal, medical, or technical translation, also plays a key role. This allows the translator to ensure high accuracy and meet customer requirements. Ultimately, a translator's work is an integral part of global communication and knowledge sharing.

Domestic developers are generally more tolerant. However, if you call our team lead a coder, the chances of a friendly conversation with him will significantly decrease.

This article presents topics that may generate keen interest among programmers. The degree of their influence depends on the level of experience, professional skills, and personal beliefs of the specialist.

The debate about replacing the conditional operator with polymorphism

When I published my first article "Give up the if-else statement", I was pleasantly surprised that in just a few days it garnered over one hundred thousand views. For the Medium platform, this is a significant achievement. It showed that interest in the topic of code optimization and best programming practices is great. The article received a wide response and inspired many developers to think about more efficient approaches to writing code.

I didn't expect my text to provoke such a strong reaction. Readers were so outraged that they created an entire thread on Reddit dedicated to my opinion. It seems that writing poor-quality code using familiar approaches has become some kind of sacred ritual, and my criticism offended the feelings of those who adhere to these principles.

If you are interested in this topic, I recommend reading my articles "How to Replace if-else with the Command Pattern and Event Handlers" and "If-else - Polymorphism for the Poor." These materials will help you gain a deeper understanding of how to improve your code structure by replacing if-else constructs with more efficient approaches, such as the Command Pattern and Event Handlers.

Some people believe that beginners can't just jump into object-oriented programming (OOP). Some argue that this requires careful study of all aspects, a deep understanding of the concepts, and a complete understanding. However, this leads to novice developers perceiving object-oriented thinking as something extremely complex and inaccessible. It's important to understand that OOP can be mastered in stages, starting with the basic principles and gradually deepening your knowledge. This approach will help eliminate the fear of OOP and allow beginners to confidently develop their programming skills.

Setting deadlines without understanding development

One of the first projects I implemented was planned by a colleague of mine, a political science master's student. For this project, we had to develop a solution from scratch. We started by deploying and configuring three cloud environments, then created a database model, developed business logic, and implemented the backend and frontend. This experience not only deepened our knowledge of cloud technologies but also refined our software development skills.

According to my colleague's estimate, I was expected to complete all the project tasks myself within 34-36 hours. However, no one clarified how realistic this timeframe was, as the work schedule was immediately presented to the client.

Developers are very irritated by this situation.

Comment on articles to assert yourself

In articles, developers share their experiences, proposing new approaches and programming methods. Their texts often challenge established practices, demonstrating how code can be written differently. However, under such articles, you can find comments from experienced developers who state: "I've been working in this field for 20 years and have always used proven methods, which, in my opinion, are more effective." This emphasizes that there are many approaches to software development, and everyone is entitled to their own opinion. It is important to remember that innovation and tradition can coexist, and it is worth being open to new ideas, even if they contradict traditional methods.

Comments often reflect the opinions of their authors more than the topic under discussion. This means that someone who has been writing code the same way for 20 years, without updating their style or experimenting with new approaches, is only referring to the article to confirm that their knowledge is still relevant. Dear commentators, unfortunately, the world of technology does not stand still. It is important to be open to change and constantly evolve to keep up with modern programming trends.

Reading comments is not always a pleasant process. Critics actively express their opinions. Every piece of advice from the article can cause controversy, and the proposed methods and recommendations can be questioned due to their lack of universality.

Noticing flaws in someone else's code

It's rare to find a positive assessment of someone else's code. Criticizing it is much easier. This does not require a deep understanding of how and why the code was written. It's easier to call someone else's work poor quality than to admit your own gaps in knowledge.

You can get hung up on any detail. It's important to be able to notice even the smallest nuances, as they can become the basis for deep analysis or an interesting idea. In everyday life, details often go unnoticed, but they can inspire new discoveries or help find solutions to complex problems. Whether in creativity, business, or personal relationships, the ability to focus on the little things opens new horizons and promotes development.

  • curly brackets on the same line,
  • or putting them on separate lines,
  • or choosing the K&R style with an eight-space indent.

A Google search for "curly brackets discussion" reveals a huge number of results that can boggle the imagination. This term covers a variety of topics related to programming, syntax, and code style. Discussion of curly braces is an important aspect of the work of many developers, since their correct use affects the readability and structure of the code. As a result, it is worth paying attention to the various approaches and opinions presented in this area to improve your programming skills and improve the quality of the projects you create.

Variations of the arrangement of curly braces. Screenshot: Niklas Millard / Medium.com

The debate over the proper way to indent code—using tabs or spaces—remains hot among developers. Both approaches have their advantages and disadvantages, and the choice often depends on personal preference and team standards. Using tabs allows for easy customization of indentation width based on each developer's preferences. On the other hand, spaces provide more predictable code display across different platforms and editors. It's important to remember that consistent indentation across a project is critical to maintaining readability and usability of code. To avoid confusion, it is recommended to use one of the methods throughout the project and adhere to generally accepted coding standards.

Criticism without Brake (Code Reviews and Pull Requests)

Toxicity among developers often manifests itself during code reviews and pull requests. It is important to recognize that it is during these moments that conflicts and misunderstandings can arise, which negatively impact teamwork and project quality. Maintaining constructive and respectful communication during such processes helps create a positive atmosphere and improves the final development result.

Code review is a process in which developers evaluate and analyze the code written by their colleagues. It is an important stage in software development, helping to improve code quality, identify errors, and ensure standards compliance. The code review process promotes knowledge sharing among team members and helps to improve the professional skills of all developers. Rather than causing embarrassment, code reviews create an opportunity for constructive criticism and collaborative growth.

The situation with pull requests is often similar. It is very frustrating when, after many hours of work on an interesting feature, you propose its integration into the main branch of the repository, only to have your code rejected. It is especially frustrating when the decision is made by those who were not involved in the development. This can be demotivating and cause frustration in the collaboration process.

During the code review stage and after creating a pull request, some developers openly communicate with others how they should write their code. There is no sense of pity in this process unless "others" includes those giving advice.

Believing that comments are only needed for bad code

Code comments: are they necessary? This issue has been debated for a long time, and even the builders of the Tower of Babel could not come to a consensus. If you decide to ignore comments, be prepared for your code to become the subject of discussion among your colleagues. Comments not only make your code easier to understand, but also help other developers quickly understand the logic of your decisions. Proper use of comments can significantly improve the quality of your code and simplify the process of maintaining and updating it.

Comments often attract attention during the code review stage. This may signal that the code is not written clearly enough and requires additional clarification. Well-structured and understandable code minimizes the need for comments, making it more accessible to other developers.

Captain Obvious was here. Screenshot: Niklas Millard / Medium.com

Counterargument. Thoughtful comments make code much easier to understand for future developers. They help not only those who will work with your code, but also you when you return to your project years later. Comments serve as a kind of guide that makes it easier to navigate the program logic and allows you to quickly restore context. Therefore, high-quality code documentation is an important aspect of its maintenance and development.

In the previous article "Yes, Your Code Needs Comments," I already touched on this topic. Code comments are an important aspect of development that help make code more understandable and maintainable. They serve to explain the logic, functions, and structure of the code, which is especially useful for other developers and for yourself in the future. Without comments, code can become difficult to understand, especially if it is complex or extensive. Therefore, if you want to improve the quality of your code and make it easier to maintain, don't forget to add comments.