The web for non web people

The more I work time I spend working on the web, creating sites for various reasons the more I see there are people who work on the web every day and can not write a single line of code to create a site. Fortunately the web is not all about complicated programing and making boxes and images look nice. The web is a communication platform, it is a tool for all types of people to use to make connections, whether that is talking, trading goods, expressing an opinion, the web is a platform where anyone and everyone should be able to go to communicate freely.

It also happens that  not all people who spend their day to day working on the web could, if left in a small room for a few hours, create themselves some semblance of a website. But I don’t think that is necessarily that important. I also believe there are great thinkers who understand above all else what makes the web great, what makes the web terrible and these people can see a road down the good paths whether or not they can get there by themselves. I think if you want to be native to the web you need to hit most of these main points.

Out of body experiences

Though it is not an easy feat to achieve, being able to getting into another’s shoes and seeing a project you are working on from another perspective is a great skill to have. You do not need to be the designer or the developer. Anyone who spends lots of time thinking about a site in any way has to be able to remove themselves from that role and find a way to be someone who hasn’t seen it before. There are tools for this and things like usability testing and analytics to help us see what it is others are seeing, but even if you can’t have that out of body experience allow yourself to acknowledge that there are other people seeing this creation of yours and wondering “What the fuck?” Keep that in your back pocket, pull it out as often as you can, sit back and really think about what someone else might think of what you are doing, and you’ll be better for it.

A road built out of intersections

In that same vein it is important to realize the internet is a big place. Understanding that people have the freedom to go in any direction at any point is a sobering fact when you are creating an on-line experience. Users can come and go from any page, leave a page in the middle, find a page in the middle, start at the end and zigzag all the way to the homepage. This is the way of the internet. When you can, again, step back and think, ‘what about people coming just to this page?’ or, ‘what about people who read the content starting here or there?’ you are thinking about the web as it truly is, free open and full of intersections.

Not just a newer, shiner brochure

I hope it goes without saying in the year 2011 that the web has to be thought of differently than a piece of print collateral. Not only can web sites and applications do many more cool things, even static webpages are intrinsically not print. For one thing, when you think about paper, well, it’s all the same more or less. Some of it may be thicker or thinner or shiny or matte, but it’s all paper. Not to mention print art is specified to a paper size and weight. When working with a browser there are people coming from a site on a variety of different browsers, computers, monitor sizes and even mobile devices; all of these things matter.

I think the web industry has created this problem for themselves in some ways. There isn’t a great way to show what a website is supposed to look like as a rough concept without a program like Photoshop. But a static image make a website not. If you’re going to work on the web in any way you’re going to have to accept the fact that what you’re seeing will not ever match 100% what another person is seeing. That’s not a bad thing if you’re not afraid of it, be ready to be flexible, the important part is that the content is readable, the design works for your content and make sure nothing is seriously broken. It’s not lowering your standards, it’s being realistic.

My old diskman isn’t an ipod, what gives?

Ah, so you bought a discman in 2001. It came with the awesome over-the-head headphones and plays CD’s with mostly minimal skipping, congrats. But what’s that, you want to load your .mp3 files on to it and control it with a cool touchscreen interface? Well guess what, it wasn’t made for that. Your 2001 discman is not a 2010 ipod. Sorry. This is the same deal as trying to force your modern website to match perfectly in IE6.

IE6 was produced in 2001, at the time it was a great browser, it really was. However, it’s so far past its prime as a piece of software it is growing digital mold. Microsoft itself is telling folks to stop using it. Since that time they have released two major browsers IE7 and IE8 (neither of which are perfect) and our working on Internet Explorer 9 as I write.

Are people still using IE6? Yes they are. Corporations have built frameworks around that browser and the operating system it originally came on (Windows XP) and don’t want to, or can’t afford to change. So yes, sites in certain situations should be made to accommodate IE6. But here’s the deal, things will never work the same way in IE6 as they work in other, newer browsers. Like the last section, be willing to be flexible, the internet has many forms, content is content in all browsers, links work everywhere and people can buy stuff from your store, get your contact info on any browser despite your design matching pixel for pixel in ie6.

Talk to the developers, we’re people too

Sure we like to hide in our little cubes or at our desks and listen to our music. But on the inside we actually like to talk, well, at least some of us. And those who don’t like to talk probably do like to talk about the internet. It might all sound like technical babel, but if you press them a little, developers and designers can actually explain things in English, I dare you, give it a try.

Finished is a bad thing on the internet

When it comes to finishing something people are generally wired to think that finishing is a good thing. If you finish something, you can be done with it, you can feel a sense of accomplishment and most importantly you can move on. With almost all forms of projects finishing is a really good thing.

Finished is a word that can be used in a negative way as well. Those damn dirty Finish people! Only joking, no racial slurs here. Of course I was refering to the word finished as in done, dead, knocked out, down for the count. That is a pretty negative thing and generally is bad for a business, sports team or my late grandfather.

It turns out, that when it comes to the internet, being finished in the accomplishment sense is not really possible. Yes, you can finish you design, finish a site build, finish a widget or a feature but can you actually be finished with a website? Unfortunately too many people would answer this question with a resounding yes. The correct answer to this question is no.

I know others have been preaching on this subject for some time now, so it might not be a new concept, but think about it. Name a site that you enjoy checking out, it doesn’t have to be daily or weekly, but think of a site that has engaged you, made you think, shown you something awesome. I’ll will bet money that the sites that fit these criteria were not launched one day, someone breathed a sigh and said, ‘there, finished’ and they didn’t touch the site again until it was time for version two, six months or a year later. Essentially websites are not printed materials, the best sites are living breathing entities. When a site is actually “finished” it is likely on the way to the grave.

Sites that sit for long periods of time with no new content are less relivant, google knows this and weigh their search rankings on sites that are updating frequently. Google, which is actually a company made out of pretty smart people and not a giant scary machine, is taking a perception of an outdated site and putting that into their search engine results. The search engine is simply perceiving what a normal human would percieve, an old site that hasn’t been updated is likely old news and therefore less important.

What does this mean

The point I would like to make here is this. Launch your site before it is ready. Speed to market still means something and the sooner you are up and running on some level the sooner people start to notice what you are doing. Every feature you waited to add in the original launch is a value add to frequent or infrequent visitors when you release it down the road. The biggest companies working on the internet all knew this and started off very slowly. Amazon was a mere shadow of what it has grown into. Google has and will always be slowly adding features, their site is never finished, but they do it tastefully, little changes here and there that keep adding new value to their product.

Something I believe is useful is something generally refered to as a soft launch. A soft launch is a launch ofsite that you start having friends family and anyone else start looking at. Yes it is available to the internet as a whole, but you don’t start marketing very hard right away. I have made this part of my process when launching sites. Just this weekend I soft launched a site, This site has no where near the amount of features I would like it to have, I am still working on things, tuning this and that and getting the site ready to be heavily marketed. However, in this state people I tell or any of the site owners tell are taking a look, getting an idea of what is coming. Also, the site owners are adding content, learning the admin panel and generally becoming framiliar with the site. When we finally do start telling the whole world about the site we will all have had time to iron out the bugs, add some final touches and really be ready to launch.

But, we wont call that finished either because finished on the internet is the same as dead. Don’t finish your sites, continue to work on them, your will start to gain traffic faster and those visitors will thank you for continuing to improve your product.

Back to my web roots

Here and there I do a little pro-bono project as I imagine many web designer/developer types are prone to do. I am not sure what it is about the web but occasionally it demands of us our time and effort on something we know will never pay out. I don’t think you’d see the same thing from professionals in other fields. Imagine a free surgery, a free day in court; those things just don’t happen (and if they do I’m going to say with some assurance not as often as a free website happens).

I think this is because information, as Jeff Veen once famously (in my mind) said, wants to be free and those of us working on the web want to make it free. I also think this is because at our roots web designer/developers also want to make things for people who would appreciate them, money or no. We just all had to make a living too. And if this is not the case for most designer/developers out there it is at least the case for me. I do occasionally enjoy helping a good cause or a poor but deserving organization to a good website. I also generally like to see how fast I can do it.

When free is going on, why not try for a bit of speed? I think either of these projects took less than 6 hours, and without having to build in wordpress or any fancy jquery bells and whistles, these two sites harken back to my roots. When web pages were hypertext documents, the written word with links, a couple pictures here and there and a lot of love, quickly. The difference now of course, theses sites validate as XHTML Transitional, include stylesheets, not mustly old table structure and look considerably better than the pro-bono sites I had built when I was a young lad with fresh eyes to the web. Here’s to going back to my roots and a couple of old fashioned, pro-bono sites.

Thoughts on An Event Apart

I posted earlier last month about my excitement involving my chance to attend An Event Apart in Minneapolis this year. I just wanted to take a couple minutes and write my thoughts, impressions and opinions about the conference. As this was my first conference and I had heard so much about the quality (and of course the major names in web design, development, UX and content strategy) I was, at times, excited, nervous and delighted.

First impression

Nothing sets the stage for a promising day of learning like a gorgeous hotel in the middle of my favorite big city. The Hilton Minneapolis not only provided a great location, fantastic conference rooms and decent wifi (I never had any issues while others may have). An it never hurts that the first thing I had a chance to eat was a spectacular omelet, and while we are on the subject of food and venue, I’d like to make a note. There was so much delicious food available both days, I could have gone there just to eat. I was seriously in epic food heaven. I also found myself riding the escalators to the open 2nd floor balcony and gazing out at the busy city streets in-between speakers just because I could. The setting and food both get some erroneous amount of stars because they both pleased me.

Speakers, teachers, comedians, story tellers

So, the real reason to be there was not the plethora of food. The real reason to be there was because some of the largest brains in all of web design, front-end development, UX and content strategy. The beauty of the whole thing was that these people were not only extremely knowledgeable, they were approachable, gracious and generally good humored, fun folks. While some talks were drier than others, many of the talks kept me not only interested in subject matter but entertained as well.

I enjoyed every presentation but allow me to mention some highlights.

Ethan Marcotte (@beep) has been leading the charge for the last few months with a principal he calls adaptive design. The ideas that a flexible gridflexible images + CSS3 media queries = a design for all screen sizes and mediums is one of the best ideas I have ever heard of in web design. I think, to the point that he is making, this is finally a design structure that is native to the web. No longer forced to stand in the shadow of print design this is a place where web design can be what it needs to be, it’s own unique type of art and science. Fighting screen sizes with a fixed layout has been a folly for years, fighting devices with a fixed layout is rather silly and honestly I had been hesitant to do it because it seemed so much like a losing battle. Finally, though I had been playing with this already, Ethan’s demonstration is a point I can look at and say, this is when it all changed, this is when web design stood up, got out of print designs shadow and moved on.

The other presentation I will mention, though there were many memorable ones (and if I had a mind to I could write many many paragraphs about each presentation), is the presentation by Minnesota native and epic content strategist Kristina Halvorson (@halvorson). As someone who does not specialize in the content strategy game (but wishes I had a much, much better grasp on it) I was absolutely floored by her presentation. Something that I battle with when dealing with clients is that I have no plan set in stone for how clients should attack their own content and how I should help them with it. Kristina helped by providing me with some tips on actually providing some direction, an outline and a process surrounding how a client could tackle their content and how I can get involved in assisting them in that process. It doesn’t sound like a lot, but some direction I obtained from her presentation plus knowing she has a book out on the subject is going to give me a lot better grounding in content strategy as I try to help clients attain their content goals moving forward.

The personal touch

One of the bigger things at the conference for me was the after party. The food was great, the speakers were awesome but you know me, I just want a beer. Well, not really. I really enjoyed hearing from others in the field and getting the “community” part of the web community figured out — and in person, not on twitter for once. I had the chance to talk to a lot of great folks, not near as many as I would have liked but, most importantly I got up a little courage to follow up with one of the presenters.

In my mind I am still the youngest one in the room. Was that the case at AEA MN? I suppose there could have been younger people or people my age all around, usually not, but it happens. I am sure whatever the case I am not that much younger or that much less experienced, but, it can get to feel that way. Fortunately I was inspired by another young person (still older than I am by a bit) who has really made a name for herself with her knowhow and success. I sat down to talk to Whitney Hess because I have found myself inspired by her success and notoriety. Would I like to be working at her level, well, I am not sure, but having the community know who you are and respect your thoughts would be a really nice thing. It was really easy to see how Whitney has achieved what she has. She was instantly friendly, open, smart, funny and really everything you would expect someone working at her level would be. We chatted about a lot of different things, but what I took from the conversation and the whole night was this:

  • Essentially, being worried about getting out there and shaking hands is all in my head. I don’t look young, I don’t feel young, that is a barrier I have provided for myself. Even if you feel, or actually are 12, get out there.
  • If you’ve had a successful project you have something to teach someone.
  • Don’t expect the people with more experience to be unfriendly or unwelcoming of you and your ideas. I think at some level we all have a desire to pass on what we know and learn from those who know less.
  • And by the way, get your twitter handle on a card and hand it out in social situations. Great way to have people remember you by connecting afterwards on twitter.

That was my experience with An Event Apart. Really a great group of people attending the conference, an awesome line up of presenters (although, I do still wish I could have had the chance to see Andy Clarke’s talk), and just generally an excited, passionate atmosphere that has carried on for me weeks afterward. I am still excited to be working on the web as a part of the web standards movement. It is an exciting time to be a web designer/developer.

Everybody WordPress for the Weekend

So when I am not too busy on the weekend I’ll take a few hours to to sit down and work on a “just-for-fun” web project. Sometimes it is something for me, sometimes it is a learning project or a design project with no real aim, but recently my friend James Krantz and I have been working on a wordpress custom WordPress site. The intent with the site is to give it as gift to some old friends of ours. They are currently using a blogger blog and we both think it is holding back their potential and creativity so we are building them a new wordpress site.

James and I occasionally team up on little projects as he has a knack for developing complicated back-end systems (including ruby on rails, ajax and php) where as I specialize in front end development, design and theming WordPress sites. In this case James is building a custom plugin that acts as a rating system for the blog posts. I am developing an adaptive layout and turning it into a WordPress theme but I am not going to let James have all the fun and do all the complicated development. So, when I needed a custom widget I gave it a go myself.

What I needed was a widget that would list all the authors who work on the blog with some easy to set options. Right now it has the ability to show or not show the number of posts, include or exclude the admin account and include or exclude people who have not published a post. I think there is room to add more functionality in the future but essentially the widget enacts this function:

wp_list_authors( $args );

Read more about this function in the wordpress codex.

There are more features that could be added in the future but, for the moment the widget is just supporting what I feel are the most important options. The widget admin panel looks something like this:

It’s pretty simple but, to me, being able to make some simple functionality an easy to use widget is worth the time. I also know there are others who do not have the time to build such a widget. This widget also allows for users of a blog to add, change or edit setting in their sidebars, which is an important feature of WordPress. So, for your downloading pleasure, here is the code of my widget. Just install it like a WordPress widget and check the widgets menu area to title it and make changes. Enjoy!

download link: list-authors

Also, I will be adding this to a developer page at some point so check for updates if you are hoping for some more features.

HTML5 for Web Designers Review

I waited the full ten days for the shipping of A Book Apart’s first “brief book” HTML5 for Web Designers by Jeremy Keith. A Book Apart is a joint venture by Jeffery Zeldman, Mandy Brown and Jason Santa Maria dedicated to making short books, 90 pages in this case, for the folks on the front lines creating websites for a living. Because I match this target audience I thought I could weigh in on the book and the direction A Book Apart is taking.

I decided to just get my thoughts out on the book, the scope, depth and the idea of these short focused books.

The Format

The idea of a shorter more digestible book format is a winner for me, but it has its certain trade-offs. I think a book that I could read in just an hour and a half or so has a lot of worth because it is very obtainable for busy people. I generally group web design/development books into either ‘hammock readers’ and ‘desk readers’, where the desk readers are books I have to work my way through lesson by lesson at my computer and hammock readers are those I read here and there in my free time but can take a few weeks reading at leisure. I think HTML5 for Web Designers has to be a part of a new subset. Even with a very short attention span you can set a couple hours and a simple goal of finishing the book while sipping some ice tea and taking it easy and be done before you know it. The book might not have all the examples you want, all the background info you might be curious for, but it gets you the basics and tells you where else you can look if you still need more information. And honestly, the fact that it is in print makes a difference for me, I don’t have he capital for an Ereader and sitting at the computer reading a pdf is a real drag.

For reiteration sake I think the format works, quick, to the point and something I can tackle in a couple hours without loosing focus.

Jeremy Keith

I have read a book by Mr. Keith before, I am actually currently working through his Dom Scripting book to reiterate my knowledge of the DOM and JavaScript to much success. Jeremy has a clear precise and very thorough approach to topics whilst maintaining a dually practical and theoretical viewpoint on the subject. For this book you can tell at times he had to cut himself off a little and leave a few things for further investigation, that being the point of a shorter book however, it seems to have went just fine and he even snuck in at least one bit of “whimsy”, a word that floats around the A Book Apart webpage, that made me laugh. I think they did get the right guy for this book.

The Book, Apart?

Trying to deal with the topic that as is pointed out covers a spec that is 900 full pdf pages in one tiny little book is a daunting premise, but, as the scope is directed at someone just on the design/front-end development end of things it becomes a bit more manageable. Like everyone I have seen a lot of HTML5 hub-ub around the blogosphere and even seeping into the higher traffic spaces like youtube but there were things of which I still had little understanding.  I had read about the semantics of HTML5 spec (of which there is an entire chapter dedicated) in some detail and have been using class names to simulate semantics like article, section, and hgroup for the last year or so. However things like canvas and all its potential are still a little lost on me. Jeremy gave me a little better grounding but it seems like something like canvas really needs its own book. I understand the basic intentions but I would not be sure after reading even how to begin working with it. Jeremy does have a chapter dedicated to using HTML5 today, but, I am not sure after reading this that I am really in any hurry to do anything but play with HTML5 right now. As things solidify towards 2012 and what sounds like the first version of implementation of the language I am sure I will be ready to make the move, but, I wont be using it for client projects until that time, at least, I don’t believe I will.

This book, though brief and at times missing some detail I’d like was high level and written with a standards compliment front-end developer in mind. More importantly has me very excited for HTML to become the norm on the web.

Favorites/Final Thoughts

My two favorite sections of the book were surprisingly the history of HTML section and the semantics section. I am a sucker for history and semantic mark-up so this might lead to a bit of a bias but I feel these areas were well flushed out and really contributed to my understanding of the goals of HTML5. It is not just a new language for the sake of a new language or to kill flash or any such nonsense, it is a new language to improve the internet for all users in many ways.

My last point is on the clarity I am finding in the web world this week and is only half related to my new understanding of HTML5 provided by this book. On Thursday on The Big Web Show I watched Nicole Sullivan explaining that a good stylesheet is made out of many reusable widgets or pieces. So basically, if I have a certain type of arrangement of content I could potentially copy that and move it into another page in a different place on the page and not have to restyle based on its movement. There was a place in the semantics section of Jeremy Keiths book where I got that same idea in my head. HTML5 is working to create documents that are chunks of code that can exist anywhere in a web document and not have to be recoded or restyled. Clearly the Web is moving this way from everything I have been seeing and it is a result of content management systems and a whole host of really smart designers/developers who understand the potential power and flexibility the web STILL has as a medium (plenty of potential is, as of yet, unrealized). Personally the prospect (and practice) of this idea is a thrilling one.

Great job to everyone involved on this book, it was an enlightening experience in many ways and I look forward to more.

Organize your CSS

I have been looking for ways to improve my stylesheets ever since I started writing them. The first stylesheets I had written were disorganized, unstructured and when I look back at them I usually don’t like what I see in so many ways. Writing CSS is one thing, writing good CSS is another thing. I have been working on this list for a while and I’d appreciate additions and feedback!

Starting with helpful comments

A great way to start a CSS document is to start it with a comment about various styles that go into this document. If you are familiar with wordpress, wordpress requires a comment to tell what sort of theme it is and who wrote it. I encourage another set of comments that list the fonts, colors and other mandatory style choices such as font weights and border thickness around images. Here is one I did a few sites ago:

/* Fonts:
 * Header Font: Chollaunicase
 * Paragraph Font: Helvetica, "Helvetica Neue", Arial, sans-serif
 * Colors:
 * background grey
 *         #CCCCCC
 *         rgba: 204,204,204,1
 * Logo Purple:
 *         #662d91
 *         rgba: 102,45,145,1
 * Nav Blue:
 *         #29ABE2
 *         rgba: 41,171,226,1
 * p grey:
 *         #4D4D4D
 *         rgba: 77,77,77,1
 * Highlight Orange:
 *         #F15A24
 *         rgba: 241,90,36,1
 * borders red:
 *         #ED1C24
 *         rgba: 237,28,36,1

Getting started with a section that explains some of these choices might keep you or another designer sane later in the game if maintenance is required.

Let Eric Meyer help, please

I hardly need to explain this one if you have ever heard of or created a reset style sheet. I have yet to find a need to make any additions to Eric Meyer’s reset stylesheet and it makes everything so much easier when you have it implemented. Save yourself time and energy and use this on every project. Eric Meyers Reset Stylesheet.


Validation, not just for HTML anymore. The W3C also has a validation service for your CSS which doesn’t only help you make sure all your css is up to snuff (sorry browser hacks and css3 browser specific styling will not be valid) but it also makes suggestions based on styles you have repeated. I have used this at times to remove duplicate lines of CSS to create much leaner stylesheets. These suggestions can sometimes hinder your organization so I usually take them with a grain of salt, I am not a computer and I can not always make sense out of oddly organized CSS.

Organize those styles

I have found it very helpful to organize my stylesheets in a sort of mirror to the way I have organized my XHTML, with certain exceptions. I use a few different comments and indentations to do this allow me to demonstrate.

    #header  //houses the .logo, .nav and .search-field

First, I use giant comments to denote major sections of my CSS. I use the “#” selector or “.” selector to note whether the parent of this section is a ID or a Class attribute followed by the name of the class or ID tag and an explanation. I will use these for every section of my document when it is applicaable. NOTE: It is often worth while to create a miscelanious section for styles that work across the board such as fonts and other oft-used styles.

    #header //houses the .logo, .nav and .search-field
   background: transparent url(img/header-background.gif) 0 0 no-repeat;
   border: 1px solid red;
   float: left;
   .nav ul{
      float: left;
      list-style-type: none;
      padding: 0 5px 10px 0;
      .nav ul a{
         font-weight: bold;
         text-decoration: none;
          .nav a:hover{
             text-decoration: none;

This part of my organization is where I copy the indentation from my HTML. I know that .nav is always contained in #header so for ease of reading later I will just use the same indentation I am using in my HTML elements. This way I avoid that long, hard to follow, vertical line of CSS and instead I have something indented that gives me a hint of structure without having to keep looking at the HTML. This all adds to a stylesheet that is much easier to work in.

Give your CSS some order

Since I began working on CSS I had thought there was a better way to list my seemingly random styles. I toyed with positioning properties being first or color and font properties being first but I had no real idea of why or how to list my styles. In the land or organization there is fortunately always a fall back. Alphabetize.

  background-color: rgb(225, 225, 225);
  border: 1px solid rgb(218, 16, 45);
  display: block;
  height: 20%;
  width: 20%;

From what had been a seemingly random lists of styles and properties, with just a little bit of alphabetization I can always quickly identify which style properties belong where without having to guess. When an entire stylesheet is formatted in such a way it makes finding the right style properties very quick and easy. This also removes the potentially random results you might obtain otherwise.

There are many advanced style techniques you can apply to a document and stylesheets can get long and at times verbose. Keeping in mind a simple set of organizational rules is something that has helped keep me sane when working with complex CSS documents. Though this is what I have found to be very effective there are a lot of different way these results can be achieved. I’d like to hear what you think and what if any of these best practices you use, or what others you find to be more effective.

An Event Apart Minneapolis

I am super, phenomenally excited to announce that Creature Works Labs, my current employer, has decided to send me to An Event Apart Minneapolis.

As someone who is more or less addicted to learning all there is to know about how to create great web experiences this is something that will really bring a year of learning and perfecting my web talents and skills to a wonderful pinnacle.

I think this is because I am ambitious enough to want to be speaker / writing in the future. What subject will I try to tackle if I were to try to write or speak or shine some new light on a subject? I am not sure. I have a bit of the teaching bug in me that my Grandfather passed down to my mother. I certainly don’t feel the need to teach right now, I have so much to learn it would be silly to think I could teach anyone. But somewhere deep down, I know that one day I would like to be a present, teacher, writer myself.

The great thing about An Event Apart is that they have collected the absolute best teachers and writers from the field. Minneapolis will feature Jeffery Zeldman, Eric Meyer, Dan Cedarholm, Luke Wroblewski, and Jeremy Keith, among many others. I have read one book from each of the amazing web minds named above and they have all impacted the way I work and enhanced my love for the web medium. Having a two day conference where I will hear the words right from the horses mouth(s) is just a stunning culmination to the last year of reading and learning.

I am stunned, elated, excited, and really ready to learn some more, grow some more and meet some great people. Hang on, looks like there is food too, looks like I’ve died and am in heaven. Please disregard this post as postmortem narratives filled with hope and ambition are usually fairly depressing pieces.

365 Days of Web

About a year ago I decided the internet was the way for me. Though I had spent four years of college dancing around the subjects not altogether unrelated to the web (which further blog posts will discuss) and my entire life from about the age of 12 enjoying working with computers, the web and other media (and there will be some rants about the problems higher education can incur), I had never quite said to myself that I should do “web design.”

You know where I am, but how did I get here?

The fact that you are reading this post and have come to this site give you the end of the story. At some point I clearly either accepted that web was where my skills fit or rather I embraced the career path and realized it was not only a career but a passion (which is actually the case). Also, as someone who fancies a good story about how we got where we are today, I’d like to take a moment and explain what has happened in the last 365 days of web also known as the last 365 days of my life.

Mind you 365 days is not an exact number, but I think I am close enough to round down (about 3 weeks) to make it a nice round year in my life.

The beginning of the journey

365 days ago I was kid with a Film/English/Art BA from Augsburg College saying to myself: “Now what do I do?” I had worked doing graphics for a small company, I had worked at a health club doing customer service / cleaning duties and I had a terrible economy crashing down around me. I should have convinced myself about three years earlier that I didn’t have the nerve or the desire to pursue a job in Hollywood working my way to the position I would still probably love – editing video; further I planned to try to make a living so that great American novel was not forthcoming in the near future despite my love for writing.

Well, I had to get a job and I had my criteria set: ‘see if I could find something remotely creative in a business setting.’ After searching the best jobs to apply for were in the web field and I decided to give it a shot as I had done some (bad) web work before. I also found out how little I knew. It was at about that time I funneled all of my waking hours into a medium that seemed to give me a fighting chance to survive in life, and my passion bloomed from there. 365 days ago I only knew HTML 4.0 and I was comfortable in the adobe software suite and that was it. I still thought tables were the way to go.

My new web

In three weeks I learned tables were dead, there was a thing called web standards and you could make stuff look awesome with CSS. This was both shocking and enlightening news and over those three weeks 2 things happened. I was prepared for my first job which happened to start at the end of that 3 week period and I discovered the new web as I started experiencing it was totally awesome. As an aside, I did have other skills the position required and I did not totally lie my way through the interview process. I simply was met by a team that liked my combination of skills and abilities. It was also an internship so some learning was part of the job.

From there I had a mentor at the internship (and I thing mentor-ship will make an appearance as a later post). Mike pointed me to so many useful resources I had not been aware of until this point. A List Apart, Konigi, UXbooth, Boxes and Arrows, so on and so forth a list of web resources I still keep and maintain. I stuffed my feed reader, aligned my twitter account with web designers and developers and kept reading more books and exploring new technologies.

I have continued learning and practicing my skills working as a Front-end Developer/Designer at Creature Works Labs in Waconia, Minnesota and on my own personal side learning projects.

Now what?

I have spent countless hours refining my skills working on the web. There have been some distractions here and there, what with a Wedding and a College Graduation also taking place in the last year, not to mention my new apartment, countless visits to my wife in Sioux Falls, SD while she completed her internship and my four nephews, friends, other family so on and so forth I have had a busy year. Next year wont have fewer things going on, but I will continue to spend my free time learning new technologies and now with the blog live, I will begin passing along what I learn and my thoughts on web technologies, theory and emerging trends.

Here’s to more of the web in 2010. Thank you all for your support, I am looking forward to continuing to add to the web community in my second year on the web.