I personally know some developers who are very talented and can create wonderful pieces of software with no or little struggle. Because of these gifted individuals, our industry is full of high expectations. But the sad truth is: not everyone is a ninja/guru/rockstar developer.
And that’s exactly who I am: a mediocre developer. This article will guide you through surviving in the industry if you are not a genius.
I fail to remember a lot of the things. Like functions and methods from the standard library, arguments positions, package names, boilerplate code and so on.
So, I have to google it. And I do it on a daily basis. I also reuse code from old projects. Sometimes I even copy-paste answers from StackOverflow or Github. Yes, it is actually a thing: StackOverflow Driven Development.
But I am not alone. A lot of other developers do it too. There’s a popular twitter discussion which was started by the creator of
Ruby on Rails.
But why is that bad in the first place? Well, there are several disadvantages about it:
- It allows you to copy bad design decisions or vulnerable code from other people
- It forms a specific mindset: if we can not google something up, then “Houston, we have a problem”
- When the internet will go down, we won’t be able to work
But, I don’t think that it is a big problem. It even may serve as your secret weapon. I have some pieces of advice to follow to decrease negative effects.
How to survive:
IDEto get autocompletion and suggestions, so you won’t have to google the language basics
- Remember where (not how) you have already solved this problem. So you can always look there for the solution
- All code you paste into the project should be analyzed, refactored, and reviewed later. This way we won’t harm the project with the bad code, but help it with the fast solution
Machines always do what they told. Sometimes they are just told to do the wrong thing. So, the main problem in software development is not machines, but developers’ mental capacity. It is very limited. So, we - mediocre developers - cannot waste it to create complex abstractions, obscure algorithms, or unreadable long code blocks. Just keep it simple.
But how can we tell that this code is simple and that one is complex? We need to use
WTFs/Minute method to measure code quality.
The principle is very easy and clear to understand. Whenever you find something in the code you do not understand - it is too complex. What can you do?
- Rewrite it to have cleanner design
- Provide documentation
- Add comments to the most tricky parts. But remember, that comments are the code smell themselves
How to write simple things from the beginning:
- Use correct names for variables, functions, and classes
- Make sure that every part of your program does only one thing
- Prefer pure functions over regular functions
- Prefer regular functions over classes
- Fallback to classes only in a strong need
Some developers proved to deliver high-quality code. Like this woman: Margaret Hamilton, lead software engineer of the Apollo Project. In this picture she is standing next to the code she wrote for the moon mission:
But, whenever I write any code - I do not trust myself. I can screw things up really badly even in the easiest parts of the project. This may include:
- Language errors
- Logic errors
- Design errors
- Style errors
- Security errors
- WTF errors (my all-time favorite!)
The thing is: anyone should not be allowed to write code with obvious errors. At least, we should try. But how can I protect the project from myself? There are multiple ways to do it.
How to survive:
- Write tests. Write a lot of tests. Starting from integration tests down to unit tests. Run it in the
CIbefore each pull request. This will protect you from some logical errors
- Use static typing or optional static typing. For example, we use
- Use automated style checks. There are tons of the style checkers for every language
- Use quality checks. Some tools run some complex heuristic algorithms on your code base to detect different problems like this line has too many logics inside, this class is not needed, this function is too complex
- Review your code. Review it before merging to
master. And sometime after the merge
- Pay other people to audit your code. This technique has a huge positive influence! Because when developers look at your code for the first time it is easier for them to spot inconsistencies and bad design decisions
When my team has developed our first big software project almost ten years ago, we have shipped it as
java source files. And it failed to compile on the target server. That was several hours before the presentation to the client. This was a big failure! Somehow we have managed to get it up and running, but it was a life-changing experience.
That happened because there was a lot of configuration and a lot of complexity in the build pipeline. And we could not properly manage the complexity of this system. Since that day to reduce the complexity on this step I try to pack my programs in isolated environments. And to test them in this environment before the actual deploy happens.
In the last years with the rise of
docker (and containers in general), it became as easy as ever.
docker allows you to run development, tests, and production in the same isolated environment. So, you would never miss any important things along the way.
Wound’t you? Talking about myself, I always forget something while creating servers, initially configuring them, or linking them together. There are so many things to keep in mind! Hopefully, we can still automate it. There are different awesome tools to automate your deployment process. Such as:
packer. Read about them to find which one do you actually need for your tasks.
I also try to set up
CD as soon as possible. So I will be reported if my build failed in testing or in deployment.
How to survive:
- Automate anything you use for deploy
dockerfor application development, testing, and deploying
- Use deployment tools
Oh, at last, my application is in production. It is working now. I can have a short nap, nothing is going to break. Wait, no! Everything is going to break. And yes, I mean it: everything.
Actually, there are some tools to make finding and fixing existing problems easier.
Sentry. When an error happens for any of your users - you will be notified. Has bindings to almost any programming language
- Different services and tools to collect logs from multiple processes and servers into one place
- Server monitoring. That’s the place where you can configure monitors for CPUs, disks, networks, and memory. You can even spot the time to scale before the users will actually break your service
To put it shortly, we need to monitor our application in production. We sometimes use all of these tools, sometimes only the most required parts.
Wow, that’s a lot of things to learn. But that’s how it works. If we want to write good software we need to constantly learn how to do it. There are no short ways or magical tricks. Just learn how to be better every single day.
In conclusion, we need to understand two basic things:
- Problems happen to everyone. The only thing that matters is how ready we are for these problems
- We can reduce the sources of the problems to some acceptable rates
And it has nothing to do with your mental capacity or mindset.