Programmer a pragmatist From Journeyman to Master Review Essay Example

Programmer a pragmatist: From Journeyman to Master Review Paper Essay on Programmer a pragmatist: From Journeyman to Master There are books that teach us to certain aspects of our profession. Some speak of a particular technology or programming language, which could be not relevant at the moment, when you brought it from a bookshop. Others teach us, their methodologies, they say they are the best, giving examples that are sure to show the power of their words. Third acquaint us with the operating systems, their advantages and disadvantages. Fourth talk about the fashion database management systems and their correct application. All of this is wonderful. Each of these books leaves a trace in our soul. Some are forgotten after we finish them, we throw the other, not having read the half, others still remembered many years later. All this makes us stronger, more confident, we build more and more new systems, solve increasingly complex problems. But very often we do not have enough glue that would have stuck together all our knowledge and allow go to the next level. After all, human development, as much in this world is a spiral, is an iterative and ongoing process. And this is one of the few books that will allow to rise a few levels up and move in this spiral at a faster pace The main slogan of the book -. Never stop in its development. If you are familiar with one programming language and feel that further study within the framework of the current project is simply impossible, begin to learn another language. And though hell never come in handy, but this knowledge will never be superfluous. Here is what says in one of his interviews, Bjarne Stroustrup on this issue: We will write a custom essay sample on Programmer a pragmatist: From Journeyman to Master Review specifically for you for only $16.38 $13.9/page Order now We will write a custom essay sample on Programmer a pragmatist: From Journeyman to Master Review specifically for you FOR ONLY $16.38 $13.9/page Hire Writer We will write a custom essay sample on Programmer a pragmatist: From Journeyman to Master Review specifically for you FOR ONLY $16.38 $13.9/page Hire Writer  «It seems to me that the language we use to express their ideas and become part of us, so if you know only one language, can It seems as if proponents of other languages ​​represent a danger for you personally. It seems to me that the way out of this situation the development of other languages. I doubt that you can be a professional in the field of software and know only one language. Maybe economic reason: the fundamental knowledge beyond the boundaries of language, unlike many practical skills. Therefore, if I know only the language of X and toolkits, and you are a supporter of the language Y and its toolboxes, you represent a threat to the source of my income. Again, the decision seems to me in the knowledge of multiple languages ​​and tools (as well as a solid understanding of fundamental concepts)  » The same view is shared by the authors of this book, but in a broader context.. After all, our toolkit is not just limited to programming languages.  «Unfortunately, knowledge and experience are expiring assets. Your knowledge becomes obsolete to the extent that, as new techniques are developed, languages, technology and the operating environment. Changing the balance of forces on the market can make your experience outdated or completely inapplicable. Taking into account the rate at which sped days of the Internet, it can happen pretty quickly  » The only way out of this situation -. Investment in the equity portfolio of knowledge on a regular basis Many. The authors raise the issue of modularity and connectivity. The authors of this book is no exception. But they use some unusual term orthogonal ».  «The term orthogonal is borrowed from geometry. Two lines are orthogonal if they intersect at right angle, for example the coordinate axes in the graph This term was coined in computer science to denote certain variations or disconnectedness independence. Two or more objects are orthogonal, if the changes made to one of them, do not affect any other.  » It was not whether you have a case where you have a month before the end of the project know that DCOM for building client -servernoy architecture does not fit? And you have to look for alternative solutions I was in this situation, and only orthogonal system allowed to move to .Net Remoting for a week and will not break the terms. The situation in which turned out to be my team is not original. This happens all the time, and it is not only in the experience (which is clearly lacking in my case), but also in the fact that the adoption of the final solution a risky business. The basic principles of object-oriented design, iterative design process, modularity, and more directed to the postponement to a later date the adoption of many decisions. In fact, this problem can be considered more widely, not just in the context of a design solution, but also in the context of the views of man on the world in general and the software development process in particular. Chris Date is in the introduction to his excellent book An Introduction to database systems quotes the following excerpt of Bertrand Russell:  «I was accused in the habit of changing their opinions But how could a physicist, working since 1900, for example, boast in the middle of the twentieth century, the that his opinions did not change nilis over the past half century? That philosophy, which I appreciate and which I try to follow is scientific in the sense that we must always strive to obtain irrefutable knowledge, but new discoveries may reveal past mistakes are inevitable for any impartial mind. Whenever and whatever I say, now or in the past, I never claimed it the ultimate truth. I say only that at one time expressed my opinion was quite reasonable I would be very surprised if further research showed that it should be revised. Besides, I never expressed my opinion as the final verdict but simply pointed out that this is the best I could do at the time to reach a clear and accurate understanding. My goal was, above all, clarity around  ». Therefore, never hesitate to admit (and especially myself) that you made a mistake. Perhaps this is not a bug at all, can be under the circumstances, with the experience and knowledge this was the only correct way out Are not you were in a situation where a project manager, a representative of the customer, or who? -That of guidance comes to you and asks: How much time do you need, to complete the so-and that something? And how often do you meet: Week or Three days, when exactly understand what you did not understand (sorry for the pun), you have to The authors are advised to speak: Ill be back to you with this later . you almost always can get better results if you do not hurry up and spend some time to go through all the steps described in this book. by the estimates made on the fly ( for example, the office coffee machine), will have to return again and again as, indeed, and coffee, losing the peace . what do you think of an ode to the requirements? Perhaps your requirements have to get in your career? Or maybe you have faced the problem of over-specification? Maybe you are faced with the documents, which took dozens of pages, which was defined as Bitik should be dedicated to one or the other option, which invents its own terminology, completely contrary to the subject area? When everything behind it is simply impossible to make out the semantics what the system should do in the end? Unfortunately, not everyone wants to constantly expand their knowledge Helpful tips in the book a lot. If I continue to describe everything that impressed me in the same spirit, the description itself drags on a little book. Much of what the author describes intuitive to each of us, a lot can change our point of view on some aspect of software development. The authors do not offer a silver bullet and there is no guarantee that the path from apprentice to master can be simple. No, it is not so The main thing is that they want the authors, is that make you proud ownership. I wrote it, and I stand behind my work. Your signature should be recognized as a quality mark. people need to see your name in the title of the program and expect that it will be a solid, well-prepared, verified and documented. It should be a truly professional work. Written by true professionals. pragmatic programmer .