31
Aug 10

2 months

Faveroo Logo

that's a pretty sweet logo

On June 3rd I typed the following into my Terminal.

mkdir faveroo
cd faveroo
git init

On August 15th I typed the following into my Terminal.

cd ~/src/faveroo
php deploy.php production

Then I watched and held my breath as my carefully crafted deployment script worked its way through 2 months of code and pushed them across the line. Then I fired up my browser and went to http://faveroo.com and waited for the now familiar homepage to show up… I’m sure it took less than a second to load, but it seemed like an eternity, finally it was up. I worked for the next few hours exercising the application through all its various operations, squishing little bugs here and there that popped up from being in a different environment. Two months of development, and finally it was live, and it actually worked. A few hours later we started hooking up people with sweet deals and putting money in the bank, mission accomplished.

Faveroo.com is my first project at my new job at 614 Media Group. It was a skunkworks project up through the end of July, so I couldn’t come to this blog and talk about it. I did all of the coding for Faveroo and my colleague Jeff Guciardo did all the design work to make it look so pretty (it’s probably the prettiest thing I’ve ever had the opportunity to create). The basic premise of the website is that our team of dedicated sales people go and find great local deals, then we throw them up on Faveroo.com, and then we help people save some cash. When you buy a Faveroo you save some money, the business makes money, we make money, and 3% of the sale automatically goes to charity, it’s win-win-win-win. But I’m neither marketing nor sales, so I will stick with what I know and what I knows is tech, so let’s talk about that for a minute.

Faveroo is a PHP website that includes the public frontend, a private backend, and a series of maintenance scripts that make sure everything works like clockwork. When I was starting up the Faveroo project I was given carte blanche as to how to build it. All of our other web properties use the classic LAMP stack, so to keep operations fairly sane and because I deeply love PHP, I decided to build out Faveroo on a classic LAMP stack as well. The code is Object Oriented, nearly MVC, PHP 5.2 code. I looked around, had been for a long time, at various PHP Web Frameworks. I had just come off of working with rails on a side project and so I knew the joy and frustration of work with a framework.

As you may be aware, I’m crazy in love with Flourish and decided that I would use it as a major component. I have been a fan of Flourish for a while now, probably over a year, but this was the first big application I was going to use it on, and really the first large scale from scratch application I have ever written. Now don’t get me wrong, I’m no rookie to this slinging code stuff, I’ve maintained huge legacy applications, built middle-ware up from nothing, and even rewritten large applications to the point that almost all of the original code has been replaced. But this would be the first time that if I didn’t like something in my code, it was because I was the stupid jack-ass that made such a boneheaded decision. Well, not the first time, but the first time I couldn’t easily blame someone else ;)

I want to say that the decision to go with Flourish is probably what made the rapid turn around time possible. It’s a wonderful library that helps you do things right but doesn’t force you to do anything you don’t need. The thing that amazed me as I used it is I started off only wanting to pull bits and pieces, maybe some fCryptography here and a little fMessaging there, but as I got familiar (and boy howdy did I get familiar) with the docs, I just found more and more amazing functionality and a beautifully coherent system. Flourish was clearly written to be used, and by the end of the project I found I was using almost every class. It’s clearly a tool written for real world use from real world experience.

Flourish and jQuery are really the 2 big external dependencies for Faveroo, the rest of the code was written by me. I found this minimal system worked very well for me. I wrote a router in about 100 lines of PHP code, it’s nothing earth shattering but I think it has a few novel ideas. I’ve since built a new version of this router that is shorter and has less complex code paths. At some point in the future I may try to make a more generic version of this router and release it open source. All of the model classes are fairly straightforward using the excellent fActiveRecord as a base.

I spent about a week spinning up my minimalist framework, but it paid off big. I knew how the system worked every step of the way, and more importantly, I could alter it in minor ways to achieve dramatic results. All of this is possible with established frameworks, but here I got away without having to climb up a learning curve. This gave me more time to understand the problem domain and to learn how to best use Flourish.

With this experience under my belt I’m looking forward to continuing to learn, and hopefully to contribute back to, Flourish and PHP development in general. This project has shown me that in 2 months I can go from nothing to cash hitting the bank account. I feel reinvigorated to make cool things that add value to people’s lives and reassured of my abilities as a programmer. After a long period feeling burned out and wasted, I remember why I love programming, and why I love creating, and why this is the only thing I can ever see myself doing.


05
Aug 10

Flourishing

flourish logo

Flourish's sweet logo

Looks like my claim of writing fast and furious didn’t come to pass, oh well. For the last few weeks I’ve been working on a hush hush project for work. It’s not done yet but we are nearing the end of the road for the MVP to be released soon. I wanted to write a quick update to discuss what it’s been like getting back on my developer feet after burning out.

First off I’m engaged in my work again. For months I had felt disconnected, on autopilot, just trying to get through the day and hit some milestones. Secondly, I enjoyed playing cowboy for a while but have cone to realize that not all the habits I picked up in Corporate America were bad. Thirdly, I’m back to getting serious amounts of work done and am solving interesting problems.

Enough touchy feely hippie bullshit, let’s get down to some business. I’ve been building a largish scale php application for the last couple of weeks and I wanted to reflect on the process.

I started off looking at various php frameworks a few weeks before starting this new project. I had kept an ear to the ground in the php framework area since forever so I knew the big players. I had also dabbled in some ruby on rails so I knew the bliss of when a framework gets it right, and the frustration of running up against something you would have done differently.

I looked into several frameworks CakePHP, Symfony, Zend Framework, Fat Free PHP, Yii, Noloh, and Recess! to name a few. They were all quite interesting but they all felt oddly foreign. Imagine if ruby on rails came out and it was a port of .Net web forms for ruby, blech. All the frameworks I looked at felt like they were trying to pave over PHP and make it into ruby lite or .Net lite. Each one was well put together on the whole and with some effort I’m sure I could have become proficient in any of them. Then I remembered an old friend I had played with before, Will Bond’s unframework Flourish.

If you haven’t taken a look before I urge you to do so now. Flourish is exactly what PHP needs, a strong core of classes geared toward common web tasks, with an eye towards simplicity, security, and consistency. After having used Flourish for a few weeks I can do nothing but sing its praises. Let me say that working with the combination of Flourish + PHP is a completely different experience than just writing PHP. Flourish gives you a sane construct around which you can build high quality applications. Here’s a list of things Flourish provides:

  • Cross Database support for DB2, MSSQL, MySQL, Oracle, PostgreSQL, and SQLite
  • An extremely good ActiveRecord implementation
  • Filesystem with psuedo-transactions
  • Safe consistent handling of Requests
  • Session handling with special resources for Authentication
  • Classes for creating HTML including a quality Templating mechanism
  • Great Utility classes (think ActiveRecord rails people)
  • Amazing Email support
  • Classes for handling Dates, Numbers, and Money
  • High quality Exceptions and Handling Facilities

The thing that you will notice with Flourish is that it’s a library that’s seen real world use. It provides a high quality core but understands that it shouldn’t try to be everything to everyone. The components interoperate nicely but you also function in isolation quite capably. It truly hits all the high points you would want from a library, but there is even more.

DOCUMENTATION: The Flourish documentation is some of the best I’ve ever seen. There is full PHPDoc for every class, which is nice, but more importantly there is “Class Documentation” that explains how the class is intended to be used, with code examples to get you started. The documentation is written very well and is incredibly in-depth. You could sit down and read it like a book, it’s that good.

COMMUNITY: The Flourish discussion boards are active and I have never seen a posting go unanswered. Will Bond himself usually answers within a few hours of your posting, I know he has more than once helped me fix some tricky bug or better explained how something worked to me. The ability to reach out and communicate with the author is amazing, it also makes you want to provide support for the project.

CONSISTENCY: The Flourish API is amazingly consistent. I keep finding myself saying, “That’s how I would have written it” while using it. If you learn how fCookie works, you know how fSession works, and you even know how fRequest works. Flourish simplifies things to the point that it’s worth it to go the extra mile to add a bit of security to your code, because it makes it dead simple. Then you look back and realize that it also has helped you write self-documenting code, and jesus, did it just fucking cut my lawn too, what the hell?

SECURITY: As I alluded to earlier, Flourish encourages writing secure code. Flourish takes security seriously enough to have an entire compendium on just that topic and how it relates to PHP. My code is definitely more secure now that I use Flourish, from better security in parsing Request variables, to easily preventing Cross Site Request Forgeries, Flourish has you covered.


Ok, so I didn’t really expect this to turn into a huge love fest about how much I love Flourish but that’s where we are at. I want to over the course of a few blog posts really explore Flourish. I haven’t fully figured out what format these are going to take, but if you are a PHP developer who wants to take their code to the next level, stay tuned.


25
Jun 10

Out of the world

The sun

This smarmy bastard's finally come back to Ohio

I’ve been out of the world for a little while, approximately 40 some days. I unplugged from a lot of things to focus on some big changes in my life. There was a kind of, cliche alert, perfect storm of events that made me feel like dropping off the grid for a while and just relaxing.

First off, this blog, which brings immeasurable joy to so many (for free I might add, actually the hosting costs me money) got 1337 h4x0rz pwned. You see I made this mistake where by I tried to express myself… foolish bastard that I am. Someone decided that all the good will and popularity I had generated through months of concerted effort and promotion would be better used to sell some scummy fake AV software. I quickly fired up my ftp and an editor to find out what was going on, I was able to detect the hack right away (normally don’t have giant evals at the top of my pages), some quick regex work and I was able to disable the attack within less than an hour of detecting it. But I had been compromised, and even though I had been able to address the immediate issue steps needed to be taken to protect my blog and the fine people that come and read it. I decided to take it down until I could get it cleaned up properly. I felt terrible, but I had taken steps to prevent such a hack from occurring, I couldn’t figure out what had happened. Then I saw this and realized that is exactly what had happened to my site. I felt a little bit better that this wasn’t my fault and I wasn’t alone.

The second major thing is that I quit my job. I worked at HMB for just over 2 years, and I learned an immense amount, worked with some of the best people I’ve ever met, and went from Ramen Noodles on milkcrates to my comfy house and filet mignon (if Burger King is still putting filet mignon in their hamburgers). It was a fantastic place to work right out of college but towards the end I felt like it wasn’t where I wanted to be in life. I found an opportunity to go work for a young media company in town that needed an experienced PHP programmer to take over for their “web guru.” I’m incredibly happy to report that I took that opportunity and am currently running with it.

The third major thing is that I was burned out. My last project at HMB was difficult, difficult for me personally in every way I can think of. I realized near the end that I was at my breaking point, I was frustrated, angry, and plain unhappy. I felt like I had nothing left to give, I felt completely worn down, and I knew that something would have to give.

That’s where I found myself a month and half ago, in a strange position where I was frazzled and broken but ahead of me sat this golden opportunity. I decided that I would unplug, unwind, and rebuild. I had become that proverbial Windows XP box with the 2 years expired Kapersky that was slowing to a crawl. My hardware was fine, but I needed to reformat (preferably with Ubuntu or maybe into a Hackintosh) and recover. One of the things that went on the chopping block was blogging, not intentionally at first, but once I stopped, well an object at rest tends to remain at rest…

I’m happy to announce with the relaunch of this blog that the “reformat” worked. What you see before your eyes is a fresh WordPress 3.0 install (with all the old content recovered from my numerous backups), a visual reboot (this is an out of the box cleanr right now, I’m planning on adding my own personality in gradually), but most importantly, a happy blogger typing. I’ve spent the last month and half settling into my new job at 614 Media Group. I’m not sure what my title is, on one piece of paper it says Web Guru, which I don’t much care for, I’ve seen and heard “Head of Web Development and New Media” which I like, even though its a bit wordy. I can tell you though that I’m in charge of PHP development (along with iPad and iPhone development to come) and that I’m loving it. I have a swanky new office, I get to work in TextMate and git and PHP all day, it’s a dream come true. I work with friendly, hip, funny people. I’m still finding my place there, but I have already figured out it’s where I belong. For the first time in a long time, I’m building things, and it feels so good to build again.

I’m not really sure what else to put in this post, I plan to start up the blogging again, refreshed and reinvigorated. You can expect to see a heavier focus on PHP and Cocoa, but I will still go off on my other loves, Ruby, LISP, JavaScript, and probably fall in love with some more. And even though I’m happy and contented I will still have amusing rants (just ask Heather if you don’t believe me.) I haven’t decided how much I’m going to blog yet, I’m hoping for a couple posts a week, but I’m sure I have plenty of topics to cover from the time I was gone so it might be coming a bit fast and furious for a while.

In conclusion I just want to thank all the people that helped support me when I wasn’t feeling at my best. My wonderful girl Heather, my dear friend Jeremiah, my family, and so many others. I also want to thank HMB for giving me a place to grow and learn, I’m still proud of the work I did there and proud of the work they do. I’m sorry I was gone for so long, if you come back and give me your eyeballs I hope to open them a little and maybe make you smile.


07
May 10

stir trek

Stir Trek 2010: Iron Man Edition

They are watching Iron Man 2 this time, but kept the Stir Trek name

This post is a little bit late but c’est la vie. I will be talking at Stir Trek today about all the new goodness baked into the latest release of jQuery, version 1.4. I’m taking a page from this very cool HTML5 Presentation and have decided to skip the normal PowerPoint and do the whole presentation in HTML5. It was actually quite easy to do and since I’m showing off jQuery I can have live demos in my slides, so no fumbling between PowerPoint and a browser. I used the HTML5 Presentation as a template so you will notice that the look very similar, I’ve kept their stylesheet and their slide javascript. The presentation is functional in most modern browsers but is definitely fine tuned for Google’s Chrome browser.

My presentation tries to be a quick redux of the information found at the jQuery 1.4 Launch Site, specifically the great introductory series jQuery 1.4 Hawtness by the very talented Paul Irish. I took the javascript code examples from the jQuery 1.4 Hawtness videos and built functioning demos around them to better illustrate how they work to an audience.

Keeping in the spirit of my open-source free-love hippie nature, the presentation is completely free for anyone to use. You can find the full source of it on github, feel free to download it or fork it and make it better. Well I’m going to go run through the things I plan on saying for the next couple of hours, so pardon the brief post. It’s been an interesting time in my life recently and once everything settles down I’ll have some big news for everyone, so stay posted.

Edit: Realized that I can host whatever I want on my domain so instead of just linking to the source code on github I can actually host the presentation on this server. If you want to check it out go to http://ihumanable.com/jquery/presentation.html, remember it works best in Chrome but should work ok in other modern browsers, for IE users you will have to load up Chrome Frame.


12
Apr 10

saying nothing

Dialog saying "Error: An Error has Occurred"

Thank you, very helpful

As a software developer I have the great joy of making things that piss people off. Nothing makes someone angrier than after an hour of meticulously entering financial data, you hit the submit button and get back the error pictured to the right. In actuality, good software developers go to great pains to make their systems as resilient as possible. A large amount of the code written for any complex piece of software will be dealing with error conditions, recovering from the recoverable, and gracefully reporting fatal errors in a way that indicates exactly what happened and why and what to do about it.

One of the best features an error message can have is Google-ability. If the error has a prominent and distinct feature, then a Google (insert your favorite search engine here) Search will be able to deliver relevant results with a much higher degree of accuracy.

Good Error Message Example:

Error ERS1708A - Invalid Character
The field "Zip Code" should only contain numbers, "47CD101" is invalid.
Examples of valid input: 44130, 90210, 43220

Bad Error Message Example:

Form Invalid!!

The first error might be a little overkill, but the first part meets are Google-ability test. Typing ERS1708A into Google will pull up solutions for this problem. The error goes on to report exactly what went wrong in a user friendly way, it even goes so far as to give some samples of what correct input looks like. The second example gives you a vague idea that something bad has happened, something dealing with a form, and if that form happens to have 100 fields on it, well good luck figuring it out (maybe it’s even one of those awesome programs that will clear your entire form on error). The problem is that you are equally likely to get either of these error messages from the same input depending on how much effort the programmer put into error recovery and reporting.

We all know that we should strive to help out the end-user and give them good error messages (even better if we can have robust recovery so we don’t have to report errors). The problem is that programmers often have to be toolmakers as well. Sometimes when making a tool for other programmers to use we let our error reporting skills slip, these aren’t mouth breathing users, these are 1337h4x0rz and will find your undocumented command line tool completely natural. I ran into this mentality today while troubleshooting a Windows Service installation problem. The Service works great on my development machine, works fine on other peoples laptops, but on the security locked down Mobile Data Terminals that the Service actually has to run on, no dice. The error that was being reported during installation was…

The system cannot execute the specified program

This fails in every way imaginable. Completely un-Google-able, go ahead and try it, you will find everything from people installing things on WinPE, to game development, web controls, Server installation…. a deluge of crap. The error message is amazingly useless, the system can’t do something, what can’t it do, I don’t know, it doesn’t even tell me. Can it not execute the install.bat file, maybe the executable called by the install.bat, maybe the executable that executable invokes, who knows?!

Well being a clever programmer and systematic debugger I was able to isolate each piece working towards the fact that what the message actually should have said was, “Although I have all the permissions necessary to access and execute all the programs you want me too, one of the programs requires that the system have the Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) installed on the machine before you try to execute it. If you install that, then I can find the dependencies I’m missing and everything will be cool, kthxbye!”

Error messages are one of the few times that we as programmers get to actually directly communicate to the user. Don’t waste this opportunity by effectively saying nothing to the user. The error message is a traumatic thing for most users, happily working along until it pops up, keep it short, sweet, descriptive and helpful.


07
Apr 10

sitting

meetings demotivational poster

In case you didn't read it: None of Us is as dumb as All of Us.

<rant>

There is a lie we like to tell ourselves that goes something like this, “I am in control of my life.” You are not, it’s a cultural lie though, one of those things that we’ve all agreed makes us feel better so we politely nod our heads and lie to each other and all get through the day a little easier. It’s similar to that radical 90′s style lie I grew up with during school that went something along the lines of, “Everyone is special and magical and made out of ponies.” Everyone gets a trophy, even if you didn’t win, because you are special just for trying. It’s a lie that everyone knows is a lie, but it makes people feel better, so what’s the harm.

Well over the last few months it’s become apparent to me that these things are lies, that I’m no more in control of what goes on in my life then my dog is of his own. At any moment someone could walk through the door and kill us all just for laughs, or someone could hand me a million dollars. The uncertainty of it all is unsettling and exciting. The one thing that has slowly crept into my life recently is the subject of my post, and that is the hallowed institute of meetings. Somehow I went from a code ninja hacking down mountains of whatever was thrown in front of me to a table jockey. I am now scheduled to attend no fewer than 8 meetings per work week.

That works out to 1.6 meetings/day, and rest assured there is at least 1 meeting everyday. I know people that do nothing all day but meetings, it boggles the mind. I would say that I “hate” meetings, but that really doesn’t convey the depth of my loathing for them. Meetings are the bane of my existence, I could stomach maybe 1 a week, a short sweet status meeting, but what I can’t handle is the bread and butter corporate meeting, and I’m going to detail why.

  1. Marketspeak: I don’t know what the fuck happens to people when they get in meetings but everything, everything gets some fancy new moniker. Sure I could say that I’m working on some stuff, but wouldn’t it be better to say that goal-forwarding has been achieved on several Tier-1 action items. There are no people anymore, just assets and resources, dehumanized by the cruel tongue of Marketspeak. Every concept, no matter how simple, is wrapped in shiny new clothes, as though you might confuse the dog turd covered in whipped cream as a delicious fudge sundae.
  2. Teleconferencing: There is always some person (sorry, meant to say “stakeholder touchpoint”) who thinks its appropriate to call into the meeting on a 1992 Nokia Celfone while in the middle of a monsoon while driving through a tunnel. Bonus points if this person has a thick accent that makes even high-fidelity communication less than understandable. The other issue is having 10 people on one side of the conference line and 10 on the other, and the fun of each side trying to figure out who is talking.
  3. Pointless Status: Managing people is difficult, so management is obsessed with the idea of status. The problem is that status is normally not quantitative but qualitative, too bad that doesn’t fit into the Holy Spreadsheet. People are forced to turn things into percentages, I’m 80% done reflanging the spline, even if that doesn’t make any sense. Status reports are a proxy for involvement, they are a way to feel connected to a process you don’t have any part in.
  4. Workturbation: Meetings are insidious, if you have 8 hours of meetings you will go home mentally exhausted, more than likely frustrated, and with a feeling that you’ve really put in a hard day’s work. The problem is that when you try to figure out what you’ve actually accomplished the list is either non-existent or incredibly paltry. Meetings feel like work but rarely accomplish anything of actual significance. Meetings also have the incredible ability of spawning meta-work just for the sake of the meeting itself. Before the meeting you have to prepare whatever pointless agenda you have for your meeting, secure a place to have the meeting, work around everyone’s schedules. Afterward someone prepares the minutes and it gets emailed to the companyname-all mailing list where inevitably the tiny list of things that were actually decided are rehashed again and again. Personal bikesheds are floated around, and more than likely all the chatter on the email list will require ANOTHER FUCKING MEETING to sort out.
  5. Punting: Punting is the amazing technique where something interferes with the meeting so it is moved down the road to another meeting. Punting is sometimes necessary when someone wants to discuss in detail some trivial point, but the best and most frequent kind of punting is the following. Design meeting is convened, difficult non-trivial thing is brought up that requires actual thinking and problem solving, meeting participants get frightened by the idea of actually having to dust off the critical thinking part of their brain instead of blithely parroting made up statuses of underlings, issue is tabled to be dealt with in the future, a piece of me dies inside. Keeping the meeting moving becomes MORE important than getting anything decided or accomplished.

The list is in no way exhaustive or universal. At the end of the day though, a meeting is taking up time you could be doing something, they should be looked at that way. All that time you are sitting in meetings talking about all the stuff that could be getting done if everyone wasn’t stuck in meetings all the time… my head hurts. What we need are people with their hands on the problem empowered to make decisions and move things forward. Then we can meet once a week to talk about how things are going, instead of sitting around all week wondering why nothing is getting done.

</rant>


31
Mar 10

micro-optimization

nero fiddling as rome burns

Yea, I know it's on fire, but check it, I almost got Freebird down pat.

As all good developers should know, one of the cardinal sins of software development is premature optimization. Premature optimization is bad for a whole host of reasons. But there is another set of optimizations that are in the same realm of bad, micro-optimizations.

I recall learning at some point that in C and C++ it is more efficient to use the pre-increment operator rather than the post-increment operator. Why is this the case, well it’s because of the minor difference in behavior between the following two snippets.

  int source = 10;
  int destination = 0;

  destination = ++source;

  printf("Destination: %d", destination);  //Prints "Destination: 11"

Compare with this snippet

  int source = 10;
  int destination = 0;

  destination = source++;

  printf("Destination: %d", destination); //Prints "Destination: 10"

WHA!? This is actually exactly what we would expect, pre-increment increments the value BEFORE assignment while post-increment increments the value AFTER assignment. What does this all mean, well basically that if you use post-increment you are executing more instructions, because the compiler has to keep the old value around to return to the assignment. That means that unless you are assigning the value and require the particular behavior that post-increment gives you, you can generate faster code by using the pre-increment operator (this may be handled by compiler optimizations these days).

All of the for-loops that you’ve written for(int i = 0; i < something; i++) are identical to and SLOWER than for(int i = 0; i < something; ++i). NOOOOO!!!!! Don't worry though, because this is a micro-optimization, its something to not care about, because in reality that one or two extra machine instructions isn't your bottleneck. Micro-optimizations are all those tricks that make code faster that in the vast majority of cases (although not all cases) don't really amount to any actual noticeable performance gain. A new processor can do something in the magnitude of 100,000 MIPS (Millions of Instructions Per Second). Every second it does 100,000,000,000 Instructions, that is 100 billion instructions. every. single. second. Changing from post- to pre- increment saves 1 or 2 instructions, so for every time that gets executed you have saved a 100th of a nanosecond.

Micro-optimizations are rarely worth the hassle, and, as with premature optimization, the solution is to benchmark and trace where your actual bottlenecks are and go about solving those. It doesn't matter if you're screaming through your increments saving a whole nanosecond if your crappy no index having table is taking a whole minute to read because you are doing a table-scan.

But wait, there's more. Micro-optimization, like everything in programming, can be directly applied to life in general. I work with a person who will spend 5 minutes discussing how to save 30 seconds, this is another incarnation of the micro-optimization. It's that shortcut you take home that actually takes longer, or some everyday voodoo that is draining your time without paying you back, or that client that provides you with 2% of your income but eats up 40% of your effort. Micro-optimizations abound all around us, in the little picture they seem ok, but in the big picture they are nonsense. Take a fresh look at the things and obligations around you and examine them for micro-optimizations, see if the things you do make sense in the big picture.


18
Mar 10

kids writing code

3 children at a computer

you doody head you forgot to clean up your EventStruct!

Last night I went out to get some dinner and as I sat in the drive-through waiting for the unbridled joy that is Cain’s chicken I listened to the radio. WOSU’s All Sides had a piece about child poverty and mentoring. It was interesting and thought provoking, one of the guests said something that rang true and made me think. (Paraphrasing because the audio is currently unavailable) He started to realize that the kids were excited to have him come talk to the class every week, not because they were interested in his stories about the Post Office, but because they wanted to know that someone cared about them. It was a powerful thing to remember, that children need to know that someone cares for them, and that not all children are that lucky.

In writing this blog one of my favorite memories is doing the research to write the teaching post. It reminded me of the heady days of my youth spending hours inside of the amazingly good QBasic help file trying to get something to work, stumbling and bumbling, put beaming with pride and a giddy happiness when I finally got the program to work. These days the amount of programming languages geared towards teaching have only expanded, and systems like Alice put LOGO’s turtle graphics to shame (although I still love that LISP-laden turtle).

This started the old gears turning in my head, and although this thought is pre-pre-alpha, I thought I would get some feedback and just jot down what I’m thinking. What if there were an after school program for elementary school aged children where IT professionals donated their time and talent to helping kids learn how to program. Children need mentoring, the IT community has a wealth of talented and caring people, let’s put these two things together and see if we can do some good. The logistics of this are a little daunting, but I want to lay out the reasons why now is the right time for just such a program.

Programming is the new literacy. Don’t believe me, here is an article entitled Programming is the new literacy. As we move forward into an increasingly wired future, programming, scripting, mark-up, are going to become skills that are normal to have. Children are already more “plugged-in” then ever before, the benefits of understanding the machine they’ve been using since they were in diapers is apparent. As the information economy continues its march into the 21st century, people will need these skills. From a simple formula in an Excel Spreadsheet to whipping up a ruby script to do batch processing, these will become the differentiators of tomorrow, helping people achieve.

Hardware has never been more accessible. Moore’s Law is a thing of beauty, I just bought a more than capable HP refurb for $150 to act as a media server. OLPC has shown that putting affordable computers into children’s hands is possible, and it looks more and more likely that school districts in the Industrialized Nations will be following suit in the next decade or so. Companies routinely donate their old computers which means that if $150 is too much (which it is for a lot of low income families) then you can get a donated computer free. Children can also access computers at libraries and schools for free.

Software has never been more accessible. The number of languages specifically targeting teaching has only been growing. If you haven’t already, go read the teaching post, it is a round-up of just a handful of the neat and nifty software meant to help kids learn to program. The learning curve has never been gentler, you can go from a learning language like Hackity Hack (which is based off of Ruby) to the full Ruby language fairly easily, and from there you can explore the whole world of Ruby development from Rails to Unicorn and back again.

Programming is about more than computers. Although the immediate goal of learning to program is to instruct a computer in how to perform a given task, the side benefits are immense. Programming teaches children a structured way to solve problems, learning about control structures teaches the ideas of Boolean Logic, writing formulae increases and reinforces the understanding of mathematics. Programming is also empowering, being able to sit down at a keyboard with nothing more than your wits and a good idea and turn it into something real is an amazing feeling for a child. Programs let children learn and explore, make mistakes and figure out how to solve them, with gentle encouragement and careful guidance a child can turn their ideas into reality, and that’s a powerful lesson.

Where to go from here? I’m not exactly sure, the logistics of setting something like this up are a little out of my league. For right now this is just a good idea, I’m at step 3 of the idea ladder. Leave a comment, let me know what you think, if you are a parent, would this kind of program interest you? If you are an IT professional, would you volunteer at such an organization? If you are a business owner, would you support such an organization? If you are a child, would you like to learn to program?

I’m not sure where this idea will go from here, but I’m excited to find out.


17
Mar 10

let me google that for you

let me google that for you

I wonder what Google's legal team thinks of this website

I was recently given the task of writing a Windows Service in Managed C++ (or C++/CLI I can’t quite figure out what it’s actually called). Having had 3.5 years of C++ experience from college and basic literacy I started clicking around in Visual Studio like a blind man searching for a nickle. Everything was going great until I got to the code it generated… there were ^’s and gcnew’s and all kinds of craziness. It looked like the Standard Template Library and C# had gotten together with a bottle of tequila, the next day C++ was knocked up and throwing up carets all over the place. This was not the C++ I had learned back in college on our quaint little Unix box editing code in pico, this was some new monster that vaguely resembled an old friend. Undaunted I clicked this link and began the journey on the road of enlightenment. Right now I have a Windows Service that builds and hopefully over the next few days I can confirm that it actually works.

This got me to thinking about the vast wealth of information sitting literally at our fingertips. I recalled the phone call I had with my mom over the weekend that went something like this.

Mom: They asked me at work to archive some files by burning them to a CD.
Me: Oh, how’d that go?
Mom: Well I had to use a Mac, and I don’t know those so I asked for help.
Me: Makes sense.
Mom: The only person who knew how to do it said to use Toast, but that wasn’t installed. :(
Me: What did you do?
Mom: Well I thought, how hard can this be, googled it, and followed the tutorial, it was really simple.
Me: You’ve just taken your first step on the road to geekdom, congratulations.

The dirty little secret is that for anyone that’s good with computers, unless you ask them a question directly in their area of expertise, they might have some vague notion but will more than likely just end up Googling it. “My computer crashed and the BSOD said STOP CODE 0xA70000084, what does that mean?” What you will hear on the other end of the phone is me biding my time while I type “STOP CODE 0xA70000084″ into Google and look for the answer. Because, and this may surprise everyone who is not a computer person, having a CS or MSI degree does not mean that you programmed Windows. There is a world of stuff for us programmers to try to hold in our brains, and every error code shooting out of Redmond is low on the totem poll.

If all us nerds are just Googling things, then why don’t normal people do it. We know that everyone Googles stuff: “Naked ladies”, “Hot naked ladies”, “Other naked ladies I haven’t already seen”, “How to erase your browsing history”, etc. Why don’t non-technical people think about typing that perfectly searchable error code into that happy little textbox? There are a litany of reasons from laziness to sloth, but I think the one that most people fall into is intimidation.

Google is power!!! You ask it a question and you get a list of a gajillion results. Don’t believe me, I’m going to search for blue screen of death and it returns 9,710,000 results in less than half a second. If you are a non-technical person that is a sea of information, its even worse for technical problems, as the most relevant links are normally some discussion board with a thread 900 replies deep, the solution normally some incantation you chant over the motherboard while spraying the monitor with goat’s blood. For the technical doing things like digging around in the System32 directory and clicking around is everyday no big deal stuff. For the non-technical, who normally have the “I hid this for your protection, don’t touch these files or your computer will explode” screens still on, it can be a terrifying leap of faith.

system32 scare screen

for a normal user this is like a grizzly bear with chainsaw arms

The thing that we can do to encourage our non-technical friends and families is to teach them to fish. Normally we just want to give them a fish and get on with our lives. When you take the time to explain how resilient a computer is and how easy it is to find the information, after a while they will come around to solving their own problems. And it’s like sweet sexy meth when they do. Try to remember what it was like to have that thrill for the first time of being able to command the computer to do your bidding, once they get a taste they will want more, which may actually end up being more work for you, but it’s the good kind of work that furthers another’s understanding of the world.

Drop some lmgtfy love on your loved ones, help them help themselves, introduce them to the intoxication of solving their own technical problems. Once people realize that computers do what we tell them and not the other way around, the world will be a much better place.


16
Mar 10

ideas

chimpanzee in classic thinker pose

In the future, we will rule this world!

Ideas are interesting things, we have them all the time, we dismiss them frequently, and we value them heartily. Some people don’t like to talk about their ideas, don’t want people to steal their million dollar brain baby, and I can respect that, but a million dollar idea with zero execution is worth nothing.

Ideas, like misery, love company, if I tell you an idea your brain will immediately start thinking about it, having its own ideas and interpretations. Then you tell me your ideas that my ideas caused and I get more ideas and so on and so forth, this is the basis of a conversation. That our ideas can grow and change organically, that we can piggy back off of each other, this is the basis of our society. But let’s get out of the woods of the abstract and into the city of concrete.

What I want to talk about today are those entrepreneurial ideas that we all have from time to time. Those things that you are certain will make you rich and famous, or the ideas that leap back into our minds when we see some new thing, a worldwide pornography distribution network, Tim Berners-Lee stole my idea! What should you do with these ideas, how should you handle them, and why and what and huh.

Every person will have their own way of handling the little lightning bolts that leap into their head but I want to take you through the path that I’ve found helpful for me.

  1. Write it down – I write down almost every business thought I have, no matter how far fetched, and no matter how overloaded with tasks I am. This seems a little silly, if you are actively working at one thing it can even feel disloyal to start thinking about something else, what am I a squirrel easily distracted by a shiny piece of tinfoil? No, in my opinion you can never have enough ideas in reserve. It doesn’t take too much time to jot down enough information to be able to recall it later, and it doesn’t mean you aren’t serious about your current set of priorities. We would all like to think that everything we are working on will always work out, but you will never be sad that you have more ideas to fall back on.
  2. Percolate – Go do something else, even if you aren’t actively thinking about something, after writing it down it will be floating around in your brain someplace. Great ideas refuse to fall to the wayside, if you find yourself coming back to something in your head more than a few times, move onto step 3.
  3. Talk it out – Share your idea with other people, sanity check it, see if they laugh at you. Don’t get discouraged too easily though, great ideas can sound crazy and still be great ideas. After discussing it with a few people you can get a handle on how realistic it is and how excited you should be about your new idea.
  4. Prototype or Shelf – If you’ve made it to step 4 you have to look around and prioritize, it’s easy to be swept up in the novelty of a new idea, but strive to objectively adjudicate whether or not you have the free time to move forward. If you do, grab some technology you are comfortable with and make a prototype, don’t invest too much time or money. If not shelf the idea, keep a short list of things ready made to work on and add this idea to it.
  5. Focus Group Lite – If you made a prototype put it in front of some people, or float a pilot program. See how people react, sometimes an idea can sound great until you see it, then you realize some fundamental flaw. If this stage is good then move onto step 6.
  6. Jump in with both feet – Get cracking. If you have the time, passion, and indication that people could use your idea, go for it. It will be difficult and you will probably fail, but you will be better for it.

Ideas are nothing without execution, but they are still valuable. Make sure you save your ideas, bounce them off of other people, and if your gut and other people tell you to go for it, take the chance. You may not always succeed, but you will rarely be disappointed that you tried.