JavaRush /Java Blog /Random EN /Coffee break #17. How to write pseudocode and 5 things th...

Coffee break #17. How to write pseudocode and 5 things that will help a junior achieve success

Published in the Random EN group

Why do you need pseudocode and how to write it?

Source: Dev.to Coffee break #17.  How to write pseudocode and 5 things that will help a junior achieve success - 1 If you are faced with a truly complex programming task, pseudocode—a logical presentation of the algorithms for future code—can help in its implementation at the syntax level. With pseudocode, you can outline the logic of an application without writing a single line of programming language.

Why use pseudocode?

In large projects without pseudocode, you can simply get lost. Writing pseudocode allows you to think ahead about potential problems. You get the opportunity to observe the pure logic and execution order of the program without worrying about possible syntax errors. Creating pseudocode before writing real code helps you complete projects faster. You can think of it as a blueprint for your program. Having pseudocode in front of you makes it easier to understand where and what should be and how it should all work together. So when you get to the actual assembly stage, you won't have to think long about what needs to be done, because you've already determined it in advance. The main advantage is that pseudocode does not depend on any programming language. The logic you write can be used by anyone and implemented in any language. This gives you the freedom to reuse and improve the architecture of the application you create. If you are not a programmer, thanks to pseudocode you can share the principle and logic of your future application with coders. This will make it easier for you to explain what exactly you require from them. Pseudocode can be written in any format, including using the academic format. It is well structured and detailed, but involves a lot of math. Or you can simply write a short outline of what you expect from your code.

How to write pseudocode

A small note in Word or even Notepad will be enough. Here is an example of simple pseudocode written in English. If you wish, you can write in Russian.
IF userlogin = true
 	API call to get user data
 	Assign data to variables
 	Re-route user to dashboard
 ELSEIF userlogin failed more than 3 times
 	Don't allow more attempts
 	Send user notification email
 	Re-route user to home page
 ELSE
 	Log bad login attempt
 	Show error message
 	Clear login form
You don't have to get too technical, but the more detailed you are, the easier it will be to write actual code. Imagine that you are creating a sketch of your program. This gives you the opportunity to think ahead about what you want to achieve and see how your code will work as a whole. The main things to focus on when writing pseudocode are:
  1. Program execution logic.
  2. Details the complex parts of your program.
  3. Consistent formatting.
As you write pseudocode, you'll begin to see where you need to add more detail and where you can remove something. Remember that this “sketch” is primarily for personal use, so write it in a way that makes sense to you. Personally, I love pseudocode. It helps me think more clearly when it comes to writing actual code. When all the logic of your program is already planned, you have much more time to experiment with performance and optimization. Plus, when you finally get to writing code, you won't have to stress yourself out.

5 things that will help a junior achieve success

Source: Dev.to Coffee break #17.  How to write pseudocode and 5 things that will help a junior achieve success - 2 The IT field offers great prospects and many vacancies for beginners. But to be successful in your first job, you'll need more than just knowing a programming language: you'll also need to practice and master a range of non-technical skills. The first months of work are the most difficult for any junior. Therefore, I tried to outline 5 things that can help make it a little easier for a beginner to get into software development.

1. Ask for help

The longer you work as a developer, the more you will realize how little you know. Never be afraid to ask the meaning of a term or look up information about a concept you don't know. Don't be afraid to ask senior colleagues for help. Getting your questions answered will benefit everyone by making you a more useful employee. There are several other ways to get help (besides asking questions directly). Pair programming with more experienced developers is a great way to get up to speed and become familiar with the codebase and useful tools and techniques. You can also ask colleagues to check your code (do a code review) to get constructive criticism.

2. Take initiative

Your first job may not be exactly what you studied. It’s worth coming to terms with this in advance. As a junior, you won't always be able to choose projects to your liking. You'll likely work with many employers during your career, and each will require a different set of skills. If your current job is not your dream job, work on yourself and study the technologies needed for your future position. A great way to do this is to take on personal projects that you can add to your resume once completed.

3. Keep learning

Although you were hired as a junior, this does not exclude the possibility that by learning new technologies and tools you will be able to climb the career ladder. There are always skills that you will learn that will help you in your work. The range of these skills is very wide: from the ability to write clean code to the ability to effectively express your ideas. On the Internet you can find a lot of useful articles, videos and other resources. With their help, you can learn advanced techniques and various libraries. You can even watch screencasts on sites like Twitch and watch other people write code in real time. Another great way to keep your skills sharp (and help the community at the same time) is to contribute to opensource projects.

4. Find a mentor

Sometimes, when a junior works in a team, he is sort of isolated from the others and deals with many things alone. To overcome such problems, find yourself a good technical mentor who can help you with job and career advice. A mentor can be a colleague or someone outside your organization. In the first case, in the case of a colleague, the mentoring relationship between you develops naturally as you get to know each other better. But you can also look for mentors at some conferences and meetups, where they can give advice on various specific topics, for example, on interviewing.

5. Don't give up

Patience and determination are the two main virtues of a successful web developer. Things like waiting for tests to complete, learning a new framework, or fixing a stubborn bug require a significant degree of persistence and the ability to handle frustration. It's important to remember that if you practice something every day, your skill will gradually increase. But nothing is achieved without striving for results.
Comments
TO VIEW ALL COMMENTS OR TO MAKE A COMMENT,
GO TO FULL VERSION