Technology should empower people, never restrict them.
A History of Porting Software I've been involved in creating and maintaining commercial and open source software for as long as I can remember, reaching back to 1996 when the world wide web was in its infancy, and Java wasn't even a year old. I was attracted to the NetBSD project because of its focus on having... Continue Reading →
Wearable Technology I've been having a bit of fun with Google Glass recently. If you haven't come across Google Glass before, I'd describe it as a pair of glasses you can wear that give you personal, voice controlled, simple computer. Now I don't personally believe Google Glass is a product that is going to go mass-market... Continue Reading →
What is ApiDoc ApiDoc is a tool for creating a set of technical API documents to help developers using your libraries or classes. As a .NET developer you've probably used the MSDN references for various .NET classes on a regular basis. But how do you make the same style of documentation available to your team... Continue Reading →
If like me you've worked with C# and the .NET framework for years then you will probably have written variations on following code hundreds of time when trying to display values on screen or save values into text based files or SQL statements: The code itself is simple enough to get right first time, and easy... Continue Reading →
Getting Involved with Mvpc The Mvpc reference libraries used by all developers in Ambidect are also available to invited partners and developers. If you are interested in working with the Mvpc libraries yourself or within your company drop me an email and we'll see if we can get you building cross-platform multi-device applications too. Using the... Continue Reading →
Asynchronous APIs are becoming more popular thanks in part to the focus on asynchronous user interface design requirements on platforms such as Windows Store Applications for Windows 8 and Windows RT. This attempt to change the way developers think about long or unpredictable operations is welcome and necessary as databases and files slowly migrate into... Continue Reading →
This is the second post in the series of covering each layer of Mvpc. This article covers the View Layer. You can find the previous post on the Model Layer here. View Layer Reponsiblities Within Mvpc the view layer has very specific responsibilities. In particular the view layer is responsible for: Displaying and formatting data... Continue Reading →
When the var keyword was first added to the C# language many developers shyed away from it believing it to be a "Variant" type like found in VB.NET or the equivalent of declaring an variable as an object. Both of these are wrong, but despite this I've come across plenty of companies that still ban... Continue Reading →
Overview of the Model Layer The Mvpc design pattern is based on four layers: Model View Presenter Command This article is part of a series covering each layer of the Mvpc design pattern in detail. This post covers the Model layer. The model layer itself takes on four core responsibilities that are exclusive to itself:... Continue Reading →
Scott is passionate in following his vision of technology that engages with and empowers people. His extensive work in software development has always been focused on eliminating the barriers caused by devices, poor vendor compatibility, culture, and geographical location. It’s his strong belief that everybody should always be supported in learning new things, in nurturing great ideas, and in collaborating with others. In Scott’s view the role of technology in the world is to enable people and their growth, never to restrict it.
A long term activist for and contributor to permissive open source and idea sharing, Scott has a undying passion for building on great ideas rather than forcing reinvention, and encourages others to do the same.
Scott is currently Technical Director at Ambidect Ltd. and works with industry leading companies to create software and learning strategies built around enabling, engaging, and empowering people, not processes.
