Tuesday, July 08, 2008

eWeek looks at Computing on the Cloud

My paper copy of eWeek is generally fodder for the circular file. In fact, the magazine rarely makes it as far as my office. Instead it stays in our reception area on a coffee table along with other unread magazines. This week, though, I picked up a couple of editions to browse while taking lunch. In the process I discovered some interesting cloud computing technologies.

The first is old news for leading edge developers, but new to me. The June 30 edition ran an analysis on the Google App Engine. The Google App Engine competes with Amazon Web Services in scope and intent. Although Google currently only supports the Python language, betting an application on Google infrastructure seems pretty safe.

In a similar vein, GigaSpaces offers an application server that sits on Amazon's EC2 cloud computing solution. The GigaSpaces application server provides a middleware layer between Java or .Net applications and the Amazon Web Services backend.

A third product, Jungle Disk, has a different goal, but uses computing on the cloud none-the-less. Jungle Disk is a backup and storage solution that works with Amazon's S3 Web Service. I have not tried Jungle Disk, but eWeek offers a fairly thorough analysis that puts the product on my to-do list.

Of course the interesting common thread with all these applications is computing on the cloud. GigaSpaces and Jungle Disk take advantage of Amazon's early entry into the utility computing space. Google, however, does everything well, and should have little trouble catching up. Old timers like myself remember the days of time-sharing on mainframes. Cloud computing proves what's old is new again with one important difference; now utility computing is affordable.

Thursday, July 03, 2008

Once You’re Lucky

I often pick books based on reviews from Wired Magazine. This was true when I picked up Once You're Lucky, Twice You're Good. In Mark Horowitz's review, he claimed that "Sarah Lacy…hangs with [entrepreneurs] them, gains their trust, and gets the goods. No other recent chronicle delivers such intimate, behind-the-scene glimpses into Silicon Valley startup life." It's an entertaining read reminiscent of Accidental Empires.

My issue with the current crop of valley startups has little to do with Sarah Lacy's book, although her tales reinforce my opinion. The problem is very few of the companies actually provide a site that is useful. Even Facebook, the current reigning king of Web 2.0, doesn't help its members solve problems or get things done. Of course my days of finding a good off-campus kegger with lots of girls are long past. As Twitter, Slide, or Ning they seem even less useful.

What's interesting about these sites, though, and the stories Sarah wraps around them, is the underlying technology. Maybe an old-timer like myself doesn't see the benefit of social networking. I do see where collaboration and go anywhere sites can be very useful. I'm expecting a new wave of web startups that take Web 2.0 into truly commercially viable areas.

Monday, June 30, 2008

Thoughts on Innovation

It is not easy to foster a culture of innovation in a corporation. Ironically, I have not always felt this way. I have spent the great majority of my career at start-ups, entrepreneurial charged companies, and software makers. Each of these environments relied on the creativity of their people to remain competitive.

When I joined my current firm, we were a small and hungry software supplier in the HealthCare industry. We served a particular niche market and our growth was dependent upon finding new and inventive ways to sell more products into this niche. In my first year with the firm we doubled our number of offerings.

Something happened to that culture of invention when we were swallowed by a bigger fish. It's hard to put a finger on it, but maybe it's our build vs. buy strategy that favors buy over build. Maybe it's our market dominance and entrenched legacy customer base. Maybe it's a culture that meticulously tracks where each hour of engineering time is spent.

You can start with the existing method of starting a project around a new idea. A rigid and exhaustive procedure was established to analyze projects for funding. The firm sets aside money especially for these projects. But the process is long, bureaucratic, and daunting. Only those employees with the greatest perseverance can weather the multiple stages, detailed requirements, and long delays of this process. The process itself, then, serves to prevent innovation.

It's not that the company is not interested in innovation. This year the firm initiated a council of thinkers who are charged with encouraging the submission of creative ideas. On the surface you might think the initiative could be very successful, but I see some fundamental flaws that could stall our efforts.

First and foremost of the flaws is the establishment of yet another process. And what happens when an idea passes through the process established by the idea team? The idea is handed off to the same process as before, but possibly skipping the first stage. In affect we have put a new process in front of the old process. If the old process was a deterrent to innovation, then the new one is doubly so.

Add to the mess of procedures, a subtle lack of focus. This lack of focus was exposed by our firm's COO who made it apparent her goal is innovation in operations. The Japanese auto industry of the 1980s was cited as an example. This is fine enough, except the council had established criteria around the analysis of new product ideas. In other words, we were looking externally for innovation, when the COO expected us to look internally. The criteria to judge projects of these two types are dramatically different.

So far, the results of our council are disappointing. No idea has successfully come to fruition. And the promotion of an innovative culture is stalled.

Of course everyone holds up Google as the standard. Even among my staff, I've tried to encourage the idea of spending 20% of our time on new ideas. The key to the Google concept, though, isn't necessarily the allocation of time. Instead it's the thinking that with a new idea, many people "won't get it", at least not at first. The idea has to go through some element of trial and error before it can be tabled or killed. This is in direct contrast to our approach, which puts rigorous paperwork between the idea and a prototype.

If we really want innovation to take hold at our company, we'll need to change the model. We'll need to empower people to spend time building working versions of their idea, instead of filing a form. We'll need a little of the "just do it" attitude, instead of waiting for approvals. I guess we'll need to regain a some of our entrepreneurial mojo.

Friday, June 20, 2008

Thoughts on some Web 2.0 Sites

The expression Web 2.0 has been with us so long that we can consider it a Tired term. Founded on the principles of collaboration, and built on highly interactive technology (read AJAX), Web 2.0 sites represent the post bubble rebirth of an industry. Some of these sites offer fairly valuable services and some of them are nonsense. Here are my thoughts…

Facebook is seen as the company with the most potential for long term success. I've been using the site almost daily for over a month and I can honestly say that "I don't get it". Sure, I'm a bit of a dinosaur, having attended college (both degrees) long before social networking came to the web. But in all my use of the site over the last several weeks, it hasn't helped me accomplish anything. Facebook has been pretty successful at positioning itself as a platform for micro-applications. Here again, I don't get it. I've tried many of the applications and always end up with the same thought…"so what?". I read somewhere that everyone eventually has an "ah-ha" moment with social networking; I'm still waiting for mine with Facebook.

On the contrary I saw the benefit to LinkedIn the day I started using it nearly five years ago. This site has helped me find work, consultants, and business leads. I've heard it called social networking for business people, but there's really very little that social about it. The site generally prevents people from contacting strangers, at least without an introduction. Ironically, you can pay money to override this fundamental aspect of the site. Paying members have access to InMail messages and can reach out to people directly. Anyone in a career should be active on LinkedIn.

Plaxo is an odd hybrid of Facebook and LinkedIn. I actually avoided using Plaxo for sometime, opting instead for GoodContacts, but when GoodContacts looked like they weren't going to make it, I switched loyalties. Plaxo suffers from an identity crisis. It started as a convenient way of managing business and personal contacts online. I use it as my main address book, and sync Outlook, my Blackberry, and other sites to Plaxo. Somewhere along the way, though, the site morphed into Plaxo Pulse. The new site is a clone of Facebook, right down to the page layout and color scheme. I still use it to keep my address list, but I don't think this company will survive.

Geni is a cute social networking site for families. I checked it out after reading Once You're Lucky. This site is actually pretty good. It is easy to use and has all the capabilities needed to stay in touch with your extended family. Nonetheless I feel this site is doomed. I make this judgment simply because no one seems to know anything about it. My family is so tired of receiving web site invitations from me that they've all but ignored the Geni invites. And without active participation from my family, the site loses its' usefulness. Add in the fact that there is no subscription or advertising; I have no clue how the site expects to earn revenue.

Twitter is dumbest idea I've ever seen. Still, it's pretty addictive. I checked it out because I am starting a project that requires a similar SMS interface. My project, however, will be useful, where Twitter simply generates noise.

I have a love/hate relationship with Flickr. I use the site a lot by storing all my family's pictures there. I uploaded so many pictures that I had to buy a subscription. Flickr was a leader in establishing sharing, but now its UI seems dated. I find it difficult to use, or at least difficult to learn how to use. And I am disappointed in the site's "badge" ability; that led me to seek alternatives including Slide.

Krugle on the other hand is one of the best and most useful sites I've found. Of course you have to be a programmer to appreciate the site's benefits, but for those of us developing software for a living the site is amazing. Forget Google Code Search; Krugle is the place to go for snippets of code and projects in the public domain.

YouTube is silly and innocent fun. If you're reading this far into this post, then you already know all about YouTube.

Some people claim that Google Docs is meant to replace Microsoft Office. Google, of course, denies such claims by saying that Google Docs are meant to augment productivity suites. Frankly I don't care about the pending Microsoft vs Google wars. I like Office and I like Google Docs. I've read that Google Docs is not as feature rich as Office, and certainly the Google toolbar has nowhere near the number of buttons as the Office Ribbon. That said, I've never looked for a feature in Google Docs that it didn't have. I guess that says something for the feature bloat in Office.

Everybody uses maps online. MapQuest was amazing when it first came out. Google, however, really lifted the bar when it introduced Google Maps. Now all the map providers have full screen maps that pan as you drag them. They all have satellite pictures and zoom. Google has Street View and Live and Birdseye View. Of Google, Live, Yahoo! and MapQuest, I like Live best. But they're all good.

I checked out Slide because I wanted a cool way to show pictures on my web site. Slide has some cool features, but I was a little disappointed. I can't imagine building an entire business around slide shows so I don't look for this site to last long.

Popfly is Microsoft's site to demonstrate how cool their Silverlight technology is. It's kind of cool for developers building mashups and who don't mind using Microsoft technology. That's probably a pretty small group, but since I am technology agnostic, I use it and think it's a pretty cool site.

Delicious on the other hand is about as uncool as you can get. I think the site is ugly and serves little purpose. On the contrary, Trailfire, is of similar ilk but is amazing friendly and helpful. What a difference a thoughtful UI can make. Unfortunately, Delicious is the better bet for longevity in this space as they have the backing of Yahoo! and some web 2.0 brand recognition.


Wednesday, April 30, 2008

Stay away from Fanbox

I am normally a proponent, and sometimes early adopter, of new technologies including Web Sites and Web Services. I'm also a believer in the value of personal networking. I have accounts all over the web including Face book, LinkedIn, and Plaxo Pulse. I've even signed up for some of the losers such as Friendster, Naymz, and Spaces. I never had a bad experience until I came across Fanbox (notice that I refuse to link to it).

It started with an innocent looking message from a colleague; Dawn has a question for you. When I clicked on the link, I was directed to Fanbox and presented a somewhat racy question that was apparently directed at someone with a much different demographic than me. Ironically I had been introduced to Fanbox a few days early by Sterling Brown and given Sterling's reputation I was intrigued. So I clicked on an answer to the question.

Here's a clue, if you get a message about a question, don't click on it! Answering the question kicked off a wizard inviting my contacts to Fanbox. Fanbox apparently scanned my Outlook Contact list, even though I never click a link for that purpose. It then asked if I me to send a question so I immediately clicked cancel. Later I discovered that Fanbox forwarded the question to my contacts and causing me much embarrassment.

It's really a shame because the fundamental technology of Fanbox is pretty cool. They have reproduced a workstation desktop and point-and-click user interface deployed over the web. The desktop comes with storage, email, and that mimic Microsoft Windows pretty closely. Apparently a Web-based Windows environment is a solution looking for a problem, because Fanbox has jumped on the social networking bandwagon. Outside of social networking, I did not see any real value to the site. There certainly is nothing that would persuade users of Facebook or Google Docs to jump to Fanbox.

So Fanbox has resorted to tricks to obtain members. Grabbing my contact list was akin to spyware or worm tactics. Maybe someday a company with vision will snatch up the Fanbox technology and deploy it provide some real benefit. Until then, avoid Fanbox like the plague.

Wednesday, April 16, 2008

Plant a Billion Trees

One dollar, one tree, one planet.

Brainteaser

See if you can solve this problem.

Each number shown below follows a certain rule. Figure out the rule and determine the missing number.

January

20

March

5

April

10

December

15

July

?


Is the answer?

  1. 5
  2. 10
  3. 15
  4. 20
  5. 25

Check back in a couple of days. I will post the answer in a comment.

Cash is King

There is a common notion that most start-ups fail for one of two reasons; either they are under capitalized or do not sell aggressively. In both these cases, the firm fails to raise the appropriate amount of cash needed to sustain operations. Of course all failed businesses run out of money, but some never give themselves a chance.

A firm that never gave itself was chance is Elite Technology Partners. The company was born from the technical brain trust of Blackwood Trading, and quickly conceived a product and business model based on their experience from the other firm. Their product was greatly inspired by Blackwood, but targeted a specific strategy and different distribution channel.

Elite's founders had learned from their experience at Blackwood. Certainly, they put to use the intellectual capital gained at Blackwood. They also learned from Blackwood's failed effort to market themselves successfully. In addition, the founders recognized that Blackwood's operational model was very expensive.

However, Elite underestimated the effort required to develop a product and bring it to market. Very quickly the firm fell into a chicken and egg situation. In Elite's case, they couldn't sell product because they did not have the capital to complete it. And they could not raise cash through sales because their product was not finished. Add to their situation the economic environment during 2002, where investment capital had effectively dried up. Venture capitalists were only looking at firms generating cash through sales.

In Elite's case, the lack of cash led to a series of strategies changes that sealed the fate of the company. First, a shortage of cash caused many of their best engineers to secure positions at other employers. Elite sought an investment arrangement through key prospects that would enable them to bring their product to market. But partnerships with a large investment come with restrictions. Demands of exclusive use and ownership of intellectual property made partnership deals impractical.

To raise cash, Elite sold its' talent in consulting arrangements. The consulting business was profitable and brought in enough cash to keep the operating. Unfortunately the opportunity cost of consulting was a halt to further development of Elite's product. In the end, Elite failed to complete its' product; Elite failed to complete its' product because it failed to raise the capital necessary to build the necessary technology.

I am working with an entrepreneur who is in a similar position. He is following a conscious strategy of delaying raising despite having an established relationship with investment bankers. The entrepreneur is betting that signed contracts will make the firm more attractive to investors. This may be true, but having no cash in his firm, he will have a difficult time meeting any operational commitments.

My observations of Elite Technology Partners leads me to believe that my friend has a risky strategy. Because he refuses to seek capital, he will not have a fully functional team in place when he signs his first contract. When the contract is signed he will need to complete his technology, hire staff, and seek capital within a very short timeframe. In the three to six months needed to receive private equity cash his venture could fail.

Elite Technology Partners failed because they did not raise cash for their operations. Successful entrepreneurs beg, borrow, or steal (Ok, maybe not steal) enough to give their companies inertia. A firm with inertia will attract further investment, or generate cash organically.


Tuesday, March 25, 2008

Here’s a Good Read

I just finished Predictably Irrational by Dan Ariely. The book has to be one of my most favorite non-fiction reads. I have to admit that Mr. Ariely had me engaged from the first page of the introduction.

Here's the premise; we believe we make perfectly informed decisions, but truth be told we are a product of our nature. That nature makes decisions that are irrational; not only are our decisions irrational, but they are irrational in a consist manner. Through over a dozen chapters supported by controlled experiment, Ariely makes his point that our choices are behavioral.

Do you know why we so often promise ourselves to diet and exercise, only to have the thought vanish when the dessert cart rolls by?

Do you know why we sometimes find ourselves excitedly buying things we don't really need?

Do you know why we still have a headache after taking a five-cent aspirin, but why that same headache vanishes when the aspirin costs 50 cents?

Do you know why people who have been asked to recall the Ten Commandments tend to be more honest (at least immediately afterward) than those who haven't? Or why honor codes actually do reduce dishonesty in the workplace?

By the end of this book, you'll know the answers to these and many other questions that have implications for your personal life, for your business life, and for the way you look at the world. As a bonus you will also learn how much fun social science can be, and how to see more clearly the causes for our everyday behaviors, including the many cases in which we are predictably irrational.
Click here for more information.

I stumbled across the book while browsing "What We're Reading" on Slate. Check it out. In the meantime, I think I'll pay more attention to the books reviewed at Slate.

Friday, March 14, 2008

Middlesex

I recently finished the book Middlesex by Jeffrey Eugenides. The book is a Pulitzer Prize winner and Opra Book Club award winner. It is a well narrated but strange tale of a hermaphite exploring the roots of his condition.

It's hard to compare the story to another book. It spans three generation like many classic "come to America" novels. The subject matter will make some people uncomfortable, with its' thread of incest and gender confusion. In some ways I liken it to Running with Scissors, except that it is much more coherent and expertly told. Running with Scissor is more of a collection of oddball short stories written in a style of a middle-schooler.

I found myself drawn to the time period and location of the story. The narrator is my age, and grows up in the same metropolitan area as I did. References to Detroit places and events brought back memories of my own formative years.

Once started, I found the book hard to put down. I recommend it.

Friday, February 29, 2008

Hey Google, WTF?

Last month I started displaying ads on this blog using Google Adsense. I did it as a curiosity more than anything else. After all, a low traffic blog like mine will not generate much revenue. In fact, six weeks of Adsense has earned a whopping $9.76. Imagine my surprise, then, when I received the follow notice...

It has come to our attention that invalid clicks have been generated on your Google ads, posing a financial risk to our AdWords advertisers.Please note that any activity that may artificially inflate an advertiser's costs or a publisher's earnings is strictly prohibited by our program policies.

...

Please note that because we credit advertisers for any invalid activity we detect, we may adjust your account earnings for any days during which invalid clicks occurred.


If you were clicking your ads out of interest or to see who was advertising on your site, please note that clicking on your own ads for any reason is strictly prohibited by our program policies. Instead, we suggest using the AdSense preview tool as an alternative.

...


Ok. I understand that advertisers will not be happy about publishers clicking away on ads for no other purpose than to inflate the click-throughs. Higher click-throughs result in higher fees. In my case, however, it's pretty obvious that I'm not stealing advertisers blind. I would think that Google, for all their sophisticated engineering power, could derive an algorithm that ignore sites with a minimum number of clicks. Less than 10 in a month in my case.

Now here's the rub; I clicked on the ads because I had a legitimate interest in the products offered. It's a compliment to Google that the ads they choose by my blog have relevance to the topics I discuss. I've even downloaded whitepapers and started conversations with sales reps. I expect that Google's fancy algorithms will never determine that.

Google's note refers me to their preview tool, but it isn't supported in my browser. In short, Google's strict policy prohibits me from viewing information that has peaked my interested. Given that I am a buyer of technology I exactly represent the target market of my advertisers.

When it's all said and done, I will continue to click on ads that interest me. If Google revokes my Adsense, then so-be-it. It's a sad testament to a company that many hold in high esteem, but frankly this web behemoth seems more and more like vintage 90s Microsoft.

Thursday, February 14, 2008

Project Runway

My family has grown attached to Bravo's reality show Project Runway. Of course we love it's entertainment value. The colorful characters. The drama. The stress. The reviews. I like looking at the models. My daughter loves the clothes.


During last night's episode, I had an epiphany of sort, and yes this will tie to technology. In the episode the panel needed to eliminate two designers, reducing their number to three for a show at Bryant Park. Instead, though, the panel had deadlocked on two designers and concocted a run-off for the final spot.


During the panel discussion, the judges criticized work they felt was good and commercial viable. The problem was it didn't fit their perception of "fashion". Here's the thing; I always felt fashion was driven by consumer demand and that designer's true goal was creating clothing that people desired. Silly me.


The Fashion industry isn't about wearable clothes. Instead, it's about creating an artistic vision around clothing. This is an important distinction. Fashion designers, especially at high levels, think of themselves as artists. Entire economies and sub-cultures have formed around this concept. Those artists with the most successful vision can attach their names to commercial garments. In a sense, the Fashion industry is all about building a "brand" for the designer/artist that.

So what does this have to do with technology? Well, in case you haven't noticed, our industry works in much the same way. Think of ventures like Delicious, YouTube, and Facebook; what commercial value do they provide? Do they even make money?

I would venture to say that these firms, and the people who formed them, see themselves as technology visionaries. Like fashion, entire economies and sub-cultures have formed around their offerings. And although their technology may not be profitable, their brand has great value.

Ironically my former manager at Information Builders, Gerry Cohen, used to say "we're not in the fashion business." Firms like mine that grind out a living supplying technology and it's not very sexy or glamorous. It begs the question: is it necessary to have a visionary brand that brings attention to more commercial offerings? Or can non-sexy technology exist simply on the value they provide.

Wednesday, February 13, 2008

Data Warehousing Dilemma

We are in the midst of a long running Business Intelligence project. The original thought behind the iniative was a solution allowing analysts to explore their data. Through a combination of historical data and predictive modelling, the solution would provide key metrics to manage their business. After several mis-starts, we discovered the wisdom of Ralph Kimball.


Kimball's Data Warehouse Toolkit was an ephifany and inspiration. Suddenly before us was the solution to performance woes. His solution? A star schema, where with the warehouse measures are retained in a single table linked with related descriptive data. All the descriptive data (dimensions) were related through the single fact table containing the measures.

Our project started simple enough. Using sample report templates from our Product Management team, we determined a grain for the warehouse and computed the appropriate measures. The grain, by the way, is the lowest level of detail needed to answer the questions asked of the data.

It soon became apparent that there was a flaw in our design. Not the design of the warehouse, per se, but the design of the system. The reports designed by our Product Management team were at the level of the grain. Running them would produce thousands of pages of detail. Nowhere were we taking advantage of the warehouse's dimensions to drill into these reports. Seeing the flaw, we tasked our Product Managers with spec'ing the entry points to their reports.

What was returned to us was a disaster. Instead of taking advantage of the warehouse or even the capabilities of the Business Intelligence technology, the PMs designed more reports. These new reports were summaries with drill paths to the detail provided earlier. They also contained an entirely new set of metrics, all calculated at a different grain.

The problem of the different grain was exocerbated by many of the new metrics. These metrics were computed with division of aggregated counts. The counts, however, were not on the fact table, instead they were distinct counts of dimension values. There is the dilemma, we needed figures that could not be pre-computed into our cubes. The metrics were computed "on-the-fly" and resulted in tremendous performance problems.

I believe the solution is simple and obvious. We need additional fact tables a different grains. The purists among my team didn't see it so clearly (they will by time we're finished). The problem is Kimble's treatse on data warehouses discourages multiple fact tables in the database schema.

Kimble oversimplifyies warehouses with the star schema. Any complex set of data will have measures that can not be summarized into a single fact table. In truth, though, multiple fact tables will be an integral part of any practical solution based on a data warehouse.

The 33 Strategies of War

I just finish the War book in Robert Greene's amoral series. This is one of those non-fiction books that starts great but becomes a bit of a drag to finish. That said, I would recommend it. History buffs and self-help freaks may find it intriguing.

Greene outlines 33 strategies of War, and then attempts to demonstrate how these are used in everyday life. Many of the strategies are polar opposites; like #4 Create a Sense of Urgency and Desperation and #11 Trade Space for Time. One strategy suggests a quick strike and the other recommends waiting.

I like the historical references. I was especially interested in tales of Alexander the Great and Napoleon, two of Greene's favorites. I also found the stories around the Austrian leader Klemens von Metternich fascinating; I was unfamiliar with Metternich prior to reading this book. Greene also uses several stories of Samurai warriors, another culture that I found intriguing.

Frankly, I found the self-help side of the book a little light. This is much more a history review than a treatise on how to beat your co-workers to a promotion.

Greene's amoral series includes to other volumes, The 48 Laws of Power, and The Art of Seduction. I should check out the latter book...I need lots of help there.

The Kite Runner

Khaled Hossein spins a tale worthy of Charles Dickens. As I read The Kite Runner I was reminded of the stories David Copperfield and A Tale of Two Cities. The first because of the person propose and decades long story line. The second because the situation becomes dangerous for the protagonist when he travels back home.


Hossein, however, avoids the flowery language and odd analogies of Dickens. Instead he writes in a more direct style reminiscent of Hemmingway.


Did I just do that? Did I compare a first novel to Dickens and Hemmingway. How cliche'. Needless to say, I enjoyed the book and recommend it. And don't let Hossein's Afghan roots fool you, the book it definitely written from an American point of view.

Thursday, January 24, 2008

Maybe Blogger's not so bad

Yesterday I submitted a post complaining about blogging with Blogger. I switched the host from Doteasy to Blogspot, and has resolved most of my issues. So maybe Blogger isn't that bad, but they could improve their support for FTP sites.

There is still some quirkiness though. For instance, I changed my feed setting from "full" to "short" expecting that my feed will carry the first paragraph or two of my posts. Instead the feed shows none of the post. I also can't figure out how to include comments on the main page. And the comments page is styled with Blogger's default color and font scheme.

I have also set my main page to hold seven days worth of posts, but I see that it goes back a month. There must be a setting that I am missing, because the QA of a site like Blogger can not possibly pass errors this obvious.

By the way. I have a new URL for my feed. For those of you who subscribe (both of you) please change the feed to: http://iambillmccann.blogspot.com/rss.xml

Wednesday, January 23, 2008

Blogger Frustrations

I have been using Blogger for about a year. Prior to using Blogger, I published my blog manually by typing html and updating links on the pages. Blogger has made publishing much easier, but there are some things I haven't had the time to figure out.

For instance, I don't know how to write a summary for RSS feeds. It was pretty easy using manual methods. I would simply copy the first couple of paragraphs of my post into atom.xml and I was done. Blogger, though, seems to post the entire article to my feed.

I also struggle with styling. My posting on "How Much Detail in Requirement", for example, switches to the "smallest" type size on the bullet list. I have manually adjusted it many times, but I can't get the text to match. I also struggle with the vertical spacing. Unfortunately, Blogger's WYSIWYG editor isn't all that. Maybe I'll switch to Google Docs for editing my posts.


I have trouble with my template too. I like the top of my blogger pages to match the style of my web site. Unfortunately, Blogger's styles clash with my stylesheet resulting in odd colors on my links. I can fix this manually, but I haven't found the time...so I look stupid instead.


The problem could be related to my host. I use Doteasy to host my blog and web site. Blogger supports richer layouts, but you have to host with Blog*Spot. I'm thinking of hosting with Blog*Spot and using links to connect my blog with my web site.

Of course I'm secretly hoping that someone reads this post and has quick and dirty solutions for my problems.

Are we dumbing down programming?

Her resume looked great. She was coming to us as a high end (price) developer. But as I listened to her describe an abstract class in response to my asking her about abstraction, I had to wonder; have we made it too easy to be a programmer?

It's true that abstraction is the most intangible concept of OOP. During my phone screens of candidates, though, I find myself wishing I had tipped them off. I will be asking about OOP. Go look up "object oriented programming" on
wikipedia.

I generally blame our universities for this failure. OOP is largely conceptual, and should be introduced and reinforced by any Computer Science department worth their accreditation. Once in the workplace, software engineers rarely get the proper mentoring on solid coding habits.

We really can't lay blame entirely on universities and trade schools. No, much of the problem lies with the technologies we use to build applications. High on the list of offenders are Visual Basic, Visual Studio, Java, and .Net. Throw in HTML, XHTML, XML, and all the mark-up language derivatives. Then add in any of the web development tools like Cold Fusion and Flash. Of course the scripting languages, JavaScript, VBScript, and Perl virtually prevent solid coding practices.

My obsession with OOP stems from a very specific business need. I have to support ten software products with a very modest staff. The most basic way to accomplish this is by reducing the amount of code. An obvious way to reduce code is reusing code. Unfortunately I inherited a situation based on copy-and-paste code. After three years of fighting copy-and-paste habits, we still support multiple versions of code that perform the same task.

Many developers confuse using objects with OOP. Dropping a control onto a form does not constitute object oriented programming. In fact, there will be nothing reusable in the result. In addition, the automatically generated code written by the action of dropping the control is almost certainly unreadable. But then, many developers today don't even realize code is being generated.

So our tools have dumbed down programming skills. Especially for those developers who rely on the designers and tools built into their development environments (IDE). For me, I'd like to find an engineer or two who would love to create the next Visual Studio, instead of dragging controls from a toolbar like some pre-programmed automaton.

Thursday, January 17, 2008

Small Company Blues

At dinner with a friend yesterday, he lamented about problems rolling out technology in a firm he is managing. Apparently his team misses their delivery dates; by a large amount. As he described his situation I felt like I was experiencing deja-vu.

His story in brief; he has four people maintaining his technology. These people are responsible for bringing clients online, handling technical problems, and building new capabilities. Projects are frequently months late. A core component of the system is constructed on an antiquated platform (Paradox) and only one individual has working knowledge of the code. And on and on.

This is a very common situation in technology firms managed by "non-technical" people. It is caused by the number one oversight of CEOs who have never worked with sourcecode. I even see it here, at my current firm. The problem is that there is little accounting for maintaining the product. The assumption being, when the product is delivered to the customer, its' developers are free to work on the next thing.This is a dangerous trap and I have seen many very intelligent executives fall in it. Inevitably, the development team becomes forced into choosing between support of the current product and construction of the next. That decision is a no-brainer, and construction of the next thing gets continually put on hold.The solution is fairly simple, but it is a bitter pill for developers. The team must be split, with one group providing support and the other working on the next thing. Of course no one want to be trapped providing full-time support. In my role, I have tempered this morale issue through job rotation. In the end it is necessary to prevent the continuous interruption of new development.

No Country for Old Men

I didn't see the movie. I read the book. Here's your warning: this blog is a spoiler for the story, so if you plan on seeing the movie, take a pass on this posting.

I finished
No Country for Old Men with mixed feelings. Admittedly I found the story riveting, after all I could hardly put the book down once I had started it. Call me soft, though, I don't like when the bad guy wins.



It is fast paced with a riveting story line. The language is simple and boiled down to the basics. There are no flowery descriptions of peoples feelings or dramatic landscapes. Given that most scenes carry a fair amount of blood, this is a good thing. Characters aren't very deep or well developed, or maybe they just don't live long enough to get developed. It's a perfect story for a Coen brothers movie.



One more thing...the book would be easier to read if the dialog was surrounded by quotes. I don't see why a basic grammar rule would be flat out neglected.

You might also like ...