blog posts

If You Are Learning To Code And Build Your First Program, Or You Are In Your First Job As A Software Developer, Or You Are Just Entering The Induofficial Documents Instead Of Stack Overflow

The Stack Overflow site is your best friend, the developer paradise when you first start coding. This site is a technical question and answer reference in the field of programming, and with its help, you can get different answers to your questions in less than a minute. The Overflow stack lets you go about your business when you have doubts or bugs and do not know how to fix them. But statistics show that less experienced developers (seniors) go to the Orfolo stack for answers and prefer to refer to official documentation about the language or tool they use.

Most of the time, using the Overflow Stack site lacks an understanding of the technology you are working with it. Using this site can be helpful in the short term. Still, if you do not have in-depth knowledge of the tool or language, Oroflow stack answers are not the key to solving the problem, and you should use official references to understand better the device you are working on.

While it may be good in some ways to connect with the larger community and use sample code or find practical solutions, you must understand the language or tool you are working with them. It may be a little tedious to read the documents, but it is essential to understand the language or framework you are dealing with it.

Widen your vision

Novice developers need to remember to broaden their horizons as they work and think about how to fit their code into the system. Typically, novice developers focus on just that when working with a plan, while experienced developers have a broader perspective. It takes time for experienced developers to think about the potential side effects of what they do and how to adapt to the system.

Guarantee the quality of your work (QA)

Most teams have automated or manual tests to ensure that new features meet the requirements, are high quality, and do not violate any existing performance.

In agile environments, the anti-pattern problem arises when things fall behind (i.e., you go from the developing stage to the quality assurance review stage and back to the nascent stage). This problem occurs when the developer does not understand or meet the acceptance criteria; That is, he did not pay proper attention to the to-do list to get the job done.

Before your work reaches the review stage, you can improve the quality of your work by doing thorough tests. Minimize your team members’ work time by considering pilot scenarios and avoiding procrastination. QA topics can help you get projects done faster if you work alone.

Do not ignore the world around your profession.

You will soon realize that understanding why you do what you do is more important than how you do it. If you do not understand the business, industry, or organization you work in, you may produce things that people do not need or will not use. A significant part of the mistakes of novice developers is due to their misunderstanding or assumptions about the field in which they work.

Tests are your safety valve and compass.

Test writing is essential for novice developers, Especially when they work in a team or are involved in maintaining a more extensive system designed by several developers. Tests are a great way to assess code issues and identify vulnerabilities. Try running your own set of tests at various intervals to ensure you are safe from unwanted problems and understand what changes the code should make. If you work alone and have not yet written a test, it is worth spending some of your time testings in the language of your choice.

Separation of worries

SOC is an essential principle in planning and design for segregating the program into separate sections; So that each section addresses a concern. Separating concerns or following the SOC principle can signify a skilled developer. Experienced developers have an instinct to identify individual circumstances and restrict them. However, what does it mean to be concerned in this area? The problem is a collection of information that can affect the code of a computer program.

Novice developers often try to identify and isolate different concerns. A good rule of thumb is to create a file for each area of ​​responsibility in the code.

A helpful trick to identify distinct areas of responsibility is the AND Test. If you needed to use the word AND when describing a file or a class in your code, you have most likely identified responsibilities that could be separate. Consider this example:

• The Conference class is responsible for scheduling AND displaying conference timetables. (Fails the AND test).

The conference class is responsible for planning and displaying the conference schedule. (Rejected in AND test)

in return:

• The ConferenceScheduler type is responsible for scheduling conferences.
• The SchedulePresenter is accountable for presenting plans.
• That is, the ConferenceScheduler type is responsible for scheduling the meeting.
• SchedulePresenter is responsible for delivering programs.

When you split your code like this, you may have temporary files, perhaps less than 50 lines of code. Working with an application that consists of small classes that all work well is probably easier than an integrated application that includes several large types that each do different things.

Write short methods

Novice developers have a code smell problem in their code; That is, they write long methods or functions. The second problem is not following the usual naming patterns that indicate what the process does—combining these two mistakes results in a lot of low-quality code. It is not interesting to try to understand a long and complex method that activates a chain of events to achieve the final result. To solve the above problem, first, write a long process, then divide it into private methods, each of which executes a step, and finally document everything.

Consider this example in the Ruby programming language. We want to be able to call a method that makes a delicious pizza with our selected toppings and condiments:

• def make_pizza_with(toppings)
•   preheat_oven
•   divide_and_roll_dough
•   add_toppings(toppings)
•   bake_pizza
•   slice_and_serve
• end

The make_pizza_with method calls for other methods, each executes a step in the process. Each of these methods contains its own set of sub-steps that complete them, for example:

• def preheat_oven(temperature, time)
•   walk_to_oven
•   turn_on_oven
•   turn_dial_to(temperature)
•   set_timer_for(time)

Add pizza special from the cabinet. You can quickly implement the make_pizza_with method at this low level of detail, eliminate the separate steps and instead have all the various information needed to make a pizza, such as going to the oven, taking the ingredients out of the fridge, or taking out the tray. However, writing such an instruction is annoying. As readers, we are interested in high-level steps in a process, not all the details. If you treat your methods the same way, your code will be more readable and easier to maintain.

But when do we break parts of an effective method into smaller methods? Often, you realize this when you have to write a comment explaining what each part of your code does. In this case, you have to break the extensive method into smaller methods.

Look for constructive criticism.

We all love praise, and it energizes us to keep working. In addition to the importance of recognition, constructive criticism is essential to help you progress as a developer. As a novice developer, you still have a lot to learn, and constructive criticism can help identify areas that improve your approach and code. If you work with other developers who review your Pull Requests, you may receive regular, line-by-line feedback on your code. Still, you may also welcome feedback on your overall approach to solving other problems or skills, such as working with team members. Shake hands. If you work in a team with a well-developed workflow, such as programmingDuo, feedback from the other party helps you write better.

Find a coach

A technical coach can help you improve your skills faster and avoid making common mistakes. The question is, how can you find a coach? It is sporadic for us to go to a colleague or friend and ask if you will be my coach. “We’re doing things that started decades ago. Many people did it earlier than us, and they have a lot of knowledge in that area,” says software developer Nii Ashikwei Tetteh. “You will be responsible for the infrastructure and the basics, but if you want to make sure you do not deviate from your goals, you have to have someone who can monitor the way you go and what you do.”

Please familiarize yourself with your text / IDE editor and its keyboard shortcuts.

Like a hammer for a blacksmith, a microscope for a scientist, a blackboard for a teacher, a text editor, or an integrated development environment (IDE) is a tool for your job. If you are comfortable and fast with the device you choose, you will work more innovative, and other developers will enjoy working with you. Have you ever programmed with someone uncomfortable with their editor and realized how frustrating and annoying it could be?

It does not matter which IDE you choose as your coding tool. If you work on learning different aspects of a device, your coding speed will increase. If you use a modern IDE such as Eclipse or IntelliJ and a static language such as Java, the IDE offers many suggestions for improving the code, such as new features and methods or expressions that can simplify; Pay attention to these suggestions.

Do two-way programming with more experienced developers.

Pair programming with experienced developers can be daunting. They are faster than you at writing code, solving problems, and identifying bugs and errors. In this case, your responsibility is Driving, which means controlling the keyboard. While the experienced developer is in charge of the Navigator, he sits back and leads. Two-person programming teaches you valuable tips. Sometimes working alone can be easier or more enjoyable, but it may not help you learn much.

Accept your lack of knowledge or ignorance.

Software development is a broad and multifaceted field related to many areas. There are experts in almost every subset of software development, from databases to security and performance optimization. Experienced software developers do not know everything and are more likely to be developers. Novices, there are many things to learn. The best way to add to your knowledge is to acknowledge your lack of knowledge or ignorance. You may hear or read the names of terms or technologies you do not understand daily. In this case, do not shake your head and pretend that you know; Rather, ask. If you do not talk about it, you will miss the opportunity to learn. You’ve probably noticed that most experienced developers are more likely to admit a mistake they made or something they do not realize. Many people are afraid to reveal their ignorance or ignorance, but this is what you need to do to learn, So ask questions to make things clear to you.

Have side projects

Side projects are your playground. They are a place to pursue interests and experiment with new tools without the hassle of high impacts or high risks. For novice developers, side projects are a great way to fill knowledge gaps, gain experience, make decisions, and identify valuable tips. Side projects do not have to be large or impressive. Projects that you can complete in a day or less are ideal.

Use the experience of experienced programmers around you and other inexperienced programmers.

People often respect the experienced people around them, but they disrespect the young and inexperienced programmers or think they do not know and understand as much as they do. Remember that you can learn from everyone around you. Software development is a vast field, and everyone has something to teach you.

In the story, the following tips will help you do your job best and upgrade A job is not out of reach.