Each profession has their own way of referring to things. Things the average person won’t understand. Doctors with their medical terms. Cops with their cop terms. But there’s no jargon like IT jargon.

Two Imaginers got together to write a few terms relevant to their specific roles within the company.

Dane & Terry discussing Tech terms


UI (User Interface)


User Interface is the look of a product, machine or computer. It’s the design of the mechanism which allows us to interact with it. Examples of interfaces are touch screens, buttons and keypads. User Interface is also known as human-computer interaction. UIs share eight common characteristics which should be met and up to standard. These eight characteristics include: Clarity, concision, familiarity, responsiveness, consistency, aesthetics, efficiency and forgiveness. In a nutshell, this means that not only should the UI of a product be clear, but it shouldn’t be over-explanatory. It should be familiar, in other words, easy to use, responsive and consistent to avoid human errors and confusion. It should also be enjoyable to use and not disorientate people when they make a mistake, but rather help them correct it.


UX (User Experience)

User Experience refers to how the user interacts with the product. How they feel while using it and the experience they take with them after use.User experience is very important as this will determine the success of a project and released product. The UX of a product should be simple, familiar and effective. It should be pleasing to the eye, and easy to understand.



The word beta means two. The beta version of software is the version of software rolled out to a selected group of users for testing. The software usually goes through alpha testing beforehand, and is very close to the final product which will be rolled out to the public. Feature changes will most likely take place during the beta test stage as the developers get to know the needs of users in real life scenarios.



Scrum is a methodology framework which allows team members to make changes to a product where necessary. Scrum can be classified as an agile approach to software development. In scrum, team members will hold a daily stand up meeting, called a scrum, where one of the team members will be nominated as a scrum master. In this particular meeting the scrum master will give each team member the chance to answer the following three questions:

What did you do yesterday?

What are you doing today?

What are your impediments?

The scrum master is not responsible for the final outcome. The responsibility rests on the team as a whole.




Back-end developing:

The multi-stranded, behind-the-scenes coding of all apps or websites. The gears and Dane & Terry Discussing tech Termsmechanisms that make up the machine of any programme—the stuff that the user doesn’t see. These would be states and behaviors of objects that give your app its purpose, as well as the handling of information and calculations that determine the front-end results that appear in your user interface (i.e. what the eventual user sees and interacts with). Pretty much the dirty work.


Integrated development environment (IDE):

A suite of software containing all necessary features to write, compile and test software. Used by software developers  on a daily basis, it contains a text editor, a compiler, an output console from which the results can be viewed, a debugger, etc. IDEs usually support multiple languages. The IDEs that we use most frequently are IntelliJ and Eclipse.

Application programming interface:

The conduit that forms a communicative link between two applications, allowing them to share and process information. For example, if you connect to a specific website, you upload data that is interpreted by the server, which then performs the required actions, and then sends it back to you. So, in essence, it is a glorified messenger.


In our case, it is the identification and isolation of software errors for purposes of fixing or removing them entirely. These checks are performed on software in order to ensure smoother operations so that they run the way they were meant to.


There you have it, a list of terms that we use every day, and that doesn’t even cover half the stuff we deal with on a daily basis. So, the next time you get yourself caught up in a conversation with a computer geek, at least you’ll have a few terms to throw around.