Category: Structure

Another important aspect of writing good programs is clear code, not the number of tests or the number in the code coverage report. Everything is simple here. Think: Can others read the code? Or, even better, can you write the code yourself today and understand it weeks later? “In computer technology, there are only two […]

Good software is designed with computer user experience (UX) in mind, and this is a pretty broad topic with a lot of research and results. The more lessons learned from these studies are taken into account, the better the software will be in use. Let me give you a couple of examples so you can […]

In most cases, the developer can solve the problem quickly. If you find it costly to hire experienced programmers, think about it: the more experience a programmer has, the faster he will create a functional, accurate, reliable solution that will be easy to maintain. And this is a lower cost in the long run. In […]

When a developer writes a program, he makes sure that it works in many different environments, on machines with different resources, and in different time zones. The software should run on screens of various sizes and orientations, with limited memory and low processing power. For example, if software is written for a web browser, it […]

High-quality programs have easy-to-read and understandable code, they can be easily extended, they work well with other software, and their support does not turn into a nightmare. Code quality should not be compromised; the use of quick but sloppy decisions due to a tight deadline, excessive excitement, agitation, irritation, etc., is unacceptable. One of the […]

Confusion often arises with these definitions, and as a result, all specialists are simply called “programmers”. In fact, the programmer is the person who writes the code. He was given a task, told how to solve it, and he, following these instructions, writes code in a certain programming language. And a software engineer, before writing […]