Let’s take a look at a few words and expressions that will be very useful for you to understand the jargon of devs. If like me you have a digital connection , you have certainly already heard conversations between developers. When I joined the digital / web industry, I was parachuted into an open space where 95% of the occupants were web developers . And I did not understand anything, but absolutely nothing, what they said!

I did not intervene in their Honduras Cell Phone Numbers List and yet I found it extremely frustrating not to understand them . So I put myself in the shoes of the client or the project manager , who does not necessarily have a technical background , and who finds himself in the middle of a technical conversation with a developer … Here is a little preview of this very mysterious language that we hear in an open space full of developers … Not all developers have the same job …

Let’s start at the beginning: do you know the difference between the front and the back ? I invite you to read this article on the developer profession , published by THE developer of the group (yes, they are rare!). The front-end It is the emergent face of the code, what the user sees on the screen and with what he can interact with : buttons, sliders, menus, fonts, animations … The front-end developer ensures that the design of the application is correlated with what the web designer planned upstream.

It Is Not Always Easy To Understand The Language

It uses client side programming languages (HTML, CSS, Javascript…) . Its roles: Request information from back-end developers and display it to the user; Manage user actions; Transmit information / requests to the back-end . The back-end It is the submerged face of applications and websites. It is invisible to visitors but it is absolutely essential: it is even the heart of the application . Without a back-end your application would be like an empty shell!


The back-end developer uses server-side programming languages (PHP, Ruby, SQL…). Its roles: Collect database information, format it and send it to front -end developers ; Retrieve the information sent by the front-end developers in order to save them in the database. We also speak of a full-stack developer . This is the little genius! From the front, from the back, he knows how to do everything … A little advice: do not make a comparison between the back and front devs , it could upset them! I heard that front developers are not real developers…

And on the back side, you cannot code without creating bugs (Guess what: according to a front dev ). commitstrip backfront (1) Git, their favorite tool! Git ? Branch ? Sweater ? Push ? Merge ? PR ? Prod ? Pre-production ? and so on… It’s the daily life of developers: I have the impression that they are only talking about that! We could devote a whole paragraph to it! That’s good, that’s what we did! Git is anopen source codeand version management system.

Back To A Few Words And Expressions To

It is acollaborative toolbut that we can very well use even if we are working alone on a project. the Master branch If the developers work together on a project, they have a “master” branch, the main branch. It centralizes the “clean” code , ready to be deployed on the servers. In general, this is the branch that is put online on “ pre-production” environments (or pre-production for close friends) , so that the project managers do their tests and check that everything is working well.

Once validated tests, are deployed Production ( “in prod “) to end users. MERGE ON MASTER If we want to code a new feature, we create a new branch that starts from “master” . We then test what is done on this new branch. Once this is validated, we “ merge onto master ” : we make this new functionality available to everyone on the main branch. At this point, the developer is so happy to have done something that works that he shouts it in the open space “This is it, I have merge!” “.

Git push / Git pull When we Git push, we make the code we developed on our own machine available on a Git branch so that everyone can access it if necessary. Conversely, we can also retrieve a piece of code on another branch: we then do a “git pull” . Besides, let’s talk about ” machine “: it’s a word that we like in this environment. We might think we are super modern and all that, but we still talk about our PC / Mac as a machine! It is also certainly what we called the Minitel in the past… (for the youngest: the Minitel, that’s it ). git – words and phrases to talk like a web developer “ I PUSH MY BRANCH!

Leave a Reply

Your email address will not be published.