When I talk to developers about code complexity, they often say: want You want to write some simple code, but due to deadline pressure or underlying issues, you don’t have the time or knowledge needed to complete and simplify the task.
It’s true that when you put time pressure on developers, they tend to write complex code.However, there is no deadline have It invites complexity. Instead of saying, “This deadline prevents me from writing simple code,” it’s the same thing to say, “I’m not a fast enough programmer to do this easily.” In other words, the faster you are as a programmer, the less likely the quality of your code will be affected by deadlines.
Okay, that’s nice to say, but how do you actually do it? Become Faster? Is it some magical skill that people are born with? Does being somehow “smarter” than others make you faster?
No, it’s not magic or innate. In fact, there is one simple rule that, if followed, will ultimately solve the problem completely.
Whenever you stop and think about it, something is wrong.
It may sound unbelievable, but this works very well. please think about it. When I’m sitting in front of an editor and the coding doesn’t progress, is it because I’m typing slowly? I doubt it. “Too much input” is rarely a developer productivity issue.Instead, pause where you are do not have This is the cause of slow typing. And what do developers typically do during these pauses? Stop and think. Think about problems, tools, email, etc. But whenever this happens, it’s an indication that there’s a problem.
The problem is not the way of thinking itself, but sign Of some other problem. It could be one of many problems.
Understanding
The most common reason developers stop thinking is because they don’t fully understand words and symbols.
Something like this happened just the other day. It took me hours to write what was supposed to be a really simple service. I kept stopping and thinking about it and trying to figure out how it should work. Finally, I realized that I didn’t understand one of the input variables to the main function.i knew name But I never read the definition of that type. to understand What does that variable (word or symbol) mean? Everything became clear as soon as I looked at the code and documentation for this type, and I wrote the service like this: devil (Pun partially intended).
This can happen in almost infinite ways. Many people jump into programming languages without learning anything (,), [, ], , , +, *, and % have what they actually mean in that language. Some developers don’t understand how computers actually work. Remember when I wrote The Unique Secrets of Rockstar programmers? Here’s Why! Because if you really understand it, you won’t have to stop and think about it. That’s also a big motivation behind my book. Understanding that there are unbreakable laws of software design can eliminate many “stop and think” moments.
Therefore, if you notice that you have stopped thinking, do not try to solve the problem in your head, but look for points that you did not understand outside yourself.Then let’s go look With something that will help you understand it. This also applies to questions like “Will a user ever read this text?” We may not have a user experience research department that can actually answer that question, but at least we can draw a picture, show it to someone, and ask for their opinion. Don’t just sit there and think—do something. Only action leads to understanding.
drawing
developers sometimes stop thinking because they can’t hold enough concepts in their heads at once. Many things are intricately connected and need to be thought through. In this case, it is almost always more efficient to write or draw something than to think.What you want is possible look in, or somehow perceived outside of oneself. This is kind of an understanding, but it’s special enough that I wanted to call it out on its own.
boot
Sometimes the problem arises: “I don’t know what code to start writing.” The simplest solution here is to just start writing whatever code you know. can Write now.Please select the part of the problem that you understand completelyCreate a solution, even if it’s just a single function or an unimportant class.
The “core” of your application is often the simplest piece of code you start with. For example, if you want to create a YouTube app, start with a video player. Think of this as a continuous delivery exercise.actually product First, no matter how silly or small the product is.Any other video player that doesn’t have a UI, even if it completion The product is not available yet.
If you don’t even know how to write core code yet, start with the code you’ve written. teeth about) I know. Generally, you will find that once one part of the problem is solved, it becomes much easier to solve the remaining parts. In some cases, the problem may unfold in stages. That is, solving one part reveals the solution to the next part, and so on. Create the parts that don’t require much thought to create now.
skip a step
Another special understanding problem is when you skip some steps in the proper order of development. For example, suppose a Bike object depends on Wheel, Pedals, and Frame objects. If you try to write the entire Bike object without writing the Wheel, Pedals, or Frame objects, you’ll need to do the following: think Detailed information about classes that do not exist. On the other hand, if you created a Wheel class when there was no Bike class at all, you might want to think twice about how the Bike class uses the Wheel class.
A good solution is to implement enough Bike classes to get Wheels to where you need it. Next, write the Wheels class sufficiently to meet your immediate needs in the Bike class. Next, go back to the Bike class and continue working until you need one of the next foundation pieces. Just like in the introduction, find a problem that you can solve without thinking and solve it right away.
Don’t jump beyond the stages of system development and expect productivity to increase.
physical problems
When you don’t eat enough, you tend to get distracted and start thinking because you’re hungry.It may not be a thought about I’m hungry, but I’m won’t do that I think if I had a full stomach I would be able to concentrate. This can also occur with sleep, illness, or any kind of physical problem. This is less common than the “understanding” problem above, so always look for points you didn’t fully understand the first time.If you are sure that you really understand allIn this case, a physical problem is a likely candidate.
distraction
If a developer gets distracted by something external, such as noise, it may take some thinking to remember where they were in the solution. The answer here is relatively simple. Before you start developing, make sure you are in a distraction-free environment or one that is free from distractions. Some people close their office doors, some wear headphones, and some hold up “do not disturb” signs. In some cases, you may need to work with your manager and colleagues to create a truly distraction-free development environment.
self-doubt
Sometimes developers sit back and think, unsure of themselves and their decisions. This solution is similar to the solution in the “Understand” section. If you’re unsure, learn more until you’re confident enough to write code. If you’re feeling anxious as a programmer in general, you may have these issues: many Learn more, including the basics listed in “Why programmers suck.” Think about each part you need to learn until you really understand it, then move on to the next part, and so on. The process of programming always involves learning, but as your knowledge increases, it becomes faster and faster and requires less thinking.
wrong idea
Many people stop thinking in order to make smart decisions because they have been told that thinking is what smart people do. However, this is a mistaken idea.If you could become a genius just by thinking everyone That would be Einstein. Truly wise people learn, observe, decide, and act. They acquire knowledge and use that knowledge to address the problem at hand. If you really want to be smart, you should use your intelligence to take action in the physical universe. Don’t use your intellect just to think great things to yourself.
caveat
All of the above are the secrets to becoming a fast programmer When I sit down to write code. If you’re busy reading emails and attending meetings all day long, you won’t be programming at all. That’s another issue. Some aspects of it are resemble (This is a bit like an organization “stopping thinking”), but it’s not the same.
Still, there are some similar solutions you can try.Perhaps the organization does not fully understand you Or because of your role, they send you a ton of emails and put you in so many meetings. Perhaps there’s something about your organization that you don’t fully understand, like how to attend fewer meetings or receive fewer emails. 🙂 Perhaps even part of the organizational problem could be solved by applying the solutions in this post to groups of people rather than individuals.
-Max
