이 소프트웨어 엔지니어링 용어를 알고 계십니까?

타조 알고리즘

to stick one’s head in the sand and pretend there is no problem

Reference

요다 조건

if (x == 5) {
   // do something
}

They would write:

if (5 == x) {
  // do something
}

Yoda says “Become powerful you have, the dark side in you I sense.”

If you are interested, there is actually an English to Yoda Translator

The thinking behind this is that it’s less likely for a programmer to make a mistake and write x = 5 by accident, which would cause an error. While this may seem like a small thing, it can actually help to prevent a lot of bugs in your code.

So next time you’re reading some software engineering code and you see an if statement written in reverse, you’ll know that isn’t incorrect and the programmer may just be a star wars fan.

Reference

상태 418 나는 찻주전자입니다

The term “Status 418 I’m a teapot” is derived from the HTTP status code 418, which is defined as “I’m a teapot”. The code was originally meant to indicate that the server was a teapot, but it has been repurposed to indicate that the client is attempting to brew coffee with a teapot.

In simpler words, it is used to describe a situation where the client is trying to perform an action that is not possible. For example, if you try to brew coffee in a teapot, it will not work because the pot is not designed for that purpose. Similarly, if you try to do something that is not possible with a piece of software, it will also fail.

I’m a teapot, I can not brew coffee

The term “I’m a teapot” can be used in both positive and negative situations. If you are trying to do something and you know it’s not possible, you can use the term to describe your situation. On the other hand, if someone else tries to do something that’s not possible and they succeed, you can use the term to describe their accomplishment.

In either case, the term “I’m a teapot” is a way of describing a situation where someone is trying to do something that cannot be done.

Reference

버그

하이젠버그

Heisenbug is a term used to describe a software bug that disappears or changes behavior when an attempt is made to study or debug it. The name “heisenbug” is a pun on the Heisenberg Uncertainty Principle.

Reference

힌덴벌레

A bug with catastrophic behavior. Think something along the scale of your entire database being wiped off. 

If you manually execute a SQL Delete statement without a where clause, it is more of a mistake than a bug. However, if you write a function to do the above, now that sounds like a Hindenbug.

Reference

강남스타일 버그

When Psy release Gangnam style, he was about to literally break Youtube. Youtube initially stored its view count as a 32-bit number, i.e 2,147,483,647 views but Psy had different plans. Although saw a weird number of views, this deserves to be on the list of funny terms.

Youtube decided to move to a 64-bit counter so they are probably safe for a few more years. In case you are wondering, that's Nine Quintillion Views Lol.

코드 유형

젠가 코드

Jenga Code is a term used to describe a style of programming that results in the whole thing collapsing when you touch a single block of code. Named after the game where players try to remove wooden blocks from a tower without them falling down.

If you ever get a feeling that you don’t know what that line/piece of code does but removing it breaks everything down, well you might be working with some Jenga Code.

Reference

스파게티 코드

 This term is used to describe code that is messy and difficult to read. It’s often the result of bad coding practices or a rushed development process.

If you’re working on a project with spaghetti code, it can be tough to make sense of it all. But with a little patience and perseverance, you should be able to untangle the mess and get things back on track.

하이드라 코드

A little backstory about Hydra. 

Hydra was the offspring of Typhon and Echidna, the father and mother of all monsters respectively. Hydra’s lair was the lake of Lerna, which was claimed to be the entrance to the UnderWorld. Heracles’ second of the set of 12 labors was to slay the Lernaean Hydra. Hydra had a regeneration feature: for every head chopped off, Hydra would regrow two heads.

One head off, two heads Grow!

Heracles eventually managed to cut off all of Hydra’s heads with assistance from Iolaus.

Hydra Code is code that simply can not be fixed. For every new “fix”, two new bugs get introduced. Your best bet would be to rewrite the code.

Reference

매직코드

Magic Code is Code that is usually taken verbatim from websites like StackOverflow. Although it might solve your problem, you don’t know how it works or why it works. It magically solves your problem.

관습법 기능

A bug in the application that has existed so long that it is now part of the expected functionality, i.e it is a feature

It’s not a bug, it’s a feature

Reference

포켓몬 예외 처리

If you have watched Pokemon, you must be familiar with it’s catch-phrase

Gotta Catch ’Em All

try:
    // Some Code
except Exception as Pokemon:
    // print("Catching all Pokemons", Pokemon)

Reference

야크 깎기

Reference

원숭이 패치

Reference

신앙 기반 프로그래밍

Reference

하이 주도 개발

console.log(`HI.... ${varValue}`)

Most of us have our own version of Hi , personally, I use Yooo and a bunch of -x-x-x-x-x-x-x-

Reference

결론

Let me know if you know of any other such terms in Software Engineering.

Want to Connect?

Find me on LinkedIn: https://www.linkedin.com/in/rahulbanerjee2699/

Originally Posted on https://www.realpythonproject.com/do-you-know-these-software-engineering-terms/