(One)
The first story comes from my first internship company.
When I first company internship, I was the person in charge of the front end of a long I'm still young compared to the "young man", in fact when I was a junior, and he has been a thirty year old. The so-called master, self-cultivation of personal. I heard from him a word of advice is the most: "This demand can not do." I do not know if he thought I was too much food or what, anyway, eventually to the needs of my hands, after his superb social skills will become extremely simple that I landed early after the second company suited to some "responsive "the development process.
Once at the dinner table, he explained in detail how to "negotiate" with us to reduce their workload, in fact, is how the "I'm too lazy to do this demand," translated into "this demand I can not do." He said that in the front for so many years, never met a real product and unreasonable demand, product manager, although most do not understand programming, but I found that once they make a complex needs, that they will have a basis in fact, is already XXX realized in this demand, so the demand can be achieved. Such a causal seemed to have no problem, but as a programmer. The first reaction is definitely - you want me to do *** demand BAT, then you'd give me a *** BAT salary of duck! Of course you can not say that on the surface, then that is a set of bells and whistles theory and practice. To be honest some things the needle can not learn, or to rely on themselves to realize.
Here I share some personal experiences to avoid unnecessary tedious work. When you're a shorter duration of the project, and the need to achieve a seemingly simple to implement complex needs, you can make "I need an extension of time to achieve this demand, the demand for our overtime requirements undone like" in fact the whole world knows that this demand requires fast on the line, this time the product manager will make concessions, then you can make some simple and feasible alternatives, to note that the demand can be changed, but not the best cut, to avoid being accountable boss, because you never know what you think tasteless function is to "core competencies" not the boss's eyes. The second case is in the face of the project have a long cycle, encountered a more complex needs, and if this demand is not linked with other modules, other modules you could do first, do complex modules, time to time is not enough, they can use the previous method, if the module is the core module, you can estimate a time to achieve, if the schedule is not enough, it proposed to recruit people to help you complete some simple module (module and then slipped the inclusion complexity to simple module in interns to do, would not Miya, manual funny). The above two methods for reference purposes only.
(two)
The second story comes from a phone interview.
In an article about my personal growth experiences mentioned, how to enhance their capabilities through the interview, the first year of work, I have been convinced of this approach, and never tired to try. Of course, because my salary is slightly lower first formal job, and he wanted to quit as soon as possible. Once about half past nine pm, suddenly received a phone call us praise is a senior programmer. To be honest, I disturb itself for this big night ran the rest of your electric face very exclusive, but because the other side is "996 Pioneer" company, so out of courtesy not hang up the phone directly.
There are several impresses problem, say it to everyone Lehe Lehe.
1. You write on your resume you will vue, that you know how to write data two-way binding it? I wrote an article dedicated to explore the two-way data binding of vue , I tell him to rewrite the core idea is the object with Object.defineProperty get / set, specifically I have a blog to write. However, he did not give up goose, still to this "source" inquisitive, finally I can only suggest that he "could not write to me."
2. You write on your resume you will js, what do you think of js engine? Works chicken hen you js engines? Have you discovered bug browser js engines? This question I really do not, I wonder if you have any suggestion about front-end specialist.
In the interview I have met many of these programmers, they ask you questions would you ask not really, but to show off that he would not be you. I found that many senior programmer or a few aspects of a very profound insight in a way, this is a good thing for the company, but if you make this type of programmer to interview a newcomer to the "new" that result is likely to be disastrous. They have like-minded friends to climb very good impression, and for those who are not very understanding of the field of his dig is very exclusive. Sometimes companies just need a small number of write activity page farmers, during the interview have to experience a bombardment XX experts in the field, which is absolutely no benefit for the company.
To prevent this from happening, I rarely asked in the interview "new" when a number of purely technical issues, in part because I positioned myself sector is very accurate, the boss we do not need rocket science, but a little training almost all get moving bricks certificate. So why not find a nice spot to sit next to your little sister Yangyang Yan it?
(three)
The third story comes from a keyboard Man.
Because some nausea operations CSDN, I found a new blog platform intend to migrate in the first half, and found that "Nuggets" of fishing in troubled waters function more attractive than the blog. So it often would catch fish on top. One day receive a message, copy and paste as follows:
"When I saw what you wrote, it had been able to copy a document written document worse than ......"
Do not know the "Great God" I looked at how many articles come to the conclusion, but surely this great God is certainly very powerful, the point went in to see his personal data, he found, were not written an article, presumably certainly disdain to write articles super God, and found exactly GitHub address, so want to go observe what is now the great God how to write code, but also for everyone to be a reference ( https://github.com/chance9077 )
In my plain level and concluded that - this is a new novice is no longer new.
Write blog itself is a process of accumulation, and then look at the article I wrote two years ago, there are many places are "a mess", this should be a normal thing, but this does not affect the people at the same level to Two years ago I read the article, may be stages for the people in terms of () => {} ratio function () {} code reading itself is a stronger shit. Each stage of each stage can have people read the article, if you think someone else is badly written, you did not need to spray, if you really want to spray, you should also do a better job than him and then sprayed.
Some people think a blog is a very easy thing, I heard the most is the two words in the official csdn group:
XXX article only a few words, the amount of reading Why so high?
XXX well written article I did, why I read than high?
Some people after experiencing this frustration will choose to give up, in fact, stick with it, people have become winners. He insists, is the easiest way to succeed in this industry. According 2/8 theory, 80% of the people are white prostitute resources online, only 20% of the creative, which is 20% of the people inside, only a maximum of 1% of the people insist on creation. If you want to spray me, please you first become that 1%, then, do better than me, then I will hear from him. No power, it will only beep of people, the better, the more such people there is, the more a reflection of my values.
(four)
Finally, talk about my own, a programmer does not know how the evaluation.
I have repeatedly mentioned in the blog - do not forget the early heart. At first I thought it did not forget the early heart, was always square, then gradually became, not forgetting the beginning of the heart, that's pretty good. Now I have the beginning of the heart do not care, now is the heart line, the wind moving (manual funny). So what my heart is the beginning of na? BAT, is the beginning of my heart. If there is anything changed my mind at the beginning, it should be the last to Kang interview experience changed my view of manufacturers.
I found no boss is willing to pay a salary you drink tea and chat, all of capitalism is the same purpose, which is squeezing surplus labor value of employees, so why do not I choose a higher paid job when it? Work, and a job of a 12K955 20K996, the count hourly wage, the former 333 / hour, which is 342 / hour, which is the hourly rate is even higher, if the normal tax, then the latter will be more cost-effective. Words to say, but it really gives the choice to fool would choose the former. Because some people did not even have a choice, for today's young people who, desperate to make money is to save the down payment to buy a nest. "Buy a house" is the beginning of a lot of people's hearts.
From the time I left the company, the harvest of a very philosophical advice - what things are a matter of course, there is room to the age, naturally there will be room, do not focus on how the money is to come. Unfortunately, this statement can not be fulfilled in me, because I just graduated to buy a house (manual funny), but I found that many programmers is indeed between 30-35 buy their first home, so I never worry about the future What happens, I only care about the weekend's schedule this week, next week and the weekend schedule, go down after the incident, chanting say the future. Maybe ten years after prices really like Ma said, it is like onions Bu Bu also possible.
About programmer this line, in fact, the vast majority of people moving bricks, I always say a word - actually write code like easy to drink, because I often "novice group" say such things, so people think I'm ridicule them, it is not. I think there is no difference on the nature of the work of programmers working with the UI, but the UI is generated chart to see the prototype in mind, then PS out, while we are looking to generate code UI map in mind, then mind something to write it out, sort of like elementary school when the plug-writing.
For me, the work should be a very easy thing, I have never met do not need, just the same as ever mentioned in the above, the most complex needs look at the code level, already has a precedent, so unless the product deliberately finding fault, otherwise you can not do what needs does not exist.
Life is short, carpe diem!
