yourfanat wrote: I am using another tool for Oracle developers - dbForge Studio for Oracle. This IDE has lots of usefull features, among them: oracle designer, code competion and formatter, query builder, debugger, profiler, erxport/import, reports and many others. The latest version supports Oracle 12C. More information here.
On any significant size project I am going to have a team of developers reporting to me. Over the years those numbers have varied greatly. I have managed 1 developer and teams of developers. I have the most fun on projects where I have between 4 and 10 developers.
I also prefer to be partnered with a good project manager or none at all. A bad project manager just makes it harder to keep the team motivated and the client happy. I would say less the 5% of the gigs I have been on have provided a good project manager. 25% of them have provided bad ones, and the rest of the gigs the responsibility fell on me, the software architect.
The point of all this is that my job requires me to manage programmers and communicate to stakeholders effectively. Reading books on project management and general management have not been fun, but has been necessary. I was happy to see one come out that targets more of what I have to do, and that is manage programmers.
Below are the chapters in the book.
1. Why Programmers Seem Unmanageable 2. Understanding Programmers 3. Finding and Hiring Great Programmers 4. Getting New Programmers Started Off Right 5. Becoming an Effective Programming Manager: Managing Down Insert - Rules of Thumb and Nuggets of Wisdom 6. Becoming an Effective Programming Manager: Managing Up, Out, and Yourself 7. Motivating Programmers 8. Establishing a Successful Programming Culture 9. Managing Successful Software Delivery Tools
In the very first chapter the authors hit a nerve. I went to school for electronic engineering and worked in that field before moving into programming. Because of my work in the engineering field I have always been comfortable with the engineering practices that made there way into the programming field. The authors are however correct when they say a majority of programmers today do not have to know anything about software engineering. They are simply programmers because they decided they wanted to be and were lucky enough to get a job with that title.
The point is that you most likely will not have a team of software engineers. Managing and working with engineers is much simpler that working with the self made programmer that was previously an artist, musician, writer, or any other field. This book helps identify different personalities and offers tons of advice on how to work with them in a positive way.
I wish we could put a law in place that in order to hire programmers an organization must follow the guidance offered in the chapter Getting New Programmers Started Off Right. 80% of my starting week have been a complete waste of my time as well as the organization's time. Rarely are they ever ready for you.
One very cool section of the book is the 60 page insert titled Rules of Thumb and Nuggets of Wisdom. It contain short blurbs and quotes from some of the leaders of the programming industry. Cracking open this section you can lose track of time going through them and thinking about them.
The thing I liked most about this book is that it borrowed some of the best processes in the industry, but is absolutely not process centric. Meaning you'll hear some nuggets of Scrum and other processes, but none of them are highlighted in the book. This book is all about understanding the programmer, your environment, and yourself, and how to make the right decisions given your environment.
My belief is that compiled information is knowledge, knowing what to do with the knowledge is wisdom. I see a whole lot of knowledge these days, but very little wisdom. The authors of this book have successfully compiled wisdom. Reading this book will change the way you work with programmers. Every single chapter of this book is a real gem.
This book will become a classic to turn to over time. Every manager interacting with programmers should read this book. That includes CIOs, Software Architects, Enterprise Architects, and Lead Developers. You don't need to have the word manager or director in your title. If in your role you find you are managing a team of developers, you should read this book.
The other day I found myself in a discussion with a prospect regarding the merits of capturing complete stack traces for every transaction that flowed through their production system. You see AppDynamics doesn’t do that; we capture problematic business transactions, and this bloke seem...
In Part 1, I looked at what could be behind Facebook’s acquisition of WhatsApp and subsequent purchase of Oculus Rift. How are these seemingly different acquisitions related? There is no question that both Facebook and Google are in a race to build the next-generation computing/communi...
In the pharmaceutical industry, the drug development clock is ticking at the rate of warp-speed. As a result, companies are constantly looking for solutions to help them accelerate time to market – and many are realizing that implementing a cloud-based information management system can...
Good morning! Or evening, if you happen to be reading this on the other side of the world. Our topic for today is the internet. What? You already know about the internet? No, no, I don’t mean that internet, the boring old one you use to access YouTube and send Facebook updates, e...
Having an effective BYOD policy is one of the most critical steps to ensuring BYOD success. Learn the basics for securing your company's data and clarifying the process.
Employees like the ability to choose. Whether it be choosing the hours they work or whether or not they can teleco...