How to become a "magpie" programmer? Reprinted from the House Guest College

I am often thinking that software developers are very similar in some ways to Magpies-a bird that is notorious for stealing shiny objects to decorate their nests. Like Magpie, the definition of a software developer is an unusually intelligent and curious animal. However, we are very, very easy to be distracted by shiny new toys.

I don't think it's inspiring to read the Ultimate Developer Tool list, like Scott Hanselman. On the contrary, it is tiring. The pace of reform in the software world is relentless. We are surrounded by a variety of so-called shiny and new things, the concept itself begins to disintegrate, repeating these clichés over and over again until they become meaningless nouns. "Shiny" and "novelty" eventually become commonplace, even commonplace. So, novelty is no longer the only, shiny is no longer interesting. In the end, you will be bored with endless pursuit of shiny new things.

I'm not the only one who thinks so. Jeremy Zawodny also noticed the shiny new things that are reducing luster:

A year ago, I retired from Steve's blog because he was accustomed to writing stifling fashion gadgets and writing the latest and brightest things-often a few times a day. I've seen too many people just to keep up with the speed of the hype and forget to think about whether these shiny new things can really help in achieving the Grand Blueprint.

Dave Slusher agrees that:

[Robert Scoble] said that there were too many emails sent to him, and these were ineffective public relations. He suggested that we write the news on his Facebook wall. I've been watching Scoble's Facebook at that time, so I'm sure he said it many times. Can Twitter, don't email. Can Jaiku, don't Twitter. Leave a message, send a message, make a phone call, send an e-mail, don't send an email, don't call. That's enough! I have not tried to get in touch with him, I just think this is the usual magpie, from this platform to talk about the platform, talking about rubbish, I feel bored. I gave up TechCrunch more than a year ago because of the same feeling. I'm tired of the so-called alternative-a little different from the way things are now, and not recognizing that this tiny change is worth the subversive abandonment of everything we have. I formally renounce the pursuit of newer, more shiny things.

It's not just that the tech news is endless. is also the Software religion War tide tide falls inevitably, but this war unceasingly let us disappoint, just like the deviated road the rock to run to a fast flowing stream. I bet David Megginson's summary of this process sounds familiar:

• Elite (master) developers found that too many mediocre people were using their current programming language, and began looking for programming languages that would better differentiate them from those of powerless colleagues.

• Elite developers are reluctant to take the usual path and seek out new, lesser-known, less-user languages.

• Elite developers have driven the development of new languages by contributing code, writing multiple libraries, and then propagating new languages. Sub-Elite (senior) developers follow the footsteps of elite developers, but also to learn the new language, opened up books, training and other markets, but also accelerated language development and testing.

• Sub-elite developers often have a huge impact (because elite developers tend to be lone heroes who tend to work independently in research projects rather than in production development teams), and they promote new languages in the workplace.

• A large group of developers who focus on regular learning then think that they have to buy books and take courses to learn a new language.

• Back to the beginning, elite developers found that too many mediocre people were using their current programming language, and began looking for other programming languages that would better differentiate them from those of powerless colleagues.

Now, please sit down, because next I will tell you some bad news. Are you interested in Ruby on Rails? That was last year's vane, and we are now moving in other directions.

If you think, statistically speaking, the vast majority of programmers have not yet experienced any form of dynamic language-let alone ruby--that is ridiculous. Some of the dynamic language features have penetrated Java and. NET fortresses, and have gradually achieved varying degrees of success. These so-called thought leaders will leave the virtual abandoned town before anyone has a chance to get there.

I became a programmer because I love computers and love computers, and you have to be passionate about change. I was just so. But I think magpie developers sometimes change their craft instead of being a disservice. Andy Hunt and Dave Thomas are thinking that pragmatic programmers (utility programmer) is an important part of the last wave of Ruby's change.

The user does not care whether you are using j2ee,cobol or something else. They just want you to provide the functionality they want. So, you need to help them find out what they really need and then imagine what the system is like.

Instead of being complacent or blind to go. Chasing the forefront of technology is not as good as focusing on building an effective system for yourself or your customers [with COBOL]. Not only easy to use, but also easy to understand and quickly deploy. The framework uses a mix of techniques: techniques for modeling, techniques for code generation, reusable components, and so on. The fundamental tenet of our work is the principle of pragmatism, which is designed to work effectively, not simply because of novelty or fashion.

When we try to use the all-purpose application framework to end all other application frameworks, we (as an industry) are going to die.

Don't feel enough if you can't decorate your nest with the most shiny and up-to-date stuff. As long as it works and can satisfy you and your users, who cares what technology you use?

The new thing is beautiful, it has a kind of the mystery of the half cover of the pipa. Don't unconsciously let the pursuit of new, shiny things become your goal. Don't be a magpie developer. The selective pursuit of shiny and novel things can help you become a better developer.

How to become a "magpie" programmer? Reprinted from the House Guest College