Code

"I don't care – as long as it works," or The Best Advice for a Programmer

"I don't care – as long as it works," or The Best Advice for a Programmer

Free Course: "Quick Start in Python"

Learn More

After the app shipped, our technical lead left the company, and I was promoted to take his place. At that moment, I noticed something strange: I felt like I had to continue his tradition. I didn't end up rewriting the code over and over again, but the same perfectionist spirit seemed to awaken within me. This commitment to quality and improvement became my priority, and I realized how important it was to maintain high standards in development.

After my promotion, I was tasked with developing end-to-end sign-on for corporate clients. The task involved writing a small feature, consisting of only five lines of code. This feature was supposed to provide convenient and secure access to the system for all users, which would significantly simplify the authorization process and increase the level of data security. As a result, despite the simplicity of implementation, this feature significantly contributed to improving the user experience and optimizing work with corporate clients.

At this point, questions and doubts overwhelmed me.

  • What is the best way to write it? And where should I put it then?
  • Place it in a separate file? Or maybe along with other end-to-end sign-on code?
  • Should it be a class with one public function?
  • Since it is so small, it would be better to tuck it somewhere and forget about it. But would it be right?

It was as if a shadow of perfectionism had settled within me. I'd internalized its thinking, fixating on a decision that didn't really matter. This decision didn't impact the results of our work and wasn't critical for the clients paying for our company's services.

I couldn't make a decision on my own, so I reached out to the VP of Engineering. I asked him about the best way to handle this small feature. I expected a long discussion, similar to the ones I'd had with my previous tech lead.

The conversation was brief, but its content radically changed my approach to programming and my professional work in general. The answer I heard became an important lesson for me and forced me to rethink my methods and work strategy. I realized that correctly perceiving information and being open to new approaches can significantly impact results. Now I strive to apply these principles in my practice to achieve better results and continuously develop as a specialist.

"I don't care how it looks." The main thing is that the system functions effectively."

Photo: Jason Hogan / Unsplash

I felt an unexpected sense of freedom.

As a tech lead, I am responsible for my team and its success. My job is to guide and support my colleagues, ensuring effective collaboration and high results. It's important to create an atmosphere of trust and mutual support so that each team member can realize their potential and contribute to the overall project. I'm proud to work with this team and strive to help it grow and reach new heights.

Our goal was to quickly deliver a finished product. We weren't satisfied with the previous approach, which relied on academic standards, perfectionism, and online articles. Why should I worry about whether our code will appeal to outsiders or whether it meets someone else's expectations of correctness? We strive for efficiency and practicality, focusing on the real needs of users, not theoretical norms.

Approaches and best practices are constantly evolving. As the editor of Better Programming, I can attest to this as an important aspect of content creation. A blog post may be theoretically sound, but without practical value, it will have no real-world impact. It's important to consider that successful content must not only be informative but also applicable to real-world situations.

A conversation with my VP radically changed my approach to team management. I realized the importance of effective communication and strategic thinking when working with a team. I now focus more on developing relationships within the team and creating a motivating atmosphere. This experience has helped me better understand the needs of my employees and optimize work processes. Successful team management requires not only skills but also the ability to adapt and continuously learn.

I realized that my procrastination was actually hidden fear.

"Remember your question. We'll come back to it after the release."

Now I said these words often, and the whole team knew what to do first. We developed new functionality, ran tests, fixed any bugs found, marked the task as complete, and moved on to the next one. Meanwhile, the list of tasks requiring repeated attention remained on the side.

We released new releases regularly, but disaster still did not occur, despite the fact that our code left much to be desired.

Having standards for the codebase and using best practices within the team is the norm. However, if these standards hinder the team's efficiency, slowing down the process due to the need to adapt the code to a certain style or due to rigid engineering beliefs, this can negatively impact the end result. It is important to find a balance between adhering to standards and maintaining productivity in order to achieve a high-quality result in an optimal time frame.

It doesn't matter whether you're just starting to learn programming or already have experience in this field. The main focus should be on ensuring that your code functions effectively. Focus on the practical application of your knowledge and skills, not on meeting someone else's expectations. Develop your skills by creating working solutions, and this will lead to a successful career in programming.

Your code should be safe, reliable, and efficient. However, it's important to remember that at the beginning of development, there is always a window of time when code flaws don't seriously harm the company, since it is not yet running on a large scale. Don't worry about this unnecessarily. The main thing is to ensure that the code functions.

As the project evolves, it will inevitably be necessary to rewrite and improve the code. Remember to return to any issues that arise after the release to take them into account when developing the next version of the product. This will help optimize functionality and improve the quality of the final product. Feedback and analysis of problems at previous stages will lay the foundation for a successful upgrade.

Failure to have a working application on time can lead to significant financial losses for the company. It is important to ensure timely development to minimize risks and maintain a competitive advantage.