Matthew D. Groves
This blog has gone through a lot of changes since its early days. I used to blog a lot about politics, interesting news stories, pop culture, and generally nerdy stuff. These days, I mainly blog about programming and software development, with the occasional other tidbits thrown in.
Since I started this blog, I’ve become a father of two kids, I’ve obtained an MBA and a PMP, and I’ve switched jobs twice. I used to work for The Ohio State University, and Quick Solutions after that. I currently work for Telligent as a software development engineer. I also will take part in “side” projects from time-to-time: contracting on small projects, writing, contributing to open source projects, Android development–whatever strikes my fancy or helps me to provide for my family.
I’m also heavily involved in the developer community. I have been an officer in the Central Ohio .NET Developer’s Group. I also attend many local developer events, as well as the occasional speaking engagement. I run a blog about aspect-oriented programming (AOP) called CrossCuttingConcerns.com.
Beyond computers, I enjoy watching baseball (the Cincinnati Reds), movies, TV, and books, etc, storage auctions, and spending time with my family.
Ways to contact me:
- Twitter: @mgroves
- Email: webmaster -at- this domain
- Leave a comment on one of the blog posts.
All of the opinions of this blog where the author is “mgroves” are mine alone, the other author’s opinions are theirs alone. There is no affiliation, implicit or otherwise, between the views expressed on this blog and any company that I work or have worked for. If there is any material on my site that harms you (in a legal sense), please contact me immediately and I will most likely remove the content, no questions asked. If you would like to use any of the content of this site for any reason, feel free to do so at your own risk. All the information is for entertainment purposes only, and I make no warranty about my site’s content, and if applying it results in voided warranties, legal action, security holes, or anything else, the responsibility is your own.