September 03, 2008

My Book Reading Journal

I'm keeping a reading journal on my wiki. I'm trying as time permits to write some reactions and thoughts that are churned up by the reading in sub pages, but lately I've just posted a link indicating that I've read something.

I'm posting some of my past readings to but only if I re-look at the book or find myself recalling/using the resource in some way. I also sometimes reference a good article on the reading list, but I read so many of those I don't think I could manage listing them.

I found a nice little tool to pound material into my head when I don't have motivation to read an article. It is called Spreeder as in Speed/Reader. I usually turn it up to 450 word per minute and let'r rip. (my poor brain!)

Continue reading "My Book Reading Journal" »

December 13, 2007

YouTube Mac wants to be a PC commercial Mash-up

I just posted a terrible, poorly editted, little video showing Mac (from the Get a Mac ads) trying to show how he is a PC. I through this together to try get something free from a contest. My friend Kevin Reynen once said the most useful app a Mac can run is Microsoft Windows and this is my omage to his intelligence.

This was created for a MaxiumPC contest to win a 8Gig Sansa Media Player

Enjoy Mac wants to be a PC!

August 22, 2007

OIT page on NetFiles

In an attempt to raise the OIT search word ranking in the U of M g00gle appl1ance I've created a file in NetFiles that point to the https://wiki.umn.edu/view/CraigGjerdingen/OfficeOfInformationTechnology page. Please ignore this shameless promotion.

June 29, 2007

OIT Alphabet Soup

ADCS, ATAC, CESL, CITP, DMC, EFT, iFellow, iRoc, NTS, OIR, OIT, OVPR, TEL, UTELL, WebCT... Oh my, can you tell someone has let the Linux geeks run the shop for a while. To help short through the alphabet soup that is the Office of Information Technology OIT at the U of M, I've added a section to my site, the unofficial guide toOIT at the U of M.

June 11, 2007

Using OIT to Game the U of M Google Search Appliance

OIT

So as of my last post, my standings in the Google appliance haven't moved one bit. Setting aside any narcissism and paranoia induced explanations, I have I have to conclude that simply naming the links in the blog to OIT had no noticeable effect on my pages standing.

Therefor, I decided to rename the page from Office of Information Technology - OIT to OIT - Office of Information Technology. I reflected this change in the Title element as well as in the first H1 element and the first normal body content.

Results should be processed in a week or so. (yes - this post about gaming the Google appliance is just another shameless promotion for the OIT page.)

May 29, 2007

Gaming the U of M Google Appliance to Promote my OIT Page

I have a page that is about OIT, it pretty much contains everything you'd want to know about OIT at the U of M if you are a new employee and trying to orientate and tap into the organization.

So I posted on Friday (May 25th, 2007) a link the to Unofficial Office of Information Technology wiki and today (May 29th, 2007) it is on the first page of results. At about the 6th position. This post will link to a print version of the wiki page. Meaning it wont have all the standard wiki navigation to work through to find the real content. If it gets indexed it should push it up yet another spot or two.

However, one thing that could stop this is that typically the Google appliance wont follow querystring links. These tend to lead them into infinate search spaces. So I'll give it a few days and check back and review the results or lack of them. (I might give it a week).

But in gerenal I think the experiment worked.

(yes - this post about gaming the google appliance is just another shameless promotion for the OIT page.)

May 25, 2007

Mash-Ups with the Office of Information Technology OIT Services and their relationships with Wikis and Blogs

So here at the U of M, there are a bunch of sites and groups devoted to helping you teach, do research, learn and "support the people" who teach, research and learn. But they typically look at themselves organizationally rather than from their customers perspectives. This leads to confusion and the mistaken perception of less value in the services offered than really exists.

A byproduct of this organizational, rather than service approach to showcasing our wares, is a series of "Unofficial" pages that are popping up on UMWiki wikis and UThink blogs. I've started two The Unofficial Guide to the Office of Information Technology (OIT) and another is The Unofficial - How to get your MSDN Software for Computer Science and Software Engineering Majors and Graduate Students. I was originally motivated to do this when I found the excellent UMN Itlabs Unofficial Web

This post falls into the category of being a "no one will officially tell you but..." post. See, by posting this blog entry I will elevate the rankings of the unofficial pages to which I just referred. This is because for some reason the folks behind the university google appliance have increase the value of items posted to UThink. [I however find the hypercard, simple DB structure of the UMWiki much more useful.] So posts like this and the information sites they referer to are just the start. This bit of "google gaming" info may seem like just a tiny bit of info that would help someone promote their site in the google rankings at the U of M, but I think it is leading to something much larger.

But where is this headed? Open Architectures and Mash-Ups
I believe that over time issue like the lack of offering of certain servicesby OIT, like blackberry accessible email, or web standard calendaring, or a suppported secure research and development "LAMP" stack, and other university service groups will be overcome by self interested individuals creating solutions to the barriers to information that exist in the technology choices implemented by OIT and unit areas. There is not enough knowledge and resources withing OIT (nor could there be), to pick the right emerging technologies, fund the efforts to create these mash-ups, and provide support to the population who would use them. It will be students, staff and faculty, satisfying their own self interests (scratching their itch), that will do it. Most of what is happening or will happen, will be unfunded, and unofficial efforts by all the smart people how call this home for some part of their life.

I think the scenario will go something like this. Some ADCS employee, or lab asssistant, or EADs developer, who will be in a degree program and have to do a capstone project, or will be a fellow in some innovation group, or have a grant, or who is just borded, will create a open SOA gateway from technology X, exposing it to all the potential mash-up applications that students and staff are becoming used to in the wider world of web 2.0

I think that project like the one started by Alexander Saint Croix UMFoundrywill be the catalyst for this to occur. (I'm not banking on Alex's efforts being "the answer", although they may turn out to be) but eventually it will happen, or more correctly is already happening and we are just starting to see signs of it poking out here and there. (A comment on why it is able to happen now.) But without something like the UMFoundry or a knowledge base on the UMWiki it will never reach its full potential.

April 21, 2007

Wiki vs. Blog

Well... for me, I guess there is no contest. A wiki is more of a knowledge store, card space, card file, hyperlink database, call it what you want... It stores and structures data in a way I find helpful and manageable.

I think it is safe to say this blog has been abandon. More of the same but with more frequent posts and updates can be found here https://wiki.umn.edu/twiki/bin/view/CraigGjerdingen/WebHome

February 16, 2007

Chapter 7: Ruby on Rails

Rails feels like just what it is, a reflective inspection and auto build (aka code generation) of a well designed Model View Controller connected to a nice implementation of Martin Folwers Active Record design pattern. I think the lession here isn't how great Rails is, but how much can be gained by following well designed patterns...

Continue reading "Chapter 7: Ruby on Rails" »

February 07, 2007

Transformation: Ruby Smells

I keep hearing people say they couldn’t possibly use Ruby because it lacks automatic refactoring tools.


Marting Fowler tells us that Refactoring is the art and science of turning smelly code into good code, in small, incremental steps. Provably correct, by construction. Algorithms for giving your code a makeover without breaking it in the process.


Continue reading "Transformation: Ruby Smells" »

February 06, 2007

Beyond Javas: Chapter 6. Ruby in the Rough

Java's leadership run, at least for applications, might be drawing to an end. This book points out one language and two frameworks (one in Ruby and one in Smalltalk) that have something special to offer. One possible alternative language, Ruby. It improves on Java, but that doesn't mean that Ruby will succeed, or that it's the best possible alternative. Dynamic Languages...

Continue reading "Beyond Javas: Chapter 6. Ruby in the Rough" »

Scott Gu's Blog: ASP.NET AJAX 1.0 Released

Microsoft extends the Common Type Library to the client-side. This provides cross platform, cross browser support for a core JavaScript type-system, JSON-based network serialization stack, JavaScript component/control model (Observer Pattern), as well as common client JavaScript helper classes.

Continue reading "Scott Gu's Blog: ASP.NET AJAX 1.0 Released" »

Sizing Up .Net 3.0 Windows Presentation Foundation (WPF)

Extensible Application Markup Language (XAML) by Microsoft is a declarative XML-based language used to define objects and their properties, relationships and interactions for Windows Presentation Foundation (WPF). ...


Personally, my thoughts are, "Microsoft released the .Net 2.0 framework about the same time Web 2.0 was really peaking and they COMPLETELY missed it"... It had to be a major embarrassment for them. Now it looks like they are...

Continue reading "Sizing Up .Net 3.0 Windows Presentation Foundation (WPF)" »

February 01, 2007

Chapter 5. Rules of the Game

The premise of the book: conditions are ripe for an alternative applications programming language to emerge, because Java is abandoning its base. I'm not going to pretend to know what's next. Hopefully, I'll lay out some interesting languages and frameworks that have promise. This chapter, then, suggests the characteristics that the language should have to have broad commercial success.

Continue reading "Chapter 5. Rules of the Game" »

Patterns Of Enterprise Applicaton Architecture (by Martin Fowler) Chaper 1 and 2

Chapter 1: Layering
Most common technique to break apart a complicated software system. Layers is the cake analogy for software. Each layer rests on a lower layer. Higher layers use services of the lower layers. Lower layers are unaware of the higher. Layers hide layers beneath them.

Chapter 2: Organizing Domain Logic
Simple logic doesn't require decomposition and can be done in a "Transaction Script". But complex logic is where objects come in, and handle this problem with a "Domain Model", primarily around the nouns of the domain. Logic for handling calculations and validations are placed in the model.

Continue reading "Patterns Of Enterprise Applicaton Architecture (by Martin Fowler) Chaper 1 and 2" »

The views and opinions expressed in this page are strictly those of the page author. The contents of this page have not been reviewed or approved by the University of Minnesota.