Hail to zhihu: Good girls don’t have sex

I was chatting with a programmer friend the other day, and he couldn’t figure out what framework APIS he was talking about.

Embarrassed, I asked him, “Don’t you have any ideals? What is the one thing you desire most right now?”

Without hesitation, he said, “Look at the frame source code!”

I can’t believe this is happening outside of work.

When I asked why this was the thing you wanted most right now, he said, “Don’t you ever have a moment of curiosity? When a project is idle and waiting to die, you always want to find a framework to look at the source code and console yourself.”

That makes sense. I can’t argue with that.

A man with so much ambition must be a rare talent.

So I decided, in private, to block him.

Over the past few years, I’ve been running around on GayHub and StackOverflow, and I’ve become more and more of an introvert, working like a porter in high-intensity, fast-paced iterations, absolutely copying without a single thought.

Both groups of programmers were able to excel, both front-end and mobile, and OVER time, I got to know a lot of great programmers. And then I found a cruel commonality

They don’t read the source code.

Is the technology bad? Each one is very impressive, API names and parameters, memorized backwards.

Can’t you read it? They can talk about design patterns. They can make compilers strike. They are fearless in the face of thousands of bugs.

I asked one of them, “I see you tinkering with apis all day, not curious about the source code implementation?”

“Nonsense,” he said. “Must be curious.”

I asked: “why don’t you see a source code? It’s a small case for you.”

He sighed. “No, there’s no need.”

“Good programmers don’t read the source code,” he added significantly.

I was talking to a man who was himself a full-stack engineer, fluent in the spelling of Java, C++, JavaScript, etc., proficient in ninety-eight and one design patterns, even senior architects were amazed.

He first wrote articles on Zhihu, which were mostly API manuals. After gaining some followers, he began to operate his own wechat public account.

The first half of the year, almost no flow, he grated teeth insist, but also die too much face refused to write source code analysis of the article. Finally, a year later, awesome List’s articles helped launch my own brand.

In the meantime, he has never stopped collecting all the funky framework tutorials and reciting their apis.

Such a full stack, understanding framework source code probably do not need to think at all.

I also know a programmer.

He was the kind of guy who could make you feel unfathomable even copying code. He exuded the air of a porter. Over the years, all the major projects he has worked on, from the framework level to the business level, have come from his own painstaking efforts, cloned from various blogs.

Most people in the IT community are struggling to “reuse” code to the extent that they can in order to fulfill a requirement, basically a mobile code repository with clipboard properties, not a traditional 996 code store.

This man, however, was a mudslide in the circle.

One of his favorite things to do is to poke around on StackOverflow, leaving hundreds of error lines on the issues of popular frameworks like an unevolved programming ape.

IT industry, only to go to the top of the pyramid can be capricious, he also, in the circle involuntarily, will be in some strange colleagues under the criticism of the implementation of a line or two of code.

Most of us in the IT industry are forced to do what we need to do in an environment that still requires independent programming. Not when, even to gnawing others source, over time, people will become impetuous.

But he’s not affected.

I asked him: “How do you keep a normal mind, meet those needs you can not fulfill, how can you still live so carefree, not the slightest worry?”

“Have you ever copied code from StackOverflow on a tight project?” he laughs.

I understood immediately.

Even if it is not their own things, you can also use the omnipotent Google to deal with, in the brainless replication at the same time, still want to maintain their consistent use of doctrine.

It’s like we have several wheels to work with when faced with the requirements of a project, and then secretly copy the wheels that we really want to use after the project goes live.

This kind of authenticity, not everyone can adhere to, especially after going out of the society, see all the numerous if the stars of the wheel tutorial, still choose in the major forums and groups of shameless questions, this is very rare.

Like him as if live immortal programmer, for the framework source code, certainly will not have vulgar expectations, he knows he will meet how shocking the framework and do not understand the source code, so, he is not worried.

I hope you understand that the value of a programmer is always measured by the requirements he addresses, not by the source code he reads.

Having dinner with friends last week, he said some of the IT voices he knows always think that IT is not enough to just deal with the demand, always look at the source code.

He told me, “But you keep telling me not to be impetuous, to keep my feet on the ground, to be comfortable with the business. You seem to have a special appreciation for the ability of programmers to deal with business quickly.”

People need to learn from each other.

The people around me, when I work with them, I certainly tolerate them and waste their time on source code that is not good for the business.

However, if he really wants to become an excellent member, it is still not to yield to the vulgar era of plagiarism shameful, or to compromise in the knowledge of the mainstream society.

Always CTRL + V, always take the doctrine.

We should always be full of expectations for the beautiful, full of desire for the future, and hold classics in awe.

To remember ah, can be original and not original, source code and far source code, is the most ignorant mature.

Don’t take it seriously.

Debut scatter flower ~

Welcome to my new blog bug Whine