The technology world is a bit different than fantasies, where everyone is polite, managers may smile and hide their real message by the way they say “you’re doing good, real good,” but programmers often speak their minds, and when that mind has something unpleasant to say, look out for words like this:

“CODE DOESN’T COMPILE”
These three words may seem factual or even innocuous, but they hide true venom. After all, they signal that the code may run smoothly, but that doesn’t matter to anyone else. They gave it a go where they wanted your code to run, and it got blocked It could be that they don’t have the right libraries installed. Maybe they’re using a different version of the compiler. They may even have a different switch set on the optimizer. Whatever the real reason, nobody knows, and nobody cares. All they want to tell you is that you skipped the second lesson of programming class, the one when the instructor teaches where to put the semicolons.

“HEAVY”
For some reason, “light” is a compliment when it comes to programming and “heavy” is an epithet i.e. Insult, like putting way too many notes in your guitar solo. But “feature-rich” is a compliment and “missing features” is an insult,
NOTE: You can’t have features without adding code and making the stack fatter and thus heavier.

“SUIT”
If you associate fine dressing with power and status, in the programming world, you have another thing coming. The people who build software wear something more comfortable. A cross between a kimono and kilt might be nirvana, otherwise a hoodie if you’re younger.

Linus Torvalds once wrote, “If you want me to ‘act professional,’ I can tell you that I'm not interested. I'm sitting in my home office wearing a bathrobe. The same way I'm not going to start wearing ties, I'm also not going to buy into the fake politeness, the lying, the office politics and backstabbing, the passive aggressiveness, and the buzzwords.”
If you, as a programmer, even seem to be guilty of one of those, you’ll be wearing the epithet, regardless of how you dress for work.

“FULL OF ANTI-PATTERNS”
Some call them stupid ideas or sloppy thinking, but programmers like to toss around the phrase “antipattern” to describe a way of building code that isn’t recommended, saying your code is full of antipatterns is worse than saying it’s bad. It’s saying your programming is immoral.

“FANBOI”
Long ago when PCs ruled the planet and Apple was almost bankrupt in the year 1997 during the introduction of the DOTCOM BUBBLE IN THE US STOCK MARKET a few loyal users continued to sing the praises of Apple and predict that the world would one day come to cherish the beauty and sophistication of its products. The PC-lovers dismissed their addiction by calling them “fanbois.”Though the Apple-loving individuals were right, it doesn’t mean that someone is now paying you a compliment by calling you a fanboi. They mean you’re willingly ignoring reality because of overzealous devotion to a weird principle or idea,

“SLOW”
Computers are fast. After decades of Moore’s Law, everyone simply expects computers to get faster and faster. But obviously, programmers don’t always deliver something that’s fast. Many hardware designers like to crow that they’ve delivered their side of the bargain. It’s the software developers that produce inefficient code that sucks the life out of the faster chips. Although turning down the temperature and taking your time results in the best-flavored meats, slow-roasting your code is a no-no.

“N00b
Could anyone be as clueless as a new hire? They would probably spell this with letters and not digits.

“CRUFTY”
A design that’s tossed together, often with leftover codes or waste from other projects. Is just like a sloppy, stitched-together Frankenstein that barely works. When you see the word “crufty.” Likely, it’s not only your code they’re commenting on; it might be you and your ideas.

“DEV/NULL”
In UNIX world, the null device is a black hole that forgets all information sent to it. It’s mainly used to test device drivers and other code that processes data. As a metaphor, it’s a perfect offhand way to say the memo you wrote isn’t worth storing on disk or sending to the printer.

“KLUGE”
Sometimes you don’t have time to polish that side project you put together on the weekends, only to find 2,000 other developers suddenly depend on it. With the second wave of interest come the insults. What is this thrown together in a single file? At best your programming is seen as a fix that may succeed temporarily but will eventually fail because it isn’t thorough enough to solve the problem correctly -- even if it stands the test of time.

“BITROT”
Code will generally start to fail as the operating system, libraries, or other systems are updated. The newer versions have more features, in other cases, the programmers have fixed a bug that your code assumed was there. The old code doesn’t fail completely, at least at first. But it starts to get more calls to the OS or the libraries begin to fail. If you don’t invest in renewing your knowledge and improving your code, you start to rot like an old fish. Folks can be harsh when pointing this out.

“BRITTLE”
Code that is fragile and when your code compiled and passed all of the unit tests, you celebrated. But then someone changed the inputs or tossed in a divide by zero and your code crashed. That’s when you realize there’s more to writing code than making sure it works on the first test.

“CARGO CULT PROGRAMMER”
This insult references a famous tale from Richard Feynman about an ancient tribe that lashed together some logs to build what looked like an airplane. Why? They knew the winged contraptions brought amazing visitors with valuable cargo from the sky. They thought that building something that looked like it had wings would produce the same results. In the case of software, the one who builds a system based on a shallow misunderstanding of the problem is the one who gets labeled a “cargo cult programmer.” One day the half-baked theory you based your work on might look humorous even to you.

“EYE CANDY”
Some people write command-line code that delivers the answers in simple text. Others build flashy user interfaces with dancing code, flashing buttons, and eye-catching colors. They may even embed several videos, sometimes with beautiful models with eyes that never quite meet yours. Is there anything underneath? The boss isn’t going to look at the code. In other words, a pretty interface but terrible or fairly working codes. Even though most web designers don’t code often here at Webbikon Technologies, Best Web Design Company in Abraka, we design and develop websites that suit your demand

“MANGLER”
"Mangler" has the obvious insulting quality and a very calm one, if you’ve mangled the code -- well, what else can you expect? The term is also used as a replacement for the word “manager,” as in “project mangler” or “division mangler,” Of course, managers have a different term for the people who overpromise and underdeliver. They’re called programmers.


“NO-OPS”
Someone who does nothing is a no-op, in reference to a blank binary instruction that flows through the CPU without changing anything. No-ops pad the instruction stream and help with debugging. Some processors use no-op codes with clever representations in hexadecimal.

“NOTHING”
The only thing worse than being insulted is being ignored.

Okay na