Head and shoulders of a grey-bearded Daniel F. Dickinson looking slightly down and to the right (of the viewer)
Daniel F. Dickinson's introduction card

Contact Daniel via a contact form or on LinkedIn

Disambiguation: Sites that are not Daniel’s

Daniel F. Dickinson, in brief

Daniel Dickinson (he/him) has been using and exploring computer and electronic technologies for over three decades1. He is proficient with various flavours of Linux (including various ‘distros’ for desktop, server, and embedded systems) as well as modern Windows.

The code Daniel has written is scattered among various open source and proprietary projects2. For the interested, a number of Daniel’s current and old projects can be viewed at danielfdickinson on GitHub.

Daniel also enjoys sharing his knowledge with others and seeks to improve himself and the world around him. For an example; participating as a critical member of a team of volunteers in providing a successful programme for kids 8-12 (eight to twelve) called Bots and Bytes at the Midland Public Library. In the same vein, Daniel volunteers with the Gateway Centre for Learning in Midland, Ontario.

Resumes

One-page

Long version

Footnotes


  1. Daniel’s interest in tech began in grade school with the Commodore 64 (for which he wrote a hidden TSR3 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. ↩︎

  2. Since the proprietary projects are not owned by Daniel, he can’t show them to you. ↩︎

  3. People will tell you that this is technically impossible. If you have the right documentation (Daniel 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 Daniel had to swap out the kernel ROM to access the RAM underneath). Daniel thinks he even has a printout of the code somewhere in his residence. ↩︎