Coding With Fun
Home Docker Django Node.js Articles Python pip guide FAQ Policy

Criticize code, not people! 15 years of programmer's workplace motto


May 30, 2021 Article blog


Table of contents


Success is bound to be a process of continuous learning and growth. I n the process, guidance and empirical talk from others will give us some inspiration and tips, thus avoiding many unnecessary detours. Choose the good and change it.

In my 15 years in software development, I have gone through many different stages. A t some point, I can't wait to throw all my software development work into hell, preferring to run into the mountains and old forests to feed the cattle. A t other times, everything that works in software development is perfect for me. Today, I finally got my career and personal life in balance, and I can tell myself that I love software development, but I can't forget that it's not always perfect, and it's not perfect for everyone.

This article will share some of the experiences I've learned over the past 15 years that have brought my career and personal life together.

How to achieve harmonious coexistence? Here's what I've learned to share:

First, often change jobs

When starting a career in software development, it's usually started with a beginner, but the pay for a beginner is usually low. N o matter how hard you try, it's not easy to make rapid progress in a company, especially if you're in a small company. If you want to quickly improve your skills and your salary, you need to change jobs often in search of a better position.

If you don't have too many burdens in your life, don't hesitate to change your job.

Second, do a good job for yourself, not for the company

Study hard, improve your skills, and try to do the right thing, but remember to do it for yourself, not for the company. Because when something goes wrong with your job or when the company doesn't need you anymore, you're a number you can sacrifice.

Your time belongs to you, it is your most precious treasure.

If you're fired, think of it as a good opportunity to do things you don't dare do

At one point you work unenthusiastically in a mediocre position, and at another you find a good job at another. Sometimes you're afraid of losing your job, but sometimes being fired is probably the best thing that can happen to you.

A few years ago, I had a good job, a high salary and a lot of ease. B ut the economic crisis has hit, and the company has laid off half of its employees who have no projects to do. I 'm one of them. A t the time, I thought it might be the worst thing that could happen to me, because this job has changed my life a lot, and these changes are probably the best things that affect many aspects of my life. I was very disappointed by the dismissal because I did everything for the company and I sacrificed a lot of personal time for the company.

Now that I'm in a dynamic company, I can do what I want to do and do what I love. The new job made me feel very attractive, and Monday was no longer so annoying.

You can make good friends at work,

But when you change jobs, most of these friends will be lost

Over the years, I've met a lot of people at work. In the company I used to work for, we went to company parties, company lunches, and corporate "events" where everyone went, but all these wonderful harmonys weren't as real as we thought.

Many people just want to please their boss and be critical of colleagues and bosses who are not on the scene. I realized how much time I had wasted on these activities. Now I only go to the activities I want to go to, no longer worry about what other people think.

It was difficult to keep in touch with my former colleagues, and as time went on, I lost touch with most of them. Although I have made some good friends, in most cases, these relationships disappear when I change jobs, and most of my good friends are not important to my career.

If you settle for the status quo, you will lose your chance

One of the worst things you've done in your career is to be too comfortable at work without thinking ahead. If you become comfortable with the status quo, you will be afraid of any changes in your career and of any changes that may occur in your company.

That's the case with one of my friends, who has been doing a comfortable job for more than a decade; he's comfortable and doesn't want to learn anything new, which leads to fewer opportunities for him to improve professionally or in life, and as time goes on, I see him getting scared - and, of course, he hates Mondays.

I've also been working on a very comfortable job for nearly two years, which I can't learn anything new. A nd this job is very easy for me, there is a lot of free time every day. This kind of work made me feel like I was mortgaged for the future, so I decided to change my job.

Sixth, criticize the code, not criticize people

If your co-worker does something wrong, there are many ways you can point it out. B ut never blame people, because doing so will only make you an enemy, not only for you personally, but for your profession. Y ou try to help everyone as much as you can, and if you think you can do it, help him improve the code, but you need to explain why to him and not force it. Remember, life is all about circles, and what happens to your co-workers happens to you as well.

Some developers tend to have a great attachment to what they do, as if their work represents their "baby", and any criticism of it is personal or interpreted as criticism of themselves.

Remember, criticism of code is not criticism of people. J ust because someone has written bad code in the past doesn't mean he's a bad developer right now. T he code is bad, but people don't necessarily. Anything can be improved.

Improving work tools and workspaces

This is very important. I f your work computer is slow, you'll take longer to get things done, and time is money. If your monitor is small, you won't be able to divide the screen into different screens, which can also waste your time.

Now that I work from home every day, I've decided to buy a nice chair, a big monitor (so I can split it into screens when programming), and I'm going to buy a powerful computer. This may seem expensive, but over time it will save you a lot of money.

Now that I can do more projects on my own, I can do what I have to do faster and my back won't hurt.

Also, I have more time to do exercise, so I don't need to do a back massage, at night my eyes can get more rest, I can enjoy reading in bed.

If you have paid or unpaid leave, take it if you can

Time is the most precious thing you have. W ork and money are not the whole of your life. Also, taking an annual vacation is good for you, so you can take the opportunity to think about whether you're happy with what you're doing, or to put aside your day job and try to do something different.

In addition, rest can help you understand what you are doing and whether you are satisfied or dissatisfied with what you are doing.

I always have the best ideas in my free time, and the best decisions in my life are made in my free time.

Avoid technical debt

"Technical debt" is a concept in software development that refers to the implied cost of additional work due to simple (limited) solutions rather than better methods that take longer. Still, I prefer Ward Cunningham's analogy of treating technical debt as financial debt when dealing with it: the extra effort to add new features is equivalent to interest on financial debt.

If you solve a problem quickly, don't think enough, don't use better practices, you'll pay for it in the future, and you'll have to spend hours of free time solving it.

Ten, learn to improvise, do not take the change too pessimistic

I remember the first few months I worked in this industry and I was sure the project would be well defined and the client would know what they wanted. However, I quickly realized that this was not the case.

It makes me anxious because I want the work to be finished on time, which is often impossible. Y ou have to learn to accept that things change all the time, and a lot of times these changes can cause you not to finish a project on time, but it's not your fault. Relax and embrace these changes.

If you don't make decisions at work, others will make decisions for you

If you want to be the one who decides to use a new technology in a project, or a new method, you must know the new technology or method you want to use before telling colleagues about your decision.

If you don't, they may impose their techniques on you or reject your ideas.

Twelve, keep your own rhythm

The world of software development is changing with each passing day, you have to be normal, relax, continue to learn and grow, and always at your own pace. I f you can't learn everything, don't be depressed. The key is to learn important and basic things perfectly and keep up with other technologies.

Thirteen, learn how to read the document

Using something in a hurry will prevent you from reading the document well or understanding the API correctly.

If you want to make sure you're doing the right thing without wasting time, don't try to take shortcuts. R ead the document well. Otherwise, you may not work in the best way possible.

Be critical of the source code of Stack Overflow, Google, and other sources. Don't copy the solution, understand it.


Fourteen, learn to put down the work

Don't take home your work problems. I f there's a bug or a technical problem that you don't know how to solve, leave it until the next day. Y ou'll save yourself a lot of time, and you won't hate your job because you're solving problems all day. Resting the mind is more efficient.

If you don't, anxiety will keep you awake, and the next day you'll face the same problem while falling asleep.

It's not very practical, but it's one of the most valuable lessons I've ever learned.

conclusion:

I'm writing about personal experience in this article, which may seem obvious. B ut in many cases, even if we know how these methods can improve our work and life, we won't do it, and life will eventually force us to do it. Don't leave it until the last minute; if I use these same techniques at the beginning of my work, I believe I will save a lot of time and a lot of detours in the work that follows.