Recommended still has the 240fps with no Readings for Lateral Dev Hires at ThoughtWorks -- An Unofficial Opinion

Recommended still has the 240fps with no Readings for Lateral Dev Hires at ThoughtWorks -- An Unofficial Opinion - Overall, the A3's improvements for 2017 are pretty significant and make this nice-size, reasonably priced phone even more appealing for those who like the idea of the Galaxy S7 but can't quite stretch their budget that far. Its waterproofing and fingerprint sensor are both convenient and practical, and the good-looking design makes it easy to forget that this phone has a price tag that's half that of many flagship phones the blog 12 katherinejohns, well we have collected a lot of data from the field directly and from many other blogs so very complete his discussion here about Recommended still has the 240fps with no Readings for Lateral Dev Hires at ThoughtWorks -- An Unofficial Opinion, on this blog we also have to provide the latest automotive information from all the brands associated with the automobile. ok please continue reading:

All thoughts mentioned in this post are in no way endorsed or validated by ThoughtWorks. These are solely my opinions (and a few co-workers). You are still the best judge of your capabilities, and needs.

Quite often experienced folks joining ThoughtWorks have a common set of questions: What should I read to prepare myself for ThoughtWorks? What kind of technologies does ThoughtWorks work on? Will I go on a Ruby or Java or Mobile project?

I doubt there is any good and precise answer to these questions. But, there certainly are some practices that I feel our in the DNA of ThoughtWorks. Agile & Extreme Programming practices drive most of this. Unfortunately, Agile means totally different things to different people outside ThoughtWorks. And, quite often, nothing will prepare you for the radical changes that are going to come to your way of working at ThoughtWorks.

So, I thought, why not try come up with some recommended readings for Dev Lateral hires (experience range of 3 - 10 years), to introduce them to some of our development practices, coding styles, unit testing beliefs, etc. I asked a few of my colleagues - namely Unmesh, Chirag, Sunit and Aman on what they felt should be the minimum recommended reading list for Lateral ThoughtWorkers. This is what we all came up with.

I may have used my discretion to sanitize the final list, therefore if you don't like the list -- blame me! :)

Highly Recommended Book Reading

Refactoring, Improving the Design of Existing Code (Martin Fowler)
This book introduces you to refactoring, code smells and patterns to help you refactor your code into something much more readable, maintainable and extensible. If you are new to refactoring, this will be an eye-opener. Note that examples in this book are targeted towards Java developers, but core concepts are valid in almost any serious programming language. Couple this reading with IntelliJ Refactoring shortcuts to realize how easy it is to perform useful re-factorings by Java programmers. At ThoughtWorks, the most popular Java IDE is IntelliJ. Its refactoring capabilities are beautiful.

Test Driven Development (TDD) By Example (Kent Beck)
TDD - A fundamental practice that has been very highly suggested by proponents of Extreme Programming (XP). This book (again in Java) helps developers in understanding how to think Test-First, and how unit testing affects the design and development of your code. It is a simple, tiny and very nicely written book that gets-to-the-point. Warning: You are not supposed to "read" the book, but follow it as-if Kent Beck himself is pairing with you. If you do not code along with this book, you may as well not read this book. If you are joining ThoughtWorks, you will benefit tremendously by understanding TDD.

Extreme Programming Explained (Kent Beck)
An excellent introduction to the values and practices of Extreme Programming, and our preferred flavour of Agile. It will give you an insight into how we work, and why we do things the way we do. A must read -- whether you are a developer, QA, BA, PM or any technically connected person who is joining ThoughtWorks. The book is deceptively simple. Understanding this book will explain to you the meaning of "being" Agile, versus "doing" Agile.

Clean Code: A Handbook of Agile Software Craftsmanship (Robert C Martin a.k.a Uncle Bob)
Coding is our bread and butter. Well, we prefer it nice and clean! Clean Code is taken very seriously at ThoughtWorks, and the techniques, tips and recommendations mentioned in this book are invaluable. This book is packed with code examples (in Java), and isn't something you read over a plane journey, but something you couple with an IDE, coffee and a leave-me-alone-to-do-as-I-please environment.

Other Recommended Book Reading

12 katherinejohns

Selasa, 01 Mei 2018