7 mistakes seemingly harmless cause the dev fired


If you get fired for annoying reasons, that’s just an excuse for the real cause. Let’s take a look at some mistakes and the real cause of our dev sack!

Mistake 1: Chasing & intriguing

You probably know the story. There was an application developer for Nissan who was exposed to “stealing” the code on Stack Overflow. The original description from Stack Overflow in the recent update has “flipped” him.

Alas! Most programmers are honest, hardworking individuals. We study and work very diligently to produce good products.

But every industry has its own “dirty” secrets. And with this programming industry, we often copy paste code from the internet, anyone has ever done it.

We are all pressured by a very heavy deadline, and will find ways to get the job done. And in addition to picking up Stack Overflow or CodePen searching in just a few hours, then copy / patse, there is still a faster way. Is a way too smart?

Not really, the society is now extremely scrutiny. Especially in an extremely competitive technology environment, journalists, bloggers, or even colleagues sitting next to them, will be ignoring the tricks of your life and work little by little.

You just need to be careless, just to make your mistake on the face of the newspaper, it is true that “an impetuous blessing, thousands of years of loading … land”, the whole career is lost.

Mistakes despite being “naive”, but dishonest, can be mentioned:

  • Copy / paste / steal code (directed / stolen)
  • The lie (seemingly harmless) about people, work, agreements, …
  • Access and sharing of documents does not fall under authority.
  • Use company resources for personal purposes.

Even the career has not yet been threatened, the pressure from the community and public opinion will gradually lead dev to even bigger mistakes.

Mistake 2: Judgment is careless

Speaking of this, I remembered an incident with American Airlines website. Dustin Curtis has written a blog post complaining about the interface design of this web. Dustin only wrote to release immediately, but did not expect any reply.

Yet, yes, I received an email from the designer at American Airlines. This front-end designer confessed (this word is very important) that the site has a lot of problems to solve. Designer continues to explain the difficulties of designing for large companies.

Is this designer too good?

Wrong. This is also a case of a lack of judgment. Turns out, American Airlines did not allow it, and did not want him to be too open to such customers.

As a result, this designer was fired.

The intention of this designer, no doubt, is respectable and noble. But let ‘s say that American Airlines is the offender. Is he in a position with powers or duties to provide compensation? Does he know every aspect of the problem?

He should have taken into account the consequences for his actions: Is this really a design error, a user error, or a browser error? Could this be software conflict?

  • Will this email push American Airlines into lawsuits?
  • Does this affair affect current legal disputes?
  • The real cause of the problem?
  • Could this email be a (legal) disadvantage for the company?

In this case, the designer gave an assessment when he didn’t fully understand the problem. “Careless judgment” not only leads to wrong decisions, but also a way of thinking about not considering the company as its company . And colleagues are not their relatives . When developers have a view on such work, they not only make wrong decisions, but also make decisions that affect their co-workers’ wages, and cause their family’s difficulties.

“Careless judgment” has many forms:

  • Highway company secrets (to people who should not expose)
  • Using company assets for wrong purposes
  • Lower your colleagues or boss
  • Beyond the limit of responsibility

This designer should have asked Dustin more about his experience. And at the most, sympathize with this person, not so much.

Mistake 3: Defensive to relieve pressure

There are 3 programmers working at the advertising agency, all three must meet the important deadline. They are forced to complete a website for their customers to meet their marketing needs. But unfortunately, the deadline has passed, but the product is still incomplete.

Project scale continues to expand, with more and more features piling up for them to be completed before the deadline is getting closer. This is their fault.

Their mistake here is silence, resigning these changes without a word of mouth, leading to a situation where deadlines will not be like this.

As a human being, of course everyone will ever be in such a situation, blamed when something goes wrong. And when we are attacked, we will stand up for ourselves. But these three did not do so.

When there are obvious problems in front of us, we neglect to do anything. The problem is getting more serious, we also shut up. Only when we touch dozens of angry emotions against us, do we decide to act, usually with justified sentences like:

  • “That’s right, but …”
  • “So, when you …”
  • “At least I don’t …”
  • “Look who is talking! As well as that.”

Rash and offensive is a sign that we are “defensive”. When that happens, we have gone over the limit. We are creating difficulties when others want us to explain the problem, or to participate in ‘healthy conflict’.

At first, most people will endure or pass. But if we keep repeating, the relationship gap with colleagues will become more and more stretching, and you will lose your job when people are no longer patient.

Mistake 4: Blockade & isolate yourself

We will start with a situation again. Your company has just won customers, the boss asks you to head this project. Customers want products that are very specific, like a site using Bootstrap for example. Your colleagues ignore customers, say nothing.

After that, they were “as innocent as fairies” using the Foundation instead of Boostrap without speaking with their boss or customers.

The boss, and the client’s – have just been ‘blocked’. The blockade here may be construed as follows: not knowing or intentionally not knowing the question, or asking, especially to postpone or prevent something.

This is a common habit in the programming industry. A large number of staff members in the community are dealing with things like this. The boss asks A, he will return B. Ask for advice, get a blank look again.

In other words, this attitude is no different than bullying passive-aggressive type. Expressions can vary, from ignoring colleagues and your boss, to “forgetting” you when you have a match or event.

Suppose you were blocked by a colleague. How will you encounter the situation?

  • They make eye contact with people, except you
  • Shake hands with everyone else, except you
  • Report people about events, assemblies, meetings; except you
  • Type you from the communication loop.

This ‘blockade’ model gradually destroys all relationships. If you are left out, you may be the first to leave. So, don’t be bullied.

Mistake 5: Criticism & Confession

Programmers are very smart. You have been taught and trained to think abstractly, from top to bottom, from beginning to end. This is an extremely valuable skill and requires a high level of thinking. But the forte always comes with shortcomings.

Including ‘elitism’

‘Essence’ is based on simple facts, you are usually the smartest person in the room (take a little selfie). But so, does that mean you can give off critically or intellectually bad comments? Absolutely not.

“Famous” developers are rough, gruff, even condescending people. We often laugh at customers’ understanding (programming) , despise other programmers , treat people badly .

Typically, as the scandal of Linus Torvalds (the father of Linux), put his finger in the face of Linux kernel developers. He still insisted that his attitude was right, and was willing to threaten “limbs” and ” swear ” if you disagreed with him.

This type of programmer loves to see others fail. To prove other people wrong, show they are smarter or better than everyone else. They often berate in a very “savage” way, cruel or humiliating.

These programmers do not know that such an attitude will kill morality. It will take a while, but employers will quickly eliminate this “negative” type of person.

Mistake 6: Fear of consequences

Codingo, StackExchange user, is a new developer. At this time, I was doing my first job after graduation. And just got dropped at my first capacity assessment.

He was criticized for asking too many questions . There are obviously many more reasons, such as low code quality. But anyway, this reason is too weird, because he just asked to be better.

Those who are too obedient and reserved are from here.

How do I know? He was filled with fear. In the questions he posed, he said:

“After six months with my first job after graduation, I was just put into Performance Improvement Plan. I am sure I will be fired sooner or later, but I would like to hear some advice to be better in the future. ”

It was as if all his hard work was worth nothing.

Programmers obviously face the amount of overload. People are always looking forward to them “miracles” in “unexpected” situations without warning. To add to the tragic part, employers also want them to be submissive .

The programmers unfortunately are in this situation, struggling to meet all “love books”. They are afraid of making mistakes, afraid of being fired, so they will finish the work at least, just enough to survive. They do not have space and environment to create, to start; they will just tell their boss anything they think he wants to hear.

And sooner or later, yes or no, they are finally fired.

Mistake 7: Only names, gossiping and speaking badly to others

Gilbert Gottfried (comedian, and voice of Aflac duck), decided to write a happy status, joking about the Japanese tsunami. Right after the tsunami in 2011.

He rubbed the pain of an entire nation at a time that could not be more appropriate, nothing fun there.

Aflac immediately fired him.

The programming community also witnessed similar situations. We joke about customers, superiors, colleagues. How silly we are about everyone else.

Instead of sincere discussion of the problem, we sat again and again mockingly. We make it personal.

If there are people who suggest ideas, we will reject that idea right away (of course by logic and arguments). We criticize others on social networks. We will completely “destroy” them, letting them know how wrong they are.

Worse, I swear, I swear, but the solution doesn’t give anything.

Why do so many people make these mistakes?

Those who suffer from these mistakes often lack one of the following qualities:

  1. Attitude . Difficult and dishonest members will drain the vitality of a team. You will learn how to stay away from them. Their superiors began to notice, and their dying days were approaching.
  2. Ethics . The consequences of unethical behavior will automatically spread. If you find colleagues are stealing things, you will be awkward. If you ignore it, you lose credibility when people find out you already know and don’t say anything. If you report back to what you see, your co-workers will reduce your faith because you reported it.
  3. Judgment . If your judgment is careless, your good will often cause trouble. And because you have a good idea, your ability to exchange incidents with others is very low, making the problem even more serious.

Without these features, you are in danger. The question is, how can you avoid these mistakes, when you are unfamiliar with the above rules?

Simple. Or choose a “type” of people you want to play.

In general, in life, each person is divided into the following four “types”:

  1. Simple . These dev are very naive. In fact, I don’t know anything, but I think I know. To be a “naïve (innocent) person” type, you just lack of knowledge or inexperience is enough.
  2. You idiot . This type of dev understands the law. They know what they need to do, or even the consequences if they butter the problem. But even if they knew it, they would ignore it. Only when they fall will they feel pain, see the consequences and learn. If you spend too much time with this type of person, you will get sick all the time.
  3. Ridicule . Devs are no different from “idiot” … using stimulant drugs. They laugh and humiliate others, anyone. They have a special sense of satisfaction when spreading contempt wherever they are present.
  4. “Wisdom” house . These experienced programmers know how to “release the shrimp to catch the shrimp”. They can analyze and receive feedback, even the feedback is full of sarcasm. They are curious (not prickly), always ask good questions and find ways to answer. They study and work constantly to build themselves and those around them, because they understand how simple people are.

Once you have decided (or accepted) what kind of person you will become, find trustworthy people who can help you reach that goal. Spend more time with them, share with them your thoughts and ideas.

If you want to be knowledgeable, find a wise man, or a senior as an example to look forward to. No matter if it’s a colleague or friend; It doesn’t matter if you meet in person or online. Wise men often have very rich experiences. They understand the social environment, as well as successfully capture the “political” world at work. Share your decisions with them, learn to think like them. But remember, you must always be the one who makes the final decision.

When you decide, master that option. Thus, you can prepare yourself for any results – even if you lose your job.

There are also other cases of dismissal for extremely small reasons

The feeling of losing my job is very painful and I can’t help it. Especially when you don’t do anything wrong.

True enough: devs are also fired for extremely small reasons.

The problem of false release is like this, the reason they give when you are fired, is rarely a true reason. If employees are fired for stealing property. It may also be the real reason, but also because:

  • I can’t trust you anymore
  • I know he was dishonest
  • I need to eliminate people, thanks for giving me the reason

“Micro” concepts such as relationships, prestige, and fun – are more important than your code’s ability (which is also important).

“Those ‘superstars’ obviously don’t make these mistakes.”

The truth is there is. Imagine your best friend explaining to your boss, telling you to steal company property. The accuser will need to have very clear evidence to accuse you. Even now, you are likely to be forgiven.

No need to doubt, you can be fired for lack of capacity. But the process comes to a decision, completely dependent on the “micro” concepts we have discussed. Capturing these advanced concepts, you will be more confident, more confident, and more respectful – these concepts will protect your position.

Until their colleagues were caught watching Porn

If he mastered these high-end techniques, there is a high possibility, he will be passed. This will make people uncomfortable, you should also be uncomfortable.

You will never make such stupid mistakes.

As we have seen, it is not that simple. These mistakes (causing catastrophic cost loss), although quite recognizable, we know it’s wrong, but it’s extremely easy to commit.

But after reading the article, you are already new. You have been exposed to the cruel reality that few programmers are willing to accept. Learn these “manipulation” skills from those you know. Along with practice, you will avoid being harmed by others, and avoid deadly mistakes.

ITZone via Sitepoint

Share the news now

Source : TechTalk