The embarrassment of Full-stack engineers
Today, I have no intention of Baidu's "full-stack engineers". I found my situation quite similar to that described in Encyclopedia.
From Baidu encyclopedia full stack engineer Co., http://baike.baidu.com/view/12046150.htm.
"
If a company does not understand the value of Full-stack engineers, the position of full-stack engineers will be very embarrassing. it is not nice to say that full-stack engineers will do everything and will not do anything. Once upon an interview, the other party asked a very basic question and he could not answer it. However, he could make products and know what the problem was, and he would not make any mistakes, but he just cannot answer the question. It is very easy to test him. Therefore, when applying for an interview, he may suffer losses in some cases, and he may not be able to earn a higher salary for those who have been deeply engaged in one aspect.
He often forgets the code syntax and Some APIs because of various technical barriers, so he often needs to check the API or even query the syntax. He thinks that I can hardly work without Google. In the eyes of some people, this is a manifestation of insufficient technology. He only remembers a Key, an index for how to find answers, not all. the human brain is not a computer, and he cannot write down everything.
"
I interviewed a company some time ago and did not answer any questions. I wrote an SQL statement on the system architecture, thread, windows Services, and requirements. On the way home, I was wondering why I had nothing to think about when I involved some details.
After five years in this company (not in the IT industry), the initial business and reports of the company were all implemented by manual excel + email. From business requirement analysis, data structure definition, database design, system architecture, uidesign, coding development, deployment, online testing, and a series of other tasks all need to be implemented by me. I have never stopped my head from work to work every workday. I am so tired.
The Initial Report Module html (jqueryui, easyui, and highcharts) + ajax + asp.net ashx (simple layer-3) + SQL stored procedures mostly write SQL
Up to now, the CRM module html (jquery, knockout, bootstrap) + ajax + asp.net mvc (three layers) + memcache + ef, most of the time to implement business logic
In the early stages of system development, server-side development, system framework, service, scheduling, and messy backend technologies are often involved. One day to a later day is to process the Service vs and stamp F6 in chrome. I felt like I was moving to the monkey, learning and forgetting, learning and using, so that I could not answer the question "you are proficient in that aspect" asked by the interviewer ".
Currently, the front end is popular with html5, css3, and angularjs. I really don't know if I should focus on a technology.