• Skip to content
  • Skip to primary sidebar

Sazbean

Software Development Management

Main navigation

  • Home
  • About
You are here: Home / Archives for Tech

Tech

Aaron Worsham / Oct 24, 2008

Ruby one-liners get answered

rubymegyarshThe guys over at Rails Envy, a Ruby on Rails enthusiast podcast, have a running joke.  Their catch phrase? – ‘Rails can’t scale.’ Yeah, I wasn’t too sure I got the joke either.  Then I heard it myself in CIO level discussions from smart business people parroting things they didn’t understand and read somewhere once in an article in a magazine bylined by a guy in a suit who looked corporate and trustworthy.  Rational reasoning and discourse can sometimes be co opted by bumper-sticker wisdom even at the highest levels.

Here is the thing about corporations; enterprises are in the business of managing calculated risk within the market or industry they operate.  They do this by forcing non-core operations to be conservative, risk-adverse and predictable.  It’s a bit like hedging your business’s bet in the junk bond market (core business) by backing it with rock solid, non sexy T-Bills (non-core like software development).  Sure, the return on the T-Bills is lousy but you know in three years you won’t be out that investment.  Java, backed by Sun Microsystems, and .Net, backed by Microsoft, are some of the blue chip securities of the programming world.  Enterprises trust them.  One-liners like ‘Rails can’t scale’ are the one-handed brushoff of entrenched corporate IT’ers to the mere idea of using something new like Ruby or Rails.

Still, Ruby is a persistent pitch man, especially in the web technologies.

Corporate IT: Ruby uses green threads and Rails is single threaded, why are we even talking?

Ruby: Ruby’s MRI is green threaded, but the JRuby interpreter uses native threads in the JVM, just like Java.  Also, Rails 2.2 just released 2.2 RC1 that is thread safe.  Merb was thread safe from the start and just released 1.0 RC2.

Corporate IT: There aren’t enough ruby programmers to staff a project.

Ruby: The Rails Rumble contest didn’t have any problems finding entrants.  Five hundred programmers just gave up a weekend to write 248,000 lines of code. Teams up to four completed 131 different Rails projects in under 48 hours, so you can see just how productive a small group can be in Ruby.

Corporate IT: Sorry but we need dependable database connectivity, not this serial locking business.

Ruby: So pooled connections in jruby and Rails 2.2 scratch that itch?

Corporate IT: There still isn’t a big company backing it so no support.  No support, no chance bub!

Ruby: Have you ever actually called Microsoft about a .Net problem?  Or maybe Sun to support your Java app?  Maybe you have, or at the very least arranged a support contract with a .Net or Java consulting company.  Try instead one of the fine Ruby consulting companies like EdgeCase, HashRocket or ThoughtWorks.  Sun already bankrolls the JRuby guys and for the Softies out there, Microsoft is putting its wallet behind Ruby on the CLR.

Corporate IT: Books?

Ruby: New one every day.

Corporate IT: You’ll get me to use some text editor in place of my IDE when Heck freezes over.

Ruby: Not a problem.  NetBeans guy, Eclipse, or IntelliJ?

Corporate IT: Yeah, okay, you win.  Now can I have that stack of waterfall project specs back, they were holding up the table at that end.

Ruby: Have you ever considered Agile?

If you liked this article, consider subscribing to this blog via email or RSS. Also, consider subscribing to have our free weekly newsletter sent to your email inbox.

Photo attributed to Megyarsh @ Flickr CC

Aaron Worsham / Oct 14, 2008

To lead programmers, you must be humble

dogcupsuperfantastic

I’m tired of talking about how great I am.  What about you, what do you think of me?

There may have been a point in time when someone understood all that there was to understand about computers.  Early on there may have been one person who could stand above his fellow scientists and claim to be the authority on everything in this young field.  Where wizards stay up late makes a good case for a few individuals who may have filled that natural desire we have for an overall authority on a subject.  Yet those men, great scientists and tremendous minds in an unproven field of study, were some of the most humble ambassadors of technology we will likely ever see.

Today we have no overall authorities.  No normal person can hope to represent enough deep expertise to be considered an expert in more than one specialty.  Exceptional people may be able to handle two or three fields before being overwhelmed by the fire hose of information needed to keep up.  Hollywood has it wrong, again, about smart people in technology because there are no generalists out there that know everything.  Computers is similar to any other complex system like medicine, law, scientific research and finance.  It demands that you specialize to do be considered an expert.  (This may also be why I like House as a show but have problems with a plot device that pretends there are doctors that can ever know everything.)  Anyone who either pretends to be an expert on the whole of technology or really has convinced themselves that they are will be doomed to huge management failures.

Pete Johnson Chief Architect at HP and a guy who clearly knows what he is doing around a computer wrote up good article on Dzone about why programmers hate working for Software Architects.  Pete’s experiences run parallel to my own as a manager of programmers and his first point sums up my advice to anyone who wants to lead a programmer.

  • Be humble
  • Ask your people for advice on subjects you don’t know.
  • Make it public knowledge that you are the least important person in the room.
  • Stand back and let them shine before your customers, but stand in front of them to take blame.
  • Programmers can sniff out BS.  Honestly admit when you’re unsure of a direction.
  • Keep them informed and let them know when you are giving fact and when its your opinion
  • Ask only what you would be willing to do yourself.  Prove it by doing it occasionally for them
  • Keep a diverse RSS list and forward on good information to experts in your group
  • Be humble

What’s on your list?

If you liked this article, consider subscribing to this blog via email or RSS. Also, consider subscribing to have our free weekly newsletter sent to your email inbox.

Photo attributed to SuperFantastic on Flickr CC

Aaron Worsham / Sep 24, 2008

The impossibility of speed

speed1Microsoft, founder, organizer and social chair of the Desktop First Foundation, now sees through their own well trenched oppositions and admits that maybe, possibly it makes some sense for some applications to simple live out on the internet.  They now join Google, Yahoo, Apple, Salesforce.com, NetSuite, ZoHo, Meebo, Zimbra, as well as an uncountable number of neuvo-funded startups who have banked on the internet as the universal delivery platform for the future.

Oh, also, Google and Amazon agree that users get antsy when they have to wait more than half a second for their application to respond, affecting customer satisfaction and repeat usage.  Google’s VP Marissa Mayer recounted having experienced a 20% drop in usage for results delivered as little as .5 seconds slower than typical.

Possibly not for the first time, your customers are demanding the convenience and portability of online web applications while still clinging to expectations that web applications should consistently respond as fast as desktop applications.  An immovable object just shook hands with an irresistible force.

The problem with web applications, frankly, is the web.  Months of tuning web code can save seconds in application speed only to be lost in the network through slow routing, lost packets, or bandwidth throttling.  This is the impossibility of speed on the internet.  You have very little control out there.

To keep up with our need for speed, we will have to move more and more interface code off the server and onto the desktop’s browser in the form of Javascript.  Google’s chrome team seems to agree, focusing their performance efforts for web apps on a high speed Javascript engine.  SproutCore, famous for running Apple’s MobileMe web platform, is a fully modeled MVC framework in Javascript perfectly suited for this kind of application.  Servers could begin to revert back to simply offering data storage.  Instead of pageviews, we may soon be tracking information requests.  An online ad industry addicted to clicks and impressions may have to get back on the wagon and find a whole new model (they’re so agile).  This could be interesting.

I’ll just suggest this to any kid starting out the web development world: Learn JavaScript

Photo attributed to pctalbot @ Flickr CC

« Previous Page
Next Page »

Primary Sidebar

About Sazbean


Sarah Worsham (Sazbean) is a Webgrrl = Solution Architect + Product Management (Computer Engineer * Geek * Digital Strategist)^MBA. All views are her own.

Business + Technical Product Management

My sweet spot is at the intersection between technology and business. I love to manage and develop products, market them, and deep dive into technical issues when needed. Leveraging strategic and creative thinking to problem solving is when I thrive. I have developed and marketed products for a variety of industries and companies, including manufacturing, eCommerce, retail, software, publishing, media, law, accounting, medical, construction, & marketing.

Copyright © 2008 - 2026 Sazbean • All rights reserved.