Five years of work has been in small software companies mixed, always feel that their expertise has not been greatly improved. Of course, the middle also changed one or two companies, the interview of the company on a lot of home, always feel that the formal software company (regardless of size) for the basic knowledge of the assessment are very important, and no matter what you say you have served before what NB Company, do what NB project, come up first to take a basic topic to check your level. At first I was rejected, always feel the test these things do not have any use, anyway, some things work is not necessarily used to get, as long as they can make something to it. What does it look like to "make something"? This problem always feel difficult to answer from the theory, take my work for the past few years, in the past few years, mainly for the mold manufacturing industry to do software development, but also developed some things such as various reports, warehouse procurement system, outsourcing management system, cost management system, APS and so on, some features customers can also use up, Some of the features of the customer although used up but always appear a variety of bugs, when certain functions need to be extended, the total feeling a little overwhelmed, from a certain point of view, these years I did "make things" come out, but if from the perspective of software quality, I completed the quality is debatable.
Small company people are relatively few, there is no so-called testing department, everything has to rely on their own, even implementation is also a person to complete, so in the premise of limited human energy in small companies want to develop good one function seems some difficulty. So I've been thinking over the years what kind of person I want to be in the current environment (small companies). Do you want to become an integrated talent (demand analysis, software development, implementation) or in a certain area of knowledge to do fine? Of course, this problem in different small company situation choice is not the same, for example, my last small company asked me to be a comprehensive talent, the reason is that people less things, do not ask my boss why not recruit such words, I just want to answer because I am not the boss, reason is so simple. In the last company I also really cultivate or have to become a comprehensive type of people, for example, I am a small company software products iteration, implementation, after years of accumulation (success or failure of experience summary) is a set of their own methodology, because this article is not to say this aspect, so here do not start speaking, I will write a separate article to share my experience of working in a small company when I have the chance. At present, I serve a small company, but this company is a little more formal, the minimum demand analysis, implementation of this piece does not need me to worry too much, in this company I would like to software development this piece to do fine, the least worthy of the name of software development engineer. How to do the fine-doing professional? I think the first step is to put the foundation to a good supplement, so there is this series of articles, about the Java tutorial Books a lot, why should go to the interview and other books? First of all, I work in this company so far is still relatively happy, the boss is more open-minded, allowing me to play in the module I am better at, so there is no intention of leaving, but in case of resignation for some reason? The short-term effect of this book can not only supplement the basic knowledge, but also better face the possibility of leaving the situation, and then chose this book to read.
I will read this book at the same time, will I think there is a question of knowledge points out to share, on the one hand, by repeating the knowledge point of the blog article to understand more deeply, on the other hand through the way blog share to let more people see, and through the discussion will also promote my understanding of some problems. Here is a series of catalogs for this series:
1, Java Programmer Interview (fourth edition), Java programming basic concept
2, "JAVA Programmer interview Treasure (fourth edition)" of the transfer and reference
3, "JAVA Programmer interview Treasure (fourth edition)" of the cycle, conditions, probability
4. Java memory management of Java Programmer Interview (fourth edition)
5, "JAVA Programmer interview Treasure (fourth edition)" Object-oriented
6, "JAVA Programmer interview Treasure (fourth edition)" Object-oriented
7, "JAVA Programmer interview Treasure (fourth edition)" of the Inheritance and interface
"JAVA Programmer interview (Fourth edition)" Reading notes before the words