Debugger
From APIDesign
Debugger is a program that helps to find out what other programs are doing. Often people use debugger to understand why their own code does not do, what they would like it to do. However debugger is incredibly useful for other purposes as well. Here the story.
Contents |
Building Modular systems
Chapter 1 of TheAPIBook discusses the art of building modern software systems and concludes that these days we are building systems that we don't understand. As an example it mentions that in order to write a web page one needs to understand HTML and possibly a Servlet API, but you don't need to have knowledge of anything that lays below: Glassfish server, Java VM, Unix libraries, Linux kernel, the VirtualBox nor even the hardware. At the end you can deploy a massive solution and in fact understand roughly one percent of it!
Some people may find it freightening that we use systems without real understanding, but The Art of Building Modern Software chapter concludes that such level of cluelessness is OK and in fact completely necessary. Brain has limited capacity, and the learning time is finite as well. As such we just can't understand everything. It is enough to know just the surface:
- the Servlet API - but not its actual implementation in the Glassfish server
- the user or command line interface of VirtualBox - to install Linux into it and to launch it
- the apt CLI - to install Java and Glassfish
Knowing these interfaces is enough. The details behind them are unimportant (if things go well).
Btw. this is also the reason why API design is important. Well designed application programming interfaces encourage cluelessness. The less knowledge people need to use a technology, the better the technology is. That is why read TheAPIBook and learn how to do it! But let's now get back to topic of debugging.
Cluelessness of an API User
I am using word cluelessness for the blessed state when one does not need to know the internals behind APIs. However in fact I mean selective cluelessness: when there is no need to know to make things work, the less we know the better.
However when things go wrong, then we should concentrate on what is wrong and get as deep knowledge of the affected area as possible. We should select that we want to know everything about a particular part of (for example) Glassfish and learn every detail about it (for example why it throws NullPointerException).
These days it should not be hard to increase our knowledge about our libraries. Most of them are OpenSource and thus getting access to their source code is easy. Putting a breakpoint on appropriate line, launching own application under debugger is usually easy as well. Moreover it is also easy to play with the code - modify a line, compile (using Maven or make) and use the modified version. There are no barriers to increase our knowledge about Glassfish, Java, Linux, etc.
In spite of the above easiness, I don't see people doing it. I don't see them looking at sources of libraries they use. Rather than that they treat them as blackbox. In spite of all the freedom we have, we decided to stay clueless (in the negative meaning, with the selective part).
blackbox. google things out.
Knowing Every Detail
maven, NetBeans Platform (customer) and iOS, open source
When Things Don't Happen
originally for things went wrong, now often for things that don't happen.
Follow
