Planning Too Much Before Writing Code - Deepstash

Learn more about computerscience with this collection

Find out the challenges it poses

Learn about the potential impact on society

Understanding the concept of Metaverse


Discover 76 similar ideas in

It takes just

11 mins to read

Planning Too Much Before Writing Code

Do not look for a perfect plan before jumping into writing code. 

Look for a good enough plan, something that you can use to get started. The truth is, your plan will change, but what it was good for is to force you into some structure that leads to more clarity in your code. Too much planning is simply a waste of your time.


2.96K reads


Having the Wrong Attitude Towards Code Reviews

Coding newbies often look at code reviews as criticism. Look at every code review as a learning opportunity. 

You are a forever code Learner. You need to accept that.


1.17K reads

Writing Comments About the Obvious Things

Most comments can be replaced with Better-Named elements in your code. If you are tempted to write a what comment to clarify the code, please do not point out the obvious. Remove comments like these if you have to deal with them.

Educate programmers who write comments about...


1.43K reads

Picking the First Solution

Your job as a professional programmer is not to find a solution to the problem. It is to find the simplest solution to the problem.

Simple means the solution has to work correctly and perform adequately but still be simple enough to read, understand, and maintain.


2.5K reads

Writing Code Without Planning

Writing Code Without Planning

Writing quality programs is a process with a flow:
Think. Research. Plan. Write. Validate. Modify.

One of the biggest mistakes you can make as a beginner programmer is to start writing c...


3.53K reads

Obsessing About Performance

The good rule to remember about this is: if you cannot measure the suspected performance problem with the code, do not attempt to optimize it.

If you are optimizing before executing the code, chances are you are doing it prematurely. There is also a big chance that the optimization you are ...


1.07K reads

Not Targeting the End-user Experience

Do not be that developer. Be one of the professional ones who put themselves in their end-users’ shoes. They imagine what the users of this particular feature need and how they might behave. 

They think about the ways to make the feature easy for the users to find and use, not about the eas...


1K reads

Not Questioning Existing Code

If the author of that code is long gone or cannot remember it, research that code and try to understand everything about it. 

Only when you completely understand the code you get to form an opinion whether it is bad or good. Do not assume anything before that.


1.23K reads

Not Picking the Right Tool for the Job

Everyone has their list of favorite tools to assist them in their programming-related activates. Some tools are great and some are bad but most tools are great for one particular thing and not so great for many others.

Relying on a tool’s popularity rather than how much it fits the ...


944 reads

Not Understanding that Code Problems Will Cause Data Problems

An important aspect of a program is often the management of some form of data. The program will be the interface to add new records, delete old ones, and modify others.

Even the smallest bugs in a program’s code will result in an unpredictable state for the data it manages. This is especial...


910 reads

Not Quitting

Don't be attached to code because of how much effort you put into it. Bad code needs to be discarded if it isn't working. If you're not happy with a solution, you'll be stuck with it.

When it comes to writing programs, the right mentality is to fail early and fail often. Th...


2.24K reads

Planning for the Unknown

Do not write code that you do not need today. Do not plan for the unknown future. Writing a feature because you think that you might need it in the future is simply wrong. 

Always write the minimum amount of code that you need today for the solution that you are imp...


1.93K reads

Not Taking Breaks

You will often be in the zone and forget to take breaks. 

Take a lot of short breaks. Leave your chair and take a short walk. Come back to the code with fresh eyes.


1.09K reads

Not Googling

  • Unless you are using a bleeding-edge technology, when you run into a problem, chances are someone else ran into the same problem and found a solution for it. Save yourself some time and Google It First.
  • Sometimes, Googling will reveal that what you think is a...


2.21K reads

23) Over-Using Shared State

Every variable we define represents a shared state. It holds data that can be changed by all elements in the same scope as that variable. 

The more global the scope is, the worse the span of this shared state. Try to keep new states contained in small scopes and make sure they do not leak u...


966 reads

Not Using Encapsulation

The big idea here is that you want your code to have High Cohesion and Low Coupling, which is just a fancy term that means keep related code together (in a class) and reduce the dependencies between different classes.


2.29K reads

Reinventing the Wheel

In programming, some wheels are simply worth reinventing. Programming is not a well-defined domain. So many things change so fast and new requirements are introduced faster than any team can handle.

However, if you need a wheel, do not buy a whole new car and put the car that you ar...


1.05K reads

Not Using the Right Data Structures

The most common data structure mistake is probably the use of lists instead of maps to manage a list of records. Using lists for scalar values is okay and often the better choice for large collections. 

Not using stacks when writing code that requires some form of Recursion...


1.72K reads

Obsessing About Best Practices

  • I think the term “best practices” is actually harmful. It implies that no further research is needed. Here is the BEST practice ever. Do not question it!
  • There are no best practices. There are probably good practices today and for this programming language.
  • Some of what we pr...


1.14K reads

Not Using Source Control

Source control is not about just pushing your changes for others to have and build on. It is a lot bigger than that. Source control is about clear history. Code will be questioned and the history of the progress of that code will help answer some of the tough questions. This is why we care about ...


836 reads

Making Existing Code Worse

Here are a few wrong practices that usually make the code a bigger mess than what it was (not a complete list): 

  • If you Copy/Paste a code section to only change a line after that, you are simply Duplicating code.
  • If you need to use a value in multiple places, that value belongs...


1.49K reads

Underestimating the Importance of Code Quality

Never underestimate the importance of code quality. Look at coding as a way to communicate implementations. Your main job as a coder is to clearly communicate the implementations of any solutions that you are working on.

If you are not consistent with your indentation and capitalization, yo...


2.74K reads

Not Writing Tests

If you think you are an expert programmer, you are a newbie. If you are not writing tests in code, you are most likely testing your program manually.

There is nothing wrong with manually testing your code. However, you should manually test your code to figure out how to automatica...


1.31K reads




Product designer

Related collections

More like this

Doing It Badly

It's a normal human trait to wait for the perfect time before starting anything. This can cause long delays, stress, and anxiety. Indecision leads to inertia and while it is good to plan first, one should dive into action and expedite up the decision-making process to avoid losing the 'time...

Rules of storytelling, according to Pixar

  • Emphasize trying more than success.
  • Having an initial theme while writing is important but don’t get too attached to it.
  • Cutting things out is important part of the writing process.
  • Challenge your characters

Disruption of Progress

Disruption of Progress

Whenever an outside force interrupts our progress - we skip gym for a day or two for example - it sends a message to our brains that we aren't good enough and we can't do it and that we should just give up.

Disruption is the biggest obstacle to overcome bu...

Read & Learn

20x Faster





Access to 200,000+ ideas

Access to the mobile app

Unlimited idea saving & library

Unlimited history

Unlimited listening to ideas

Downloading & offline access

Personalized recommendations

Supercharge your mind with one idea per day

Enter your email and spend 1 minute every day to learn something new.


I agree to receive email updates