Photo & Cards
Daniel Dickinson has been using and exploring computer and electronic technologies for over three decades1. He is proficient with various flavours of Linux (including varieties of desktop, server, and embedded systems) as well as modern Windows.
Daniel still enjoys software and firmware development, but prefers integration and extending existing open source solutions to quickly achieve desired goals2.
The code Daniel has written is scattered among various open source and proprietary projects3. For the interested, a number of current projects can be viewed at danielfdickinson on GitHub4. Daniel also created some history of public projects which he created, or to which he has contributed, at the dfd-code-history ‘organization’ on GitHub.
Daniel also enjoys sharing his knowledge with others. This included participating as a critical member of a team of volunteers to provide a successful programme for kids 8-12 (eight to twelve) called Bots and Bytes, for the Midland Public Library. In the same vein, Daniel volunteers with the Gateway Centre for Learning in Midland, Ontario.
Daniel’s interest in tech began in grade school with the Commodore 64 (for which he wrote a hidden TSR5 early in his high school career, not realizing the implications of what he was doing). This interest carried onto PC’s with DOS, then Windows 3.1, and continues with the current generation of desktop, mobile, and embedded (smart) devices and covers multiple operating systems. ↩︎
This is in part ‘informed laziness’ (the realization that most of the time reinventing the wheel doesn’t create a significantly ‘better’ wheel, just a different wheel). In short he has discovered the importance of depending on the work of others. ↩︎
Since the proprietary projects are not owned by Daniel, he can’t show them to you. ↩︎
People will tell you that this is technically impossible. If you have the right documentation (I had the Jim Butterfield books), use the chainable hook (wedge) for the keyboard, and (prevented on modern operating systems and hardware) use self-modifying and self-relocating code (and you don’t know or believe that it’s impossible) you can make magic happen. Of course the technique ends up meaning you have to use special tricks if you cannot avoid using the kernel routines (because part of the secret was that I had to swap out the kernel ROM to access the RAM underneath). I think I’ve even got a printout of the code somewhere in the house. ↩︎