Want to speed up your web development process or maybe any software programming that you do. These five concepts will speed up your work flow. If you stick around there is an additionally one for you.
Break up your big problems into small ones
Whatever it is you are trying to build or whatever solution you are trying to solve, one of the best ways to make progress faster is to divide the problem into manageable portions.
For example, say you were tasked with building a membership platform for a company so users can interact with each other. You could start simply with the layout. Figure out how to design your website to at least 70% and then you could worry about what language you want to use.
You could go the other way. To get started working on the back end code for users and authentication before you build out your views. Even when learning a complicated area this is just a great way to tackle problems. It also gives you motivation to continue as with each little step you feel motivated to continue.
Or say you are writing code to solve a problem. Don’t try to be cute the first time around. Run through the steps one by one. And then code the steps one by one. You can put it all together afterward you get it working.
Breaking up big problems into smaller ones is one of the core principles of problem solving and will definitely speed up your web development process.
Design first and execute after
When building your web application you want to focus the majority of time on designing what you’re going to build. The design will change but the thought you put into designing it is really where the value lies.
The design always changes so you shouldn’t get worried about how correct your design is as long as you did spend some time considering how your design should be. Why? You inadvertently become a master of our own problem. You would have spent enough time on your problem that not only would you be able to adapt quickly to design changes but you could also predict where they might occur.
Sounds like magic but it isn’t. It’s the result of a well thought out plan. Get this. It’s never the plan that brings great results because no plan survives contact with the enemy but it’s the thought that goes into planning that brings great results. Your design becomes more adaptable while still maintaining shape. Something that is only possible when you are actually learnt in the problem you are attempting to solve.
Understand the problem you are trying to solve
This sounds like common sense but you would be surprised how often this isn’t implemented because of a plethora of reasons human communication can be quite tricky.
As a result one of your first goals is to ensure you understand the problem you are tasked to solve. This will save you a lot of rework and unnecessary work. This is actually especially hard for over enthusiastic developers that think they know what is best and what the client wants.
However this is an ill conceived approach brought about by a lack of self awareness. Figure out exactly what you are trying to solve first and fix that. Fix that and only that. Then you can maybe add some additional features. It seems simple. But the unnecessary and over loaded with features is a way to common software development.
Ignore the unnecessary details until you need them
Well this one is open for interpretation. But the explanation is clear. Don’t get bogged down by unnecessary details. I’m afraid to even mention a possible example because there is someone who will say “that is not unnecessary because; You need to have this because <insert some reason here>”. What those people don’t understand is that they are right and wrong at the same time. If you didn’t know that was possible you learnt something today.
The rule of being right and wrong at the same time simply means the path is up to you. Often in this case ignoring unnecessary details allows you to solve the problem quicker. Then you could further dig into how to make the solution more efficiently. So this is primarily a time consideration and not about code quality consideration. If you need to push something out quickly don’t do more than is necessary it will only slow you down.
Something you might have never been taught because of how BAD!!! it is but some things that fall under the unnecessary category includes:
- Passwords and authentication (OMG..can you believe it)
- Fancy layouts
- Friendly workflows
- Mobile optimizations
- Browser support
- Color schemes
- Progress bars for long loading tasks
The list can goes on.
Does this mean you will be creating applications without password protected. Common dude. Context matters. Maybe provide a unique URL or something. Figure it out. It’s up to you to decide if it is unnecessary. How you plan to implement later and what are the downsides to leaving it out is for you to consider but you can leave it out.
Work with the tools you are most familiar with
You can learn on your own down time but if you want to produce something quicker or faster than usual it’s best to work with tools you are most familiar with. This means if you want to try something new you should get familiar with it first. Whether it is a language or some framework. Maybe it is a git provider or hosting platforms whatever the tool is, stick with what you know. Also remember the title of the article. It isn’t five ways to become a more all rounded developer. If you want to speed up your web development stick with what you know.
Create your own workflow. Create your own templates. Create your own repository of custom functions and classes that you frequently use. Your own treasure cove of custom snippets. Your most often accessed stackoverflow links. All in one location. So for that next project you need to implement you can execute… execute…execute.
Do one thing at a time
Bonus round. For sticking around. This is faster because you can consider your project as a destination. You don’t reach your destination faster by spreading yourself to different directions. Since all of you still will need to reach that same location. So focus on one step at a time and you will get there. In the end it will be faster than jumping all over different parts of your project.
These five steps can really bring a lot of benefits to your software development process. It can save you from wasting time and allow you to bring your projects to completion quicker than you usually would.
What steps do you take to speed up your software development project?