The most used IT terms in Dactyl Group

Each discipline has its own profession-specific terms. There is no different in Dactyl Group. Even complex systems or mobile app and web development cannot do without their own dictionary. And as they say - Brno is a city of progress, so if everything is to work perfectly, knowledge of (not only) technological jargon is simply a must. 

Let's take a look at the IT terms that ring through the Dactyl office on a daily basis and have a nice breakdown!

IT dictionary in Dactyl Group

The language of IT enthusiasts sometimes can be a great unknown for ordinary people. In most cases, however, it is far more workable than it might seem at first hearing. After all, communication must also work with colleagues from other departments in the company.

We will mention the most common examples from our established Dactyl language. We will pay attention to common terms from development, design or even testing. But you can also look forward to some of our unique words.

Let's start!

Standard developer-speaking

Let's start lightly - with the basic concepts that everyone needs to know. Backend and frontend. The frontend is the visible part of the web application, so all visitors can admire it. The backend part is used for web administration and data processing. It may not be visible, but without it, the final solution would not be possible.

In our work we regularly encounter the repository. And not just any repository. A repository refers to a space for data that holds the source code of software. In the context of software development, it also contains a versioning system. In our case, this is either distributed Git or centralized SVN, a flexible tool for managing source code versions.

In Dactyl Group we often use the term agile development. It is a software development methodology that is specific in its iterative progression through all phases of software development in different sized iterations. Above all, it allows us to react flexibly to changes in customer requirements and to verify iterations during development. 

Next up is a bug. Unfortunately, even the development of applications and web systems is sometimes not without some defects. Bug is an English term for a software error... and we won't call it anything else. 

Key terms in Dactyl Group

In Dactyl Group, we have also our own names. How did we come up with them? We are not afraid of mythology and legends, on the contrary, we are often inspired by them. Thus, our servers bear the names of important gods and mythical heroes, such as Hades or Perseus.

We have iconically named our main server and most important and powerful machine as Zeus. But don't worry, lightning doesn't fly from it!

ApékÁčko, esdékÁčko, cétéÁčko…  We simply enjoy the letter "A" (Áčko). Mostly, we're classically abbreviating commonly used English abbreviations. An APK is an .apk file, a collection of applications that we use on a daily basis. SDK is a set of development tools for software packages. Call to action (CTA) or "call to action" is probably familiar for everyone. It is a distinctive button that prompts a desired action. Logically, it is a key element of every website and e-shop.

And we'll stick to expressions taken from English. 

"Hey, the app has a lot of fíčur!"

There's not a day goes by when there isn't some kind of fíčura. Fíčura comes from the English feature and the meaning of the word speaks for itself. In our context, we usually refer to the properties and functions of the applications we are working on.

"Have you thrown it on the reviewčko yet?"

Similarly, in our repertoire you will find, for example reviewčko. Again, we base our repertoire on the English word review. We refer to any kind of review or opinion... like a code check by another developer! 

Uniques from design and testing

Not all specific concepts are necessarily related to development and programming. Therefore, we have to look into other segments of our team. 

For example emvépéčko (from the English MVP) does not refer to the most valuable player, but to the minimum viable product. It delivers clear value to the user, is easy to test, and can be reliably delivered to production - in short, compact, functional, and high quality design. 

Sanity testing is also worth mentioning. Although working in our industry sometimes tests our nerves, this term refers to testing features from older versions to see if they are affected by the new version. 

We'll stay with the testing for a while. 

We use a temporary test server - staging server - for top development and subsequent delivery of a flawless product to the customer. We test everything thoroughly first and fix any shortcomings before launching into full operation. 

In the offices, you will also hear us referring to various "kejsy, kejsky"... simply cases. What are they?

• Test case: a set of conditions that can be used to determine if the final product performs as intended. 
• Edge case: refers to a non-traditional to edge case - for example, testing a product on very slow hardware or a non-traditional screen size.
• User case: this time we focus on the common case, the use case and the expected user action when using the application.

We have successfully gone through the most frequent terms of our colleagues in the Dactyl Group. Of course, that's not all, but we'll take a closer look at other terms next time. 

And what about your most used IT terms?

Do you have any questions? Are you interested in the world of technology and want to start your project with first-class software? You've come to the right place! Contact us.