|
The Craftsman #31 Turn Off This Force Field
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
Ship's time: 1330, 2/21/2002
As Alphonse grudgingly acknowledges yet again the value of unit tests, he delves into database theory with Jerry - and Avery, eventually, emerges from the woodshed.
The Software Development Reprint is entitled .
|
 |
 |
|
The Craftsman #30 The Woodshed
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
Ship's time: 1230, 2/21/2002
As Avery and Jean are sequestered for some serious attitude adjustment, our apprentice Alphonse proceeds with Jerry on the dosage tracker testing. Will they actually get something done before Avery and Jean emerge?
The Software Development Reprint is entitled .
|
 |
 |
|
The Craftsman #29 Move the Date
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
Ship's time: 1130, 2/21/2002
Is all this testing nonsense just make-work for morons? After working on the suit registration requirement for nearly four hours, the only production code the team's got to show for it is ...
The Software Development Reprint is entitled .
|
 |
 |
|
The Craftsman #28 An Encapsulation Break
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
Ship's time: 1100, 2/21/2002
In the high-G end of the gamma arm, Jasmine and Jerry lock horns on object-oriented philosophy. Alphonse and Avery look on and ask some pertinent questions.
The Software Development Reprint is entitled .
|
 |
 |
|
The Craftsman #27 Carole's way, or the HighWay
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
Ship's Time: 1000, 2/21/2002
Avery's obstinate resistance to acceptance tests creates a stumbling block for the DTracker team, as our intrepid apprentice Alphonse wisely decides to remain neutral.
The Software Development Reprint is entitled .
|
 |
 |
|
The Craftsman #26 A Tabled Requirement
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
Ship's Time: 0900, 2/21/2002
Taking the plunge into a safety-critical project, Alphonse and the team wrangle out an acceptance test - but competitive currents threaten to sink their progress.
The Software Development Reprint entitled Red Light, Green Light is
|
 |
 |
|
The Craftsman #25 Register Suit
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
Ships Time: 0800, 2/21/2002
Alphonse and Avery explore the reqiurements of the Dosage Tracking system with their customer. Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #24 Oh No!
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
Alphonse and Avery start working on a new project: The Dosimeter Tracker. Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #23 Raggedy.
Robert C. Martin
Software Development,
2001
|
 |
 |
 |
Alphonse and Avery get a lot of good work done while developing a rapport. Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #22 Bug Eye.
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
Alphonse meets Avery, a somewhat nervous and know-it-all apprentice. Click to see the Software Development reprint.
|
 |
 |
|
The Craftsman #21 Patchwork
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
After our apprentice stops fidgeting about being patronized, he learns a thing or two about putting two and two together -- and cleaning up after himself.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #20 Backslide
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
The thrill of independent effort soon pales when Jerry rains on Alphonse's parade. Painfully, our apprentice realizes the bitter truth -- and pushes the delete key.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #19 Teaching Tolerance
Robert C. Martin
Software Development,
2004
|
 |
 |
 |
As our apprentice grows accustomed to his new mentor's deceptively slow pace, he learns a lesson in appreciation of both her knowledge and her knitting.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #18 Slow and Steady
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
When his new mentor's pokey pace seems to make progress a thing of the past, Alphonse blows up and learns a lesson about the importance of taking your time.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #17 Call in the Guards
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
Expecting the worst after his run in with jasmine, Slphonse learns a new use for the if statement and and discovers that his new mentor's mundane facade belies a rigorous mind.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #16 Excess Politesse
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
An overdose of etiquette helps Alphonse, now chastened by
embarrassment, complete the code -- but the New Jasmine makes him awfully uncomfortable.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #15 Ess Are Pee
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
In which our enthusiastic apprentice cleans up his file at Jasmine's request, while conducting an imaginary dialogue that gets him in way over his head -- all by himself.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #14 Transaction Actions
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
Working with a new journeyman is a harrowing experience for Alphonse. Can he withstand Jasmine's gimlet eye-and live up to his new nickname?
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #13: Objects.
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
Alphonse surprises Jerry by finding a more elegant solution to shipping a file over a socket. In the process, he meets Jasmine, his new tutor.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #12: Three Ugly Lines
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
Jerry and Alphonse attempt to ship a file over a socket. They discover ugliness.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #11: What's main() got to do with it?
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
This article begins the SMCRemote project. Alphonse learns that main() is often the last function you want to write.
Click to see the Software Development refprint.
|
 |
 |
|
The Craftsman #10: Dangling Threads (Iterations Unbound)
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
Alphonse and Jerry learn the consequences of modifying containers in different threads.
Click to see the Software Development reprint.
|
 |
 |
|
The Craftsman #9: Dangerous Threads
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
Alphonse and Jerry discover the frustrating and bizzare world of concurrent threads.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #8: Socket Service 3 (Tests are a form of documentation)
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
Alphonse and Jerry work on the socket service project. Alphonse learns that unit tests are a form of design documentation.
click for the Software Development reprint.
|
 |
 |
|
The Craftsman #7: Mocket to me.
Robert C. Martin
Software Development,
2003
|
 |
 |
 |
Digging deeper into the SocketService framework, Jerry and Alphonse find that substituting tests into the real application code can lead to designs that meet the needs of real users-is this a job for the MockObject pattern?
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #6: Once is not Enough.
Robert C. Martin
Software Development,
2002
|
 |
 |
 |
The first time I ran the SocketServer test, it passed, but Jerry was not convinced. Sure enough, further tests failed. Was I losing it? How can a program behave like that?
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #5: Baby Steps
Robert C. Martin
Software Development,
2002
|
 |
 |
 |
It seemed like incremental absurdity, but Jerry's madness concealed a method: Sneaking up on a solution one test case at a time made me realize I was actually learning something.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #4: A Test of Patience.
Robert C. Martin
Software Development ,
2002
|
 |
 |
 |
The apprentice struggles with his mentor's quixotic guidance: Spend hours or days writing code, and then blithely throw it away? How pointless is that?
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #3: Clarity and Collaboration.
Robert C. Martin
Software Development,
2002
|
 |
 |
 |
Though I hate to admit it, when Mr. C's journeyman tore my maiden effort to shreds, he taught me some important lessons in simplicity and the necessity of teamwork.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #2: Crash Diet
Robert C. Martin
Software Development,
2002
|
 |
 |
 |
On day two of my apprenticeship, I learned how to cut my code down to sizeby dividing a gargantuan function into logical conceptsand began to understand the value of organization.
Click for the Software Development reprint.
|
 |
 |
|
The Craftsman #1 Opening Disaster.
Robert C. Martin
Software Development,
2002
|
 |
 |
 |
I was delighted to be accepted as Mr. Cs apprentice. But despite high hopes, my first attempt at coding for the master developer quickly hacked my hubris down to size. Would I make it?
Click for the Software Development reprint.
|
 |
 |