I’m going to pull YOU in as a potential prizewinner. That means a FREE TRIP TO HELSINKI, FINLAND for you if I win the contest (Facebook contest winner gets two tickets) and you get drawn from the list.
Yesterday in my zeal to win a trip back to Helsinki, Finland I lost all common sense and spammed the crap out of Twitter, Facebook, LinkedIn and a few texting streams.
I know better. I should have done better. Impatience is no excuse, but it got the better of me.
There’s no funds or funny stuff required. Visit Helsinki has arranged a contest where contestants’ photos are displayed in a Facebook media album and all you need to do is Like those of your favorite participant. In this instance, me.
And in case you need further motivation, as I noted in the previous post here I’m working on a book about maker communities. One of the coauthors, Jarkko Moilanen, works in Helsinki and I’d like a chance to get with him face-to-face for a bit. I also hope to interview former Maemo/MeeGo community members (now with Jolla) to get their perspective on collaborative communities.
I have many friends in Finland and several of them have jumped in to help. But so far it’s not nearly enough– I’m being beaten pretty soundly by another contestant and could use all the assistance I can muster.
All of this has been a lot of work, especially in my very conservative locale. Every time I hit some sort of social or functional wall, I think, someone should write a maker community how-to book.
And when a common political rant emerged on the hackerspaces.org general discussion list on that very subject, it all came together for me: *I* should write that book.
My apologies: this article was accidentally scheduled for publication before it was completed. It is now updated.Okay, enough griping about Cowtown’s obstacles in attaining some degree of technological leadership– what are some resources currently available to improve the situation? Today I’ll go over some that are key, focusing on communities rather than places. Not all listed are exclusively oriented around technology, but it is at least included in their scope.
I’ve mentioned these organizations in previous articles, but it’s worth gathering them together and highlighting.
Fort Worth is surrounded by many nice lakes and as a consequence we have more than our share of committed fish stalkers. But I’m curious: why wouldn’t that sort of dedication translate to opportunities in technology?
That’s not just a rhetorical question. As I wrote last time [“Cowboys and Culture“], we can be a laid-back bunch in these parts, exhibiting a skepticism over urgency that would make Show-Me-Staters proud. And as I promised in that previous article, I will now share the perfect example of one that got away… and maybe shouldn’t have.
Folks are laid back here.
Stereotypical cowboy talk includes words like “mosey“, a colloquial verb describing walking much like glacial describes progress. Like their trail-dusting forebears, Fort Worthians are usually in no hurry. Whatever it is, it’ll wait.
This is at once endearing and maddening. Sometimes it can’t wait, and that’s especially true with technology.
June is looming and I’m excited: the second-ever Cowtown Code Camp is being held on the 14th and I hope to make it.
Last year it was thrilling enough that we even had this sort of event in Fort Worth; everyone in tech in DFW knows Addison, Irving, Frisco, Plano, Richardson and North Dallas are where you go for software and related events. It’s a circle of cities that has held tightly to this honor for years, and facilitated a self-fulfilling situation. Developers go because that’s where the events are, and the events are held there because developers go. Breaking into that cycle, even for a single occasion, was special in and of itself.
My current day job involves supporting safety systems on locomotives. This is a relatively young field and can be thought of as air traffic control for trains. Even though the associated technologies (GPS, cellular communications, data acquisition, etc) are mature, the overall development is fairly new. This means we talk a lot about IT. And not always kindly.
We’re part of engineering, so even from our geeky perspective IT is still a THEM. Sure, I do some coding when I have the time but it’s just not under IT auspices. And when our coffee talk turns to IT, as it frequently does, it’s laced with the usual fear and suspicion. IT guys don’t play well with others.
As a fringe IT guy myself I know it’s a mistake to paint all software developers with a brush as broad as “coder culture”, but there are some stereotypes that I’ve seen generally run true.
Last week I blathered a bit about where I’m at and hope to go. For those interested, I’m gonna share more details today.
In case it doesn’t come across in other contexts, I’m ultimately a maker at heart. Nothing pleases me more than to be designing, writing or building. Something. Anything. I’m even happy with repairing stuff– assuming the designers put reasonable thought into that aspect of their product. I’m convinced though that pointy-haired bosses excel at ensuring all products leaving their domain are as repair-unfriendly as possible.
For most of my adult life, I’ve made things at the direction of others. At Texas Instruments, as a (now-reformed) defense worker, I contributed to radar and guidance system design. At Stanley, I worked on ways of improving existing mechanics’ tools as well as inventing great new things that Marketing feared to approve. At Medtronic, I mainly supported development and testing of surgical tools designed to cut into your skull and spine. At Nokia, I designed quality-monitoring software solutions and supply chain processes.
All of that was wonderful.