Skip navigation.
ACCU Overload Journal Bibliography (sorted on name)

ACCU Overload Journal (sorted on name)

There's also a reverse chronological version. For more information, see this webpage.

[Abrahams, 2003]
David Abrahams. Error and exception handling. Overload, 11(57), October 2003. (PDF)
[Antonsen, 2003]
Frank Antonsen. Stream-based parsing in C++. Overload, 11(56), August 2003. (PDF)
[Antonsen, 2004]
Frank Antonsen. Letters to the editor(s). Overload, 12(59), February 2004. (PDF)
[Armstrong, 1996]
Nigel Armstrong. Some pitfalls of class design: a case study. Overload, 4(13):14–16, April 1996. Software Development in C++. (PDF)
[Arnold, 1993]
Peter Arnold. Make...or break?. Overload, 1(1), April 1993.
[Arnold, 1995]
Peter Arnold. editor << letters;. Overload, 3(9):34–35, August 1995. (PDF)
[Arregui et al., 2012]
Hugo Arregui, Carlos Castro, and Daniel Gutson. Curiously recursive template problems with aspect oriented programming. Overload, 20(109):20–23, June 2012. (PDF)
[Asproni and Fedotov, 2004]
Giovanni Asproni and Alexander Fedotov. An experience report on implementing a custom agile methodology on a C++/Python project. Overload, 12(64), December 2004. (PDF)
[Asproni, 2006]
Giovanni Asproni. How to shoot yourself in the foot in an agile way. Overload, 14(71):16–17, February 2006. (PDF)
[Asproni, 2009]
Giovanni Asproni. ACCU 2009. Overload, 17(91), June 2009. The 2009 ACCU Conference took place in March. The conference chair, Giovanni Asproni, provides a report. (PDF)
[authors, 2006]
Various authors. Letters. Overload, 14(75), October 2006. (PDF)
[authors, 2007]
Various authors. Letters to the editor. Overload, 15(78), April 2007. (PDF)
[Bailey, 1994]
David Bailey. Run-time checking for C++. Overload, 2(4), February 1994.
[Baker-Munton, 1995]
Kristen Baker-Munton. editor << letters;. Overload, 3(9):33–34, August 1995. (PDF)
[Balaam, 2010]
Andy Balaam. Scalable graph coverage. Overload, 18(97), June 2010. Optimising data processing is often about compromise. Andy Balaam finds the right balance. (PDF)
[Balaam, 2012a]
Andy Balaam. Footprint on modify. Overload, 20(112):16–19, December 2012. Tracking history can be done in a variety of ways. Andy Balaam describes one technique with many advantages. (PDF)
[Balaam, 2012b]
Andy Balaam. Tail call optimisation in C++. Overload, 20(109):10–13, June 2012. Stack based languages can be very powerful, but often can’t deal with arbitrary recursion. Andy Balaam finds a way around this limitation. (PDF)
[Barber, 2012]
Pete Barber. Unit testing compilation failure. Overload, 20(108):23–27, April 2012. We usually test that our code does what we expect. Pete Barber tries to prove that his code fails to compile. (PDF)
[Barber, 2014]
Pete Barber. Capturing lvalue references in C++11 lambdas. Overload, 20(119):19–20, February 2014. How confusing does it get when references refer to references and references are captured by value? Pete Barber shows us that it all falls out in the C++ consistency wash. (PDF)
[Barrett-Powell, 2004]
Tony Barrett-Powell. Handling exceptions in finally. Overload, 12(62), August 2004. (PDF)
[Barta, 2002]
Vaclav Barta. Building Java applications. Overload, 10(49), June 2002. (PDF)
[Bashir, 2007]
Omar Bashir. Upgrading legacy software in data communications systems. Overload, 15(82), December 2007. Changing operational software is a risky business. Omar Bashir offers a case study in matching risk with reward. (PDF)
[Bashir, 2009]
Omar Bashir. Orderly termination of programs. Overload, 17(89), February 2009. Ensuring a clean shutdown is important. Omar Bashir presents some techniques. (PDF)
[Bashir, 2010]
Omar Bashir. Using design patterns to manage complexity. Overload, 18(96), April 2010. Simpler programs are more reliable. Omar Bashir sees how to make improvements. (PDF)
[Bashir, 2013]
Omar Bashir. Has the singleton not suffered enough. Overload, 20(117):15–21, October 2013. Singletons are much maligned. Omar Bashir considers why. (PDF)
[Bass and Unknown, 1998]
Phil Bass and Unknown. editor << letters;. Overload, 6(24):35–36, February 1998. (PDF)
[Bass, 1998]
Phil Bass. STL implementations: Personal experiences. Overload, 6(26):29–34, June 1998. Whiteboard. (PDF)
[Bass, 1999]
Phil Bass. The state pattern - a new implementation. Overload, 7(33), October 1999.
[Bass, 2000a]
Phil Bass. Standard C++. Overload, 8(35), February 2000.
[Bass, 2000b]
Phil Bass. Supporting threads in standard C++ (addendum). Overload, 8(38), August 2000.
[Bass, 2000c]
Phil Bass. Supporting threads in standard C++ (part 2). Overload, 8(36), April 2000.
[Bass, 2000d]
Phil Bass. Supporting threads in standard C++ (part 3). Overload, 8(37), June 2000.
[Bass, 2002a]
Phil Bass. C++ exceptions and linux dynamic libraries. Overload, 10(48), April 2002. (PDF)
[Bass, 2002b]
Phil Bass. Implementing the observer pattern in C++ - part 1. Overload, 10(52), December 2002. (PDF)
[Bass, 2002c]
Phil Bass. Template titbit - a different perspective. Overload, 10(48), April 2002. (PDF)
[Bass, 2003]
Phil Bass. Implementing the observer pattern, part 2. Overload, 11(53):10–13, February 2003. (PDF)
[Bass, 2004a]
Phil Bass. The curious case of the compile-time function. Overload, 12(62), August 2004. (PDF)
[Bass, 2004b]
Phil Bass. Evolution of the observer pattern. Overload, 12(64), December 2004. (PDF)
[Bass, 2005a]
Phil Bass. The curate's wobbly desk. Overload, 13(70), December 2005. (PDF)
[Bass, 2005b]
Phil Bass. Grain storage mis: A failure of communications (27 march 1998). Overload, 13(67), June 2005. (PDF)
[Bass, 2005c]
Phil Bass. The trial of the reckless coder. Overload, 13(67), June 2005. (PDF)
[Bass, 2006]
Phil Bass. Visiting alice. Overload, 14(72), April 2006. (PDF)
[Bass, 2010]
Phil Bass. The quartermaster’s store. Overload, 18(100):11–13, December 2010. Be careful what you wish for. Phil Bass tries to simulate a missing language feature. (PDF)
[Baus, 2006]
Christopher Baus. Pooled lists. Overload, 14(76), December 2006. Christopher Baus explains the advantages of using a pooled memory allocation strategy for high performance applications. (PDF)
[Belch et al., 2009]
Yaakov Belch, Sergey Ignatchenko, and Dmytro Ivanchykhin. Project-specific language dialects. Overload, 17(94):17–25, December 2009. Today’s languages force a one-size-fits-all approach on projects. Yaakov Belch, Sergey Ignatchenko and Dmytro Ivanchykhin suggest a more flexible solution. (PDF)
[Bellingham, 1995]
Alan Bellingham. editor << letters;. Overload, 3(8):41, June 1995. (PDF)
[Bellingham, 1997]
Alan Bellingham. Shared experience: a C++ pitfall. Overload, 5(20):27–31, June 1997. C++ Techniques. (PDF)
[Bellingham, 1998a]
Alan Bellingham. Self registering classes - taking polymorphism to the limit. Overload, 6(27), August 1998. (PDF)
[Bellingham, 1998b]
Alan Bellingham. Structured analysis: OOD’s older brother? Overload, 6(26):19–22, June 1998. Whiteboard. (PDF)
[Benfield and Strobel, 2014]
Lee Benfield and Mike Strobel. Anatomy of a Java decompiler. Overload, 20(119):11–15, February 2014. Java byte code can be reverted back into source code. Lee Benfield and Mike Strobel show how. (PDF)
[Blundel, 1998]
Richard Blundel. Dynamic function calling using operator overloading. Overload, 6(26):8–13, June 1998. Software Development in C++. (PDF)
[Blundell, 1997a]
Richard Blundell. An introduction to the UML. Overload, 5(22):8–12, October 1997. (PDF)
[Blundell, 1997b]
Richard Blundell. UML - objects and patterns. Overload, 5(23):5–9, December 1997. Software Development in C++. (PDF)
[Blundell, 1998a]
Richard Blundell. UML – parameterised classes (templates) and utilities. Overload, 6(25):13–17, April 1998. Software Development in C++. (PDF)
[Blundell, 1998b]
Richard Blundell. UML – state-transition diagrams. Overload, 6(24):3–8, February 1998. Software Development in C++. (PDF)
[Blundell, 1998c]
Richard Blundell. UML interactions & collaborations. Overload, 6(27), August 1998. (PDF)
[Blundell, 1999a]
Richard Blundell. A simple model for object persistence using the standard library. Overload, 7(32), June 1999.
[Blundell, 1999b]
Richard Blundell. Thoughts on functoids. Overload, 7(31), April 1999.
[Blundell, 1999c]
Richard Blundell. UML relationships and associations, aggregation and composition. Overload, 7(30), February 1999.
[Blundell, 2000]
Richard Blundell. Automatic object versioning for forward and backward file format compatibility. Overload, 8(35), February 2000.
[Blundell, 2002]
Richard Blundell. File format conversion using templates and type collections. Overload, 10(52), December 2002. (PDF)
[Booth, 1995]
Peter Booth. Thinking in C++ (Bruce Eckel) reviewed by Peter Booth. Overload, 3(10):29, October 1995. Review. (PDF)
[Bourguet, 2003a]
Jean-Marc Bourguet. Exported templates. Overload, 11(54), April 2003. (PDF)
[Bourguet, 2003b]
Jean-Marc Bourguet. Letters to the editor(s). Overload, 11(57), October 2003. (PDF)
[Brazier, 2007]
Tom Brazier. Managing technical debt. Overload, 15(77), February 2007. Software projects often cut corners in the rush to meet deadlines, resulting in bad code. Tom Brazier helps us to budget the cost of "doing it wrong". (PDF)
[Breymann, 1995a]
Uli Breymann. A deeper look at copy assignment. Overload, 3(11):28–34, December 1995. C++ Techniques. (PDF)
[Breymann, 1995b]
Uli Breymann. editor << letters;. Overload, 3(8):42, June 1995. (PDF)
[Breymann, 1996]
Uli Breymann. An implementation pattern using RTTI. Overload, 3(12):14–18, February 1996. C++ Techniques. (PDF)
[Brown, 2003]
Silas S. Brown. Indexing stl lists with maps. Overload, 11(53):18–19, February 2003. (PDF)
[Brown, 2008]
Silas S Brown. Letter to the editor. Overload, 16(83), February 2008. (PDF)
[Brown, 2012]
Silas Brown. Web annotation with modified-Yarowsky and other algorithms. Overload, 20(112):4–7, December 2012. Annotating text automatically requires word disambiguation. Silas Brown introduces the Yarowsky algorithm to help. (PDF)
[Bruntlett, 1999]
Ian Bruntlett. Beyond ACCU. Overload, 7(32), June 1999.
[Bruntlett, 2000a]
Ian Bruntlett. Intuitive multi-paradigm design:. Overload, 8(38), August 2000.
[Bruntlett, 2000b]
Ian Bruntlett. User defined types: Qualities, principles and archetypes. Overload, 8(39), October 2000.
[Bruntlett, 2010]
Ian Bruntlett. Socially responsible recruitment. Overload, 18(97), June 2010. Finding talented people is hard. Ian Bruntlett highlights an under-appreciated source. (PDF)
[Buontempo, 2009]
Frances Buontempo. Floating point fun and frolics. Overload, 17(91), June 2009. Representing numbers in computers is a non-trivial problem. Frances Buontempo finds using them is hard, too. (PDF)
[Buontempo, 2012a]
Frances Buontempo. Allow me to introduce myself. Overload, 20(110):2–3, August 2012. Using data mining techniques to write an editorial. (PDF)
[Buontempo, 2012b]
Frances Buontempo. Large objects and iterator blocks. Overload, 20(110):22–24, August 2012. Arrays can cause memory issues in .Net. Frances Buontempo shows how iterator blocks can help to relieve the pressure. (PDF)
[Buontempo, 2012c]
Frances Buontempo. Originally, Overload didn’t have an editorial. Overload, 20(112):2–3, December 2012. Frances Buontempo considers history, predictions about the future and how to shirk off writing an editorial. (PDF)
[Buontempo, 2012d]
Frances Buontempo. Too much information. Overload, 20(111):2–3, October 2012. Overload usually has an editorial. Frances Buontempo explains why she hasn’t had time to write one for this issue. (PDF)
[Buontempo, 2013a]
Frances Buontempo. Decisions, decisions. Overload, 20(117):2–3, October 2013. The last Overload editorial described a Fantasy Language. Now, how do you learn one? (PDF)
[Buontempo, 2013b]
Frances Buontempo. The good, the bad and the discordant. Overload, 20(113):2–3, February 2013. There are several signs of bad code. Frances Buontempo considers ugliness, stench and discord in a search for beauty. (PDF)
[Buontempo, 2013c]
Frances Buontempo. How to program your way out of a paper bag using genetic algorithms. Overload, 20(118):7–9, December 2013. It is often claimed people cannot program their way out of a paper bag. Frances Buontempo bucks the trend using genetic algorithms. (PDF)
[Buontempo, 2013d]
Frances Buontempo. Knitting needles and keyboards. Overload, 20(114):2–3, April 2013. Traditionally, both journals and developers have editors. Frances Buontempo considers the role of an editor, in another attempt to avoid writing an editorial. (PDF)
[Buontempo, 2013e]
Frances Buontempo. Learning fantasy languages. Overload, 20(116):2–3, August 2013. The last Overload editorial described a Fantasy Language. Now, how do you learn one? (PDF)
[Buontempo, 2013f]
Frances Buontempo. Not so much a program, more a way of life. Overload, 20(118):2–3, December 2013. In an attempt to continue and improve on the successful formula of previous editorial avoidance techniques, Frances Buontempo considers what a program really is. (PDF)
[Buontempo, 2014]
Frances Buontempo. Random (non)sense. Overload, 20(119):2–3, February 2014. It’s not pretty and it’s not clever. Frances Buontempo considers if the cut-up method can be used to generate editorials. (PDF)
[Cacciola, 2006]
Fernando Cacciola. Introducing CODEF/CML. Overload, 14(74), August 2006. This article introduces a C# serialization facility that proposes a novel separation between object models, representing the serialized data, and class descriptors, representing the binding to the receiving design space. (PDF)
[Charney, 1998]
Reginald B. Charney. Data attribute notation - part 2. Overload, 6(29), December 1998.
[Charney, 1999]
Reginald B. Charney. Data attribute notation - part 3. Overload, 7(30), February 1999.
[Charney, 2003a]
Reg Charney. C++ standards library report. Overload, 11(53):23–24, February 2003. (PDF)
[Charney, 2003b]
Reg Charney. C++ templates. Overload, 11(53):25–26, February 2003. (PDF)
[Cheshire, 2002]
Andrew Cheshire. Template metaprogramming: Shifting down a gear. Overload, 10(50), August 2002. (PDF)
[Clamage, 1997]
Steve Clamage. C++ committee draft. Overload, 5(19):15, April 1997. The Draft International C++ Standard. (PDF)
[Clare, 2008]
Bill Clare. Globals, singletons and parameters. Overload, 16(86), August 2008. One size rarely fits all. Bill Clare considers different approaches to parameterization. (PDF)
[Corfield et al., 1995]
Sean A. Corfield, Keith Derrick, George Wendle, Chris Simons, Dave Midgley, and Dr Brennig James. editor << letters;. Overload, 3(10):25–28, October 1995. (PDF)
[Corfield et al., 1996a]
Sean A. Corfield, Dave Midgley, Roger Lever, Chris Simons, Andrew King, Alan Griffiths, and Jay. editor << letters;. Overload, 3(12), February 1996. (PDF)
[Corfield et al., 1996b]
Sean A. Corfield, Allan Newton, Graham Jones, Phil Bass, and Steven Youngs. editor << letters;. Overload, 4(15):35–36, August 1996. (PDF)
[Corfield et al., 1996c]
Sean A. Corfield, Remi Sellem, Bryan Colyer, Phil Bass, Colin Harkness, and Steve Watson. editor << letters;. Overload, 4(14):18–19, June 1996. (PDF)
[Corfield et al., 1996d]
Sean A. Corfield, Peter Wippell, Dave Midgley, Roger Woollett, and The Harpist. editor << letters;. Overload, 4(13):30–31, April 1996. (PDF)
[Corfield, 1994a]
Sean A. Corfield. The casting vote. Overload, 2(5):18–21, September 1994.
[Corfield, 1994b]
Sean A. Corfield. The casting vote. Overload, 2(4), February 1994.
[Corfield, 1994c]
Sean A. Corfield. So you want to be a cOOmpiler writer?. Overload, 2(5):10–11, September 1994.
[Corfield, 1994d]
Sean A. Corfield. The virtual interview. Overload, 2(5):7, September 1994. John Max Skaller was interviewed by Sean A. Corfield.
[Corfield, 1995a]
Sean Corfield. The casting vote. Overload, 3(6), March 1995.
[Corfield, 1995b]
Sean A. Corfield. Books and journals. Overload, 3(7):42, April 1995. (PDF)
[Corfield, 1995c]
Sean A. Corfield. The casting vote. Overload, 3(11):18–19, December 1995. The Draft International C++ Standard. (PDF)
[Corfield, 1995d]
Sean A. Corfield. The casting vote. Overload, 3(9):18–21, August 1995. The Draft International C++ Standard. (PDF)
[Corfield, 1995e]
Sean A. Corfield. The casting vote. Overload, 3(7):18–22, April 1995. (PDF)
[Corfield, 1995f]
Sean A. Corfield. Design patterns reviewed by Sean A. Corfield. Overload, 3(9):38–39, August 1995. Books and Journals. (PDF)
[Corfield, 1995g]
Sean A. Corfield. Editorial. Overload, 3(11):3, December 1995. (PDF)
[Corfield, 1995h]
Sean A. Corfield. Editorial. Overload, 3(10):3–4, October 1995. (PDF)
[Corfield, 1995i]
Sean A. Corfield. Editorial. Overload, 3(9):3, August 1995. (PDF)
[Corfield, 1995j]
Sean A. Corfield. Editorial. Overload, 3(8):3, June 1995. (PDF)
[Corfield, 1995k]
Sean A. Corfield. Editorial. Overload, 3(7):3–4, April 1995. (PDF)
[Corfield, 1995l]
Sean A. Corfield. From chaos to classes (Daniel Duffy) reviewed by Sean A. Corfield. Overload, 3(10):29–31, October 1995. (PDF)
[Corfield, 1995m]
Sean A. Corfield. namespace – a short exposé. Overload, 3(8):18–19, June 1995. The Draft International C++ Standard. (PDF)
[Corfield, 1995n]
Sean A. Corfield. ++puzzle;. Overload, 3(8):43, June 1995. (PDF)
[Corfield, 1995o]
Sean A. Corfield. ++puzzle;. Overload, 3(7):41, April 1995. (PDF)
[Corfield, 1995p]
Sean A. Corfield. Questions & answers. Overload, 3(7):40–41, April 1995. (PDF)
[Corfield, 1995q]
Sean A. Corfield. Scientific and Engineering C++ reviewed by Sean A. Corfield. Overload, 3(11):42–43, December 1995. Books and Journals. (PDF)
[Corfield, 1995r]
Sean A. Corfield. So you want to be a cOOmpiler writer? – part II. Overload, 3(8):12–14, June 1995. (PDF)
[Corfield, 1995s]
Sean A. Corfield. So you want to be a cOOmpiler writer? – part III. Overload, 3(10):5–11, October 1995. Software Development in C++. (PDF)
[Corfield, 1995t]
Sean A. Corfield. Subsidising lunch? – a reply. Overload, 3(7):10–11, April 1995. (PDF)
[Corfield, 1995u]
Sean A. Corfield. What’s in a name? Overload, 3(10):13–16, October 1995. The Draft International C++ Standard. (PDF)
[Corfield, 1996a]
Sean A. Corfield. The casting vote. Overload, 4(15):19–20, August 1996. The Draft International C++ Standard. (PDF)
[Corfield, 1996b]
Sean A. Corfield. The casting vote. Overload, 4(13):16–18, April 1996. The Draft International C++ Standard. (PDF)
[Corfield, 1996c]
Sean A. Corfield. Editorial. Overload, 4(16):3, October 1996. (PDF)
[Corfield, 1996d]
Sean A. Corfield. Editorial. Overload, 4(15):3, August 1996. (PDF)
[Corfield, 1996e]
Sean A. Corfield. Editorial. Overload, 4(14):3, June 1996. (PDF)
[Corfield, 1996f]
Sean A. Corfield. Editorial. Overload, 4(13):3–6, April 1996. (PDF)
[Corfield, 1996g]
Sean A. Corfield. Editorial. Overload, 3(12):3, February 1996. (PDF)
[Corfield, 1996h]
Sean A. Corfield. Heapwalking problems. Overload, 3(12):22–23, February 1996. C++ Techniques. (PDF)
[Corfield, 1996i]
Sean A. Corfield. So you want to be a cOOmpiler writer? – part IV. Overload, 3(12):7–9, February 1996. Software Development in C++. (PDF)
[Corfield, 1996j]
Sean A. Corfield. So you want to be a cOOmpiler writer? – part V. Overload, 4(13):9–11, April 1996. Software Development in C++. (PDF)
[Corfield, 1996k]
Sean A. Corfield. So you want to be a cOOmpiler writer? – part VI. Overload, 4(15):15–19, August 1996. Software Development in C++. (PDF)
[Corfield, 1996l]
Sean A. Corfield. A UK perspective. Overload, 3(12):13–14, February 1996. The Draft International C++ Standard. (PDF)
[Corfield, 1996m]
Sean A. Corfield. Using STL with pointers. Overload, 4(13):24–27, April 1996. C++ Techniques. (PDF)
[Corfield, 1996n]
Sean A. Corfield. You can’t get there from here – a closer look at input iterators. Overload, 4(13):20–21, April 1996. C++ Techniques. (PDF)
[Corfield, 1997a]
Sean Corfield. Editorial. Overload, 5(17/18), January 1997.
[Corfield, 1997b]
Sean A. Corfield. The casting vote. Overload, 5(21):7–9, August 1997. The Draft International C++ Standard. (PDF)
[Corfield, 1997c]
Sean A. Corfield. The casting vote. Overload, 5(20):7–8, June 1997. The Draft International C++ Standard. (PDF)
[Corfield, 1997d]
Sean A. Corfield. The casting vote. Overload, 5(19):15–17, April 1997. The Draft International C++ Standard. (PDF)
[Corfield, 1997e]
Sean A. Corfield. The casting Vote I. Overload, 5(17/18), January 1997.
[Corfield, 1997f]
Sean A. Corfield. The casting Vote II. Overload, 5(17/18), January 1997.
[Corfield, 1998a]
Sean Corfield. Broadvision - part 2. Overload, 6(27), August 1998. (PDF)
[Corfield, 1998b]
Sean Corfield. Broadvision - part 3. Overload, 6(28), October 1998.
[Corfield, 1998c]
Sean Corfield. Broadvision: A lesson in application frameworks. Overload, 6(26):26–29, June 1998. Whiteboard. (PDF)
[Corfield, 1998d]
Sean A Corfield. Java 1.2 and JavaScript for C and C++ programmers. Overload, 6(26):34–36, June 1998. Reviews. (PDF)
[Corfield, 1998e]
Sean A Corfield. Sean's show. Overload, 6(26):2, June 1998. Editorial. (PDF)
[Corfield, 1999]
Sean Corfield. Broadvision, part 4. Overload, 7(32), June 1999.
[Cornish, 1999a]
Steve Cornish. Error logging and patterns. Overload, 7(34), December 1999.
[Cornish, 1999b]
Steve Cornish. Exceptions - the basics. Overload, 7(33), October 1999.
[Cornish, 1999c]
Steve Cornish. Exceptions - the details. Overload, 7(34), December 1999.
[Cornish, 1999d]
Steve Cornish. SAX - a simple API for XML. Overload, 7(34), December 1999.
[Cornish, 2000a]
Steve Cornish. Exceptions - guidance. Overload, 8(35), February 2000.
[Cornish, 2000b]
Steve Cornish. XML in applications II DOM - the document object model. Overload, 8(36), April 2000.
[Crickett, 2002]
John Crickett. Developing a C++ unit testing framework. Overload, 10(52), December 2002. (PDF)
[Dalgarno and Beuche, 2007]
Mark Dalgarno and Danilo Beuche. Software product line engineering with feature models. Overload, 15(78), April 2007. (PDF)
[Daudel, 2003a]
Jeff Daudel. Letter to the editor(s). Overload, 11(58), December 2003. (PDF)
[Daudel, 2003b]
Jeff Daudel. A unified singleton framework. Overload, 11(56), August 2003. (PDF)
[Davies, 1995a]
David Davies. Classes and associations. Overload, 3(11):5–15, December 1995. Software Development in C++. (PDF)
[Davies, 1995b]
David Davies. OOA – the Shlaer-Mellor approach. Overload, 3(8):5–12, June 1995. (PDF)
[Davies, 2006]
Rachel Davies. Pair programming explained. Overload, 14(73), June 2006. Rachel Davies explains how to implement pair programming and why it can be an effective practice for programmers. (PDF)
[Davies, 2007]
Rachel Davies. Live and learn with retrospectives. Overload, 15(79), June 2007. How can a team learn from experience? Rachel Davies presents a powerful technique for this. (PDF)
[Deigh, 2007]
Teedy Deigh. A practical form of oo layering. Overload, 15(78), April 2007. (PDF)
[Deigh, 2008]
Teedy Deigh. The way of the consultant. Overload, 16(84), April 2008. Effective communication is a challenging reponsibility of the communicator - Teedy Deigh offers some observations on how consultants can meet this challenge. (PDF)
[Deigh, 2009]
Teedy Deigh. WRESTLE: Aggressive and unprincipled agile development in the small. Overload, 17(90), April 2009. Agile development is all the rage. Teedy Deigh introduces a popular variant. (PDF)
[Deigh, 2010]
Teedy Deigh. A practical, reasoned and inciteful lemma for overworked and overlooked loners. Overload, 18(96), April 2010. Popular movements need a rallying cry. Teedy Deigh offers a timely one. (PDF)
[Deigh, 2011]
Teedy Deigh. Despair programming. Overload, 19(102):24, April 2011. Managing relationships is vital to a successful project. Teedy Deigh looks back on a lifetime’s experience. (PDF)
[Deigh, 2012]
Teedy Deigh. A position on running interference in languages. Overload, 20(108):36, April 2012. There is much debate about the merits of different approaches to type systems. Teedy Deigh considers how to make the most of them. (PDF)
[Deigh, 2013]
Teedy Deigh. Why dysfunctional programming matters. Overload, 20(114):27–28, April 2013. Function progamming is all the rage. Teedy Deigh considers how it offers many opportunities for the serious programmer. (PDF)
[Demin, 2012]
Alexander Demin. A practical introduction to Erlang. Overload, 20(107):24–28, February 2012. The future of massively parallel hardware will need good language support. Alexander Demin takes a look at an unexpected approach. (PDF)
[Derrick, 1996]
Keith Derrick. Real world patterns. Overload, 4(14):7–9, June 1996. Software Development in C++. (PDF)
[Derrick, 1997]
Keith Derrick. Caught in the pattern web. Overload, 5(17/18), January 1997.
[Dorrans, 1995]
Barry Dorrans. editor << letters;. Overload, 3(9):34, August 1995. (PDF)
[Durbin, 1996]
Dave Durbin. More on Java. Overload, 4(14):9–12, June 1996. Software Development in C++. (PDF)
[Easterbrook, 2006]
Mark Easterbrook. Comments considered evil. Overload, 14(73), June 2006. We are taught that adding comments to code is a good thing and adds value. In practice this value is seldom, if ever, realised. Mark Easterbrook makes the case for a better way. (PDF)
[Eisenecker, 1995a]
Ulrich W. Eisenecker. Multiple inheritance in C++ – part I. Overload, 3(7):28–32, April 1995. (PDF)
[Eisenecker, 1995b]
Ulrich W. Eisenecker. Multiple inheritance in C++ – part II. Overload, 3(9):24–27, August 1995. (PDF)
[Eisenecker, 1995c]
Ulrich W. Eisenecker. Multiple inheritance in C++ – part III. Overload, 3(10):5–8, October 1995. Software Development in C++. (PDF)
[Eisenecker, 1999]
Ulrich W. Eisenecker. Polymorphism in object-oriented languages. Overload, 7(32), June 1999.
[Eke, 1999]
Nigel Eke. My pet project - monopoly. Overload, 7(34), December 1999.
[Eke, 2000a]
Nigel Eke. My pet project monopoly 2. Overload, 8(35), February 2000.
[Eke, 2000b]
Nigel Eke. The pet project - monopoly (part 3). Overload, 8(36), April 2000.
[Eke, 2000c]
Nigel Eke. The pet project (part 4). Overload, 8(37), June 2000.
[Eke, 2007]
Nigel Eke. Programming - abstraction by design. Overload, 15(77), February 2007. Nigel Eke acts as a guide to aspect oriented programming using AspectJ as an example. (PDF)
[et al, 1996]
Francis Glassborow et al. The return type of member functions. Overload, 4(15):29–33, August 1996. C++ Techniques. (PDF)
[Fabijanic, 2008a]
Aleksandar Fabijanic. DynamicAny (part 2). Overload, 16(87), October 2008. Alex Fabijanic uncovers the internals of DynamicAny with some performance and size tests. (PDF)
[Fabijanic, 2008b]
Aleksandar Fabijanic. DynamicAny, part I. Overload, 16(86), August 2008. Alex Fabijanic presents a class hierarchy providing dynamic typing in standard C++. (PDF)
[Fabijanic, 2013a]
Alex Fabijanic. Dynamic C++, part 1. Overload, 20(115):21–27, June 2013. Static and dynamic languages have different trade-off. Alex Fabijanic attempts to get the best of both worlds. (PDF)
[Fabijanic, 2013b]
Alex Fabijanic. Dynamic C++ (part 2). Overload, 20(116):16–20, August 2013. Previously we saw how to use some simple dynamic features in C++. Alex Fabijanic and Richard Saunders explore more powerful dynamic tools. (PDF)
[Fagg, 1994a]
Adrian Fagg. Borland C++ v4.0. Overload, 2(5):14–15, September 1994.
[Fagg, 1994b]
Adrian Fagg. Microsoft Visual C++ V1.5 (16bit). Overload, 2(5):12–14, September 1994.
[Fagg, 1997]
Adrian Fagg. Using objects for background tasks (3). Overload, 5(17/18), January 1997. See also corrections in Overload 19, p.30.
[Fagg, 1998]
Adrian Fagg. A delphic experience. Overload, 6(29), December 1998.
[Fagg, 1999]
Adrian Fagg. An eventful story. Overload, 7(30), February 1999.
[Fahller, 2010]
Björn Fahller. Making string retrieval fast. Overload, 18(99):17–25, October 2010. Sometimes you really do have to optimize your code. Björn Fahller looks at a string lookup data structure. (PDF)
[Fahller, 2012]
Björn Fahller. What’s a good date? Overload, 20(109):6–9, June 2012. Implementing a data type seems simple at first glance. Björn Fahller investigates why you might choose a representation. (PDF)
[Field, 1998]
Paul Field. Controlling access to objects by using private interfaces. Overload, 6(28), October 1998.
[Firth, 1995]
Bob Firth. editor << letters;. Overload, 3(7):38–40, April 1995. (PDF)
[Fishburne, 2006]
William Fishburne. Comments considered good. Overload, 14(74), August 2006. In our last issue, we offered the case against comments; in this issue, William Fishbourne responds in defence. He argues that it is not the practice of commenting that it is evil, it is the thoughtless commenter. (PDF)
[Floyd, 2012a]
Paul Floyd. Valgrind part 1 – introduction. Overload, 20(108):14–15, April 2012. Good analysis tools can really help track down problems. Paul Floyd investigates the facilities from a suite of tools. (PDF)
[Floyd, 2012b]
Paul Floyd. Valgrind part 2 – basic memcheck. Overload, 20(109):24–29, June 2012. Learning how to use our tools well is a vital skill. Paul Floyd shows us how to check for memory problems. (PDF)
[Floyd, 2012c]
Paul Floyd. Valgrind part 3 advanced memcheck. Overload, 20(110):4–7, August 2012. Valgrind provides several mechanisms to locate memory problems in your code. Paul Floyd shows us how to use them. (PDF)
[Floyd, 2012d]
Paul Floyd. Valgrind part 4. Overload, 20(111):4–7, October 2012. Cachegrind and Callgrind When your application is slow, you need a profiler. Paul Floyd shows us how callgrind and cachegrind can help. (PDF)
[Floyd, 2012e]
Paul Floyd. Valgrind part 5 – Massif. Overload, 20(112):20–24, December 2012. Poor performance can be caused by memory usage. Paul Floyd introduces Valgrind’s heap memory profiling tool Massif. (PDF)
[Floyd, 2013]
Paul Floyd. Valgrind part 6 – Helgrind and DRD. Overload, 20(114):6–9, April 2013. Debugging multi-threaded code is hard. Paul Floyd uses Helgrind and DRD to find deadlocks and race conditions. (PDF)
[Foyle, 2010]
Walter Foyle. Bug elimination - defensive agile ruses. Overload, 18(96), April 2010. Everyone thinks they understand bug economics. Walter Foyle looks again. (PDF)
[Frogley, 2001]
Thaddaeus Frogley. An introduction to C++ traits. Overload, 9(43), June 2001.
[Frogley, 2004]
Thaddaeus Frogley. More is less. Overload, 12(59), February 2004. (PDF)
[Frogley, 2005]
Thaddaeus Frogley. C abuse. Overload, 13(65), February 2005. (PDF)
[Frost, 1993]
Stuart Frost. Rumbaugh's OMT - the method behind C++ designer. Overload, 1(1), April 1993.
[Gibson, 2006]
Chris Gibson. How do those funky placeholders work?. Overload, 14(73), June 2006. The current C++ standard function binders are notoriously difficult to use. Chris Gibson exposes the secret the Boost alternative, which is so much better it seems like magic. (PDF)
[Gilb, 2005a]
Tom Gilb. How to quantify quality: Finding scales of measure. Overload, 13(70), December 2005. (PDF)
[Gilb, 2005b]
Tom Gilb. Software project management: Adding stakeholder metrics to agile projects. Overload, 13(68), August 2005. Agile methods need to include stakeholder metrics in order to ensure that projects focus better on the critical requirements, and that projects are better able to measure their achievements, and to adapt to feedback. This paper presents a short, simple defined process for evolutionary project management (Evo), and discusses its key features. (PDF)
[Gilb, 2008]
Tom Gilb. Quality manifesto. Overload, 16(85), June 2008. Software quality is a systems engineering job. Tom Gilb explains the importance of knowing where we're going. (PDF)
[Gilson, 2007]
Matthieu Gilson. The policy bridge design pattern. Overload, 15(79), June 2007. Matthieu Gilson offers some thoughts on using a policy based mechanism to build efficient classes from loosely coupled components. (PDF)
[Glassborow and Lever, 1997]
Francis Glassborow and Roger Lever. editor << letters;. Overload, 5(19):30–31, April 1997. (PDF)
[Glassborow et al., 1996]
Francis Glassborow, Kevlin A. P. Henney, Colin Hersom, Graham Jones, Phil Bass, Steve Mertz, and Walter Brown. editor << letters;. Overload, 4(16):19–24, October 1996. (PDF)
[Glassborow, 1993a]
Francis Glassborow. Minimising stack use and other uses of new. Overload, 1(3), August 1993.
[Glassborow, 1993b]
Francis Glassborow. Some thoughts on the use of new. Overload, 1(2), June 1993.
[Glassborow, 1993c]
Francis Glassborow. Some thoughts on writing classes. Overload, 1(1), April 1993.
[Glassborow, 1993d]
Francis Glassborow. Uses of classes with only private and protected constructors. Overload, 1(3), August 1993.
[Glassborow, 1993e]
Francis Glassborow. Welcome to ECUG. Overload, 1(3), August 1993.
[Glassborow, 1994a]
Francis Glassborow. new & delete. Overload, 2(4), February 1994.
[Glassborow, 1994b]
Francis Glassborow. Operators for arithmetic classes. Overload, 2(5):1–4, September 1994.
[Glassborow, 1995a]
Francis Glassborow. A better C? Overload, 3(9):3–5, August 1995. (PDF)
[Glassborow, 1995b]
Francis Glassborow. Blindspots. Overload, 3(6), March 1995.
[Glassborow, 1995c]
Francis Glassborow. C++ compilers – mainly for OS/2. Overload, 3(7):4–7, April 1995. (PDF)
[Glassborow, 1995d]
Francis Glassborow. C++ compilers for MSDOS / MSWindows. Overload, 3(6), March 1995.
[Glassborow, 1995e]
Francis Glassborow. Circle & ellipse – creating polymorphic objects. Overload, 3(8):27–29, June 1995. (PDF)
[Glassborow, 1995f]
Francis Glassborow. Date with a design. Overload, 3(11):40–41, December 1995. ++puzzle;. (PDF)
[Glassborow, 1995g]
Francis Glassborow. Diary of an observer. Overload, 3(9):15–17, August 1995. The Draft International C++ Standard. (PDF)
[Glassborow, 1995h]
Francis Glassborow. Friends - who needs them?. Overload, 3(6), March 1995.
[Glassborow, 1995i]
Francis Glassborow. Pausing for thought. Overload, 3(10):24–25, October 1995. C++ Techniques. (PDF)
[Glassborow, 1995j]
Francis Glassborow. Related addendum. Overload, 3(7):28, April 1995. (PDF)
[Glassborow, 1995k]
Francis Glassborow. Some thoughts on linkage. Overload, 3(11):19–21, December 1995. The Draft International C++ Standard. (PDF)
[Glassborow, 1996a]
Francis Glassborow. Compiler updates. Overload, 3(12):9–11, February 1996. Software Development in C++. (PDF)
[Glassborow, 1996b]
Francis Glassborow. Concerning values, left, right and converted. Overload, 4(14):3–6, June 1996. Software Development in C++. (PDF)
[Glassborow, 1996c]
Francis Glassborow. Making a date. Overload, 3(12):34–36, February 1996. ++puzzle;. (PDF)
[Glassborow, 1996d]
Francis Glassborow. Making string literals constant – a cautionary tale. Overload, 4(15):20–23, August 1996. The Draft International C++ Standard. (PDF)
[Glassborow, 1996e]
Francis Glassborow. Mixing Java & C++ ruminations. Overload, 4(16):13–15, October 1996. Software Development in C++. (PDF)
[Glassborow, 1996f]
Francis Glassborow. Return from a member function. Overload, 4(14):16, June 1996. C++ Techniques. (PDF)
[Glassborow, 1996g]
Francis Glassborow. Those problems revisited. Overload, 4(13):6–9, April 1996. Software Development in C++. (PDF)
[Glassborow, 1996h]
Francis Glassborow. We have a problem. Overload, 3(12):3–7, February 1996. Guest editorial by Francis Glassborow. (PDF)
[Glassborow, 1996i]
Francis Glassborow. Why is the standard C++ library value based? Overload, 4(16):18–19, October 1996. C++ Techniques. (PDF)
[Glassborow, 1997a]
Francis Glassborow. Candidates for inline. Overload, 5(23):9–12, December 1997. Software Development in C++. (PDF)
[Glassborow, 1997b]
Francis Glassborow. The casting vote. Overload, 5(23):12–15, December 1997. The Draft International C++ Standard. (PDF)
[Glassborow, 1997c]
Francis Glassborow. Further thoughts on inheritance for reuse. Overload, 5(20):31–35, June 1997. C++ Techniques. (PDF)
[Glassborow, 1997d]
Francis Glassborow. Getting the best. Overload, 5(21):9–13, August 1997. The Draft International C++ Standard. (PDF)
[Glassborow, 1997e]
Francis Glassborow. inline delegation. Overload, 5(21):21, August 1997. Whiteboard. (PDF)
[Glassborow, 1997f]
Francis Glassborow. The problem of self-assignment. Overload, 5(19):8–9, April 1997. Software Development in C++. (PDF)
[Glassborow, 1997g]
Francis Glassborow. The story of auto_ptr, a cautionary tale. Overload, 5(23):15–19, December 1997. The Draft International C++ Standard. (PDF)
[Glassborow, 1997h]
Francis Glassborow. The uses and abuses of inheritence. Overload, 5(17/18), January 1997.
[Glassborow, 1997i]
Francis Glassborow. Using algorithms-sorting. Overload, 5(22):24–26, October 1997. (PDF)
[Glassborow, 1998a]
Francis Glassborow. (Almost) no casting vote, standard’s report. Overload, 6(25), April 1998. The Draft International C++ Standard. (PDF)
[Glassborow, 1998b]
Francis Glassborow. Exploring patterns 3 - the adapter. Overload, 6(28), October 1998.
[Glassborow, 1998c]
Francis Glassborow. Exploring patterns: Part 1. Overload, 6(26):13–18, June 1998. Patterns in C++. (PDF)
[Glassborow, 1998d]
Francis Glassborow. Exploring patterns part 2. Overload, 6(27), August 1998. (PDF)
[Glassborow, 1998e]
Francis Glassborow. A message from the ACCU chair. Overload, 6(29), December 1998.
[Glassborow, 1998f]
Francis Glassborow. operator == (). Overload, 6(29), December 1998.
[Glassborow, 1998g]
Francis Glassborow. STL algorithms: Finding. Overload, 6(24):18–22, February 1998. C++ Techniques. (PDF)
[Glassborow, 1999a]
Francis Glassborow. Builder & factory method patterns. Overload, 7(32), June 1999.
[Glassborow, 1999b]
Francis Glassborow. Patterns - the abstract factory. Overload, 7(30), February 1999.
[Glassborow, 1999c]
Francis Glassborow. Religious issues. Overload, 7(33), October 1999.
[Glassborow, 1999d]
Francis Glassborow. Ruminations on studying design patterns. Overload, 7(32), June 1999.
[Glassborow, 2000]
Francis Glassborow. A response to the C++ SIG organiser. Overload, 8(36), April 2000.
[Glassborow, 2001]
Francis Glassborow. C++ idioms: First thoughts. Overload, 9(42), April 2001.
[Goldthwaite, 1998]
Lois Goldthwaite. Static vs member functions. Overload, 6(29), December 1998.
[Goldthwaite, 2000]
Lois Goldthwaite. Programming with interfaces in C++. Overload, 8(40), December 2000.
[Goldthwaite, 2003]
Lois Goldthwaite. C++rossword. Overload, 11(53):22, February 2003. (PDF)
[Goldthwaite, 2005]
Lois Goldthwaite. C++ properties - a library solution. Overload, 13(65), February 2005. (PDF)
[Golodetz, 2007]
Stuart Golodetz. Functional programming using C++ templates (part 1). Overload, 15(81), October 2007. Template metaprogramming can initially seem baffling, but exploring its link to functional programming helps shed some light on things. (PDF)
[Golodetz, 2008a]
Stuart Golodetz. Divide and conquer: Partition trees and their uses. Overload, 16(86), August 2008. The world is a complex place. Stuart Golodetz introduces a powerful technique to describe it. (PDF)
[Golodetz, 2008b]
Stuart Golodetz. The legion's revolting!. Overload, 16(88), December 2008. 3D meshes can be too large to deal with efficiently. Stuart Golodetz applies some ancient discipline. (PDF)
[Golodetz, 2008c]
Stuart Golodetz. RSA made simple. Overload, 16(85), June 2008. RSA is a common public key cryptography algorithm. Stuart Golodetz explains the mathematics behind it and shows us how to use it in Java. (PDF)
[Golodetz, 2008d]
Stuart Golodetz. Seeing things differently. Overload, 16(87), October 2008. The Multiple Material Marching Cubes (M3C) algorithm builds 3D models from 2D slices. Stuart Golodetz introduces it and provides a C++ implementation. (PDF)
[Golodetz, 2008e]
Stuart Golodetz. Watersheds and waterfalls. Overload, 16(83), February 2008. An introductory look at segmenting images into regions using a landscape analogy. (PDF)
[Golodetz, 2008f]
Stuart Golodetz. Watersheds and waterfalls (part 2). Overload, 16(84), April 2008. Stuart Golodetz continues his survey of algorithms for segmenting images into regions. (PDF)
[Golodetz, 2009a]
Stuart Golodetz. I think i'll parse. Overload, 17(92), August 2009. A parser is a fundamental tool in software development. Stuart Golodetz looks at how you might tackle writing one. (PDF)
[Golodetz, 2009b]
Stuart Golodetz. If you can't see me, I can't see you. Overload, 17(90), April 2009. Knowing where the doors are is only the start. Stuart Golodetz works out what he can see through them. (PDF)
[Golodetz, 2009c]
Stuart Golodetz. Through the looking glass. Overload, 17(89), February 2009. What's happening in the next room? Stuart Golodetz has to find the door first! (PDF)
[Golodetz, 2010]
Stuart Golodetz. Simplifying the C++/Angelscript binding process. Overload, 18(95), February 2010. Many systems provide a scripting language. Stuart Golodetz shows how to make it easier. (PDF)
[Golodetz, 2013a]
Stuart Golodetz. Automatic navigation mesh generation in configuration space. Overload, 20(117):22–27, October 2013. Walkable 3D environments can be automatically navigated. Stuart Golodetz demonstrates how navigation meshes achieve this. (PDF)
[Golodetz, 2013b]
Stuart Golodetz. Object-environment collision detection using onion bsps. Overload, 20(118):10–15, December 2013. Previously we considered 3D navigation. Stuart Golodetz demonstrates how to detect collisions using onion binary space partitioning. (PDF)
[Goodliffe, 2000a]
Pete Goodliffe. An application of pointers to members. Overload, 8(36), April 2000.
[Goodliffe, 2000b]
Pete Goodliffe. Experiences of implementing the observer design pattern (part 1). Overload, 8(37), June 2000.
[Goodliffe, 2000c]
Pete Goodliffe. Experiences of implementing the observer design pattern (part 2). Overload, 8(38), August 2000.
[Goodliffe, 2000d]
Pete Goodliffe. A framework for object serialization in C++. Overload, 8(37), June 2000.
[Goodliffe, 2001a]
Pete Goodliffe. Experiences of implementing the observer design pattern (part 3). Overload, 9(41), February 2001.
[Goodliffe, 2001b]
Pete Goodliffe. Techniques for debugging in C++. Overload, 9(46), December 2001. (PDF)
[Goodliffe, 2002a]
Pete Goodliffe. STL-style circular buffers by example. Overload, 10(50), August 2002. (PDF)
[Goodliffe, 2002b]
Pete Goodliffe. STL-style circular buffers by example, part two. Overload, 10(51), October 2002. (PDF)
[Goodliffe, 2003]
Pete Goodliffe. Letters to the editor(s). Overload, 11(57), October 2003. (PDF)
[Goodliffe, 2005]
Pete Goodliffe. A technique for register access in C++. Overload, 13(68), August 2005. This article discusses a C++ scheme for accessing hardware registers in an optimal way. (PDF)
[Goodliffe, 2009]
Pete Goodliffe. Creating a framework for the iPhone. Overload, 17(94):7–10, December 2009. Apple’s iPhone SDK doesn’t allow you to create a Framework. Pete Goodliffe explains how to build one manually. (PDF)
[Gough, 2003]
Raoul Gough. Choosing template parameters. Overload, 11(58), December 2003. (PDF)
[Grenyer and Higgins, 2004]
Paul Grenyer and Jez Higgins. ACCU mentored developers XML project. Overload, 12(62), August 2004. (PDF)
[Grenyer, 2004]
Paul Grenyer. All heap no leaks. Overload, 12(60), April 2004. (PDF)
[Grenyer, 2005a]
Paul Grenyer. Digging a ditch. Overload, 13(66), April 2005. (PDF)
[Grenyer, 2005b]
Paul Grenyer. Multiple streams going nowhere. Overload, 13(65), February 2005. Source: C++ output streams ostream. (PDF)
[Grenyer, 2007a]
Paul Grenyer. Continuous integration with cruisecontrol.net. Overload, 15(79), June 2007. Is CC any good? How could it be better? Did it make a real difference where it was installed? Should we all give it a go? (PDF)
[Grenyer, 2007b]
Paul Grenyer. Letter to the editor. Overload, 15(80), August 2007. (PDF)
[Grenyer, 2008a]
Paul Grenyer. Model view controller with Java Swing. Overload, 16(88), December 2008. It's recommended to keep user interface and data model separate. Paul Grenyer looks a common solution. (PDF)
[Grenyer, 2008b]
Paul Grenyer. Testing visiting files and directories in C#. Overload, 16(83), February 2008. Testing code that accesses the file system is not straightforward. Paul Grenyer looks at what is involved. (PDF)
[Grenyer, 2009]
Paul Grenyer. Boiler plating database resource cleanup (part 2). Overload, 17(91), June 2009. Timely disposal of resources is important. Paul Grenyer applies this to database access in Java. (PDF)
[Grenyer, 2011a]
Paul Grenyer. An introduction to test driven development. Overload, 19(104):13–20, August 2011. TDD is too often thought to be all about Unit Tests. Paul Grenyer works through an example to show the bigger picture. (PDF)
[Grenyer, 2011b]
Paul Grenyer. RAII is not garbage. Overload, 19(106):14–15, December 2011. Many think that Garbage Collection frees the programmer from cleanup tasks. Paul Grenyer compares and contrasts it with a classic C++ idiom. (PDF)
[Griffiths and Allan, 2009]
Alan Griffiths and Marc Allan. Software development in the 21st century. Overload, 17(90), April 2009. What's the future of software development? Alan Griffiths and Marc Allan have a timely look at recent experiences. (PDF)
[Griffiths and Newton, 2000]
Alan Griffiths and Allan Newton. Interpreting "supporting the 'cheshire cat' idiom". Overload, 8(38), August 2000.
[Griffiths and Radford, 2005]
Alan Griffiths and Mark Radford. Separating interface and implementation in C++. Overload, 13(66), April 2005. (PDF)
[Griffiths, 1995a]
Alan Griffiths. No such thing as a free lunch. Overload, 3(7):3–10, April 1995. (PDF)
[Griffiths, 1995b]
Alan Griffiths. When is an “is a” not an “is a”? Overload, 3(10):11–13, October 1995. Software Development in C++. (PDF)
[Griffiths, 1996]
Alan Griffiths. Notes on Microsoft Visual C++ V4.0. Overload, 3(12):11–13, February 1996. Software Development in C++. (PDF)
[Griffiths, 1997a]
Alan Griffiths. Editorial. Overload, 5(19):3, April 1997. (PDF)
[Griffiths, 1997b]
Alan Griffiths. Premature optimisation. Overload, 5(22):21–23, October 1997. (PDF)
[Griffiths, 1997c]
Alan Griffiths. They pursued it with forks and hope. Overload, 5(21):32–34, August 1997. News, Views, & Reviews. (PDF)
[Griffiths, 1998]
Alan Griffiths. Almost a pattern. Overload, 6(27), August 1998. (PDF)
[Griffiths, 1999a]
Alan Griffiths. Fitting in with multiple frameworks in C++ and Java. Overload, 7(31), April 1999.
[Griffiths, 1999b]
Alan Griffiths. Goodbye Overload. Overload, 7(31), April 1999.
[Griffiths, 1999c]
Alan Griffiths. The EPOC C++ API. Overload, 7(32), June 1999.
[Griffiths, 1999d]
Alan Griffiths. Uncounted pointers in C++. Overload, 7(34), December 1999.
[Griffiths, 2000a]
Alan Griffiths. editorial. Overload, 8(36), April 2000.
[Griffiths, 2000b]
Alan Griffiths. Here be dragons. Overload, 8(40), December 2000.
[Griffiths, 2001a]
Alan Griffiths. C++ standards - the "swap" problem. Overload, 9(41), February 2001.
[Griffiths, 2001b]
Alan Griffiths. Compile time indirection - an unusual template technique. Overload, 9(42), April 2001.
[Griffiths, 2001c]
Alan Griffiths. Using version control. Overload, 9(44), August 2001. (PDF)
[Griffiths, 2002a]
Alan Griffiths. Exceptional Java. Overload, 10(48), April 2002. (PDF)
[Griffiths, 2002b]
Alan Griffiths. Execute around method and proxy goulash. Overload, 10(50), August 2002. (PDF)
[Griffiths, 2002c]
Alan Griffiths. More exceptional Java. Overload, 10(49), June 2002. (PDF)
[Griffiths, 2002d]
Alan Griffiths. Mutate? or create?. Overload, 10(51), October 2002. (PDF)
[Griffiths, 2003a]
Alan Griffiths. Chaos theory. Overload, 11(57), October 2003. (PDF)
[Griffiths, 2003b]
Alan Griffiths. Editorial. Overload, 11(58), December 2003. (PDF)
[Griffiths, 2003c]
Alan Griffiths. Editorial. Overload, 11(57), October 2003. (PDF)
[Griffiths, 2003d]
Alan Griffiths. Editorial. Overload, 11(56), August 2003. (PDF)
[Griffiths, 2003e]
Alan Griffiths. Editorial. Overload, 11(55), June 2003. (PDF)
[Griffiths, 2003f]
Alan Griffiths. Three phantastic tales. Overload, 11(56), August 2003. (PDF)
[Griffiths, 2004a]
Alan Griffiths. Achieving FitNesse in C++. Overload, 12(60), April 2004. (PDF)
[Griffiths, 2004b]
Alan Griffiths. Editorial: A glimpse behind the scenes. Overload, 12(64), December 2004. (PDF)
[Griffiths, 2004c]
Alan Griffiths. Editorial: New things under the sun. Overload, 12(61), June 2004. (PDF)
[Griffiths, 2004d]
Alan Griffiths. Editorial: The value of what you know. Overload, 12(62), August 2004. (PDF)
[Griffiths, 2004e]
Alan Griffiths. Heretical Java #1. Overload, 12(59), February 2004. (PDF)
[Griffiths, 2004f]
Alan Griffiths. When is a "Pattern" not a "Pattern"?. Overload, 12(61), June 2004. (PDF)
[Griffiths, 2005a]
Alan Griffiths. Editorial: Can we change for the better?. Overload, 13(69), October 2005. (PDF)
[Griffiths, 2005b]
Alan Griffiths. Editorial: Does all this help make better software?. Overload, 13(67), June 2005. (PDF)
[Griffiths, 2005c]
Alan Griffiths. Editorial: Size does matter. Overload, 13(68), August 2005. The way that one goes about developing and delivering a software project depends critically on the scale of the project. Discuss. (PDF)
[Griffiths, 2005d]
Alan Griffiths. Editorial: The "Safe C++ Standard Library". Overload, 13(70), December 2005. (PDF)
[Griffiths, 2005e]
Alan Griffiths. Editorial: "They" have their reasons. Overload, 13(65), February 2005. (PDF)
[Griffiths, 2005f]
Alan Griffiths. "here be dragons". Overload, 13(70), December 2005. (PDF)
[Griffiths, 2005g]
Alan Griffiths. Letters: Encapsulate context. Overload, 13(65), February 2005. (PDF)
[Griffiths, 2005h]
Alan Griffiths. "The C++ Community" - are we divided by a common language?. Overload, 13(67), June 2005. (PDF)
[Griffiths, 2006a]
Alan Griffiths. C++ best practice – designing header files. Overload, 14(72), April 2006. (PDF)
[Griffiths, 2006b]
Alan Griffiths. Editorial. Overload, 14(73), June 2006. (PDF)
[Griffiths, 2006c]
Alan Griffiths. Editorial: Doing what you can. Overload, 14(72), April 2006. (PDF)
[Griffiths, 2006d]
Alan Griffiths. Editorial: Keeping up standards. Overload, 14(71):4–6, February 2006. (PDF)
[Griffiths, 2006e]
Alan Griffiths. How overload comes to you. Overload, 14(76), December 2006. You look forward to Overload arriving in the mail every couple of months. This time it came very close to not arriving at all. (PDF)
[Griffiths, 2006f]
Alan Griffiths. Life in the fast lane. Overload, 14(75), October 2006. The ISO Fast-Track is paved with good intentions, but does it lead where we want to be? (PDF)
[Griffiths, 2006g]
Alan Griffiths. Take a step forward. Overload, 14(74), August 2006. Editorial. (PDF)
[Griffiths, 2006h]
Alan Griffiths. To grin again. Overload, 14(72), April 2006. (PDF)
[Griffiths, 2007a]
Alan Griffiths. Consensus. Overload, 15(80), August 2007. It should be obvious that the process of agreeing effective standards must be dependant on attaining consensus. (PDF)
[Griffiths, 2007b]
Alan Griffiths. The essence of success. Overload, 15(82), December 2007. (PDF)
[Griffiths, 2007c]
Alan Griffiths. New tricks for an old dog. Overload, 15(78), April 2007. (PDF)
[Griffiths, 2007d]
Alan Griffiths. The power of inertia. Overload, 15(77), February 2007. (PDF)
[Griffiths, 2007e]
Alan Griffiths. Rip it up and start again. Overload, 15(79), June 2007. (PDF)
[Griffiths, 2008]
Alan Griffiths. After four years. Overload, 16(84), April 2008. After four years as editor of Overload it is time for a change. (PDF)
[Griffiths, 2010]
Alan Griffiths. Renovating a legacy C++ project. Overload, 18(98):12–15, August 2010. Over time projects tend to become hard to maintain. Alan Griffiths describes how one was improved. (PDF)
[Griffiths, 2011]
Alan Griffiths. Moving with the times. Overload, 19(106):4–5, December 2011. The ACCU is primarily a way for programmers to communicate. Alan Griffiths looks at its past, and speculates on its future. (PDF)
[Guest, 2004a]
Thomas Guest. A mini-project to decode a mini-language - part one. Overload, 12(63), October 2004. (PDF)
[Guest, 2004b]
Thomas Guest. Mini-project to decode a mini-language - part two. Overload, 12(64), December 2004. (PDF)
[Guest, 2005]
Thomas Guest. Metaprogramming is your friend. Overload, 13(66), April 2005. (PDF)
[Guest, 2006a]
Thomas Guest. The case against TODO. Overload, 14(73), June 2006. TODO - a neat way to label work in progress or an easy way to disguise the flaws in a codebase? (PDF)
[Guest, 2006b]
Thomas Guest. From CVS to subversion. Overload, 14(75), October 2006. Thomas Guest reflects on migrating his organisation's version control system from CVS to Subversion. (PDF)
[Guest, 2006c]
Thomas Guest. Soft documentation. Overload, 14(71):7–12, February 2006. (PDF)
[Guest, 2007]
Thomas Guest. He sells shell scripts to intersect sets. Overload, 15(80), August 2007. Graphical User Interfaces are in great demand but for some tasks there are better tools. Thomas Guest demonstrates the capabilities of command shells. (PDF)
[Guest, 2009]
Tom Guest. Code rot. Overload, 17(92), August 2009. Maintaining code is vital to keep it working. Tom Guest explores what happens when you neglect it. (PDF)
[Habdank-Wojewódzki and Rybarski, 2006]
Seweryn Habdank-Wojewódzki and Janusz Rybarski. The kohonen neural network library. Overload, 14(74), August 2006. Seweryn Habdank-Wojewódzki and Janusz Rybarski present a C++ library for users of Kohonen Neural Networks. (PDF)
[Habdank-Wojewódzki, 2007]
Seweryn Habdank-Wojewódzki. C++ trivial logger. Overload, 15(77), February 2007. When a fully functional logging subsystem isn't the answer what does one do? Seweryn Habdank-Wojewódzki rolls his own. (PDF)
[Hagan, 1998]
Ken Hagan. Exception discussion. Overload, 6(29), December 1998.
[Hagan, 2003]
Ken Hagan. Statically checking exception specifications. Overload, 11(57), October 2003. (PDF)
[Hall, 1997a]
Ray Hall. The C&C++ European Developers Forum. Overload, 5(21):30–32, August 1997. News, Views, & Reviews. (PDF)
[Hall, 1997b]
Ray Hall. Whence objects? Overload, 5(20):5–7, June 1997. Software Development in C++. (PDF)
[Hall, 1999]
Ray Hall. editor << letters;. Overload, 7(30), February 1999.
[Hammond, 2005a]
Peter Hammond. Can C++ learn from generics in Ada?. Overload, 13(67), June 2005. (PDF)
[Hammond, 2005b]
Peter Hammond. A framework for generating numerical test data. Overload, 13(69), October 2005. (PDF)
[Harpist, 1995a]
The Harpist. Addressing polymorphic types. Overload, 3(10):16–21, October 1995. C++ Techniques. (PDF)
[Harpist, 1995b]
The Harpist. Having multiple personalities. Overload, 3(8):30–33, June 1995. (PDF)
[Harpist, 1995c]
The Harpist. Java? Where is that? Overload, 3(11):15–18, December 1995. Software Development in C++. (PDF)
[Harpist, 1995d]
The Harpist. Joy unconfined – reflections on three issues. Overload, 3(9):12–14, August 1995. (PDF)
[Harpist, 1995e]
The Harpist. Related objects. Overload, 3(7):24–28, April 1995. (PDF)
[Harpist, 1996a]
The Harpist. The Standard Template Library – first steps auto_ptr. Overload, 4(14):12–15, June 1996. C++ Techniques. (PDF)
[Harpist, 1996b]
The Harpist. The Standard Template Library – first steps: sequence containers. Overload, 4(13):21–24, April 1996. C++ Techniques. (PDF)
[Harpist, 1996c]
The Harpist. The Standard Template Library – sorted associative containers part 1 set & multiset. Overload, 4(15):27–29, August 1996. C++ Techniques. (PDF)
[Harpist, 1997a]
The Harpist. New keywords for... Overload, 5(19):17–21, April 1997. The Draft International C++ Standard. (PDF)
[Harpist, 1997b]
The Harpist. The pitfall of being ignorant. Overload, 5(20):13–17, June 1997. C++ Techniques. (PDF)
[Harpist, 1997c]
The Harpist. Rational values. Overload, 5(21):27–30, August 1997. Whiteboard. (PDF)
[Harpist, 1997d]
The Harpist. Rational values implementation part 1. Overload, 5(22):27–30, October 1997. (PDF)
[Harpist, 1997e]
The Harpist. Rational values implementation part 2. Overload, 5(23):23–28, December 1997. Whiteboard. (PDF)
[Harpist, 1997f]
The Harpist. Standard containers for polymorphic types. Overload, 5(17/18), January 1997.
[Harpist, 1998a]
The Harpist. Exception specifications. Overload, 6(29), December 1998.
[Harpist, 1998b]
The Harpist. Exceptions & exception specifications. Overload, 6(28), October 1998.
[Harpist, 1998c]
The Harpist. Implementations & interfaces. Overload, 6(25):26–29, April 1998. Whiteboard. (PDF)
[Harpist, 1998d]
The Harpist. Object design and implementation. Overload, 6(26):22–26, June 1998. Whiteboard. (PDF)
[Harpist, 1998e]
The Harpist. Object (low-level) design and implementation. Overload, 6(27), August 1998. (PDF)
[Harpist, 1998f]
The Harpist. Rational values part 3. Overload, 6(24):23–28, February 1998. Whiteboard. (PDF)
[Harpist, 1999]
The Harpist. Overloading operators. Overload, 7(30), February 1999.
[Harris, 2007a]
Richard Harris. auto_value: Transfer semantics for value types. Overload, 15(81), October 2007. In his quest to pass around values efficiently, Richard Harris concludes by looking at ways of transferring ownership, now and in the future. (PDF)
[Harris, 2007b]
Richard Harris. auto_value: Transfer semantics for value types. Overload, 15(80), August 2007. "Copy On Write" (COW) sounds like an ideal idiom for avoiding expensive copies. But care must be taken to avoid producing a "mad cow". (PDF)
[Harris, 2007c]
Richard Harris. auto_value: Transfer semantics for value types. Overload, 15(79), June 2007. std::auto_ptr has a reputation for causing problems due to its surprising copy/assignment semantics. Richard Harris tries to separate the good ideas from the bad. (PDF)
[Harris, 2007d]
Richard Harris. The model student. Overload, 15(82), December 2007. Richard Harris begins a series of articles exploring some of the mathematics of interest to those modelling problems with computers. Part 1: The Regular Travelling Salesman. (PDF)
[Harris, 2008a]
Richard Harris. The model student: A knotty problem, part 1. Overload, 16(84), April 2008. Richard Harris explores more of the mathematics of modelling problems with computers. (PDF)
[Harris, 2008b]
Richard Harris. The model student: A knotty problem, part 2. Overload, 16(85), June 2008. Tying yourself in knots is easy. Richard Harris cuts through the complexity. (PDF)
[Harris, 2008c]
Richard Harris. The model student: Can chance make fine things? (Part 1). Overload, 16(87), October 2008. Evolution involves a random process. Richard Harris compares the mathematics to that of blind chance. (PDF)
[Harris, 2008d]
Richard Harris. The model student: Can chance make fine things? (Part 2). Overload, 16(88), December 2008. How well does evolution find solutions? Richard Harris models population change. (PDF)
[Harris, 2008e]
Richard Harris. The regular travelling salesman, part 2. Overload, 16(83), February 2008. Richard Harris explores more of the mathematics of modelling problems with computers. (PDF)
[Harris, 2009a]
Richard Harris. The model student: A primal skyline (part 1). Overload, 17(92), August 2009. Prime numbers are the 'building blocks' of the integers. Richard Harris investigates how they're combined. (PDF)
[Harris, 2009b]
Richard Harris. The model student: A primal skyline (part 2). Overload, 17(93), October 2009. How do you measure the length of a curve? Richard Harris gets his ruler out. (PDF)
[Harris, 2009c]
Richard Harris. The model student: A primal skyline (part 3). Overload, 17(94):11–16, December 2009. The prime factors of the integers show some repeating patterns. Richard Harris investigates whether they have fractal properties. (PDF)
[Harris, 2009d]
Richard Harris. The model student: A rube-ish square (part 1). Overload, 17(89), February 2009. We all have nostalgia for favourite childhood toys. Richard Harris looks at the maths behind a classic. (PDF)
[Harris, 2009e]
Richard Harris. The model student: A rube-ish square (part 2). Overload, 17(90), April 2009. A rube-ish square embodies some simple group theory. Richard Harris explores its properties. (PDF)
[Harris, 2009f]
Richard Harris. The model student: The enigma challenge. Overload, 17(91), June 2009. Codebreaking was instrumental to computing history. Richard Harris presents a simplified Enigma code for you to crack. (PDF)
[Harris, 2010a]
Richard Harris. The model student: A game of six integers (part 1). Overload, 18(95), February 2010. In how many ways can you combine a set of numbers? Richard Harris gets counting. (PDF)
[Harris, 2010b]
Richard Harris. The model student: A game of six integers (part 2). Overload, 18(96), April 2010. What are the properties of the Numbers Game? Richard Harris continues his analysis. (PDF)
[Harris, 2010c]
Richard Harris. The model student: A game of six integers (part 3). Overload, 18(97), June 2010. We now have the tools to analyse the Countdown Numbers Game. Richard Harris is ready to play. (PDF)
[Harris, 2010d]
Richard Harris. The model student: The ACCU 2010 crypto challenge. Overload, 18(98):9–11, August 2010. Electronic computers advanced cryptography enormously. Richard Harris sets a challenge, and finds a solution. (PDF)
[Harris, 2010e]
Richard Harris. Why fixed point won’t cure your floating point blues. Overload, 18(100):14–21, December 2010. Numeric computing is very difficult to do properly. Richard Harris looks at whether a common technique will help. (PDF)
[Harris, 2010f]
Richard Harris. You're going to have to think!. Overload, 18(99):4–9, October 2010. Numerical computing has many pitfalls. Richard Harris starts looking for a silver bullet. (PDF)
[Harris, 2011a]
Richard Harris. The ACCU 2011 crypto challenge. Overload, 19(103):31–36, June 2011. Ready for the biggest challenge yet? Richard Harris throws down the gauntlet. (PDF)
[Harris, 2011b]
Richard Harris. Why computer algebra won’t cure your floating point blues. Overload, 19(102):8–13, April 2011. Numerical computing is proving quite a challenge. Richard Harris sees if a computer can do mathematics. (PDF)
[Harris, 2011c]
Richard Harris. Why finite differences won’t cure your calculus blues. Overload, 19(105):4–11, October 2011. Now we know our problem in depth. Richard Harris analyses if a common technique will work adequately. (PDF)
[Harris, 2011d]
Richard Harris. Why [insert algorithm here] won’t cure your calculus blues. Overload, 19(104):21–24, August 2011. We now know that floating point arithmetic is the best we can do. Richard Harris goes back to school ready to show how to use it. (PDF)
[Harris, 2011e]
Richard Harris. Why interval arithmetic won’t cure your floating point blues. Overload, 19(103):18–23, June 2011. We’ve looked at several approaches to numeric computing. Richard Harris has a final attempt to find an accurate solution. (PDF)
[Harris, 2011f]
Richard Harris. Why polynomial approximation won't cure your calculus blues. Overload, 19(106):16–24, December 2011. We’re still trying to find a good way to approach numerical computing. Richard Harris tries to get as close as possible. (PDF)
[Harris, 2011g]
Richard Harris. Why rationals won’t cure your floating point blues. Overload, 19(101):8–11, February 2011. Numerical computing is still proving hard to do accurately. Richard Harris considers another number representation. (PDF)
[Harris, 2012a]
Richard Harris. Why automatic differentiation won’t cure your calculus blues. Overload, 20(108):4–11, April 2012. We’ve tried and rejected many numerical approaches to differentiation. Richard Harris has one final attempt. (PDF)
[Harris, 2012b]
Richard Harris. Why computer algebra won’t cure your calculus blues. Overload, 20(107):14–19, February 2012. We still haven’t found how to accurately do calculus. Richard Harris revisits an algebraic technique. (PDF)
[Hastings, 2005]
William Hastings. Polynomial classes. Overload, 13(69), October 2005. (PDF)
[Heinzmann and Bass, 2003]
Stefan Heinzmann and Phil Bass. Observer pattern implementation. Overload, 11(54), April 2003. (PDF)
[Heinzmann and Bass, 2004]
Stefan Heinzmann and Phil Bass. A template programmer’s struggles resolved. Overload, 12(61), June 2004. (PDF)
[Heinzmann, 2004a]
Stefan Heinzmann. The tale of a struggling template programmer. Overload, 12(61), June 2004. (PDF)
[Heinzmann, 2004b]
Stefan Heinzmann. Yet another hierarchical state machine. Overload, 12(64), December 2004. (PDF)
[Hennessy, 2005]
Pippa Hennessy. Sheep farming for software development managers. Overload, 13(66), April 2005. (PDF)
[Henney et al., 1997]
Kevlin Henney, Percy Richard, and Jonathan Jagger. editor << letters;. Overload, 5(20):36–37, June 1997. (PDF)
[Henney, 1994a]
Kevlin Henney. Do birds in their little nests always agree?. Overload, 2(4), February 1994.
[Henney, 1994b]
Kevlin Henney. Writing your own stream manipulators. Overload, 2(5):16–18, September 1994.
[Henney, 1995a]
Kevlin Henney. An alternative to wchar_t. Overload, 3(6), March 1995.
[Henney, 1995b]
Kevlin Henney. Anonymously yours. Overload, 3(11):22–23, December 1995. The Draft International C++ Standard. (PDF)
[Henney, 1995c]
Kevlin Henney. Change of address. Overload, 3(11):34–37, December 1995. C++ Techniques. (PDF)
[Henney, 1995d]
Kevlin Henney. Circle & ellipse – vicious circles. Overload, 3(8):23–27, June 1995. (PDF)
[Henney, 1995e]
Kevlin Henney. cv-qualified constructors. Overload, 3(8):15–18, June 1995. The Draft International C++ Standard. (PDF)
[Henney, 1995f]
Kevlin Henney. editor << letters;. Overload, 3(7):37–38, April 1995. (PDF)
[Henney, 1995g]
Kevlin Henney. Literally yours. Overload, 3(11):21–22, December 1995. The Draft International C++ Standard. (PDF)
[Henney, 1995h]
Kevlin Henney. Overloading on const and other stories. Overload, 3(7):15–17, April 1995. (PDF)
[Henney, 1995i]
Kevlin Henney. Seduction: The last? – Applying the STL mindset. Overload, 3(9):7–12, August 1995. (PDF)
[Henney, 1995j]
Kevlin Henney. /tmp/late/* generating constants with templates. Overload, 3(11):37–39, December 1995. C++ Techniques. (PDF)
[Henney, 1995k]
Kevlin Henney. Uncontained – oddities and oversights in the standard library. Overload, 3(9):21–23, August 1995. The Draft International C++ Standard. (PDF)
[Henney, 1996a]
Kevlin Henney. questions->answers. Overload, 4(16):24–27, October 1996. (PDF)
[Henney, 1996b]
Kevlin Henney. questions->answers. Overload, 4(13):31–33, April 1996. (PDF)
[Henney, 1996c]
Kevlin Henney. Rot in L. Overload, 3(12):18–19, February 1996. C++ Techniques. (PDF)
[Henney, 1996d]
Kevlin Henney. Some OOD answers. Overload, 4(16):4–8, October 1996. Software Development in C++. (PDF)
[Henney, 1996e]
Kevlin Henney. /tmp/late/* constraining template parameter types. Overload, 3(12):23–26, February 1996. C++ Techniques. (PDF)
[Henney, 1996f]
Kevlin Henney. /tmp/late/* Constraining template parameter values. Overload, 4(15):33–35, August 1996. C++ Techniques. (PDF)
[Henney, 1996g]
Kevlin Henney. /tmp/late/* specifying integer size. Overload, 4(13):27–30, April 1996. C++ Techniques. (PDF)
[Henney, 1997a]
Kevlin Henney. Allocation stats. Overload, 5(22):5–8, October 1997. (PDF)
[Henney, 1997b]
Kevlin Henney. Make a date with C++ and so to const. Overload, 5(22):15–20, October 1997. (PDF)
[Henney, 1997c]
Kevlin Henney. Make a date with C++: In the beginning... Overload, 5(19):12–14, April 1997. Software Development in C++. (PDF)
[Henney, 1997d]
Kevlin Henney. Make a date with C++ independence of declaration. Overload, 5(21):18–20, August 1997. C++ Techniques. (PDF)
[Henney, 1997e]
Kevlin Henney. Make a date with C++: Typing lessons. Overload, 5(20):10–13, June 1997. C++ Techniques. (PDF)
[Henney, 1997f]
Kevlin Henney. Safe assignment? No problem! Overload, 5(21):14–17, August 1997. C++ Techniques. (PDF)
[Henney, 1997g]
Kevlin Henney. Self assignment? No problem! Overload, 5(20):17–25, June 1997. C++ Techniques. (PDF)
[Henney, 1998a]
Kevlin Henney. Counted body techniques. Overload, 6(25):1–7, April 1998. Software Development in C++. (PDF)
[Henney, 1998b]
Kevlin Henney. Embed with C++. Overload, 6(24):9–13, February 1998. The Draft International C++ Standard. (PDF)
[Henney, 1998c]
Kevlin Henney. Make a date with C++, a touch of class. Overload, 6(26):3–7, June 1998. Software Development in C++. (PDF)
[Henney, 1999a]
Kevlin Henney. Coping with copying in C++. Overload, 7(33), October 1999.
[Henney, 1999b]
Kevlin Henney. The diary of bridget jones the weekend before OT. Overload, 7(34), December 1999.
[Henney, 2000a]
Kevlin Henney. C++ patterns source cohesion and decoupling. Overload, 8(39), October 2000.
[Henney, 2000b]
Kevlin Henney. From mechanism to method: Substitutability. Overload, 8(39), October 2000.
[Henney, 2000c]
Kevlin Henney. From mechanism to method: Valued conversions. Overload, 8(40), December 2000.
[Henney, 2001]
Kevlin Henney. minimalism. Overload, 9(45), October 2001. (PDF)
[Henney, 2002a]
Kevlin Henney. From mechanism to method: Function follows form. Overload, 10(48), April 2002. (PDF)
[Henney, 2002b]
Kevlin Henney. From mechanism to method: Good qualifications. Overload, 10(52), December 2002. (PDF)
[Henney, 2002c]
Kevlin Henney. Letter to the editor. Overload, 10(49), June 2002. (PDF)
[Henney, 2002d]
Kevlin Henney. minimalism. Overload, 10(47), February 2002. (PDF)
[Henney, 2002e]
Kevlin Henney. Minimalist constructive criticism. Overload, 10(47), February 2002. (PDF)
[Henney, 2003a]
Kevlin Henney. From mechanism to method: Data abstraction and heterarchy. Overload, 11(58), December 2003. (PDF)
[Henney, 2003b]
Kevlin Henney. From mechanism to method: Distinctly qualified. Overload, 11(55), June 2003. (PDF)
[Henney, 2003c]
Kevlin Henney. From mechanism to method: Total ellipse. Overload, 11(53):14–18, February 2003. (PDF)
[Henney, 2004a]
Kevlin Henney. From mechanism to method: Further qualifications. Overload, 12(59), February 2004. (PDF)
[Henney, 2004b]
Kevlin Henney. From mechanism to method: Generic decoupling. Overload, 12(60), April 2004. (PDF)
[Henney, 2004c]
Kevlin Henney. From mechanism to method: The safe stacking of cats. Overload, 12(62), August 2004. Source: cats, curling, exceptions. (PDF)
[Henney, 2005a]
Kevlin Henney. C-side re-sort. Overload, 13(68), August 2005. In spite of the attention given to object-oriented development, TDD and modern testing frameworks, it is worth understanding how and why unit testing has an important role to play in general, regardless of the technologies or broader development philosophy involved. This article walks through a simple example, highlighting some of the motivation behind basic unit testing and the practices involved but without following through into TDD. (PDF)
[Henney, 2005b]
Kevlin Henney. Stable intermediate forms. Overload, 13(65), February 2005. (PDF)
[Henney, 2005c]
Kevlin Henney. Vorsprung durch testing. Overload, 13(69), October 2005. (PDF)
[Henney, 2007a]
Kevlin Henney. The PfA papers: Context matters. Overload, 15(82), December 2007. Continuing his history of Parameterise from Above, Kevlin Henny looks at Singletons and Context Objects. (PDF)
[Henney, 2007b]
Kevlin Henney. The PfA papers: From the top. Overload, 15(80), August 2007. A characteristic of patterns is that experienced developers often experience a moment of recognition upon reading the write up. Sometimes the write up isn't even needed... (PDF)
[Henney, 2007c]
Kevlin Henney. The PfA papers: The clean dozen. Overload, 15(81), October 2007. Patterns are social animals and are often found in the company of others. This issue, Kevlin Henney looks at where 'Parameterise from Above' has been hanging out. (PDF)
[Henney, 2008]
Kevlin Henney. The PfA papers: Deglobalisation. Overload, 16(83), February 2008. More history of Parameterise from Above as Kevlin Henney looks at Simpletons and the Borg. (PDF)
[Henney, 2011]
Kevlin Henney. Rise of the machines. Overload, 19(101):20, February 2011. Sometimes the world really is out to get you. Kevlin Henney identifies some culprits. (PDF)
[Henney, 2013]
Kevlin Henney. The uncertainty principle. Overload, 20(115):29, June 2013. Not being sure of something is usually thought of as a problem. Kevlin Henney argues to the contrary. (PDF)
[Henricson and Nyquist, 1995]
Mats Henricson and Erik Nyquist. operator= and const – a reply. Overload, 3(7):18, April 1995. (PDF)
[Henricson, 1995]
Mats Henricson. Writing “Industrial Strength C++”. Overload, 3(8):44–46, June 1995. Books and Journals. (PDF)
[Hills, 2003]
Chris Hills. A standard individual: A licensed engineer. Overload, 11(58), December 2003. (PDF)
[Horwill, 1993]
Ian Horwill. Windows file class. Overload, 1(3), August 1993.
[Horwill, 1995a]
Ian Horwill. editor << letters;. Overload, 3(8):40, June 1995. (PDF)
[Horwill, 1995b]
Ian Horwill. editor << letters;. Overload, 3(7):35–36, April 1995. (PDF)
[Horwill, 1995c]
Ian Horwill. Wait for me! – copying and assignment. Overload, 3(7):23–24, April 1995. (PDF)
[Horwill, 1995d]
Ian Horwill. Wait for me! – virtual. Overload, 3(8):20–23, June 1995. (PDF)
[Houghton, 1997]
Tony Houghton. editor << letters;. Overload, 5(23):38, December 1997. (PDF)
[Hughes, 2000]
Tom Hughes. editorial. Overload, 8(37), June 2000.
[Ignatchenko and Ivanchykhin, 2013]
Sergey Ignatchenko and Dmytro Ivanchykhin. A model for debug complexity. Overload, 20(114):4–5, April 2013. Debugging any program can be difficult. Sergey Ignatchenko and Dmytro Ivanchykhin develop a mathematical model for its complexity. (PDF)
[Ignatchenko and Ivanchykhin, 2014]
Sergey Ignatchenko and Dmytro Ivanchykhin. Optimizing big number arithmetic without SSE. Overload, 20(119):16–18, February 2014. Addition and multiplication can be slow for big numbers. Sergey Ignatchenko and Dmytro Ivanchykhin try to speed things up. (PDF)
[Ignatchenko and Ligum, 1997]
Sergey Ignatchenko and Dmitry Ligum. STL vectors. Overload, 5(23):19–23, December 1997. C++ Techniques. (PDF)
[Ignatchenko, 1997]
Sergey Ignatchenko. Some opportunities to increase STL efficiency. Overload, 5(22):30–35, October 1997. (PDF)
[Ignatchenko, 2010a]
Sergey Ignatchenko. From occam’s razor to no bugs’ axe. Overload, 18(100):8–10, December 2010. Designing good APIs that stand the test of time is notoriously hard. Sergey Ignatchenko suggests a radical guideline. (PDF)
[Ignatchenko, 2010b]
Sergey Ignatchenko. Single-threading: Back to the future?. Overload, 18(97), June 2010. Dealing with multi-threading is notoriously hard. Sergey Ignatchenko learns lessons from the past. (PDF)
[Ignatchenko, 2010c]
Sergey Ignatchenko. Single-threading: Back to the future? (Part 2). Overload, 18(98):16–19, August 2010. Multithreading can cause notoriously difficult bugs. Sergey Ignatchenko finds mitigating strategies for programs on servers. (PDF)
[Ignatchenko, 2010d]
Sergey Ignatchenko. To DLL or not to DLL. Overload, 18(99):14–16, October 2010. Shared libraries provide both benefits and problems. Sergey Ignatchenko introduces a rabbit’s-eye view. (PDF)
[Ignatchenko, 2011a]
Sergey Ignatchenko. From the age of power to the age of magic and beyond... Overload, 19(106):11–13, December 2011. Certain abilities allowed some societies to dominate their peers. Sergey Ignatchenko takes a historical perspective on dominant societies. (PDF)
[Ignatchenko, 2011b]
Sergey Ignatchenko. The guy we’re all working for. Overload, 19(103):10–12, June 2011. Developers like to think they’re in control of their products. Sergey Ignatchenko reminds us who’s really in charge. (PDF)
[Ignatchenko, 2011c]
Sergey Ignatchenko. Intellectual property – a crash course for developers. Overload, 19(105):18–20, October 2011. Interpreting law is a tricky business. Sergey Ignatchenko introduces someone who can help you avoid expensive mistakes. (PDF)
[Ignatchenko, 2011d]
Sergey Ignatchenko. On CMM, formalism and creativity. Overload, 19(102):18–20, April 2011. No Bugs requires us to improve software quality. Sergey Ignatchenko considers some of the potential problems. (PDF)
[Ignatchenko, 2011e]
Sergey Ignatchenko. Over-generic use of abstractons as a major cause of wasting resources. Overload, 19(104):4–6, August 2011. We often find ways to hide complexity. Sergey Ignatchenko looks at how this can be sub-optimal. (PDF)
[Ignatchenko, 2011f]
Sergey Ignatchenko. Overused code reuse. Overload, 19(101):12–14, February 2011. It’s tempting to use someone else’s code rather than write it yourself. Sergey Ignatchenko reports that ‘No Bugs’ Bunny recommends caution. (PDF)
[Ignatchenko, 2012a]
Sergey Ignatchenko. -640k- 2^256 bytes of memory is more than anyone would ever -need- get. Overload, 20(112):14–15, December 2012. How fast can computers get? Sergey Ignatchenko provides us with some upper limits. (PDF)
[Ignatchenko, 2012b]
Sergey Ignatchenko. Compiling a static web site using the C preprocessor. Overload, 20(108):33–35, April 2012. Sometimes the obvious way is still too complex. Sergey Ignatchenko relates how ‘No Bugs’ Bunny found an unexpectedly simple approach to creating a web site. (PDF)
[Ignatchenko, 2012c]
Sergey Ignatchenko. Keep it simple, singleton! Overload, 20(111):19–20, October 2012. Naïve assumptions sound like a bad idea. Sergey Ignatchenko discusses how to spot good assumptions in the face of changing requirements. (PDF)
[Ignatchenko, 2012d]
Sergey Ignatchenko. Memory leaks and memory leaks. Overload, 20(107):4–5, February 2012. Correct use of memory is a major occupation of software development. Sergey Ignatchenko considers what we mean by ‘correct’. (PDF)
[Ignatchenko, 2012e]
Sergey Ignatchenko. Programming Darwinism. Overload, 20(109):4–5, June 2012. Have you ever thought your software had a life of its own? Sergey Ignatchenko wonders whether you might be right. (PDF)
[Ignatchenko, 2012f]
Sergey Ignatchenko. Replace user, strike any key? Overload, 20(110):16–18, August 2012. There is a common perception in the IT industry that the user is the primary source of all the problems. Sergey Ignatchenko asks if this is true. (PDF)
[Ignatchenko, 2013a]
Sergey Ignatchenko. Hard upper limit on memory latency. Overload, 20(116):4–5, August 2013. Achieving very low latency is important. Sergey Ignatchenko asks how low can we go. (PDF)
[Ignatchenko, 2013b]
Sergey Ignatchenko. ‘No bugs’ top five c++ cooking recipes. Overload, 20(113):4–6, February 2013. Developers often have a few favourite tricks for solving problems. Sergey Ignatchenko shares his five top recipes. (PDF)
[Ignatchenko, 2013c]
Sergey Ignatchenko. On the other side of the barricade: Job interviewer do’s and don’ts. Overload, 20(118):4–6, December 2013. Interviewing is an important skill which is hard to get right. Sergey Ignatchenko gives advice to get you thinking. (PDF)
[Ignatchenko, 2013d]
Sergey Ignatchenko. TCP/IP explained. A bit. Overload, 20(115):8–11, June 2013. Nowadays most programmers rely on network connectivity, often without really understanding the details. Sergey Ignatchenko compares and contrasts the two main protocols. (PDF)
[Ignatchenko, 2013e]
Sergey Ignatchenko. YAGNI-C as a practical application of YAGNI. Overload, 20(117):12–14, October 2013. YAGNI can seem vague. Sergey Ignatchenko offers a more precise definition. (PDF)
[Iltchenko, 2002]
Andrei Iltchenko. The C++ template argument deduction. Overload, 10(48), April 2002. (PDF)
[IPL Limited, 1993]
IPL Limited. Unit testing of C++ classes. Overload, 1(3), August 1993.
[Jackson, 1995]
Kenneth Jackson. ‘Individual’ control validation in MFC. Overload, 3(8):33–36, June 1995. (PDF)
[Jagger]
Jon Jagger.
[Jagger, 1996a]
Jon Jagger. Functionoids. Overload, 4(14):15–16, June 1996. C++ Techniques. (PDF)
[Jagger, 1996b]
Jon Jagger. Time please, ladies and gentlemen. Overload, 4(14):16–18, June 1996. C++ Techniques. (PDF)
[Jagger, 1997a]
Jon Jagger. auto_ptr || !auto_ptr. Overload, 5(17/18), January 1997. See also corrections in Overload 19, p.30.
[Jagger, 1997b]
Jon Jagger. Lessons from fixed_vector part 1. Overload, 5(20):25–27, June 1997. C++ Techniques. (PDF)
[Jagger, 1998a]
Jon Jagger. counted_ptr{type}. Overload, 6(25):7–13, April 1998. Software Development in C++. (PDF)
[Jagger, 1998b]
Jon Jagger. counted_ptr revisited. Overload, 6(29), December 1998.
[Jagger, 1998c]
Jon Jagger. pointer{type}. Overload, 6(24):13–18, February 1998. C++ Techniques. (PDF)
[Jagger, 1999a]
Jon Jagger. copy_on_write_ptr. Overload, 7(31), April 1999.
[Jagger, 1999b]
Jon Jagger. More cow_ptr ruminations. Overload, 7(33), October 1999.
[Jagger, 1999c]
Jon Jagger. A review of cow_ptr. Overload, 7(32), June 1999.
[Jagger, 1999d]
Jon Jagger. Write to learn. Overload, 7(30), February 1999.
[Jagger, 2002a]
Jon Jagger. Even more java exceptions. Overload, 10(50), August 2002. (PDF)
[Jagger, 2002b]
Jon Jagger. Exception handling in C#. Overload, 10(51), October 2002. (PDF)
[Jagger, 2002c]
Jon Jagger. An overview of C#.NET. Overload, 10(49), June 2002. (PDF)
[Jagger, 2003a]
Jon Jagger. How to write a loop. Overload, 11(55), June 2003. (PDF)
[Jagger, 2003b]
Jon Jagger. The nature and aesthetics of design. Overload, 11(54), April 2003. (PDF)
[Jagger, 2003c]
Jon Jagger. A return type that doesn’t like being ignored. Overload, 11(53):20–21, February 2003. (PDF)
[Jagger, 2003d]
Jon Jagger. Single exit. Overload, 11(57), October 2003. (PDF)
[Jagger, 2003e]
Jon Jagger. Software as read. Overload, 11(57), October 2003. (PDF)
[Jay, 2009]
Rafael Jay. Complexity, requirements and models. Overload, 17(91), June 2009. Programs can be unnecessarily complex. Rafael Jay examines a technique for doing better. (PDF)
[Jay, 2010]
Rafael Jay. Bug hunting and the scientific method. Overload, 18(100):4–7, December 2010. Do you have a proper methodology when fixing bugs? Rafael Jay puts on his lab coat. (PDF)
[Jensen, 2005]
Randall W Jensen. A pair programming experience. Overload, 13(65), February 2005. (PDF)
[Johansen, 2005]
Trond Johansen. From waterfall to evo in a medium size norwegian software house. Overload, 13(65), February 2005. FIRM was established in 1996, and has 70 employees in 4 offices (Oslo, London, New York and San Francisco). FIRM delivers one software product: Confirmit. Confirmit is a web-based application which enables organizations to gather, analyze and report key business information across a broad range of commercial applications. (PDF)
[Johnson, 2006]
Paul Johnson. A drop in standards?. Overload, 14(76), December 2006. Paul Johnson asks why, with the increase in numbers of those passing school-based examinations, today's graduates are less able than in previous times. What is going wrong? (PDF)
[Jones, 1996]
Graham Jones. Some questions about OOD. Overload, 4(15):4–6, August 1996. Software Development in C++. (PDF)
[Jones, 1997]
Graham Jones. OOD again: Some light, some shadows. Overload, 5(19):22–24, April 1997. C++ Techniques. (PDF)
[Jones, 1998a]
Graham Jones. Irrational behaviour. Overload, 6(25):25–26, April 1998. Whiteboard. (PDF)
[Jones, 1998b]
Graham Jones. Rational value comments. Overload, 6(24):22, February 1998. Whiteboard. (PDF)
[Jones, 2004]
Derek M. Jones. Letters: Software’s no different... Overload, 12(61), June 2004. (PDF)
[Jones, 2008a]
Robert Jones. Generics without templates. Overload, 16(83), February 2008. Robert Jones presents an alternative implementation of C++'s std::vector that can be used the absence of templates and exceptions. (PDF)
[Jones, 2008b]
Robert Jones. Generics without templates - revisited. Overload, 16(88), December 2008. Can you use the STL if your compiler lacks templates? Robert Jones implements iterators and alogorithms. (PDF)
[Jones, 2009]
Matthew Jones. Testing state machines. Overload, 17(90), April 2009. State machines are a common design pattern. Matthew Jones seperates their concerns to make testing easier. (PDF)
[Jones, 2010]
Matthew Jones. Debugging run time memory problems. Overload, 18(98):20–27, August 2010. The C++ Standard is often silent on what happens when things go wrong. Matthew Jones looks under the bonnet to take control. (PDF)
[Josuttis, 2000]
Nicolai Josuttis. eXtreme Programming an interview with kent beck. Overload, 8(35), February 2000.
[Joy and Gradman, 2001]
Corwin Joy and Michael Gradman. Introduction to the database template library. Overload, 9(43), June 2001.
[Kampjes, 2005]
Bryce Kampjes. Incremental design: A case study of a compiler. Overload, 13(69), October 2005. (PDF)
[Karlsson, 2002]
Björn Karlsson. What is Boost?. Overload, 10(47), February 2002. (PDF)
[Keffer, 1994]
Dr. Thomas Keffer. Why C++ will replace FORTRAN (or, at least, why it should). Overload, 2(4), February 1994.
[Kelly, 1999a]
Allan Kelly. Modern art as an inspiration for software. Overload, 7(32), June 1999.
[Kelly, 1999b]
Allan Kelly. More threading with templates. Overload, 7(33), October 1999.
[Kelly, 1999c]
Allan Kelly. Using templates to handle multi-threading. Overload, 7(31), April 1999.
[Kelly, 2000a]
Allan Kelly. Error handling and logging. Overload, 8(35), February 2000.
[Kelly, 2000b]
Allan Kelly. In response to extreme programming. Overload, 8(37), June 2000.
[Kelly, 2000c]
Allan Kelly. Include files. Overload, 8(39), October 2000.
[Kelly, 2000d]
Allan Kelly. More include file rules. Overload, 8(40), December 2000.
[Kelly, 2001a]
Allan Kelly. A deeper look at inline functions. Overload, 9(42), April 2001.
[Kelly, 2001b]
Allan Kelly. Modelling and software development. Overload, 9(46), December 2001. (PDF)
[Kelly, 2001c]
Allan Kelly. Porting (part 2) - addressing the differences. Overload, 9(44), August 2001. (PDF)
[Kelly, 2001d]
Allan Kelly. Porting part 3:. Overload, 9(45), October 2001. (PDF)
[Kelly, 2001e]
Allan Kelly. Source code modules and layering. Overload, 9(41), February 2001.
[Kelly, 2001f]
Allan Kelly. Where to begin: Porting. Overload, 9(43), June 2001.
[Kelly, 2002a]
Allan Kelly. Extendable software and the bigger picture. Overload, 10(51), October 2002. (PDF)
[Kelly, 2002b]
Allan Kelly. How about a turner prize for software?. Overload, 10(47), February 2002. (PDF)
[Kelly, 2002c]
Allan Kelly. Of minimalism, constructivism and program code. Overload, 10(47), February 2002. (PDF)
[Kelly, 2002d]
Allan Kelly. Organising source code. Overload, 10(52), December 2002. (PDF)
[Kelly, 2002e]
Allan Kelly. The philosophy of extensible software. Overload, 10(50), August 2002. (PDF)
[Kelly, 2002f]
Allan Kelly. The scoping problem. Overload, 10(49), June 2002. (PDF)
[Kelly, 2002g]
Allan Kelly. Thinking about "reuse". Overload, 10(48), April 2002. (PDF)
[Kelly, 2002h]
Allan Kelly. Writing extendable software. Overload, 10(49), June 2002. (PDF)
[Kelly, 2003a]
Allan Kelly. An alternative view of design (and planning). Overload, 11(58), December 2003. (PDF)
[Kelly, 2003b]
Allan Kelly. Build systems. Overload, 11(53):5–9, February 2003. (PDF)
[Kelly, 2003c]
Allan Kelly. Europlop 2003 conference report. Overload, 11(56), August 2003. (PDF)
[Kelly, 2003d]
Allan Kelly. Is IT worth it?. Overload, 11(57), October 2003. (PDF)
[Kelly, 2003e]
Allan Kelly. Letters to the editor(s). Overload, 11(57), October 2003. (PDF)
[Kelly, 2003f]
Allan Kelly. Ruminations on knowledge in software development. Overload, 11(55), June 2003. (PDF)
[Kelly, 2003g]
Allan Kelly. Software development and the learning organisation. Overload, 11(54), April 2003. (PDF)
[Kelly, 2004a]
Allan Kelly. The encapsulate context pattern. Overload, 12(63), October 2004. (PDF)
[Kelly, 2004b]
Allan Kelly. Where egos dare. Overload, 12(61), June 2004. (PDF)
[Kelly, 2004c]
Allan Kelly. Why do requirements change?. Overload, 12(59), February 2004. (PDF)
[Kelly, 2005a]
Allan Kelly. The developer's new work. Overload, 13(65), February 2005. (PDF)
[Kelly, 2005b]
Allan Kelly. Editorial: Need to unlearn. Overload, 13(66), April 2005. (PDF)
[Kelly, 2006]
Allan Kelly. The documentation myth. Overload, 14(74), August 2006. Allan Kelly suggests that we don't invest more in documentation for a reason: that it isn't as valuable as we claim. (PDF)
[Kelly, 2007a]
Allan Kelly. Blue-White-Red, an example agile process. Overload, 15(81), October 2007. When it comes to running a project, one size rarely fits all, but Allan Kelly finds that tailoring a core idea over time has led to repeated success. (PDF)
[Kelly, 2007b]
Allan Kelly. Creating awareness. Overload, 15(82), December 2007. One of the good things about presenting at the ACCU conference is what you learn there. Allan Kelly reviews the results of his last conference talk. (PDF)
[Kelly, 2008a]
Allan Kelly. Focus, quality, time-boxes and ducks. Overload, 16(87), October 2008. Project success depends on organisation. Allan Kelly looks at how to keep things in order. (PDF)
[Kelly, 2008b]
Allan Kelly. Future workers (prototype). Overload, 16(83), February 2008. What does it mean for IT workers to be prototype knowledge workers? (PDF)
[Kelly, 2008c]
Allan Kelly. On management. Overload, 16(86), August 2008. Management is a vital part of software development. Allan Kelly starts a new series by balancing some constraints. (PDF)
[Kelly, 2008d]
Allan Kelly. On management: Understanding who creates software. Overload, 16(88), December 2008. Software development organizations vary greatly. Allan Kelly considers what this means for managers. (PDF)
[Kelly, 2009a]
Allan Kelly. On management: Caveat emptor. Overload, 17(89), February 2009. There are many theories and practices of management. Allan Kelly offers some warnings. (PDF)
[Kelly, 2009b]
Allan Kelly. On management: Product managers. Overload, 17(90), April 2009. Product Management is a poorly understood activity. Allan Kelly sheds some light on its mysteries. (PDF)
[Kelly, 2009c]
Allan Kelly. On management: The business analyst's role. Overload, 17(91), June 2009. Some management titles are poorly defined. Allan Kelly disentangles a knotty one. (PDF)
[Kelly, 2010]
Allan Kelly. “I’m a business analyst – get me out of here”. Overload, 18(98):4–8, August 2010. Some classic roles are omitted by Agile methodologies. Allan Kelly considers how a Business Analyst fits in. (PDF)
[Kelly, 2011a]
Allan Kelly. The agile 10 steps model. Overload, 19(101):16–19, February 2011. Technical processes have tended to dominate agile thinking. Allan Kelly looks at the wider picture. (PDF)
[Kelly, 2011b]
Allan Kelly. The Agile spectrum. Overload, 19(102):14–17, April 2011. Very few teams are truly Agile. Allan Kelly looks at the range of styles. (PDF)
[Kelly, 2011c]
Allan Kelly. Integrating testers into an agile team. Overload, 19(104):7–9, August 2011. Agile has usually concentrated on how to organise developers. Allan Kelly shows how testers fit in. (PDF)
[Kelly, 2012]
Allan Kelly. Software developer business patterns. Overload, 20(111):21–24, October 2012. Patterns can be applied to business as well as software. Allan Kelly shows us how. (PDF)
[Ken Hagan, 1999]
The Hagan Ken Hagan. A letter from ken hagan annotated by the harpist. Overload, 7(30), February 1999.
[Kendall, 1995]
Graham Kendall. Putting jack in the box. Overload, 3(6), March 1995.
[Kühl, 2011]
Dietmar Kühl. Exception specifications in C++ 2011. Overload, 19(103):13–17, June 2011. The new standard is almost finished. Dietmar Kühl looks at the new exception features. (PDF)
[Kilpeläinen, 2004]
Mikael Kilpeläinen. Lvalues and rvalues. Overload, 12(61), June 2004. (PDF)
[Kilpeläinen, 2005]
Mikael Kilpeläinen. Overload resolution - selecting the function. Overload, 13(66), April 2005. (PDF)
[King, 1995]
Andrew King. editor << letters;. Overload, 3(11):39–40, December 1995. (PDF)
[Knabe, 2011]
Christoph Knabe. The eternal battle against redundancies, part I. Overload, 19(106):7–10, December 2011. The drive to remove redundancies is widely seen as a good thing. Christoph Knabe sees how it has influenced programming languages. (PDF)
[Knabe, 2012]
Christoph Knabe. The eternal battle against redundancies, part 2. Overload, 20(107):20–23, February 2012. Repeated information leads to poor quality software. Christoph Knabe continues to see how removing them has influenced language design. (PDF)
[Kuehl, 2003]
Dietmar Kuehl. A bin manipulator for iostreams. Overload, 11(55), June 2003. (PDF)
[Lenton, 1994]
Alan Lenton. Afterword. Overload, 2(5):27, September 1994.
[Lever and Radford, 1997]
Roger Lever and Mark Radford. The uses and abuses of inheritance. Overload, 5(19):6–8, April 1997. Software Development in C++. (PDF)
[Lever, 1995a]
Roger Lever. The case against learning C++ right now – right or wrong? Overload, 3(8):3–5, June 1995. (PDF)
[Lever, 1995b]
Roger Lever. Interview with Jiri Soukup by Roger Lever. Overload, 3(9):36–38, August 1995. (PDF)
[Lever, 1995c]
Roger Lever. On not mixing it... Overload, 3(7):32–33, April 1995. (PDF)
[Lever, 1995d]
Roger Lever. On not mixing it...again. Overload, 3(9):30–33, August 1995. (PDF)
[Lever, 1995e]
Roger Lever. Simple classes for debugging in C++ – part 2. Overload, 3(11):23–28, December 1995. C++ Techniques. (PDF)
[Lever, 1995f]
Roger Lever. Simple classes for debugging in C++ – part I. Overload, 3(10):21–24, October 1995. C++ Techniques. (PDF)
[Lever, 1996a]
Roger Lever. Simple classes – part 4: Game of life. Overload, 4(13):11–14, April 1996. Software Development in C++. (PDF)
[Lever, 1996b]
Roger Lever. Simple classes for debugging in C++ – part 3. Overload, 3(12):19–22, February 1996. C++ Techniques. (PDF)
[Lever, 1998]
Roger Lever. Hotel case study comments. Overload, 6(27), August 1998. (PDF)
[Lewin, 2012]
Michael Lewin. All about XOR. Overload, 20(109):14–19, June 2012. Boolean operators are the bedrock of computer logic. Michael Lewin investigates a common one and shows there’s more to it than meets the eye. (PDF)
[Longshaw and Woods, 2009a]
Andy Longshaw and Eoin Woods. The generation, management and handling of errors (part 1). Overload, 17(92), August 2009. An error handling strategy is important for robustness. Andy Longshore and Eoin Woods present a pattern language. (PDF)
[Longshaw and Woods, 2009b]
Andy Longshaw and Eoin Woods. The generation, management and handling of errors (part 2). Overload, 17(93), October 2009. Dealing with errors is a vital activity. Andy Longshaw and Eoin Woods conclude their pattern language. (PDF)
[Love and Orr, 2011]
Steve Love and Roger Orr. Some objects are more equal than others. Overload, 19(103):4–9, June 2011. Comparing objects is a fundamental operation. Steve Love and Roger Orr consider different language approaches. (PDF)
[Love, 2000]
Steve Love. A fistful of idioms - giving STL iterators a base class. Overload, 8(38), August 2000.
[Love, 2001a]
Steve Love. Are you afraid of the dark? - Making sense of the STL. Overload, 9(43), June 2001.
[Love, 2001b]
Steve Love. Are you afraid of the dark too? Making more sense of the STL. Overload, 9(44), August 2001. (PDF)
[Love, 2006a]
Steve Love. C# generics - beyond containers of T. Overload, 14(74), August 2006. Steve Love takes a look at generics in C# v2.0, how to use them to simplify code and even remove dependencies. (PDF)
[Love, 2006b]
Steve Love. A fistful of idioms. Overload, 14(72), April 2006. (PDF)
[Love, 2006c]
Steve Love. The rise and fall of singleton threaded. Overload, 14(73), June 2006. Steve Love explores how 'Singletons' in design can seem a good idea at the time, why they are generally a mistake, and what to do if you have them. (PDF)
[Love, 2010]
Steve Love. Interface versioning in C++. Overload, 18(100):22–31, December 2010. Interface Versioning in C++Updating a widely used DLL interface is non-trivial. Steve Love presents a practical approach. (PDF)
[Love, 2012]
Steve Love. Many slices of Pi. Overload, 20(107):6–13, February 2012. Many numberic estimation techniques are easily parallelisable. Steve Love employs multi-threading, message passing, and more in search of Pi. (PDF)
[Love, 2013a]
Steve Love. C++ range and elevation. Overload, 20(117):28–36, October 2013. C++ provides many features for higher-level programming, but lacks some common ones present in other languages. (PDF)
[Love, 2013b]
Steve Love. Secrets of testing WCF services. Overload, 20(113):16–23, February 2013. WCF services provide middleware for applications but can be hard to test. Steve Love describes a way to develop a testable app. (PDF)
[Main, 2002]
Chris Main. Programming with interfaces in C++. Overload, 10(49), June 2002. (PDF)
[Main, 2003]
Chris Main. Implementing the bridge pattern using templates with Microsoft Visual C++ 6.0. Overload, 11(54), April 2003. (PDF)
[Main, 2004]
Chris Main. A template programmer's struggles revisited. Overload, 12(62), August 2004. (PDF)
[Main, 2007]
Chris Main. C++ unit test frameworks. Overload, 15(78), April 2007. There are many Unit Testing frameworks for C++, but which one to use? Chris Main shares his experience of some of them. (PDF)
[Mancuso, 2004]
Renato Mancuso. Letters to the editor. Overload, 12(62), August 2004. (PDF)
[Marlow, 2007]
Andrew Marlow. Fructose - a C++ unit test framework. Overload, 15(77), February 2007. Andrew Marlow describes the development of FRUCTOSE and how it is different from other unit test frameworks. (PDF)
[Marquardt, 2008a]
Klaus Marquardt. Performitis. Overload, 16(85), June 2008. Patterns try to solve problems. Klaus Marquardt looks at one from a medical perspective. (PDF)
[Marquardt, 2008b]
Klaus Marquardt. Performitis - part 2. Overload, 16(86), August 2008. Software problems have much in common with diseases. Klaus Marquardt has a diagnosis and offers some treatments. (PDF)
[Marquardt, 2008c]
Klaus Marquardt. Performitis (part 3). Overload, 16(87), October 2008. Prevention is better than cure. Klaus Marquardt suggests some treatments to avoid problems. (PDF)
[Matthews, 1999]
Hubert Matthews. When's an object not an object?. Overload, 7(34), December 1999.
[Matthews, 2003]
Hubert Matthews. Checkedint: A policy-based range-checked integer. Overload, 11(58), December 2003. (PDF)
[Matthews, 2007]
Hubert Matthews. Exceptional design. Overload, 15(77), February 2007. Hubert Matthews discusses some ways to design programs to use exceptions. (PDF)
[Maudel, 2013]
Olve Maudel. Demons may fly out of your nose. Overload, 20(115):12–13, June 2013. Language standards give guarantees about valid program behaviour. Olve Maudel discovers what happens if you break your end of the bargain. (PDF)
[McGuiness and Egan, 2012]
Jason McGuiness and Colin Egan. A DSEL for addressing the problems posed by parallel architectures. Overload, 20(111):13–18, October 2012. Programming parallel algorithms correctly is hard. Jason McGuiness and Colin Egan demonstrate how a C++ DESEL can make it simpler. (PDF)
[Merrells]
John Merrells.
[Merrells et al., 1997]
John Merrells, The Harpist, George Wendle, Francis Glasborow, and Chris Southern. editor << letters;. Overload, 5(22), October 1997. (PDF)
[Merrells, 1997a]
John Merrells. Editorial. Overload, 5(22):3–4, October 1997. (PDF)
[Merrells, 1997b]
John Merrells. Editorial. Overload, 5(21):3, August 1997. (PDF)
[Merrells, 1997c]
John Merrells. Editorial. Overload, 5(20):3–4, June 1997. (PDF)
[Merrells, 1997d]
John Merrells. Object counting. Overload, 5(21):24–27, August 1997. Whiteboard. (PDF)
[Merrells, 1997e]
John Merrells. Whiteboard. Overload, 5(21):20–21, August 1997. Whiteboard. (PDF)
[Merrells, 1997f]
John Merrells. Whiteboard. Overload, 5(20):35–36, June 1997. (PDF)
[Merrells, 1998a]
John Merrells. Beyond ACCU... patterns on the 'net. Overload, 6(29), December 1998.
[Merrells, 1998b]
John Merrells. Beyond ACCU... Patterns on the 'net. Overload, 6(27), August 1998. (PDF)
[Merrells, 1998c]
John Merrells. Broadening. Overload, 6(26):1, June 1998. Editorial. (PDF)
[Merrells, 1998d]
John Merrells. Editorial. Overload, 6(29), December 1998.
[Merrells, 1998e]
John Merrells. Editorial. Overload, 6(28), October 1998.
[Merrells, 1998f]
John Merrells. Editorial. Overload, 6(27), August 1998. (PDF)
[Merrells, 1998g]
John Merrells. Editorial. Overload, 6(25), April 1998. (PDF)
[Merrells, 1999a]
John Merrells. Editorial. Overload, 7(34), December 1999.
[Merrells, 1999b]
John Merrells. Editorial. Overload, 7(33), October 1999.
[Merrells, 1999c]
John Merrells. Editorial. Overload, 7(30), February 1999.
[Merrells, 1999d]
John Merrells. XML. Overload, 7(34), December 1999.
[Merrells, 2000a]
John Merrells. Editorial. Overload, 8(39), October 2000.
[Merrells, 2000b]
John Merrells. Editorial. Overload, 8(38), August 2000.
[Merrells, 2000c]
John Merrells. editorial. Overload, 8(35), February 2000.
[Merrells, 2000d]
John Merrells. editorial: Concerning patents. Overload, 8(40), December 2000.
[Merrells, 2001a]
John Merrells. Editorial. Overload, 9(45), October 2001. (PDF)
[Merrells, 2001b]
John Merrells. Editorial. Overload, 9(44), August 2001. (PDF)
[Merrells, 2001c]
John Merrells. Editorial. Overload, 9(43), June 2001.
[Merrells, 2001d]
John Merrells. Editorial. Overload, 9(42), April 2001.
[Merrells, 2001e]
John Merrells. Editorial. Overload, 9(41), February 2001.
[Merrells, 2001f]
John Merrells. Editorial - coming home. Overload, 9(46), December 2001. (PDF)
[Merrells, 2002a]
John Merrells. Editorial. Overload, 10(50), August 2002. (PDF)
[Merrells, 2002b]
John Merrells. Editorial. Overload, 10(49), June 2002. (PDF)
[Merrells, 2002c]
John Merrells. Editorial. Overload, 10(48), April 2002. (PDF)
[Merrells, 2002d]
John Merrells. Editorial - on writing. Overload, 10(52), December 2002. (PDF)
[Merrells, 2002e]
John Merrells. Editorial - software quality. Overload, 10(51), October 2002. (PDF)
[Merrells, 2002f]
John Merrells. Editorial: Product definition. Overload, 10(47), February 2002. (PDF)
[Merrells, 2003]
John Merrells. Editorial. Overload, 11(54), April 2003. (PDF)
[Meyers, 2012]
Scott Meyers. Universal references in C++11. Overload, 20(111):8–12, October 2012. C++11 provides a new reference syntax, T&&. Scott Meyers explains that it doesn’t always mean ‘rvalue reference’. (PDF)
[Microsoft, 1994]
Microsoft. Microsoft Visual C++ strategy. Overload, 2(5):21–27, September 1994.
[Midgley, 1995]
Dave Midgley. editor << letters;. Overload, 3(7):37, April 1995. (PDF)
[Midgly, 2001]
Dave Midgly. Editor << letters;. Overload, 9(42), April 2001.
[Miller, 2006]
Peter Miller. Recursive make considered harmful. Overload, 14(71):20–30, February 2006. (PDF)
[Mirwaisi, 2003]
Jeff Mirwaisi. A policy-driven CORBA template library to facilitate the rapid development of doc middleware. Overload, 11(57), October 2003. (PDF)
[Moene, 2010]
Martin Moene. One approach to using hardware registers in C++. Overload, 18(95), February 2010. Testing increases software reliability. Martin Moene presents a technique for checking the control of hardware. (PDF)
[Moene, 2014]
Martin Moene. Static polymorphic named parameters in C++. Overload, 20(119):4–6, February 2014. Adding parameters to an object can be messy. Martin Moene demonstrates how method chaining can make code more readable. (PDF)
[Moffatt, 1996]
Peter Moffatt. Explorations around a linked list. Overload, 4(15):6–11, August 1996. Software Development in C++. (PDF)
[Nadle, 2003]
David L. Nadle. A C++ Petri net framework for multithreaded programming. Overload, 11(54), April 2003. (PDF)
[Nasonov, 2004]
Alexander Nasonov. A little detail. Overload, 12(60), April 2004. (PDF)
[Nasonov, 2005]
Alexander Nasonov. Better encapsulation for the curiously recurring template pattern. Overload, 13(70), December 2005. (PDF)
[Nasonov, 2006a]
Alexander Nasonov. Fine tuning for lexical_cast. Overload, 14(74), August 2006. Alexander Nasonov takes a look at Boost's lexical_cast and addresses a common user request: "make it go faster". (PDF)
[Nasonov, 2006b]
Alexander Nasonov. The singleton in C++ - a force for good?. Overload, 14(76), December 2006. Alexander Nasonov addresses some problems that arise when using Singleton in C++. (PDF)
[Nasonov, 2007]
Alexander Nasonov. Letter to the editor. Overload, 15(77), February 2007. Alexander Nasonov writes more on singleton. (PDF)
[Neri, 2012]
Cassio Neri. Complex logic in the member initialiser list. Overload, 20(112):8–13, December 2012. The syntactic form of the member initialiser list restricts the logic that it contains. Cassio Neri presents some techniques to overcome these constraints. (PDF)
[Nilsen-Nygaard, 1997a]
Einar Nilsen-Nygaard. A finite state machine design. Overload, 5(21):21–24, August 1997. Whiteboard. (PDF)
[Nilsen-Nygaard, 1997b]
Einar Nilsen-Nygaard. A finite state machine design II. Overload, 5(23):28–34, December 1997. Whiteboard. (PDF)
[Nilsen-Nygaard, 1999a]
Einar Nilsen-Nygaard. Editorial. Overload, 7(32), June 1999.
[Nilsen-Nygaard, 1999b]
Einar Nilsen-Nygaard. Editorial. Overload, 7(31), April 1999.
[Noyes, 2014]
Malcolm Noyes. Integrating the Catch test framework into Visual Studio. Overload, 20(119):7–10, February 2014. Visual Studio’s Test Explorer allows native C++ tests to be run under a managed wrapper. Malcolm Noyes takes it a step further using Catch to drive the tests. (PDF)
[Oldwood, 2013a]
Chris Oldwood. Causality – relating distributed diagnostic contexts. Overload, 20(114):18–23, April 2013. Supporting a system with many moving parts can be hard. Chris Oldwood demonstrates one way to add tags to log information to aid diagnosis. (PDF)
[Oldwood, 2013b]
Chris Oldwood. Migrating from visual sourcesafe to git. Overload, 20(118):16–20, December 2013. Migrating from one version control system to another is a big change. Chris Oldwood records the trials and triumphs of migrating from VSS to git. (PDF)
[Oldwood, 2013c]
Chris Oldwood. Simple instrumentation. Overload, 20(116):6–10, August 2013. Programs often run out of memory or grind to a halt. Chris Oldwood demonstrates how to add instrumentation to your code to track its performance. (PDF)
[Oldwood, 2013d]
Chris Oldwood. Utilising more than 4GB of memory in 32-bit Windows process. Overload, 20(113):7–11, February 2013. Some applications require a vast amount of memory. Chris Oldwood presents techniques to provide extra memory. (PDF)
[O'Neil, 2005]
David O'Neil. Two-thirds of a pimpl and a grin. Overload, 13(70), December 2005. (PDF)
[Orr, 2004a]
Roger Orr. Efficient exceptions?. Overload, 12(61), June 2004. (PDF)
[Orr, 2004b]
Roger Orr. Microsoft Visual C++ and Win32 structured exception handling. Overload, 12(63), October 2004. Source: Microsoft Visual c++, structured exception handling. (PDF)
[Orr, 2005a]
Roger Orr. Investigating java class loading. Overload, 13(68), August 2005. (PDF)
[Orr, 2005b]
Roger Orr. Microsoft symbol engine. Overload, 13(67), June 2005. (PDF)
[Orr, 2007a]
Roger Orr. Java protocol handlers. Overload, 15(82), December 2007. Roger Orr demonstrates the use of Java's URL handling to make code independent of the source of data. (PDF)
[Orr, 2007b]
Roger Orr. Release mode debugging. Overload, 15(80), August 2007. Although we try not to put bugs into software, sometimes we must track them down to remove them. Roger Orr considers the difficulties when they can only be seen in release builds. (PDF)
[Orr, 2008]
Roger Orr. When things go wrong. Overload, 16(83), February 2008. Can we reduce the pain of computer problems? (PDF)
[Orr, 2013a]
Roger Orr. Auto – a necessary evil?. Overload, 20(115):4–7, June 2013. Superficially simple language features can be surprisingly complicated. Roger Orr explores a new one that is likely to be used widely. (PDF)
[Orr, 2013b]
Roger Orr. Auto – a necessary evil? (part 2). Overload, 20(116):21–24, August 2013. Should you declare (almost) everything auto? Roger Orr considers when auto is appropriate. (PDF)
[Oualline, 1996]
Steve Oualline. Practical C++ Programming a response from steve oualline. Overload, 4(14):20, June 1996. Reviews. (PDF)
[Overload, 2007]
Overload. Guidelines for contributors. Overload, 15(80), August 2007. Thinking of writing for us? Follow these guidelines to help smooth the way. (PDF)
[Page, 1993]
Steve Page. Starting out with OWL. Overload, 1(1), April 1993.
[Parkin, 2004]
Ric Parkin. Garbage collection and object lifetime. Overload, 12(63), October 2004. (PDF)
[Parkin, 2007]
Ric Parkin. While the cat's away... Overload, 15(81), October 2007. ...instead of spending your time playing, why not learn to be multi-lingual in a multi-cultural world? (PDF)
[Parkin, 2008a]
Ric Parkin. The invisible hand. Overload, 16(87), October 2008. Large groups can behave as one, but how predicatable are they? (PDF)
[Parkin, 2008b]
Ric Parkin. It's good to talk... Overload, 16(86), August 2008. Writing code is only part of developing software. (PDF)
[Parkin, 2008c]
Ric Parkin. Plus ça change. Overload, 16(85), June 2008. Our job titles seem to be dictated as much by fashion as by anything else. Does it matter? It does to some. Oh, and Overload has a new editor. (PDF)
[Parkin, 2008d]
Ric Parkin. The sweet smell of success. Overload, 16(88), December 2008. If your last project wasn't successful, you're not alone... (PDF)
[Parkin, 2009a]
Ric Parkin. All together now. Overload, 17(93), October 2009. Can you do several things at once? Ric Parkin tries multi-tasking. (PDF)
[Parkin, 2009b]
Ric Parkin. Back to school. Overload, 17(90), April 2009. Much is made of the Knowledge Economy. But just how can you keep up to date? (PDF)
[Parkin, 2009c]
Ric Parkin. A good craftsman knows his tools. Overload, 17(91), June 2009. Are you using the right ones? Ric Parkin looks in his toolbox... (PDF)
[Parkin, 2009d]
Ric Parkin. Moments in history. Overload, 17(92), August 2009. Technology shapes our world. Ric Parkin looks back at 40 years of change. (PDF)
[Parkin, 2009e]
Ric Parkin. Watt's going on?. Overload, 17(89), February 2009. Just how much power are you using... (PDF)
[Parkin, 2010a]
Ric Parkin. The art of the possible. Overload, 18(97), June 2010. In polite company you should never talk about religion or politics. Ric Parkin makes an exception. (PDF)
[Parkin, 2010b]
Ric Parkin. Back to the future. Overload, 18(95), February 2010. The last decade has seen huge changes. Ric Parkin looks at technology and its effects. (PDF)
[Parkin, 2010c]
Ric Parkin. Dealing with growing pains. Overload, 18(96), April 2010. Expanding your team is never easy. Ric Parkin experiences the recruiting process. (PDF)
[Parkin, 2010d]
Ric Parkin. Lies, damn lies, and statistics. Overload, 18(99):2–3, October 2010. Making a good decision is vital. Ric Parkin looks at what information we use. (PDF)
[Parkin, 2010e]
Ric Parkin. A little learning is a dangerous thing. Overload, 18(98):2–3, August 2010. An opportunity for nostalgia triggers some musings on the value of education. Ric Parkin goes back to school. (PDF)
[Parkin, 2010f]
Ric Parkin. Numbers and the appliance of science. Overload, 18(100):2–3, December 2010. How sure are you of something? Ric Parkin considers how we build models, and celebrates a milestone. (PDF)
[Parkin, 2011a]
Ric Parkin. Ah! the fog is lifting! Overload, 19(101):2–3, February 2011. Futurology has a dismal track record. Ric Parkin looks at the history of technology predictions. (PDF)
[Parkin, 2011b]
Ric Parkin. Can you keep a secret? Overload, 19(103):2, June 2011. Privacy and security have been in the news a lot recently. Ric Parkin looks behind the curtain. (PDF)
[Parkin, 2011c]
Ric Parkin. A journey through history. Overload, 19(105):2–3, October 2011. Despite early pioneers, the computer revolution is relatively young. Ric Parkin takes a personal tour. (PDF)
[Parkin, 2011d]
Ric Parkin. Patently ridiculous! Overload, 19(106):2, December 2011. Software patents have a chequered history. Ric Parkin looks at some of the problems. (PDF)
[Parkin, 2011e]
Ric Parkin. Rise of the machines. Overload, 19(104):2, August 2011. Been having trouble with technology or simple devices? Ric Parkin fears for our future. (PDF)
[Parkin, 2011f]
Ric Parkin. This year’s model. Overload, 19(102):2, April 2011. Design and development requires us to think about the world. Ric Parkin considers some ways of coping with the complexity. (PDF)
[Parkin, 2012a]
Ric Parkin. The computing revolution will be televised (again). Overload, 20(108):2–3, April 2012. 30 years ago we had to plug our first computers into the TV. Ric Parkin looks at how far we’ve come since then. (PDF)
[Parkin, 2012b]
Ric Parkin. It’s not what you know, it’s who you know most human endeavours are not solitary pursuits. Overload, 20(109):2, June 2012. Ric Parkin looks at the interconnection of everyone. (PDF)
[Parkin, 2012c]
Ric Parkin. Many hands make light work. Overload, 20(107):2–3, February 2012. Some people say the parallel revolution is coming. Ric Parkin argues it’s in full swing. (PDF)
[Parkin, 2013]
Ric Parkin. Fantasy languages. Overload, 20(115):2–3, June 2013. Software is all about describing a solution to a computer. Ric Parkin imagines what his ideal dialect would sound like. (PDF)
[Parking, 2009]
Ric Parking. A crack in time. Overload, 17(94):2, December 2009. Encoding messages has a long history. Ric Parking looks back at how this affected computing. (PDF)
[Penhey]
Tim Penhey.
[Penhey, 2006a]
Tim Penhey. Dead code. Overload, 14(71):13–15, February 2006. (PDF)
[Penhey, 2006b]
Tim Penhey. Multithreading 101. Overload, 14(72), April 2006. (PDF)
[Percy, 1996a]
Richard Percy. Go with the flow. Overload, 4(15):11–15, August 1996. Software Development in C++. (PDF)
[Percy, 1996b]
Richard Percy. Go with the flow - part II. Overload, 4(16):8–13, October 1996. Software Development in C++. (PDF)
[Percy, 1997]
Richard Percy. A model for backsolving. Overload, 5(19):24–29, April 1997. C++ Techniques. (PDF)
[Petersen, 2006]
Adam Petersen. Objects for states. Overload, 14(73), June 2006. Originally captured in Design Patterns, Objects for States is described in close conjunction with the Singleton pattern. This article investigates better alternatives for implementing the pattern in C++. (PDF)
[Petersen, 2007]
Adam Petersen. Design in test-driven development. Overload, 15(78), April 2007. With its roots in Japanese just-in-time manufacturing, Test-Driven Development (TDD) puts the traditional development process on its head. Adam Petersen discusses when to use TDD, how to use it successfully, and its use in up-front design. (PDF)
[Petersen, 2013]
Adam Petersen. The signs of trouble: On patterns, humbleness and Lisp. Overload, 20(113):12–13, February 2013. Patterns can be a controversial topic. Adam Petersen considers their cognitive and social value. (PDF)
[Pilgrim, 1997]
Peter A. Pilgrim. Debug new and delete, preamble. Overload, 5(23):34–37, December 1997. Whiteboard. (PDF)
[Pilgrim, 1998a]
Peter Pilgrim. Debuggable new and delete, part two. Overload, 6(25):29–34, April 1998. Whiteboard. (PDF)
[Pilgrim, 1998b]
Peter A. Pilgrim. Debug new and delete part 3. Overload, 6(29), December 1998.
[Pilgrim, 2000]
Peter A. Pilgrim. An implementation of double dispatch in Java. Overload, 8(36), April 2000.
[Pinchbeck, 2001a]
Antony Pinchbeck. Thread pooling: An investigation. Overload, 9(41), February 2001.
[Pinchbeck, 2001b]
Antony Pinchbeck. Typesafe registry for Windows. Overload, 9(42), April 2001.
[Polton, 2010]
Richard Polton. The functional student: A game of six integers. Overload, 18(97), June 2010. The Countdown numbers game is a popular challenge. Richard Polton tries a new language to solve it. (PDF)
[Posul, 2000]
Waldo Posul. File headers. Overload, 8(35), February 2000.
[Poynter, 2004]
Ray Poynter. Letters to the editor(s). Overload, 12(60), April 2004. (aka Dr Ray Poynter CEng CPhys MBCS MInstP). (PDF)
[Quintel, 1999]
Henrik Quintel. Garbage collection implementation considerations. Overload, 7(30), February 1999.
[Radford, 1997]
Mark Radford. Observations on the design of an address class. Overload, 5(19):4–5, April 1997. Software Development in C++. (PDF)
[Radford, 1998]
Mark Radford. Protecting member data's right to privacy. Overload, 6(24):28–31, February 1998. Whiteboard. (PDF)
[Radford, 1999]
Mark Radford. Factories in C++: disposing of the product. Overload, 7(31), April 1999.
[Radford, 2001a]
Mark Radford. Designing C++ interfaces - exception safety. Overload, 9(43), June 2001.
[Radford, 2001b]
Mark Radford. Designing C++ interfaces - templates. Overload, 9(44), August 2001. (PDF)
[Radford, 2001c]
Mark Radford. Extensibility - a reason for using streams in C++. Overload, 9(41), February 2001.
[Radford, 2002]
Mark Radford. Patterns collaborations: Observer and composite. Overload, 10(51), October 2002. (PDF)
[Radford, 2003a]
Mark Radford. Reshaping an old piece of design. Overload, 11(56), August 2003. (PDF)
[Radford, 2003b]
Mark Radford. Singleton - the anti-pattern!. Overload, 11(57), October 2003. (PDF)
[Radford, 2004a]
Mark Radford. C++ interface classes - an introduction. Overload, 12(62), August 2004. (PDF)
[Radford, 2004b]
Mark Radford. Editorial. Overload, 12(60), April 2004. (PDF)
[Radford, 2004c]
Mark Radford. Editorial. Overload, 12(59), February 2004. (PDF)
[Radford, 2004d]
Mark Radford. Editorial: The buzzword adoption pattern?. Overload, 12(63), October 2004. (PDF)
[Radford, 2005a]
Mark Radford. C++ interface classes - noise reduction. Overload, 13(68), August 2005. Interface classes are a principle mechanism for separating a class' interface from its implementation in C++. I wrote an introduction to interface classes in a previous article. In this article, I intend to explore interface classes - and their implementation classes - further. (PDF)
[Radford, 2005b]
Mark Radford. Taming complexity: A class hierarchy tale. Overload, 13(67), June 2005. (PDF)
[Radford, 2006a]
Mark Radford. C++ interface classes - strengthening encapsulation. Overload, 14(76), December 2006. Mark looks at the separation of interface and implementation in C++, and how the separation helps to strengthen encapsulation. (PDF)
[Radford, 2006b]
Mark Radford. Friend or foe!. Overload, 14(71):18–19, February 2006. (PDF)
[Rahman, 1995]
Fazl Rahman. editor << letters;. Overload, 3(8):40, June 1995. (PDF)
[Rahman, 2004]
Fazl Rahman. Transforming XML with XSLT. Overload, 12(60), April 2004. (PDF)
[Reese, 2011]
Bjørn Reese. Thread-safe access guards. Overload, 19(104):10–12, August 2011. Ensuring safe access to shared data can be cumbersome and error-prone. Bjørn Reese presents a technique to help. (PDF)
[Rüegg, 2012a]
Michael Rüegg. Refactoring towards seams in C++. Overload, 20(108):29–32, April 2012. Breaking dependencies in existing code is hard. Michael Rüegg explains how seams can help and provides new automated refactorings for C++ to achieve them. (PDF)
[Rüegg, 2012b]
Michael Rüegg. Simple mock objects for C++11. Overload, 20(110):19–21, August 2012. New C++11 features can be used to implement mock objects for unit tests. Michael Rüegg shows us how he does this in Mockator. (PDF)
[Richards, 1997]
Eric Richards. Borland C++ Builder for expert programmers. Overload, 5(19):10–12, April 1997. Software Development in C++. (PDF)
[Ridout, 1998a]
Aaron Ridout. Editor << letters;. Overload, 6(28), October 1998.
[Ridout, 1998b]
Aaron Ridout. Shallow pointer. Overload, 6(28), October 1998.
[Ridout, 1999a]
Aaron Ridout. editor << letters;. Overload, 7(34), December 1999.
[Ridout, 1999b]
Aaron Ridout. editor << letters;. Overload, 7(33), October 1999.
[Ridout, 2000]
Aaron Ridout. editor << letters;. Overload, 8(37), June 2000.
[Rose, 1998]
Seb Rose. ‘There may be trouble ahead’. Overload, 6(24):31–34, February 1998. Whiteboard. (PDF)
[Rose, 1999]
Seb Rose. Objects in databases. Overload, 7(31), April 1999.
[Rose, 2003]
Seb Rose. Labouring: An analogy. Overload, 11(54), April 2003. (PDF)
[Rose, 2013a]
Seb Rose. Executable documentation doesn’t have to slow you down. Overload, 20(114):24–26, April 2013. Comprehensibility of end-to-end scenarios and quick feedback of unit tests are competing goals. Seb Rose introduces Cucumber with tags to meet both needs. (PDF)
[Rose, 2013b]
Seb Rose. Lies, damn lies and estimates. Overload, 20(117):9–11, October 2013. Predicting how long something will take is hard. Seb Rose takes us on a brief tour through the swamp that is estimation. (PDF)
[Ross, 1996a]
Alec Ross. Circles and ellipses revisited. Overload, 4(15):24–27, August 1996. C++ Techniques. (PDF)
[Ross, 1996b]
Alec Ross. Circles and ellipses revisited: coding techniques – an introduction. Overload, 4(16):15–18, October 1996. C++ Techniques. (PDF)
[Ross, 1997a]
Alec Ross. Circles and ellipses revisited: coding techniques - 2. Overload, 5(17/18), January 1997. A second approach: In-store changes.
[Ross, 1997b]
Alec Ross. Circles and ellipses revisited: Coding techniques – 3. Overload, 5(21):4–7, August 1997. Software Development in C++. (PDF)
[Rosvall, 2004a]
Sven Rosvall. C++ as a safer C. Overload, 12(59), February 2004. (PDF)
[Rosvall, 2004b]
Sven Rosvall. C++ lookup mysteries. Overload, 12(63), October 2004. (PDF)
[Rumsby, 1995]
Steve Rumsby. C++ – the official UK site maintained by Steve Rumsby. Overload, 3(8):15, June 1995. The Draft International C++ Standard. (PDF)
[Rutland, 1995]
Nicholas Rutland. editor << letters;. Overload, 3(7):40, April 1995. (PDF)
[Saha, 2011]
Arun Saha. Benefits of well known interfaces in closed source code. Overload, 19(102):4–7, April 2011. Designing a good API is a significant challenge. Arun Saha suggests taking inspiration from outside. (PDF)
[Scattergood, 1995]
Bryan Scattergood. From polymorphism to garbage collection. Overload, 3(8):36–39, June 1995. (PDF)
[Schoenborn, 2001a]
Oliver Schoenborn. Editor << letters;. Overload, 9(42), April 2001.
[Schoenborn, 2001b]
Oliver Schoenborn. Where is __FUNCTION__?. Overload, 9(41), February 2001.
[Schoenborn, 2002]
Oliver Schoenborn. Tiny template tidbit. Overload, 10(47), February 2002. (PDF)
[Schoenborn, 2003]
Oliver Schoenborn. Addendum to "Tiny Template Tidbit". Overload, 11(54), April 2003. (PDF)
[Sebright, 2004]
Simon Sebright. Letters to the editor(s). Overload, 12(60), April 2004. (PDF)
[Sebright, 2006]
Simon Sebright. Up against the barrier. Overload, 14(75), October 2006. A discussion of development against the odds, describing process, personal and environmental barriers between the people and the job they are trying to do. (PDF)
[Sebright, 2007]
Simon Sebright. A perspective on use of conditional statements versus assertions. Overload, 15(78), April 2007. Simon Sebright offers us the benefit of his experience. (PDF)
[Sedge, 2011]
Tom Sedge. Systems thinking software development. Overload, 19(103):24–30, June 2011. Many processes cause more problems than they solve. Tom Sedge shows how to tailor your own. (PDF)
[Seifort, 1994]
Justin Seifort. Shared memory class. Overload, 2(4), February 1994.
[Shagov, 2006]
George Shagov. Inventing a mutex. Overload, 14(75), October 2006. A mutex is a general purpose tool - there may be better solutions in specific circumstances. George Shagov presents one such alternative. (PDF)
[Sharp, 2010]
Helen Sharp. What motivates software developers: a workshop report. Overload, 18(99):10–13, October 2010. Keeping your team happy should be more than guesswork. Helen Sharp went and asked you. (PDF)
[Short, 1993]
Graham Short. A short exposure to C++. Overload, 1(3), August 1993.
[Shotton, 1995]
Phil Shotton. editor << letters;. Overload, 3(7):35, April 1995. (PDF)
[Shriver, 2009]
Ryan Shriver. Measurable value with agile. Overload, 17(89), February 2009. Are you solving the right problem or simply solving the problem right? Ryan Shriver shows us that both are needed for value delivery. (PDF)
[Simons, 1995]
Christopher Simons. editor << letters;. Overload, 3(7):36–37, April 1995. (PDF)
[Slettebø, 2005]
Terje Slettebø. Letters to the editor. Overload, 13(67), June 2005. (PDF)
[Smart, 1995]
John Smart. A text formatting class. Overload, 3(6), March 1995.
[Smart, 1996]
John Smart. Handling dates with locale based day and month information. Overload, 3(12):29–34, February 1996. ++puzzle;. (PDF)
[Smith, 2001]
Julian Smith. Multimethods. Overload, 9(42), April 2001.
[Sommerlad, 2006]
Peter Sommerlad. C++ unit testing easier: CUTE. Overload, 14(75), October 2006. Peter Sommerlad presents a lightweight framework for C++ unit testing. (PDF)
[Southern, 1996]
Chris Southern. Java in a Nutshell reviewed by Chris Southern. Overload, 4(15):37, August 1996. (PDF)
[Southern, 1999]
Chris Southern. Response to "patterns - the abstract factory" (Francis Glassborow, Overload 30). Overload, 7(31), April 1999.
[Sposato, 2003]
Rich Sposato. A more flexible container. Overload, 11(58), December 2003. (PDF)
[Steinbach, 2013]
Alf Steinbach. Portable string literals in C++. Overload, 20(116):11–15, August 2013. How hard can it be to make a file in C++ with international text literals in its name? Alf Steinbach shows us. (PDF)
[Stroustrup, 1998]
Bjarne Stroustrup. Generalizing overloading for C++2000. Overload, 6(25):20–24, April 1998. The Draft International C++ Standard. (PDF)
[Stroustrup, 2009]
Bjarne Stroustrup. No 'concepts' in C++0x. Overload, 17(92), August 2009. There have been some major decisions made about the next C++ Standard. Bjarne Stroustrup explains what's changed and why. (PDF)
[Summerfield, 1994]
M.N. Summerfield. Are “safe” computer systems possible?. Overload, 2(5):5–7, September 1994.
[Summerfield, 2011]
Mark Summerfield. Concurrent programming with go. Overload, 19(106):25–28, December 2011. Concurrency is becoming ever more important. Mark Summerfield looks at the approach of the new language Go. (PDF)
[Surman, 2011]
Eugene Surman. Queue with position reservation. Overload, 19(101):4–7, February 2011. Multiple threads can make processing a message queue faster. Eugene Surman needs the right data structure. (PDF)
[Taylor, 2004]
Richard Taylor. Letters: The invisibility of software design. Overload, 12(61), June 2004. (PDF)
[Terje, 2005]
Terje. Letter to the editor. Overload, 13(66), April 2005. (PDF)
[the Harpist, 1999]
the Harpist. Micro-derivation & related ideas. Overload, 7(32), June 1999.
[Thomas, 2012]
Andy Thomas. Back to school. Overload, 20(108):12–13, April 2012. The Sinclair ZX Spectrum will be 30 years old in April 2012. Andy Thomas recalls how this plucky little home computer shaped his childhood. (PDF)
[Toms and Fagg, 1994]
Mike Toms and Adrian Fagg. Letters. Overload, 2(5):21, September 1994.
[Toms, 1993a]
Mike Toms. C++ streams. Overload, 1(1), April 1993.
[Toms, 1993b]
Mike Toms. C++ streams (part 2). Overload, 1(2), June 1993.
[Toms, 1993c]
Mike Toms. C++ strings -the ANSI way. Overload, 1(3), August 1993.
[Toms, 1993d]
Mike Toms. Class struggle. Overload, 1(3), August 1993.
[Toms, 1993e]
Mike Toms. Class struggle. Overload, 1(2), June 1993.
[Toms, 1993f]
Mike Toms. Class struggle. Overload, 1(1), April 1993. A basic introduction to the uses of C++.
[Toms, 1993g]
Mike Toms. Custom controls. Overload, 1(3), August 1993.
[Toms, 1993h]
Mike Toms. Dates & times. Overload, 1(1), April 1993.
[Toms, 1993i]
Mike Toms. An e-mail conversation with Bjarne Stroustrup. Overload, 1(2), June 1993.
[Toms, 1993j]
Mike Toms. Editor's ramble. Overload, 1(3), August 1993.
[Toms, 1993k]
Mike Toms. Editor's ramble. Overload, 1(2), June 1993.
[Toms, 1993l]
Mike Toms. Editor's ramble. Overload, 1(1), April 1993.
[Toms, 1993m]
Mike Toms. Epilogue. Overload, 1(3), August 1993.
[Toms, 1993n]
Mike Toms. Epilogue. Overload, 1(2), June 1993.
[Toms, 1993o]
Mike Toms. Epilogue. Overload, 1(1), April 1993.
[Toms, 1993p]
Mike Toms. The help compiler. Overload, 1(2), June 1993.
[Toms, 1993q]
Mike Toms. An introduction to object orientation. Overload, 1(1), April 1993.
[Toms, 1993r]
Mike Toms. Members' letters. Overload, 1(2), June 1993.
[Toms, 1993s]
Mike Toms. The pedant. Overload, 1(2), June 1993.
[Toms, 1993t]
Mike Toms. Readers letters. Overload, 1(3), August 1993.
[Toms, 1993u]
Mike Toms. Templates. Overload, 1(1), April 1993.
[Toms, 1993v]
Mike Toms. Whingeing session. Overload, 1(1), April 1993.
[Toms, 1994a]
Mike Toms. char* p vs char *p. Overload, 2(4), February 1994.
[Toms, 1994b]
Mike Toms. Editor's ramble. Overload, 2(4), February 1994.
[Toms, 1994c]
Mike Toms. Epilogue. Overload, 2(4), February 1994.
[Toms, 1994d]
Mike Toms. Readers letters. Overload, 2(4), February 1994.
[Toms, 1994e]
Mike Toms. Windows waffle. Overload, 2(4), February 1994.
[Tornhill, 2013]
Adam Tornhill. Code as a crime scene. Overload, 20(117):4–8, October 2013. Forensic techniques can predict possible future crimes. Adam Tornhill shows how they can be applied to code. (PDF)
[Tripp, 2003]
Jonathan Tripp. Embedded scripting languages. Overload, 11(55), June 2003. (PDF)
[Uemlianin, 2004]
Ivan Uemlianin. Letters: Software project management classics?. Overload, 12(61), June 2004. (PDF)
[van Laenen, 2011]
Filip van Laenen. Outsource your self-discipline. Overload, 19(105):12–14, October 2011. It’s all too easy to skip those tedious but vital steps towards code quality. Filip van Laenen suggests getting someone else to do them. (PDF)
[van Laenen, 2012]
Filip van Laenen. Mutation testing. Overload, 20(108):16–22, April 2012. We all know that testing improves our code, guarding against errors. Filip van Laenen asks how we know that the tests are comprehensive? (PDF)
[van Laenen, 2013]
Filip van Laenen. Wallpaper rotation on Ubuntu using ruby and flickr. Overload, 20(115):14–20, June 2013. Repetitive tasks are ideal candidates for scripting. Filip van Laenen walks us through a simple example. (PDF)
[Vanhout, 2008]
Roel Vanhout. Iterators and memberspaces. Overload, 16(88), December 2008. Exposing a compound object's collections can be messy. Roel Vanhout introduces a powerful idiom. (PDF)
[Vollmann and Walker, 2002]
Detlef Vollmann and Josh Walker. Letters to the editor. Overload, 10(52), December 2002. (PDF)
[Vollmann, 1998a]
Detlef Vollmann. Exception usage. Overload, 6(28), October 1998.
[Vollmann, 1998b]
Detlef Vollmann. Hotel case study comments. Overload, 6(27), August 1998. (PDF)
[Vollmann, 1998c]
Detlef Vollmann. Notes on exceptions. Overload, 6(28), October 1998.
[Vollmann, 1999a]
Detlef Vollmann. Exception handling alternatives. Overload, 7(30), February 1999.
[Vollmann, 1999b]
Detlef Vollmann. Exception handling alternatives (part 2). Overload, 7(31), April 1999.
[Vollmann, 1999c]
Detlef Vollmann. Software architecture. Overload, 7(34), December 1999.
[Vollmann, 2001a]
Detlef Vollmann. Metaclasses and reflection in C++. Overload, 9(45), October 2001. (PDF)
[Vollmann, 2001b]
Detlef Vollmann. Metaclasses and reflection in C++ - part 2. Overload, 9(46), December 2001. (PDF)
[Wakeling, 2007]
Ian Wakeling. Working with GNU export maps. Overload, 15(79), June 2007. Taking control over the symbols exported from shared libraries built with the GNU toolchain. (PDF)
[Wakely, 2013]
Jonathan Wakely. Letter to the editor. Overload, 20(113):24, February 2013. (PDF)
[Walker, 2001]
Josh Walker. Template metaprogramming. Overload, 9(46), December 2001. (PDF)
[Walker, 2002]
Josh Walker. Applied reading - taming shared memory. Overload, 10(51), October 2002. (PDF)
[Wang, 2012]
Wei Wang. Black-Scholes in hardware. Overload, 20(110):8–15, August 2012. The Black-Scholes model is a financial model. Wei Wang outlines its design and implementation for those who want to understand how algorithms can be implemented in hardware. (PDF)
[Wang, 2013]
Nan Wang. The open–closed principle (OCP). Overload, 20(113):14–15, February 2013. Changing requirements and environments can require cascading changes through software. Nan Wang demonstrates how the Open-Closed principle can minimise changes. (PDF)
[Watts, 1998]
Will Watts. Exception errors. Overload, 6(29), December 1998.
[Weltman, 2001]
Rob Weltman. .NET. Overload, 9(43), June 2001.
[Wendle, 1995a]
George Wendle. Operators – an overloaded menace. Overload, 3(7):12–14, April 1995. (PDF)
[Wendle, 1995b]
George Wendle. Overloading on const is wrong. Overload, 3(6), March 1995.
[Wendle, 1995c]
George Wendle. Quantum chromo typology. Overload, 3(9):5–7, August 1995. (PDF)
[Wendle, 1997a]
George Wendle. extern "X" and namespaces. Overload, 5(22):12–15, October 1997. (PDF)
[Wendle, 1997b]
George Wendle. Painting the bicycle shed. Overload, 5(20):8–10, June 1997. The Draft International C++ Standard. (PDF)
[White, 2002]
Steve White. Introduction to WOC: Abstracting OpenGL 3-D model definition and rendering with C++. Overload, 10(47), February 2002. (PDF)
[Wigley, 2002]
Oliver Wigley. Alternatives for partial template function specialisation. Overload, 10(50), August 2002. (PDF)
[Wild III, 1993]
Frederic H. Wild III. Managing class coupling. Overload, 1(3), August 1993.
[Williams, 2001a]
Anthony Williams. Flexible functors and binders. Overload, 9(44), August 2001. (PDF)
[Williams, 2001b]
Anthony Williams. A generic non-intrusive smart pointer implementation. Overload, 9(42), April 2001.
[Williams, 2001c]
Anthony Williams. Introduction to C++ templates. Overload, 9(45), October 2001. (PDF)
[Williams, 2002]
Anthony Williams. Pairing off iterators. Overload, 10(51), October 2002. (PDF)
[Williams, 2003]
Anthony Williams. EXPR_TYPE - an implementation of typeof using current standard C++. Overload, 11(54), April 2003. (PDF)
[Williams, 2005]
Anthony Williams. Letter to the editor. Overload, 13(70), December 2005. (PDF)
[Williams, 2006]
Anthony Williams. Implementing drop-down menus in pure CSS (no JavaScript). Overload, 14(73), June 2006. Implementing drop-down menus to aid website navigation is usually thought to require lots of JavaScript. This article shows how to do it using just CSS. (PDF)
[Williams, 2007]
Anthony Williams. Implementing synchronization primitives for Boost on Windows platforms. Overload, 15(78), April 2007. Anthony Williams on the popular Boost library. (PDF)
[Williams, 2008]
Anthony Williams. Exceptions make for elegant code. Overload, 16(86), August 2008. Anything that can go wrong, will go wrong. Anthony Williams compares ways of dealing with errors. (PDF)
[Williams, 2009]
Anthony Williams. Multi-threading in C++0x. Overload, 17(93):11–17, October 2009. Threading support is being added to C++. Anthony Williams introduces us to the new facilities. (PDF)
[Williams, 2011]
Anthony Williams. Picking patterns for parallel programs (part 1). Overload, 19(105):15–17, October 2011. Designing programs for multi-core systems can be extremely complex. Anthony Williams suggests some patterns to keep things under control. (PDF)
[Wilson, 2001]
Simon Wilson. String tokenization - a programmer's odyssey. Overload, 9(44), August 2001. (PDF)
[Wilson, 2009a]
Matthew Wilson. An introduction to fast format (part 1): The state of the art. Overload, 17(89), February 2009. Writing a good library is hard. Matthew Wilson compares some existing formatting libraries, and promises to do better. (PDF)
[Wilson, 2009b]
Matthew Wilson. An introduction to fastformat (part 2): Custom argument and sink types. Overload, 17(90), April 2009. A library should be customisable and have good performance. Matthew Wilson shows how to achieve both. (PDF)
[Wilson, 2009c]
Matthew Wilson. An introduction to fastformat (part 3): Solving real problems, quickly. Overload, 17(91), June 2009. A good library must be useful in practice. Matthew Wilson looks at usability and extendability. (PDF)
[Wilson, 2009d]
Matthew Wilson. Quality matters: A case study in quality. Overload, 17(94):26–32, December 2009. How do we assess quality? Matthew Wilson takes a look at the design of one library. (PDF)
[Wilson, 2009e]
Matthew Wilson. Quality matters: Correctness, robustness and reliability. Overload, 17(93), October 2009. What do we mean by quality? Matthew Wilson considers some definitions. (PDF)
[Wilson, 2009f]
Matthew Wilson. Quality matters: Introductions, and nomenclature. Overload, 17(92), August 2009. There are many aspects of Software Quality. Matthew Wilson introduces us to some of the concepts. (PDF)
[Wilson, 2010a]
Matthew Wilson. Quality matters #6: Exceptions for practically-unrecoverable conditions. Overload, 18(99):26–36, October 2010. Being robust is harder than you think. Matthew Wilson analyses a classic program. (PDF)
[Wilson, 2010b]
Matthew Wilson. Quality matters christmas intermezzo. Overload, 18(100):32, December 2010. Sometimes it’s good to reflect. Matthew Wilson considers what he’s learnt so far. (PDF)
[Wilson, 2010c]
Matthew Wilson. Quality matters: Diagnostic measures. Overload, 18(95), February 2010. How do we catch problems early? Matthew Wilson investigates the recls library. (PDF)
[Wilson, 2010d]
Matthew Wilson. Quality matters: The worst form of ‘error’. Overload, 18(98):28–32, August 2010. Handling Except For All The Others Dealing with errors is a vital part of good programming. Matthew Wilson specifies a taxonomy. (PDF)
[Wilson, 2013]
Matthew Wilson. Quality matters #7 exceptions: the story so far. Overload, 20(114):10–17, April 2013. Exception handling is difficult to get right. Matthew Wilson recaps the story so far. (PDF)
[Wippell, 1995a]
Peter Wippell. Another “too-many-objects” lesson. Overload, 3(9):33, August 1995. (PDF)
[Wippell, 1995b]
Peter Wippell. editor << letters;. Overload, 3(8):42, June 1995. (PDF)
[Wippell, 1995c]
Peter Wippell. A “too-many-objects” lesson. Overload, 3(8):39–40, June 1995. (PDF)
[Wippell, 1996]
Peter Wippell. I do not love thee, STL! Overload, 4(13):18–20, April 1996. C++ Techniques. (PDF)
[XXXAuthorXXX, 2014]
XXXAuthorXXX. Xxxtitlexxx. Overload, 20(120):XXXPagesXXX, April 2014. XXXNoteXXX. (PDF)
[Yakyma, 2011]
Alex Yakyma. Refactoring and software complexity variability. Overload, 19(102):21–23, April 2011. Most code bases could have their complexity improved. Alex Yakyma presents a model that suggests how to do this. (PDF)