Reading "People, performance and professional ethics" thoughts

reading "People, performance and professional ethics" thoughts

As a computer professional student, future work must be accompanied by code. So the benefits of our work are going to become a qualified programmer.

How to be a qualified programmer is what we will do in the future. It is possible to succeed only if you do the lowest end. Because "a house does not sweep the world."

First,the90% programming work comes from the internal software

(90% of programming jobs is in the creating line of business software)

Computer majors may have the impression that most programmers are writing publicly-sold software or generic software.

This view is wrong. Most programmers actually write private, in-house software, such as software that tracks costs, software that optimizes shipping costs, software that helps with billing, software that designs new parts, software that calculates policy prices, software that identifies malicious orders, and so on.

A variety of commercial companies that develop internal software to solve their own problems. Most of the demand for programmers in the market stems from this, and only a handful of programmers directly write software for external customers.

The development of internal software is often tedious and tiresome. Because of their low technical complexity, very conservative technology decisions, little budget, and a lack of long-term consideration. But most of the programming work in the world is this.

　　Second, the purpose of hiring you is to let you create profits, not to let you program

(Engineers is hired to the Create business value, not to program things)

What the business companies are most concerned about (or the only thing that matters) is increasing revenue and reducing costs. As a result, they actually need not programmers, but people who can help them increase revenue and reduce costs.

Developing software, solving technical problems, and writing code without bugs are not the purpose of a commercial company. They hire you to help them complete a project that can increase revenue and reduce costs, not because you are geek.

The only value you have for your company is how much you can increase revenue and reduce costs for them.

　　Third, do not call yourself a programmer

(Don ' t call yourself a programmer)

Many of the company's managers do not understand the computer, in their mind, "programmer" is a group of high-cost labor, only on a complex machine to do something difficult to understand.

If you call yourself a "programmer", some managers will first think of firing you when the company needs to compress costs. One company called Salesforce, the slogan is "no software", meaning that if managers buy their services, they no longer need other software to manage the sales business, that is to say, no longer need to hire a programmer.

The right thing to do is to describe yourself as someone who has a relationship with increasing revenue and reducing costs, such as "the developer of XX products" or "the Improver". A Google Adsense Programmer's self-introduction, this is written: "Google's 97% revenue, and my code." "

　　Iv. do not limit yourself

(you aren't defined by your chosen software stack)

Young students often ask, which language or platform should I choose? Learning Java, is it easier to find a job than to learn. NET?

Too much emphasis on a language or platform is unnecessary. If you limit yourself to Java programmers or. NET programmers, you have lost because first you should not call yourself a programmer (for a reason), and then you will automatically be excluded from most programming work in the world.

In real life, learning a new language takes only a few weeks, and then six months to a year, you become a veteran. At that time, no one cared what language you used to be.

Genius programmers are few, but there are a lot of job opportunities that require genius programmers, most of which demand is far greater than supply. This means that even if you are not a genius programmer, as long as you are a good engineer, those recruiters will hire you right away because they know there is little chance of recruiting talented programmers. (Again, the so-called "good Engineer" is a series of records on your resume that increase revenue and reduce costs.) ）

Some of the company's personnel departments, depending on a keyword (such as Java or. NET) to filter resumes. Although such a company is not worth it at all, it is also easy if you really think about it: spend a few evenings and weekends, try to use the keyword in your current project, and then write it down in your resume.

　　V. How to improve the bargaining power of job search?

(How does I become better at negotiation?)

(1) Remember that you are not looking for a job, not a display of programming skills, but a solution to the marketing of a business need (increasing revenue or lowering costs).

(2) When interviewing, be confident and have equal dialogue. What you want is a mutually beneficial employment contract, do not ask each other, you say Yes.

(3) Employers may ask "what is your last salary" and they say, "Give me a reason to depress your pay". You have to think about how to answer the question properly.

(4) to counter-offer. It's not just about money, it's about other things you care about. If you can't ask for a higher salary, try asking for more vacations.

(5) When the other person decides to hire you, it starts to discuss salary. Because then, they have invested a lot of time and money in you, and have a certain cost, at this time they may feel that some small problems are no longer worth pestering, such as the annual salary increase of thousands of yuan.

　　Is the start-up company suitable for fresh graduates?

(Is startups great for your career as a fresh graduate?)

If you join a startup as soon as you graduate, the most likely result is that you have worked very hard in the next few years, and the company has failed miserably, you have lost your job, and you have to work for another start-up company.

If you really want to go to start-up companies, you should first find a big company for two years, save a little money, accumulate some experience, and then carefully select and then go to start-up companies.

Working in a startup company, in general, you meet entrepreneurs. Most of them don't have the ability to hire you in two years, and when you work in a big company, you meet people from other big companies, many of whom will be able to hire you or introduce you to the job.

　　Vii. is it recommended to work in a startup company?

(So would to recommend working at a startup?) ）

Choosing a start-up company is choosing a career path rather than choosing a lifestyle. Unfortunately, many people turn the two upside down, and they recommend startups that are actually recommending a lifestyle that you're interested in.

If you really like this way of life, honestly, you can get them in a big company. In many big companies, you have the opportunity to delve into the latest technology and go home to take care of the kids 5:30 on time.

　　VIII. communication skills are the most important professional skills

(Your most important professional skill is communication)

As mentioned earlier, engineers are hired not because they are programmed, but because they create business value. So, you make people believe that you can create value, which is the most important ability to help you find a job. This ability and how much you really can create value, in fact, the connection is not very close.

Some of the best programmers I know tend to be clumsy in their expression. Therefore, others do not want to work with them, but underestimate their value. Conversely, if you look very programmed and articulate, people will really look at you like that.

Reading "People, performance and professional ethics" thoughts