DEV Community

Cover image for Tech. Vocabularies/Terminologies You Should Know as a Developer - Part 1
Ernest Obot
Ernest Obot

Posted on

Tech. Vocabularies/Terminologies You Should Know as a Developer - Part 1

Technical words, also known as terminology or jargon, are a special type of vocabulary used to explain concepts unique or specific to one particular area. As a web, mobile or software developer you should be acquainted with the following Tech terminologies.

I have carefully listed some terms and also provided comprehensive definitions for each.

Agile Manifesto: A set of values that proposed how code should be done in order to have more successful projects and deliver products that mattered. It was created in 2001 by a group of 13 developers.

Agile philosophy: A set of principles for developing software products that focus on short iterations and constant customer feedback.

Algorithm : A set of instructions that should be executed in an order, similar to a cooking recipe.

Android: An open source mobile operating system mainly sponsored by Google.

Application Software: A software that is specialized on some task such as rendering a photo or editing a text.

Atomic Transaction: A series of steps in a transaction where either they all happen successfully or none of them does. A good example is a money transaction: money can’t leave a bank account but never arrive in another.

Authentication: A process to guarantee that who is making a request is who they say they are.

*Backend: * The backend is every logic and system that the final user doesn’t directly interact with but is highly dependent on.
backlog A list of tasks, features, bugs, and improvements that should or could be added to a system.

Backup: A copy from an original data that is stored in a different place in order to guarantee that all the data isn’t lost if something happens to the original database.

Big data: A type of software infrastructure to deal with an enormous amount of data. Typically used when data can’t fit or be processed by a single computer.

Bootcamp: An intensive course where a person can learn how to become a software developer. It can take from weeks to months and is focused on the practical experience of a developer rather than the theory behind computer science (as universities do).

Browser: A software application that allows the user to access the Internet.

Bug: A defect in a code or algorithm.

Bus Factor: The number of developers that must be hit.

Business Logic: All the information a user gains by using a system.

Canary Release: See incremental rollout.

Client: Any device that allows a user to connect to the Internet such as a tablet, a browser, a cellphone, a TV, etc.

Cloud Infrastructure: When a system uses remote computers over the Internet rather than a local computer. Cloud services are usually provided by hosting providers.

Code: The result of writing a programming language to perform an algorithm.

Code Review: A process where whenever someone wants to add a new code to the codebase, the code will be reviewed by someone else in the team.

**Codebase: **The files and folders that make up a software.

Commit: A “package” containing a code change that was introduced to the codebase. It contains the code change as well as who wrote it and when.

Continuous Delivery: Developing code in small incremental changes instead of one big change at a time.

Watch out for part 2

We can connect on linkedin
https://www.linkedin.com/in/obot-ernest/?_l=en_US

You can buy me a coffee for the weekend
https://www.buymeacoffee.com/megtrix

Sentry blog image

How I fixed 20 seconds of lag for every user in just 20 minutes.

Our AI agent was running 10-20 seconds slower than it should, impacting both our own developers and our early adopters. See how I used Sentry Profiling to fix it in record time.

Read more

Top comments (0)

The best way to debug slow web pages cover image

The best way to debug slow web pages

Tools like Page Speed Insights and Google Lighthouse are great for providing advice for front end performance issues. But what these tools can’t do, is evaluate performance across your entire stack of distributed services and applications.

Watch video

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay