Series Programming Without Coding | DAILY WORK OF A PROGRAMMER
Tags: Students, Developer, Programming, Coding, Thinking

Series Programming Without Coding | DAILY WORK OF A PROGRAMMER

What is a programmer doing?

Put simply, a programmer’s job is “programming,” writing code to create software. The software here can be mobile applications (Google Map, Camera 360), games (Flappy Bird, Angry Bird), web (Facebook, Instagram), Window applications (management applications, sales …) or other Internal systems for companies.

The basic process for creating a software often consists of business analysis (BA) in charge of business analysis and customer request acquisition; designer to design screens and threads; The developer will use that to write the code that makes up the program; Then the tester ran the test to find the error and … toss to the developer to fix it.

With the web, small applications, programmers will do all the work on their own, from customer requirements to design and writing code, then test the product.

Everyday programmer’s work

At this point, you probably know a little about each programmer’s job. However, many students are still not sure what job they will have to do.

As a programmer, your daily work is mostly around the computer:

Code: Most of your working time is spent coding. As a junior or developer, you will code small functions or functions. At higher positions, you will take on more responsibilities, code more complex modules.

Test: Normally, after the code completes a function, we will give it to the tester to find the error. However, before giving to the tester, we must also test and write unit tests carefully to make sure the program runs correctly, the module is completed.

Fix bug: Bug is the error we encounter when code, making the program run wrong. Code always has bugs, more or less. When detecting a bug, we have to dabble and fix the code for the program to run properly.

Learning new things: Sometimes we have to participate in a project using new technology or technology … too old without us knowing. Now we have to learn that technology ourselves (via ebooks, online courses) in order to work.

Programmers don’t just know code

However, as I said, programmers don’t always code. In addition to the code, we also have to do a lot of non-computer related things like:

Thinking: Before putting pen to write code, mistakenly, typing the code, we need to sit sketch and think about solutions. It is important to think carefully before the code, it helps you have an overview of the problem, do not forget the redundant cases.

Analysis / Design: With complex modules, before coding, you must work with your teammates and team to clearly analyze and design the module before coding. This is quite fun, in the UK every time we need to discuss is me and teammate to find the board, writing and drawing analytical drawing.

Meeting and reporting: Following the Scrum process, you will take about 10 minutes each day to attend the Scrum (Daily Meeting) to report on what you have / will do. In addition, you also have to refer to many meetings related to system design, situation reports, demo meetings for customers.

Communication with customers/stakeholders: In theory, BA will communicate with customers and get requirements, developers just code. However, in reality, in small companies or teams, sometimes the developer must talk to customers to clarify requirements, product demos. During my time as FPT, I still had to go to forums to ask customers and designers about unknown parts.

Conclusion

In this section, we have learned what most developers do every day during the first working period.

When you go to higher positions, the code time will be less, instead, you will spend more time analyzing the design, interviewing the developer if you follow the technical direction; or spend more time managing and communicating with customers if you go towards management.