Return Home
Emily Lewis spoke on the first day of BarCamp Albuquerque about web standards and markup. Her presentation wasn’t in keynote or powerpoint but rather a small standards compliant website you can find here.
Chris Kenworthy on Web Analytics, Heat Maps, A/B Testing [42:57m]: Play Now | Play in Popup | DownloadChris Kenworthy is the owner of the premier development site Dream In Code. Chris spoke at BarCamp Albuquerque this year about all the experience he has gained from launching and bringing Dram in Code to profitability. Chris says that to get real results from a website you need to pay attention to the numbers. In this talk he goes over Web Analytics, Heat Maps and A/B Testing.
As it turns out, I believe that Chris is now offering his expertise to clients as a consultant.
ROI - Frank LaFond at BarCamp Albuquerque 3 - Technical Debt [25:28m]: Play Now | Play in Popup | DownloadFrank LaFond knows more about QA than anyone I’ve met. This year was Franks second appearance at BarCamp Albuquerque, he spoke last year on testing. This year he talks about technical debt and the trade offs that companies must make between building their technical assets and the temptation of quick profits.
Running time is 25:27.
This audio file is Rich Murray at Albuquerque BarCamp 3 with his presentation entitled “future causality aspects of exponential social evolution: joint exploration of subtle features in Hubble Ultra Deep Field”.
Rich was the first presenter at BarCamp this year, and while he isn’t a web developer or designer, he is using the internet to further his exploration of Deep Space and the images released to the public from he Hubble telescope. The audio runs 42 minutes and 02 seconds.
Its amazing to me that I have been in New Mexico for over 5 years and it was only recently that I found that there is intelligent life in the web community. Today was the first ABQ web geeks meetup that I attended, and after this last weekends barcamp, I am happy to report that there is a good, smart web community in New Mexico.
I was astounded that around 40 people showed up to O’Neils Pub on Central Ave tonight from 6:00 to 8:00 pm. There they were, real web folks. Some were shop owners, some were with start-ups, some were employees, but all were on top of their game. There wasn’t a table based layout in sight. I even heard that a large NM ad agency is working studiously to get their design department up to speed on the web. That may not sound huge, but for NM its a good step in the right direction.
Maybe its just me, still high from the excitement of a thriving community, but I think its time for another sprint. A big one. Keep your eyes peeled at the ABQ web geeks community at Duke City Fix, the Refresh Albuquerque Google group and this blog for more information.
I would love to see this sprint take on not one, but two or three non-profit websites in a weekend. Get ready…. This is going to be good.
There is a concept in software development (at least web development) called agile that seems to be part of a larger trend. First lets talk about agile, then the trend.
In traditional web development, you sit down with a client and try and plan out a huge project. This can take months, going back and forth over what it really needs to do, how it needs to do it and so on. What you end up with a giant planning document and estimate that spells out what is going to happen. Many clients like it because it gives them a solid number they can attach to the project and budget for. It is all very rigid and if something changes a barrage of paperwork follows to ensure that the original document and budget is adjusted to reflect the changes. This is all about control and a clear map. Then there is agile.
Agile works like this, you set up a really rough plan of what you want, then the developers go and start building. Then you get back together and decide what is good or bad and go back to work. Rinse and repeat. The theory is that you can get a project developed faster because your not trying to guess how everything will work and plan it all out. You’re making it up as you go (at least the developmental details). Essentially you take all the planning time and exchange for actual development and testing of concepts. This is all about flexibility. All in all this seems to work, and get projects done in about the same budget range but usually faster, or better.
This seems to be part of a larger common theme. We used to all have to go to an office and punch a clock, but now there are a lot of telecommuters and “I don’t care when you work, just so long as it gets done on time”. A closer example for me is this years BarCamp Albuquerque. BarCamp is a volunteer run conference driven by and for a specific community. Traditional conferences are set up in advance and planned to death. They have to be. You have to get a venue, speakers, food and on and on. When the date for the conference is set the year prior, thats it. If you have something else going on, the conference is not going to change dates to accommodate you. BarCamp did.
BarCamp’s date was set two months prior to the event. It was also set on a holiday weekend. (That was my fault. I didn’t notice). After the conference was “full” in a few weeks, the “registered” attendees started to unregister in waves. Apparently they noticed it was a holiday weekend and had other plans. BarCamp moved back two weekends to accommodate, and the attendees came back. A traditional conference would not and could not do that.
It seems that being flexible is the way in which we all want to work now. We are all busy and have to juggle many different things. I hear work life balance is one of them, but I wouldn’t know about that, owning a small business 
. Take a minute to consider the ways you do business. Are there steps in your process that are inflexible? What would happen if you changed it? How much planning do you do? How often does it go according to plan?
I’m not suggesting that you drop everything your doing and fly by the seat of your pants. I am suggesting you take a good look at how you operate and ask a few tough questions. Like in web development, most often big up front design specifications are only done to create an airtight contract. What good is an airtight contract? It allows you to nail someone who screws you over. Think about that…. is that the right way to engage in business? Yes we need to reduce risk, and yes we need contracts, but at what level and cost? Perhaps the right approach is one based more on collaboration. A process that is based more on getting things right and taking a few risks, not trying to guess how everything will go to the letter and have enough ass-coverage to go to court. No plan ever survives contact with real people, so why do we try so hard?
So what?
I can’t tell you how to live your life or run your business, but consider:
What (illusions of) control can you give up to make your life / business better or faster?
When hiring a web developer (or other profession) have you done enough research / due diligence to make a decision based on them and their capabilities? (rephrase) – Are you hiring them for what could be (making real value for the organization and market) , or what shouldn’t be (with a plan for when they screw up)?
Just some thoughts – there is a comment section, What’s your take?
Get the ROI RSS Feed 
Subscribe to the ROI podcast in itunes