From choosing a Java framework, we will talk about the "comfort zone" of technicians"

[Preface: the comfort zone of technicians is the content of this article. As to whether Hibernate is excellent, it is a question that experts are qualified to discuss]

In the past few days, a "> DBAMy friend was very upset because the architect and programmer of his development team was preparing to continue using hibernate as the Java framework in the next project.As we all know(Some people say that he has never heard such a statement, so it cannot be "public".) from "> DBAFrom the perspective of "> DBAIt is a nightmare and unfriendly, so "> DBAWe strongly recommend ibatis. "> DBAIt seems that in this application scenario, the application ibatis is easier to control the database performance, and programmers do not need to "> SQLHowever, the developers listed the advantages of Hibernate and proved that using hibernate would be correct, and the overhead would be worthwhile.

"> DBAI also know that in the past few years, this development team has been using Hibernate and developers are familiar with all aspects of hibernae. They think they have sufficient control capabilities for hibernate, they are reluctant to leave the current technical environment, which is the main reason for their opposition to switching to other environments.

Of course, today I don't want to compare the advantages and disadvantages of these two frameworks, but I want to talk about a very interesting problem that technicians will face:Comfort Zone.

In recent years, the word "comfort zone" has often been heard by some "training Masters", which has aroused the resonance of countless eager winners. In fact, it is a common word that has existed since ancient times.

Reference I: Modern Western cognitive psychology holds that "comfort zone" refers to the scope of people's perception and association to a certain extent. In this scope, individuals or groups can operate effectively without discomfort or fear, so people will instinctively find their "psychological comfort zone ".

From the perspective of "comfort zone", architects/programmers are reluctant to switch to other frameworks. hibernate has been used for several years and is quite familiar to them. There are many uncertainties in migrating to other environments. This "uncertainty" brings them a sense of insecurity. therefore, they will naturally learn the advantages of Hibernate and hope to continue using it.

However, from another perspective, this kind of conservation will undoubtedly have some risks in the rapidly changing software industry.

Reference II: whenever people are in a comfortable zone, they will feel safe, self-confidence, and feel that they are competent for everything they do. However, if you have been in this status for a long time, just like a frog who misses swimming in a warm water basin, it will be too late to jump out one day!

Taking this hibernate as an example, firestar software recently accused JBoss of its hibernate 3.0 software of infringing the technical patents of its connected relational database and object-oriented software, if firestar wins the case and asks to stop developing the software, what should hibernate programmers do? This is like a frog soaking in the boiling water slowly, and the price may be painful.

As a technician, a positive attitude is necessary to face changes. If you stick to a small technical environment, the rate of return will naturally decline. From the perspective of the development of the software industry, this is also true.

Oops, "> DBADon't bind yourself to a database ......

-- End.

-- Updated:
Reply to a serious voice:

The "public" that I am talking about refers to DBA. Of course, if you have never heard of it, you can't say "public.

 

Shouldn't you be a DBA? Looking at the problem from a developer is naturally another thing. We once faced a case where the database execution plan went wrong and needs to be modified "> SQLThe modification on Hibernate is not very quick (because it is not a direct database SQL, of course, Hibernate 3.0 now supports naive "> SQL). In this case, if you put it on ibatis, it may be just a few minutes. Perhaps, you have made hibernate very flexible and made great changes, so you can only admire it. I really hope that people in every project can have such talents.

In addition, not necessarily hibernate "experts" can post comments. each person looks at the problem differently. DBA may have a reason to oppose this (as discussed in the blog "comfort zone "). don't forget that one field is a so-called expert, and another field may be a newbie.

Maybe you think that the English information not quoted by others is "hearsay", so what is "subjective speculation?