The Career Programmer: Guerilla Tactics for an Imperfect World
When Chris Duncan first asked me to do the foreword to his book, I didn’t think it would be that tough to do. How hard could writing a foreword be? Compared to some of the projects I worked on in the past such as BoundsChecker, writing a book, or my current job of debugging others’ impossible bugs, writing a foreword should be a piece of cake. However, within reading a couple of pages of The Career Programmer, I became extremely nervous because Chris is a far better writer than I can ever hope to be. The last thing I want to do is detract from great writing, and more importantly, an extremely important message for the software business. You’ve probably looked at the back cover or flipped through the pages and noticed that this book is not what you would expect to find in the computer books section of the typical bookstore. There are a billion books on how to use the hot technology du jour and maybe a few on project management, but this is the first book to directly address the developer and what it takes to get your real job done. Isn’t it amazing that the software engineering field has been around this long and this is the first book written for the real engineer? We’d love to say that we spend our days coding, but we really don’t.
What people are saying - Write a review
We haven't found any reviews in the usual places.
Good Coding Skills Are
Getting Your Requirements
Fighting for Quality
Keeping the Project
Managing Your Management
Controlling Your Destiny
Get a Job Sha na na na
Other editions - View all
actually approach better business world can’t chance Chihuahua company’s Consequently corporate world course create customers database deadline debugging decision makers deliver design phase detail development process diagram types didn’t document effort eight-hour day employee environment estimate experience fact food chain going happen hire idea implementation isn’t issues job security keep Killer App language living look marketing matter meeting ment milestones never Nonetheless obvious once overall overtime person political problem professional programmers project manager reality reason regression test release requirements résumé scope creep simply skills software development software development process software project someone spend step sure task techies technical testers testing there’s they’re things timeline trying typically we’re we’ve week what’s who’s won’t wouldn’t write you’re going you’ve
Page 8 - You can't get a job without experience and you can't get experience without a job.
Page xxiv - I daresay anyone who has been in the business for more than a few months can cite plenty of examples of editorial compromises due to pressure, real or imagined, from publishers, owners and advertisers," said Chris Welles, a former journalist who teaches at the Columbia School of Journalism.
Page 21 - The restaurant business can grind people up, so we try to help our employees build their self-worth and their sense of belonging to a larger community. It's good for them and it is good for the company, and believe me, I know it is good for me, too. (§} As the saying goes, "No one on their deathbed ever wished they had spent more time at the office." It usually takes a crisis to jerk a person out of their unconscious , "being lived" mode into one of conscious reflection on what really mat