Lexicon

Issue

// noun

EN A pretty general word, of course. You can have issues with people, politicians, situations, computers and so on. But if we have to dig deep into all these examples, we'll be depressed by the end of this lexicon. So let's just stick to the development lingo... If we speak of an issue at Bagaar, it will probably be about one you can create in JIRA. (If you don't know what JIRA is, you can find a spectacular explanation in this lexicon.) An issue in this case is any kind of assignment you want to give to someone in order to realise a project smoothly. The first thing you do is you define the issue. Is it a task, a bug, a user story, an improvement, a change request, a new feature or something else? Then, you describe what has to be done as clear as possible. And then you assign the issue to someone on your team, making it easier to keep track of your project's progress and to actually get things done!


NL Issue is natuurlijk een heel algemeen woord. Je kunt een issues hebben met mensen, politiekers, situaties, computers enzovoort. Maar laat ons, om hier niet compleet depressief uit te komen, die voorbeelden gewoon maar laten voor wat ze zijn. Development-speak dus! Als we het bij Bagaar over een issue hebben, gaat het in alle waarschijnlijkheid over eentje dat we hebben aangemaakt in JIRA (zie JIRA). Een issue is in dit geval eender welke soort taak die je iemand wil toewijzen opdat het project vlot kan verlopen. Eerst definieer je de issue. Is het een taak, een bug, een user story, een verbetering, een change request, een nieuwe eigenschap of nog iets anders? Daarna beschrijf je zo klaar en duidelijk mogelijk wat er juist moet gebeuren. Die taak kun je dan aan iemand van je team toewijzen, wat het ineens gemakkelijk maakt om de vooruitgang van het project met z’n allen wat op te volgen. Zo blijven onopgeloste taken niet tussen mensen in zweven en krijgen we dingen ook echt gedaan!

What's with this lexicon?

Digital transformation, Artificial intelligence, Robots takings our jobs, ... my GOD what a scary time we live in! Right? No, not really. We live in a very exciting time of endless possibilities, of genius new answers to questions we haven’t even been able to formulate... Some people just want to make good money by starting a fire and then being hired to put it out. We don’t like that at Bagaar. No apocalyptic vibes for us, we’re too zen for that.

The intelligence game will be won by those who know how to ask & answer questions critically.

Technology is evolving at a crazy pace, absolutely, and sometimes it might be a bit mindblowing, but don’t worry, humans are still the writers of this story, we decide how it goes. At Bagaar we help our clients every day to gear up for any technological challenge they may be up to, we have a very big toolbox of digital answers to their problems and are very happy to help them in writing their own story. This time we wanted to do something not only for our clients but for everyone, our moms, the guy at the busstop, politicians, journalists, whoever may be helped with a little free knowledge.

Core message here: Trojan: Nice for the greeks, not for you.

So, we wrote this lexicon in the assumption that if people would have more information, and a bit of guidance, they wouldn’t have to feel so helpless when hearing about Digital transformation, MVP’s, Frontend, AWS, Trojans, UX, UI, ... (Que?) We assembled all the buzzwords we use on a daily basis and tried to give a down to earth, simple explanation for each of them. Take it with you, read through it when you’re waiting on a train or getting your nails done and next time somebody starts a fire, you just blow it out yourself (or if it’s too big call Bagaar).

Mad Obama GIF
Suggest a new word
So, you just talked to a developer and didn’t understand any of the words he/she used? If those words aren’t in our lexicon yet, we’ll translate them to human language for you.