Review “Managing Oneself” by Peter Drucker


To call this book a book is a bit exaggerated. It contains only 60 pages which I assume you can read in under one hour. Nevertheless if you haven’t encountered the work of Peter Drucker yet this is the place to start.

The Author

Peter Drucker is best known for his concept of “Management by Objectives”. He also coined the term “knowledge worker” and “core competency”.

Main Takeaways

Drucker elaborates on three major questions:

  • What are my strengths?
  • How do I perform?
  • What are my values?

These are the basic questions to ask yourself to answer the bigger questions:

  • Where do I belong?
  • What can I contribute?

The rest of the book ponders on developing relationships and a second career for later in life.

The bottom line

I will stop writing so my review won’t be longer than the book itself. Managing yourself is a big factor in personal success. If you don’t manage yourself how can you manage others? As I already mentioned this one is a good entry into the works of Peter Drucker. It’s also perfect as a gift, so buy a bunch of them.

Review “The Passionate Programmer”

About the Author

Chad Fowler is best know for being CTO of 6Wunderkinder after its exit to Microsoft. Before he was Senior Vice President of Technology at LivingSocial.

The Book

Fun fact: the first edition of this book was titled “My Job Went to India: 52 Ways To Save Your Job” but Fowler found this title misleading: instead of improving from mediocrity to keep your job we wants You to focus on becoming exceptional and staying ahead of the pack. Continue reading “Review “The Passionate Programmer””

Review “Lessons learned in Software Testing”

I became aware of James Bach through the Google Techtalk “Becoming a Software Testing Expert”. Then I quickly got his book “Lessons Learned in Software Testing”.

In this book Bach presents with his colleagues Cem Kaner and Bret Pettichord 293 tips and tricks (“lessons”) from the test practice.

Divided into 10 chapters, this book covers almost every aspect that can be encountered in daily SW test work.

Similar to Rework, the strength of this book lies in the small, self-contained chapters. You can individually rate and apply each tip individually or not. The authors are advocates of the context-based test strategy; So there is no all-encompassing concept / strategy that works for every kind of SW product.

Therefore, the recommendations are sometimes deliberately contradictory, e.g. whether SW tests according to IEEE 829 should be documented or not. Just as a doctor only makes a diagnosis after a detailed medical history and then treats the patient, “lessons” are tools that are only to be used after a detailed analysis of the situation (industry, company, team, project, product).

At the beginning of this analysis, the tester must scrutinize himself and his mission in the development process. Insights such as that you can never find all the mistakes and therefore never completely test, sound obvious, but should always be kept in mind to get your own motivation.

The tester does not verify that the product is working, but shows that the product has a defect at a certain point. Word!

The fact that the tester primarily supports or relieves the developers is an idea that is far too rarely taken into account in practice. Test departments are often perceived as opponents rather than as partners.

The following chapters cover the handling of test techniques, bug reports, automated tests, test documentation, the exchange with the developers, as well as the management of the own test team.

The conclusion of the book are the two topics career in SW-test and creation of a test strategy.

Conclusion

If you are looking for a strict roadmap that simply has to be implemented one-to-one to ensure software quality, you will not find it here. On the other hand, if you are looking for suggestions and critical questions to continuously improve yourself and your work, you will find enough material in this book to deal with it for several weeks to months.