Everyone in the auditorium knew when she stood up that this was going to be an interesting weekend. Sister Mary, dressed in a stark white Habit, stood out from the crowd of faded jeans, Converse low-tops and silk screened Tee shirts with ironic catch phrases like some lost Lawrence Welk fan at a Neko Case concert. But what she told the audience, how passionately she expressed her excitement for what was in essence just a new website, was nothing new by then. They had heard the same that night from a dozen other local charities and non-profits participating in GiveCamp 2009. Each charity started the weekend thanking the programmers and developers and designers for donating the next 48 hours of their lives to creating something for their own personal cause. So unaccustomed to this kind of appreciation for their unique gifts in this world, the audience of software and computer experts were overwhelmed to tears more than once. At least I was overwhelmed to tears at the opening ceremony, cresting at the pique of the emotional wave with Sister Mary shouting thanks to God that ‘The Geeks Are Coming!’
The geeks give back to those that Give year round
Thoughts from KalamazooX Conference #kalx
I attended KalamazooX over the weekend, which was a great combination of design, business, and technical presentations. As someone who has transitioned from a programmer into marketing & strategy consulting, it was nice to see content that wasn’t just staring at code. I believe some of the slides are up online, but here are some thoughts, not from every presentation, but from some of my favorites:
Dave Giard – Effective Customer Communication
- Communications is a two-way street – both sides are responsible.
- It’s important to get/give feedback early and often.
- You need to add value for the customer – what does the customer feel adds value? – need to know this up front.
- Weekly status of what you did, what you plan to do next week, any issues/problems.
- A daily standup (including the client) is better.
- The most important part of verbal communications (any communications) is listening.
James Bender – Organizational Dynamics
- Plug into the company’s information highway (water cooler, wiki, blog, intranet, etc.).
- Be someone in the know.
- Evangelize yourself and your ideas (and also your team!).
- Build coalitions.
- Learn the right way to gripe.
Josh Holmes – The Art of Simplicity
- The definition of simplicity from Websters includes: lack of sophisitcation, good sense or intelligence – which is how technologists often think.
- Systems need to be designed so the user knows immediately what to do and starts doing it.
- A simple design does not mean that the problem solved was simple.
- Users may not see a request as complex – they just know it will make their experience better.
- Agile is a buzzword, but it’s what techs need to be in order to solve problems.
- The right solution is not the one other technologists understand – its the one the user does.
- Enterprise automatically adds ten times the complexity.
- Consumer space has solved bigger issues in simpler ways.
- We usually don’t understand who are users are – the top 3 things they do.
- Use the right tool for the job.
- Solving someone’s problem adds value.
Brian Prince – 5 Easy Ways to Be More Agile
- Be Subversive – start doing things without permission, without changing what you’re doing, help people see value.
- Stand up Meetings – what was done yesterday, doing today, roadblocks. Don’t solve problems – have speaking token.
- Keep – Stop – Start Meetings – Introspectives at end of each iteration. What should we keep doing, what needs to stop, what do we need to start doing – assign people to solve by next iteration.
- Must – Should – Could – Won’t Priorities (from user’s view). Keep quality and priority in the picture. Use quality in equation always.
- Keep users and client as close as possible (not usually the same). Ask – share – show. Tell stories. Use simple planning wall.
Leon Gersing – Change
- Make little changes until you don’t realize that you’ve changed.
- Be open to change.
- Know who you are.
- Don’t let others define who you are.
- There are 3 states in life – job, career, enjoying life – which are not always the same. Know which you’re in.
- Change where you work (not always the employer, but sometimes the environment, or your state of mind).
- If nothing ever changed, there would be no butterflies.
Technorati Tags: development, code, kalamazoox, code, coding, programming
Liked this post? Consider subscribing to our RSS feed or our weekly newsletter.
JSON and the Argonauts
The Greeks sure were fond of super-hero team titles. There was Jason, commander of the Argo and her crew of the best of the best, pitted against irresistible forces beyond moral man’s endurance. What does this have to do with JSON, the JavaScript Object Notation standard used by the web 2.0′s best of the best of overcome an accent foe called Same Origin Policy? Can’t think of a thing, I just really liked the title.
A funny thing happened on the way to the Mashup. I’m sure someone somewhere, maybe even here, told you that RSS feeds were going to revolutionize the way we distribute information. We were all so right in so many ways because RSS, or ATOM if you prefer, has opened up the world to the unimagined possibilities available online. Think of some way that you want to consume information. Go ahead, I’ll wait. Ok, you are all right you can consume information that way. Oh, heh, I mean almost all of you are right. That guy in the back with the Helvetica shirt in Metalica font, I’m sorry but we can’t help you with your idea. Thing is, as much as you may want to have a single page that can then pull and update XML based RSS feeds from any site in the world from within the browser without refreshing, you’re not allowed. It is for your own protection actually. We call it the Same Origin Policy.
Here is the idea. When your web browser pulls down a web page’s code from a modern site, it is usually pulling down a collection of HTML, Stylesheets, Javascript. That HTML tells the page what content goes where and what images to place by the content. The Stylesheet (CSS) tells the browser how to make that content look and how to make it act on the page. Then the Javascript is there to give the page life, make it interact with events, make it do impressive things that we have come to love and cherrish. In the AJAX world, those impressive things involve grabbing information from the server and updating the page without screen refresh. Javascript is nye omnipotent in the browser, and yet there are some quantum limitations built into the works. Beyond the sandboxing of JS, there is one little design decision from Netscape 2.0 that has totally altered the web 2.0 landscape. Netscape decided that a browser would only allow scripts to interact with domains that the page came from. If a page is loaded from www.bobsdiscountlasers.com then AJAX calls are limited to bobsdiscountlasers.com. The grand illumination of mashups, where data flows from many different locations onto one page in a relevant way, almost never happened because of this.
Web browsers weren’t designed with mashups in mind, and ‘the warts have been there from day one’, [David Boloker, cofounder of the OpenAjax Alliance and IBM's CTO of Emerging Internet Technologies] says. Browsers contain a security feature called the same-origin policy that’s meant to keep malicious code hosted on one site from grabbing data, such as stored credentials, off another site. The same-origin policy prevents websites from one domain from requesting data belonging to another domain. ~ Security services and Mashups
But, of course, Mashups do exist. We see Google Maps on thousands of pages not under the google.com domain. How is it done? We’ll get to the hero of the day in a second, for now lets look at other popular workarounds
- Mashup at the Server Side: Since the JS limitation is browser based, you could do all of your mashups at the server. The server could serve as the collector of the different sources of information, combine them intellegently and cache the results. At best this idea is inconvenient because it adds layers where they need not normally be. At worst this does not scale when you have a single location for distributed information
- Flash/Flex: The Flash VM doesn’t have the Cross Domain limitation that plagues JavaScript. A file on the server gives a list of permitted sites that the Flex app can pull data from. I have talked with Adobe Evangalists about this option and they seemed to hint that this design decision was intented to hit javascript where it was weakest.
- AJAX Proxy. Similar to the first method, a proxy allows the client to pull the information through it. It isn’t stored on the proxy, though it can be cached, and no combination is done. Again, this is a scaling issue
Stop passing code, start passing data. What all of these work arounds do is bypass the security concern with Same Origin Policy (SOP). SOP was originally intended to combat early attempts at Cross Site Scripting (XSS). Modern XSS has a nasty list of exploits that I don’t have time for here, but one way to think about it is this: If you let Javascript pull code from untrustworthy places you are inviting problems. One possible approach to this issue was to stop the push and pull of code but to allow the pushing and pulling raw data. That is what JSON is, a way to encode data to be pushed and pulled using AJAX calls. Though the X in AJAX stands for XML, AJAX really is more often using JSON because SOP will allow it to be used cross-domain. So with JSON you can pull in Google Maps and that list of Micro Brewerys right in the browser, Mash them up using Javascript, and asyncroniously keep the data refreshed, the app reactive, and your buzz in good spirits (You are walking to these pubs, right?)
My prediction; RSS feeds are going to move away from XML and on to JSON in the future. Or at minimum, support both. John Resig, the creator of jQuery, even has a converter to get us all started.
Photo attributed to jasonr611
Technorati tags: software, json, javascript, javascript object notation, rss, atom, xml, mashup, web development, code
For 'Bleeding Edge' prepare to pay in blood
If you are in software development, take a good hard look at the code you are writing right now. If the string of Roman characters resemble Java or .Net or C/C++ then I have some wonderfully awful predictions about the next ten years of your life; That language is your scarlet letter and will follow/define you for the next two jobs you end up accepting. That sounds bad but you are the blessed among the damned – You can and will find that next job. For Bleeding Edgers, the road is not so well paved.
In my last job I was a Bleeding Edger. You know one if you work with one, always looking at the latest release of the newest language to see if it has a better solution to your particular problem. In my case as a Software Manager, being a Bleeding Edger meant an obsession with ROI in our software solutions. Links to anything that could trim development time and/or expense filled my Delicious feed. I pushed my team to move beyond Java’s heavy web frameworks and to adopt Rails as a rapid application prototyping framework. We cranked out good, solid software solutions 4 times faster than our java days and I was happy. When a project came along that could use Flash, we wrote it in Flex instead because knowing how this company worked, they’d want a desktop and an offline version in the future. A year later we were cross compiling the Flex code into an AIR application and saving a tremendous amount of time, and we were happy.
But being a Bleeding Edger means there will be dark days to contrast the brilliantly sunny ones. Our ROI figures were not enough to protect all of us throughout this economic upheaval and some would have to make the sacrifice for the rest. I would like to say that, as the manager, I fell on my sword for them but that’s not really the case. The decision never reached my level. I was the highest compensated on the team and so I was killed by simple, cold math. The blood spilled that day is still dripping. It still hurts.
The software job market is a rigged system. Heavyweights in the market put enough momentum behind enough Java and .Net and C/C++ projects that they can be considered perpetual motion machines. A class hierarchy between Java and .Net, perpetuated by recruiters with a simple word match on a job board, stacks the deck against the Bleeding Edgers in the mainstream. You are a Hatfield or you are a McCoy or you are an innocent bystander likely to get shot in the crossfire. The mainstream is not a system able to help the Bleeding Edger. Sure, there will be the occasional posting that isn’t in your location and is looking for some bizarrely specific, must have requirement that categorically eliminates all humans including the guy who originally wrote the book on the library they are using. In the end, Bleeding Edgers need to work outside of the system.
For the young, there are no unemployed Bleeding Edgers only uncompensated open source code contributors. If you have the ability to live on nearly nothing, working outside the system can be a very rewarding and ultimately fulfilling life choice. For the responsibility burdened older generations, there are really only two options as a Bleeding Edger. The first, and likely most chosen, is to re-assimilate into the collective; scrub your resume of all references to Ruby and Jython, and Grail, prop up your sun certifications if you have them, and become a team player. The rest of us Bleeding Edgers, the ones the economy hasn’t driven to ditch digging, will become the countries next batch of serial startup founders. We will be easy to spot, just look for the scars.
Technorati Tags: code, ruby on rails, ROR, software, software management, software development, web development
Digital Marketing & Strategy
Connect with Sazbean