A few months ago, while scrolling through memory lane on how much I have achieved as a software developer, a lot of questions popped that I could not answer but the highlight was "what flowchart directed my tech career?" and I pondered for hours but obviously I let it slide as a normal person would. Later, that same week I kicked off a project which required me to design a flowchart and it took me so much time to study the symbols, the form of sketching including the tools required, then the question came down my thought box again "what flowchart directed my tech career?" and this time I could not let go, I had to try to draw out my tech career flowchart and trust me it was all shabby and nothing close to direct.
Wikipedia defined flowchart as "a diagrammatic representation of an algorithm, a step-by-step approach to solving a task". It involves using shapes that indicate different steps/processes and yes most importantly, the decisions. Flowchart directly influences the speed of the project in interpreting the algorithms in programming languages.
Driving a career in the tech industry requires a laid down flowchart if you want to acquire speed and accuracy especially due to the doggedness of the industry. The ability to be specific with your goal is fully dependent on how prepared you are to tackle the issue that the step is designed for. Every day, I meet people that say things like "I want to code", "I want to program and stuff", "I want to have a dark screen IDE with plenty of screens" and a whole bunch of other phrases but usually I have one reply "What's your planned endgame for all this?" and suddenly a stern look appears which then I chuckle and ask them to do some rethinking. The beauty of flowchart in design and building is you are carefully directed on what to do per time and this is exactly all you need to drive well in this tech journey either as a newbie or advanced professional. Nobody got to the top by doing everything at once but taking things by bits depending on the plan prior to that time.
And the Lord answered me, and said, Write the vision, and make it plain upon the tables, that he may run that readeth it - Habakkuk 2:2
As a developer or software engineer, every project can be depicted on a flowchart or pseudocode before fully carried out. This can be related to the tech industry as every phase of learning depicts a project; this implies that every phase can have a flowchart that directs it per time. A basic flowchart has the following processes:
- Start: Here, you have decided what you want to do, gathered relevant materials and of course starting immediately.
- Input: Here, It is time to input the time, study, research and most importantly, asking of questions.
- Data Processing: Here, it is quite simple but every studied concept is revisited, processed and search for better options is done as well.
- Decision: The decision process is quite tricky because here you decide what you want to build with the acquired knowledge.
- Procedure Call (i.e defined subprocesses): In this section, based on the project decided in the decision step, you gather all acquired knowledge and start putting the a and bs together.
- Output: This is the best step because you get to showcase what you have done with the acquired knowledge, even though it will be open to scrutiny.
- Stop: In building, you do not really stop because you have to keep working as long world-class standards would be attained.
After all the steps have been followed, you will be bold enough to learn a newer concept that will help build better projects, earn certifications and of course attain an ecstatic height in your career. There is a possibility that you jump from one stack to another till you finally come to a decision but the beauty of completion fuels you up for two things:
While you are about all this, the road is definitely not a smooth one; it has corners and potholes but the ability to drive through is all you need. You must engage the following to optimally ensure you hit the peak you desire through the flowchart model.
- Get involved with resourceful people especially in your field. It was Jeff Bezos, CEO of Amazon that said "Life is too short to be hanging around unresourceful persons".
- Be ready to make mistakes, go back and rework on the step.
- Always revisit the basics so you never forget what to do per time.
- Embrace failure because that is the path to extended learning. *Sundar Pichai, CEO of Google said “Wear your failure as a badge of honor”.
At this point, you should attempt answering the big question. The article details a relationship between flowchart in software processes and driving a successful tech career regardless of your location.
- Take some time and think of exactly what you want to do.
- Draft a plan roughly on a sheet.
- Sketch the flowchart based on the ready-made plans
- Follow the plan judiciously.
- Measure your progress and work more projects.
- Finally, observe your speed.
For the vision us yet for an appointed time, but at the end, it shall speak, and not lie: though it tarry, wait for it; because it will surely come, it will not tarry - Habakkuk 2:3
In conclusion, the idea of a career flowchart is not open to only developers but other careers like design, education, research, accounting, personal study, engineering amongst many others. Always remember that there is no time to waste, we must number our days and apply our hearts to wisdom just as the good book encourages.