Many developers feel they need to write clean code. They’re good developers only if they write clean code. They’re lousy developers if they don’t.
I feel the same way too. And I try to make my code as clean as possible.
But this attempt to write clean code actually slows most of us down. We learn slower. We make fewer things. And as a result, we contribute lesser to this world.
I want to make a point that it’s okay to write dirty code. I want to give permission for myself and for you to write dirty code in this article.
Many people try to learn code this way:
- Watch a video
- Follow along with the video
- Expect they’ll be able to code
But they fail. They can’t build things on their own. They panic when they stare into a blank file.
Well, that’s because they missed a critical step in the learning process. They didn’t sit down and figure things out.
Let’s say you finish a task before the time is up. You have another 5 to 15 minutes more. What do you do with this time?
If you get distracted during work, you may also end up with this 5 to 15 minutes left. What do you do with it?
If you find yourself in a distracting situation, like having to take care of a baby who cries every now and then. You probably have 5 to 15 minutes pockets of time very often. How do you use this time?
I think you can use it in four possible ways:
- Use it do errands
- Use it to learn
- Start the next thing
- Use it to chill
We’re already at the end of 2018. This year passed by so quickly. To be honest, 2018 is a weird year for me because it’s filled with great success, but at the same time, I feel like nothing special has happened.
It’s much simpler.
Here’s what we’re building:
Is it possible to know if an input is empty with only CSS?
- Hide a dropdown if the input is empty
- Show the dropdown if the input is filled
I found a way to do it. It’s not perfect. There are a few nuances involved, but I want to share it with you.
If you don’t want to commit a file into a Git repository, it makes sense not to have the file show up in the staging area.
You can do this with a Gitignore file.
Why you have to care about old browsers?
Who use old browsers? Probably, users with old computers?
If they use old computers, they probably don’t have money to buy a new one.
If they don’t have money to buy a new computer, they probably will not buy anything from you as well.
If they will not buy anything from you, why you have to care about supporting their browsers?
To a business person, that’s a perfectly reasonable train of thought. But why do we developers still insist on supporting older browsers?
You should not commit these four types of files into your Git repository.
- Files that don’t belong to the project
- Files that are automatically generated
- Libraries (depends on the situation)
But there are more things you can do.