Pseudo-code
Writing pseudo code is very important for developers to understand. Not only is it important to read pseudo-code but also to write it. Make sure your pseudo-code is clear and easy to understand. Sometimes you can tell how good of a developer someone is but how well they write pseudo-code.
Flow diagram
When trying to brainstorm or tackle a bug it is a great idea to use a flow diagram. By using a flow diagram or chart you can see how the program flows from point a to b to c and all the way to the final destination. I have used this technique a lot when I’d be stuck with something I couldn’t seem to figure out. Once the flow diagram is complete in front of me, almost 99% of the time, I could literally point to where my issue was. It helps you focus on the big picture and not get buried in the details.
Make sure you use boxes and circles for steps or entities and triangles for decision. Use arrows to signal flows.
If you want to take your skills to the next level you need to work on your networking skill. Networking skill is what’s going to connect you with people in your community who know and have done what you are looking for.
Tech Meetup
I suggest you go to tech meetups that are related to the technologies you want to learn or master. Even if you just wanted to keep up with a technology you have been using for awhile. It’s a great place for you as a developer to listen and learn what others have done and found in their research. In many cases, people at meetups are just like you in that they are there to learn and network. I have heard stories of people who met at a meetup and they started to learn together which helps their learning process.
Another reason to be in meetups is that there are people there with great and extensive experience that can help and guide you in your search. People go to meetups not only to learn but to share knowledge. It’s a great place for companies to find potential candidates or employees. You as a developer have the opportunity to show case your skillset in the discussion as well as the opportunity to connect with these companies.
If you want a partner to start a company with tech meetups are the way to go. Tech meetups are full of people who want to learn, grow, and build ideas.
Online Community
Another great place to be in is an online community. Nowadays it’s not just one place. You might have to join a couple of online communities dependening on the technology you want to learn. For me I have joined a couple of communities via facebook and linkedIn. All you have to do on your linkedIn account is search for your technology of learning, for example Java, Python, Javascript, etc. You will see many options of communities to join.
An online community is also a great place for you to learn from others as well as sharing your knowledge. Make your presence known in these communities if you want to give yourself a chance to find a job or someone to start a side hustle with.
Teamwork is vital to your success and the success of the company you are working for. It is very rare that you work alone unless you are working on a side project. If you are working for a company you are most likely to work in a team environment.
Being able to work together with team members is very important. As a team you have goals and plans that you want to accomplish. These goals and plans can only work if you and the team work together. If one of the team members or you are failing to pull your own weight then the team will be affected. The team can have much more success and move much farther as a unit as opposed to individuals.
Working well with others makes what you’re working on more fun, and makes people more likely to help you in the future.
When speaking to a team member, make sure you are polite and respectful. Make sure you think about what to say and how to say it before presenting your thoughts. A lot of times we as developers get into a zone while coding so when we get interupted it takes us a couple minutes to switch context and get up to speed on a topic. Be aware of that while speaking.
Another important thing is communicating bugs or defects that others may have created. Be careful not to throw them under the bus or put them in a situation to be defensive. This means that if there is an issue. Say something like “hey there is an issue arised from what you did yesterday” and go into how it’s affecting what you are working on. Be specific on what you need from them and keep it a conversation and not a command.
Keep in mind that your team members might not agree with you and that you don’t have to agree with everything they say. Make sure you allow them to be undertood and that they understand where you are coming from without arguing or being negative.
Make sure you reconize your team members on their efforts. If they help you with a task make sure let them know you are grateful. Give them credit when credit is due. Don’t hide that from them.
As the saying goes “If you want to go fast, go alone. If you want to go far, go together” as a team.