Chapter 4. Building the Perfect Team
I CLEARLY REMEMBER THINKING, "MAN, I AM OUT OF THE LOOP." I SAT IN A COMPUTECH CONFERENCE room with a newly assembled team of high-powered developers. The task at hand was to port our flagship financial software from Microsoft QuickBasic to the promising new Microsoft product, Visual Basic 3. As a resident VB guru, I would bring technical expertise and hard-earned experience to a project that would determine the future of our firm.
It was hard to believe that only three weeks before, I had finished my final day of work at the large commercial bank where I cut my programming teeth. Only five weeks before, I'd met Jack, my current boss, for the first time. I'd emerged from that interview feeling a strong connection with Jack, but also insecure about how well I'd impressed him technically. And of course, perhaps hardest to believe, it was only six weeks ago that I had plunked down $11.95 at Barnes & Noble for a brand-new copy of Bill Sempf's Visual Basic for Dummies (Wiley).
In the conference room that day, Geoff and Mark, the two dev leads for our team, were debating some fundamental architecture questions. Mark laid out his argument, saying, "Look, I know it will be a lot of extra work up front, but I don't see any way that we can get the UI experience we want if we don't write our own user controls."
Geoff responded, "You're crazy, Mark. Do you realize how much effort that takes? I've been working with C++ a lot longer than anyone ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access