multipart/mixed
Welcome

multipart/mixed is Josh Carter's home on the net. Latest Updates: New Programmer's Survival Manual: Now For Sale! (Jul 22) Essential Industry Skills (Nov 09) New to Programming in Industry? I Need Your Help (Jun 14) .

Categories

Software Articles on design, patterns, and other programming topics. I've been in this crazy industry for ten years now, and I hope to pass on some things I've learned.

Photo Photography articles and software tools. Discover the joys of external flash, autofocus woes, and IPTC meta-info.

Gallery Selections from my latest photography, art, and graphic design work.

Magic Cap A collection of resources for Magic Cap, the operating system for handheld computers. Includes software downloads, a history of MC hardware (including prototypes!), and more.

Productivity Topics revolving around productivity and Getting Things Done. Home to office supply geekery and impassioned articles on notebooks.

Reading List Mini-reviews and pondering on books I'm reading or have finished recently.

Drums Articles on electronic drumming including Reason and Live software, KAT hardware, and other fun stuff.

Fitness Craziness with iron, wheels, and whatnot.

Miscellany The bucket for "everything else."

Newest Entries

New Programmer's Survival Manual: Now For Sale!

cover

Now for sale: my book for programmers entering industry, the New Programmer's Survival Manual, is available in "beta" ebook form. If you purchase the beta, you'll also get an upgrade to the final book which will be published around September.

I expect readers of this book to fall into a couple categories:

  • College students taking Computer Science classes and wondering, "is this what programming is like in the real world?" (Short answer: no.)
  • College grads already in industry, who have noticed first-hand that the answer to the first question is "no," trying to get their heads around the disparity.
  • Professionals from other backgrounds who got into programming as a hobby or side job, now wanting to take it on full-time.

Programming at industry level requires new skills--you'll build programs that dwarf anything you've done on your own. This book introduces you to practices for working on large-scale, long-lived programs at a professional level of quality. You'll find out how to work efficiently with your tools, and discover essential new tools.

But the tools are only part of the story; you've got to get street-smart too. Succeeding in the corporate working environment requires its own savvy. You'll learn how to navigate the office, work with your teammates, and how to deal with other people outside of your department. You'll understand where you fit into the big picture and how you contribute to the company's success. You'll also get a candid look at the tougher aspects of the job: stress, conflict, and office politics.

Finally, programming is a job you can do for the long haul. This book helps you look ahead to the years to come, and your future opportunities--either as a programmer or in another role you grow into.

There's nothing quite like the satisfaction of shipping a product and knowing, "I built that." Whether you work on embedded systems or web-based applications, in trendy technologies or legacy systems, this book helps you get from raw skill to an accomplished professional.

(Note: If you're read along with my previous writing on this subject, all of the best material (and lots more) is in the final book. And you'll be relieved to know I dropped the bits about assembly language.)

Essential Industry Skills

Allow me to consult the vast oracle of the interwebs on a perplexing problem. (That would be you.) I’ve got a lot of thoughts about on-the-job technical skills needed by industry programmers, each worthy of its own book. I have one chapter in the book I’m working on.

Here’s what I want to accomplish:

  • Give the newbie programmer a picture of programming topics that seem to come up again and again. I don’t intend to teach the topics, but give a brief discussion of what they are, why they keep coming up, and some good approaches to start on. (See examples below.)

  • Choose a reasonable subset of topics that apply across a broad cross-section of industry (80/20 rule).

  • Refer the reader to other resources to find out more.

This chapter is specifically focused on programming chops, not tools or bigger-picture practices. (I’ve got other material about that.) Let me give a few examples to clarify.

Continue reading "Essential Industry Skills" »

New to Programming in Industry? I Need Your Help

I'm working on a book for people new to programming in industry. My reader may be:

  • A college student looking to become a professional programmer, wondering what school's not teaching them;

  • A recent grad who's working but has noticed that there's a lot more to professional work than what you learned in school;

  • Someone coming to programming from a completely different field, who got their feet wet and now wants to make programming a career.

Is this you? Yes? Let's talk. I'm putting together an advisory panel of "target audience" readers, whose goal is to make sure I'm answering your questions. The scope of this topic is nearly infinite; the number of pages I've got to make a high-impact book is not. I need to keep it tight and focused on the topics that are most useful to you.

In return for your help, you'll get early access to chapters as I write them. I'll try to swing a copy of the paper book for you, too, when it's printed.

Interested? Send me an email.

Dear Programming Job Applicants...

I know this might come as a shock to you, but most programming job applicants suck. I've interviewed my fair share this month, and it'll be a lot easier for all of us if I tell you upfront what I'm looking for.

As a hiring manager, my job is to make sure you can do the job you're applying for. For programming that means you need to be able to program. So when I whip out a laptop in our round-one interview and ask you to write some code, try to hide your terrified expression.

Continue reading "Dear Programming Job Applicants..." »

Is it Worth Teaching Assembly?

This is an open question to programmers: is it worth teaching someone assembly language anymore? My instinctive reaction is "of course," but let me explain why I'm second-guessing that instinct.

The Case For

Back in the 1990's I had my moment of revelation: a pal of mine, a far more experienced programmer than me, showed me how C code compiled into assembly. This was on the Motorola 68K instruction set. I learned to walk through how the stack works, how pointers work, how loops work... it all finally made sense. From that time forward, I've had no fear of C or C++ because I know how the language morphs the code I write into the code the computer sees.

Continue reading "Is it Worth Teaching Assembly?" »

Genevieve's First Ballet Recital

Photo

My daughter Genevieve performing in her first ballet recital. Photo toned to black-and-white using Alien Skin Exposure.

Coming to a Bookstore Near You

First, thanks to all the readers who followed my PragProWriMo 2009 writing--your support was invaluable. I'm happy to announce that Pragmatic Bookshelf picked up my book in December and I'm busy finishing the first draft. I'm not sure how long the whole process will take, the optimist in me wants to believe I can finish by the end of the year. Either way I'm very excited to bring this book to fruition and the folks at Pragmatic are fantastic to work with.

Quality: Beginning vs. Afterward

Yes, PragProWriMo 2009 was over yesterday. However, I can’t introduce the topic of quality and then just stop there, can I? After this it’s time to start working on my book proposal.

There are two approaches to building a quality product: build it in from the beginning, or beat it in afterward. The former approach requires a lot of discipline and effort from the engineering team. The latter requires a lot of testing and, again, effort from the engineering team.

Continue reading "Quality: Beginning vs. Afterward" »

Quality is Job 0.99999

This is intended to introduce a chapter on quality. There’s a myriad of topics here; this post is merely setting the stage.

I take it as a given that any product should be a high-quality product. Why bother making it otherwise? This seems like a straightforward goal, but the technology industry has had a hell of a time figuring out how to build quality software. There’s a joke that’s been around for at least a decade:

There’s word in business circles that the computer industry likes to measure itself against the Big Three auto-makers. The comparison goes this way: If automotive technology had kept pace with Silicon Valley, motorists could buy a V-32 engine that goes 10,000 m.p.h. or a 30-pound car that gets 1,000 miles to the gallon—either one at a sticker price of less than $50. Detroit’s response: “OK. But who would want a car that crashes twice a day?”

Any good joke has an element of truth to it—this one especially so. Auto makers can build cars that’ll drive hundreds of thousands of miles, but Windows 95 would crash after 49.7 days of continuous operation—a bug that took four years to discover 1 because other bugs would crash Windows 95 long before 49.7 days could pass.

Continue reading "Quality is Job 0.99999" »

Millie Berger

Photo

Portrait of my grandmother. I don't consider myself a portrait artist but I do get lucky once in a while. On-site lighting was two flashes bounced off the ceiling. Photo toned to black-and-white using Exposure 2 and vignetted with Bokeh.

RSS feed | Atom Feed | Subscribe in NewsGator Online