Seldom without a computer of some sort since graduating from the University of British Columbia in 1978, I have been a full-time Linux user since 2005, a full-time Solaris and SunOS user from 1986 through 2005, and UNIX System V user before that.
On the technical side of things, I have spent a great deal of my career as a consultant, doing data analysis and visualization; especially spatial data analysis. I have a substantial amount of related programming experience, using C, awk, Java, Python, PostgreSQL, PostGIS and lately Groovy. I'm looking at Julia with great interest. I have also built a few desktop and web-based applications, primarily in Java and lately in Grails with lots of JavaScript on the front end and PostgreSQL as my database of choice.
Aside from that, I spend a considerable amount of time writing proposals, technical reports and - of course - stuff on https://www.opensource.com.
Authored Comments
Thanks for the comment, Peter. And please feel free to write another article on QGIS for opensource.com. I'm planning to do some more.
Hi Sander, thanks for writing! I struggled with what to do about players that use gstreamer. As far as I can determine, it doesn't mess with the bit stream as long as the gain is set to 1 and the hardware device can accept the format and bit rate of the bit stream. But still it bothers me that it's there. Should I have docked points for players that (unnecessarily, in my case) incorporate this extra processing step, even if it's apparently transparent? Maybe I should have.