Darel Rex Finley in 888

Primary + Reviewer — An Alternative IT Plan For Corporations

2009.03.18   prev     next

MOST corporate IT departments seem to follow this philosophy: Hire a fairly large group of developers (four or more), none of them particularly high-talent. Then have them develop in a really big, multi-layered, OO, framework-intensive environment, that utilizes several different languages and technologies. This approach is based on the ideas that:

  • Developers should be easily replaceable — we don’t want most of our code written by one high-talent developer, because then he’ll be the only one who understands it, and if he leaves for any reason, or if his code becomes unworkable even by him, we’ll be hosed.

  • Big frameworks force developers to create code that can be understood and modified by other developers.

The downside of this approach is that:

  • Lots of developers cost lots of money, even if none of them are getting high-talent bucks.

  • Lots of developers are slowed down by the needs to frequently communicate with each other, to avoid stepping on each others’ toes while developing, and to figure out other developers’ code.

  • Having several developers, none of whom think of their current job as any more permanent than the last few similarly-paying jobs they’ve held in the past several years, results in a “fix it later; maybe never” attitude towards minor bugs, intermittent bugs, and other imperfections. The software winds up with a flaky, half-baked feel — and can become hard to work on despite its frameworks and other code-organization technologies.

  • Big frameworks make an application much larger and slower, create more failure points and dependencies, increase development time, and incur much larger licensing fees.

Wouldn’t it be great if there was a way to get the best of both worlds? Wouldn’t it be great to get the speed and skill of a small, high-talent development force, programming to a limited, low-cost set of languages, resulting in a snappy, low-overhead app with a minimum of failure points — while not running the risk of having to start over if your key developer disappears or creates an unworkable mess?

Wouldn’t it be great indeed.

Primary + Reviewer

How about this:

Hire two developers: A primary developer and a reviewer. They never meet each other, and communicate with each other only by sending messages to their manager, who reads them before forwarding them to the other party. Neither of these two developers know how to contact each other independently, and they are told at the time of hiring that they are expressly prohibited from doing so.

The primary developer is high-talent, and has proven his abilities through prior programming projects which he developed from the ground up. (The polish — stability and lack of bugs — of such projects is very important in evaluating a candidate.) The primary developer does all your development work. He is paid very well — somewhere between 50% and 100% more than he would make at the software development job he could get at a typical company. He still costs a lot less than a whole team of developers, but his individually high pay provides him a strong inducement to stay with your company long-term, and to develop your software with the intention of continuing to work on that same code for years to come (i.e. to agressively attack all known bugs and imperfections).

As much as possible, your primary developer should not be required to use any particular frameworks, object systems, languages, technologies, etc., but instead has tremendous leeway to decide what he thinks is best for the company and for his own efficiency as a developer. This is certainly not absolute — for example, if the primary developer thinks that a back-end database is not needed for this particular project, and data should be stored in flat files, but management has plans for how the back-end data eventually will be used in conjunction with other products that require a database, then of course management can override that decision. But this should be done only when there is a specific reason to do so. If, instead, the manager says, “I agree with these things the primary developer wants to use, but not these other things, so I’ll override those other things” — then the primary isn’t really being given any leeway at all; the manager is simply making all technology decisions.

Whatever technologies and languages the primary chooses, his code must be well-commented, sensibly organized, and use rigorously consistent (but developer-chosen) conventions of code formatting and variable naming.

The primary developer must check-in all code changes every night.

Constant Review

The other developer, the reviewer, is paid the salary of a typical developer — not a lot more than he has been making lately — but works subtantially less than forty hours a week, and doesn’t write any code. His job is to continuously review the code written by the primary developer, and (via the aforementioned managed e-mail forwarding system) talk with the primary developer, asking questions such as “what is this statement for,” and “what happens when the user does such-and-such?” That kind of thing.

The reviewer does not just skim the code looking for obvious problems, as one might have to do if asked to review another developer’s work at some typical IT department. No, this reviewer studies all the code very thoroughly, aiming to understand how it works just as well as the primary developer does. That’s his job.

The manager also looks at the code periodically, and reads all communications between the two developers, to make sure that steady progress is being made.

The primary developer may be allowed to work remotely from any location of his choosing, or may have to spend at least part of each week working in the office with the QA and requirements personnel. The reviewer, however, never comes to the office, and is known only to the manager (and that manager’s higher-ups, of course). So, although the reviewer is not paid much more than he could make elsewhere, he still has a very strong incentive to stay with your company, since his current post allows him much more free time, plus the opportunity to work from any place where he can VPN into your network.

The Primary + Reviewer system has the potential to achieve:

  • Lower development costs

  • Lower technology licensing fees

  • Faster, cleaner development

  • Snappier and less buggy end-user experience

  • Faster turnaround for user requests

  • Strong, long-term loyalty from both developers

Contingencies

If the primary developer ever does leave, for whatever reason, the code is well-written, well-commented, and thoroughly understood by the reviewer, who can now step in as the primary developer until a new primary developer is found — or can permanently occupy the primary developer seat (with commensurate pay boost), in which case a new reviewer will be hired.

If a new reviewer has to be hired, for the reason mentioned above, or because the current reviewer just leaves, then the new reviewer will spend two-thirds of his time reviewing the primary developer’s ongoing work, and the other one-third of his time studying pre-existing code.

In the absolute worst case, where both developers leave nearly simultaneously, the code is still well-organized, well-commented, and consistently formatted. Plus the manager has a good feel for it from her periodic examinations — perhaps she could step in as the primary or reviewer for a time.

Will the developers like it?

They’ll love it.

And if your primary developer ever thinks that it might be a little annoying to have to explain things to a reviewer via forwarded e-mail, and to have all his new code reviewed every day, then he’ll just remember how much less he was making at all his previous jobs, how much less real coding he got to do at those jobs, how bad it was to be unemployed inbetween them, etc.

And if your reviewer ever thinks it might be a little annoying to review someone else’s code for a living, he’ll just remember how much less free time he had at his previous jobs, and how bad it was to commute to the same cubicle day after day — and how bad it was to be unemployed between jobs, etc.

They’ll love it; they really will. And so will you.

prev     next

 

 

Hear, hear

prev     next

Best Recent Articles

Method of Implementing A Secure Backdoor In Mobile Devices

When Starting A Game of Chicken With Apple, Expect To Lose

How I Clip My Cat’s Nails

Seasons By Temperature, Not Solstice

It’s Not A Criticism, It’s A Fact

Features (Regularly Updated)

A Memory of Gateway — news chronology of Apple’s ascendancy to the top of the technology mountain.

iPhone Party-Poopers Redux and Silly iPad Spoilsports — amusing litanies of industry pundits desperately hoping the iPhone and iPad will go away and die.

Embittered Anti-Apple Belligerents — general anger at Apple’s gi-normous success.

RSS FEED

My books

Now available on the iBookstore!

   

Links

Daring Fireball

The Loop

RoughlyDrafted

Macalope

Red Meat

Despair, Inc.

Real Solution #9 (Mambo Mania Mix) over stock nuke tests. (OK, somebody made them rip out the music — try this instead.)

Ernie & Bert In Casino

Great Explanation of Star Wars

Best commercials (IMO) from Superbowl 41, 43, 45, 46, and 47

Kirk & Spock get Closer

American football explained.

Sonos and Opalum — awesome sound stuff I saw at CEDIA.

TV: Better Call Saul; Homeland; Survivor; The Jinx; Breaking Bad; House of Cards; Inside Amy Schumer

God’s kitchen

Celebrity Death Beeper — news you can use.

Making things for the web.

My vote for best commercial ever. (But this one’s a close second, and I love this one too.)

Recent commercials I admire: KFC, Audi

Best reggae song I’ve discovered in quite a while: Virgin Islands Nice

Pinball Arcade: Unbelievably accurate simulation of classic pinball machines from the late ’70s through the ’90s, with new ones added periodically. Like MAME for pinball — maybe better.

d120 dice: You too (like me) can be the ultimate dice nerd.

WiFi problems? I didn’t know just how bad my WiFi was until I got eero.

Favorite local pad thai: Pho Asian Noodle on Lane Ave. Yes, that place; blame Taco Bell for the amenities. Use the lime, chopsticks, and sriracha. Yummm.

Um, could there something wrong with me if I like this? Or this?

This entire site as a zip file — last updated 2017.09.08

Previous articles

The Ultimate, Simple, Fair Tax

Compassion and Vision

When Starting A Game of Chicken With Apple, Expect To Lose

The Caveat

Superb Owl

NavStar

Basic Reproduction Number

iBook Price-Fixing Lawsuit Redux — Apple Won

Delusion Made By Google

Religion Is A Wall

It’s Not A Criticism, It’s A Fact

Michigan Wolverines 2014 Football Season In Review

Why There’s No MagSafe On the New Mac­Book

Sundar Pichai Says Devices Will Fade Away

The Question Every Ap­ple Naysayer Must An­swer

Apple’s Move To TSMC Is Fine For Apple, Bad For Samsung

Method of Implementing A Secure Backdoor In Mobile Devices

How I Clip My Cat’s Nails

Die Trying

Merger Hindsight

Human Life Decades

Fire and the Wheel — Not Good Examples of A Broken Patent System

Nobody Wants Public Transportation

Seasons By Temperature, Not Solstice

Ode To Coffee

Starting Over

FaceBook Messenger — Why I Don’t Use It

Happy Birthday, Anton Leeuwenhoek

Standard Deviation De­fined

Not Hypocrisy

Simple Guide To Pro­gress Bar Correctness

A Secure Backdoor Is Feasible

Don’t Blink

Predictive Value

Answering the Toughest Question About Disruption Theory

SSD TRIM Command In A Nutshell

The Enderle Grope

Aha! A New Way To Screw Apple

Champagne, By Any Other Maker

iOS Jailbreaking — A Perhaps-Biased Assessment

Embittered Anti-Apple Belligerents

Before 2001, After 2001

What A Difference Six Years Doesn’t Make

Stupefying New Year’s Stupidity

The Innovator’s Victory

The Cult of Free

Fitness — The Ultimate Transparency

Millions of Strange Dev­o­tees and Fanatics

Remember the iPod Killers?

Theory As Simulation

Four Analysts

What Was Christensen Thinking?

The Grass Is Always Greener — Viewing An­gle

Is Using Your Own Pat­ent Still Allowed?

The Upside-Down Tech Future

Motive of the Anti-Ap­ple Pundit

Cheating Like A Human

Disremembering Mi­cro­soft

Security-Through-Obscurity Redux — The Best of Both Worlds

iPhone 2013 Score Card

Dominant and Recessive Traits, Demystified

Yes, You Do Have To Be the Best

The United States of Texas

Vertical Disintegration

He’s No Jobs — Fire Him

A Players

McEnroe, Not Borg, Had Class

Conflict Fades Away

Four-Color Theorem A­nal­y­sis — Rules To Limit the Problem

The Unusual Mo­nop­o­list

Reasonable Projection

Five Times What They Paid For It

Bypassable Security Certificates Are Useless

I’d Give My Right Arm To Go To Mars

Free Advice About Apple’s iOS App Store Guidelines

Inciting Violence

One Platform

Understanding IDC’s Tablet Market Share Graph

I Vote Socialist Be­cause...

That Person

Product Naming — Google Is the Other Microsoft

Antecessor Hypotheticum

Apple Paves the Way For Apple

Why — A Poem

App Anger — the Supersized-Mastodon-In-the-Room That Marco Arment Doesn’t See

Apple’s Graphic Failure

Why Microsoft Copies Apple (and Google)

Coders Code, Bosses Boss

Droidfood For Thought

Investment Is Not A Sure Thing

Exercise is Two Thirds of Everything

Dan “Real Enderle” Ly­ons

Fairness

Ignoring the iPod touch

Manual Intervention Should Never Make A Computer Faster

Predictions ’13

Paperless

Zeroth — Why the Century Number Is One More Than the Year Number

Longer Than It Seems

Partners: Believe In Ap­ple

Gun Control: Best Ar­gu­ments

John C. Dvorak — Translation To English

Destructive Youth

Wiens’s Whine

Free Will — The Grand Equivocation

What Windows-vs.-Mac Actually Proved

A Tale of Two Logos

Microsoft’s Three Paths

Amazon Won’t Be A Big Winner In the DOJ’s Price-Fixing Suit

Infinite Sets, Infinite Authority

Strategy Analytics and Long Term Ac­count­a­bil­i­ty

The Third Stage of Computing

Why 1 Isn’t Prime, 2 Is Prime, and 2 Is the Only Even Prime

Readability BS

Lie Detection and Psy­chos

Liking

Steps

Microsoft’s Dim Pros­pects

Humanity — Just Barely

Hanke-Henry Calendar Won’t Be Adopted

Collatz Conjecture A­nal­y­sis (But No Proof; Sorry)

Rock-Solid iOS App Stability

Microsoft’s Uncreative Character

Microsoft’s Alternate Reality Bubble

Microsoft’s Three Ruts

Society’s Fascination With Mass Murder

PlaysForSure and Wikipedia — Revisionism At Its Finest

Procrastination

Patent Reform?

How Many Licks

Microsoft’s Incredible Run

Voting Socialist

Darwin Saves

The Size of Things In the Universe

The Self-Fulfilling Prophecy That Wasn’t

Fun

Nobody Was In Love With Windows

Apples To Apples — How Anti-Apple Pundits Shoot Themselves In the Foot

No Holds Barred

Betting Against Hu­man­i­ty

Apple’s Premium Features Are Free

Why So Many Computer Guys Hate Apple

3D TV With No Glasses and No Parallax/Focus Issues

Waves With Particle-Like Properties

Gridlock Is Just Fine

Sex Is A Fantasy

Major Player

Why the iPad Wannabes Will Definitely Flop

Predators and Parasites

Prison Is For Lotto Losers

The False Dichotomy

Wait and See — Windows-vs-Mac Will Repeat Itself

Dishonesty For the Greater Good

Barr Part 2

Enough Information

Zune Is For Apple Haters

Good Open, Bad Open

Beach Bodies — Who’s Really Shallow?

Upgrade? Maybe Not

Eliminating the Im­pos­si­ble

Selfish Desires

Farewell, Pirate Cachet

The Two Risk-Takers

Number of Companies — the Idiocy That Never Dies

Holding On To the Solution

Apple Religion

Long-Term Planning

What You Have To Give Up

The End of Elitism

Good and Evil

Life

How Religion Distorts Science

Laziness and Creativity

Sideloading and the Supersized-Mastodon-In-the-Room That Snell Doesn’t See

Long-Term Self-De­lu­sion

App Store Success Won’t Translate To Books, Movies, and Shows

Silly iPad Spoilsports

I Disagree

Five Rational Coun­ter­ar­gu­ments

Majority Report

Simply Unjust

Zooman Science

Reaganomics — Like A Diet — Works

Free R&D?

Apple’s On the Right Track

Mountains of Evidence

What We Do

Hope Conquers All

Humans Are Special — Just Not That Special

Life = Survival of the Fittest

Excuse Me, We’re Going To Build On Your Property

No Trademark iWorries

Knowing

Twisted Excuses

The Fall of Google

Real Painters

The Meaning of Kicking Ass

How To Really Stop Casual Movie Disc Ripping

The Solitary Path of the High-Talent Pro­gram­mer

Fixing, Not Preaching

Why Blackmail Is Still Illegal

Designers Cannot Do Anything Imaginable

Wise Dr. Drew

Rats In A Too-Small Cage

Coming To Reason

Everything Isn’t Moving To the Web

Pragmatics, Not Rights

Grey Zone

Methodologically Dogmatic

The Purpose of Lan­guage

The Punishment Defines the Crime

Two Many Cooks

Pragmatism

One Last Splurge

Making Money

What Heaven and Hell Are Really About

America — The Last Suburb

Hoarding

What the Cloud Isn’t For

Diminishing Returns

What You’re Seeing

What My Life Needs To Be

Taking An Early Re­tire­ment

Office Buildings

A, B, C, D, Pointless Relativity

Stephen Meyer and Michael Medved — Where Is ID Going?

If You Didn’t Vote — Complain Away

iPhone Party-Poopers Redux

What Free Will Is Really About

Spectacularly Well

Pointless Wrappers

PTED — The P Is Silent

Out of Sync

Stupid Stickers

Security Through Nor­mal­cy

The Case For Corporate Bonuses

Movie Copyrights Are Forever

Permitted By Whom?

Quantum Cognition and Other Hogwash

The Problem With Message Theory

Bell’s Boring Inequality and the Insanity of the Gaps

Paying the Rent At the 6 Park Avenue A­part­ments

Primary + Reviewer — An Alternative IT Plan For Corporations

Yes Yes Yes

Feelings

Hey Hey Whine Whine

Microsoft About Microsoft Visual Microsoft Studio Microsoft

Hidden Purple Tiger

Forest Fair Mall and the Second Lamborghini

Intelligent Design — The Straight Dope

Maxwell’s Demon — Three Real-World Ex­am­ples

Zealots

Entitlement BS

Agenderle

Mutations

Einstein’s Error — The Confusion of Laws With Their Effects

The Museum Is the Art

Polly Sooth the Air Rage

The Truth

The Darkness

Morality = STDs?

Fulfilling the Moral Du­ty To Disdain

MustWinForSure

Choice

Real Design

The Two Rules of Great Programming

Cynicism

The End of the Nerds

Poverty — Humanity’s Damage Control

Berners-Lee’s Rating System = Google

The Secret Anti-MP3 Trick In “Independent Women” and “You Sang To Me”

ID and the Large Had­ron Collider Scare

Not A Bluff

The Fall of Microsoft

Life Sucks When You’re Not Winning

Aware

The Old-Fashioned Way

The Old People Who Pop Into Existence

Theodicy — A Big Stack of Papers

The Designed, Cause-and-Effect Brain

Mosaics

IC Counterarguments

The Capitalist’s Imaginary Line

Education Isn’t Eve­ry­thing

I Don’t Know

Funny iPhone Party-Poopers

Avoiding Conflict At All Costs

Behavior and Free Will, Unconfused

“Reduced To” Ab­sur­dum

Suzie and Bubba Redneck — the Carriers of Intelligence

Everything You Need To Know About Haldane’s Dilemma

Darwin + Hitler = Ba­lo­ney

Meta-ware

Designed For Combat

Speed Racer R Us

Bold — Uh-huh

Conscious of Con­scious­ness

Future Perfect

Where Real and Yahoo Went Wrong

The Purpose of Surface

Eradicating Religion Won’t Eradicate War

Documentation Overkill

A Tale of Two Movies

The Changing Face of Sam Adams

Dinesh D’Souza On ID

Why Quintic (and Higher) Polynomials Have No Algebraic Solution

Translation of Paul Graham’s Footnote To Plain English

What Happened To Moore’s Law?

Goldston On ID

The End of Martial Law

The Two Faces of Ev­o­lu­tion

A Fine Rec­om­men­da­tion

Free Will and Population Statistics

Dennett/D’Souza Debate — D’Souza

Dennett/D’Souza Debate — Dennett

The Non-Euclidean Ge­om­e­try That Wasn’t There

Defective Attitude Towards Suburbia

The Twin Deficit Phan­toms

Sleep Sync and Vertical Hold

More FUD In Your Eye

The Myth of Rub­ber­neck­ing

Keeping Intelligent Design Honest

Failure of the Amiga — Not Just Mis­man­age­ment

Maxwell’s Silver Hammer = Be My Honey Do?

End Unsecured Debt

The Digits of Pi Cannot Be Sequentially Generated By A Computer Program

Faster Is Better

Goals Can’t Be Avoided

Propped-Up Products

Ignoring ID Won’t Work

The Crabs and the Bucket

Communism As A Side Effect of the Transition To Capitalism

Google and Wikipedia, Revisited

National Geographic’s Obesity BS

Cavemen

Theodicy Is For Losers

Seattle Redux

Quitting

Living Well

A Memory of Gateway

Is Apple’s Font Rendering Really Non-Pixel-Aware?

Humans Are Complexity, Not Choice

A Subtle Shift

Moralism — The Emperor’s New Success

Code Is Our Friend

The Edge of Religion

The Dark Side of Pixel-Aware Font Rendering

The Futility of DVD En­cryp­tion

ID Isn’t About Size or Speed

Blood-Curdling Screams

ID Venn Diagram

Rich and Good-Looking? Why Libertarianism Goes Nowhere

FUV — Fear, Uncertainty, and Vista

Malware Isn’t About Total Control

Howard = Second Com­ing?

Doomsday? Or Just Another Sunday

The Real Function of Wikipedia In A Google World

Objective-C Philosophy

Clarity From Cisco

2007 Macworld Keynote Prediction

FUZ — Fear, Uncertainty, and Zune

No Fear — The Most Important Thing About Intelligent Design

How About A Rational Theodicy

Napster and the Subscription Model

Intelligent Design — Introduction

The One Feature I Want To See In Apple’s Safari.