Saturday, September 25, 2010

Shop Class As Soulcraft

Today I finished Shop Class As Soulcraft: An Inquiry Into The Value Of Work by Matthew B. Crawford.

The book makes the argument that separating knowledge from being able to work with the physical world is bad for workers in many ways. It is push back on the knowledge economy. The story is based on his own experience working as a motorcycle repairman after getting his PhD and working some office jobs.

If the subject makes you think of Zen And The Art Of Motorcycle Maintenance, there are a few shared ideas, but this book isn't insane.

I have mix feelings about this book.

First some good:

Sections of the book are clear articulations of thoughts that have guided my career and education. If anyone wants to understand why I chose electrical engineering over computer science and engineering over other fields, this book would be a good place to start - the core idea being working within the constraints of the physical world and seeing ones efforts cause something to actually work both theoretically and practically. Even though he does makes some comments about repair being superior to design (I think most of those comments are based on ignoring several aspects of design).

He even made some comments on creativity that very nearly matched my own.

Some ok:

He makes some good points about the modern office. Especially about how when people work in teams on poorly defined tasks it is difficult to evaluate the success of both the group and individual, vs in repair where either the repairman gets the motorcycle to work or doesn't. And how this puts managers in a strange position. Also how the knowledge of success vs failure is key to satisfaction in work. He also gets into how demoralizing it can be when the goal is something monetarily based, such as number of pages written, instead of working towards quality.

He also discusses how advertising and marketing reveals people's desires to build and repair their own stuff. He discusses marketing campaigns such as the Scion where they have people purchase options to make them feel like they are working on their car, when they are really just buying more stuff.

Some bad:

He takes most of his points to extremes - such as I toned the comments about the office way down.

My biggest issue with the book is that he encourages people to consider vocational school over college, especially since for some people they can make more money if they are willing to accept blue collar jobs. First, I question if that's true, much of the recent discussion of the labor market I've seen is about how recently those with college degrees are pulling even further ahead of those without. Second, even if it was, there are other reasons to go to college, such as just being an education person. Also this is one of the most "academic" books (outside of science and textbooks) that I've ever read which seems somewhat ironic given its subject matter. It's also a bit odd that a book suggesting going to votech made me feel like I should have taken a philosophy class before reading it.

The author doesn't bother at all with balance. He's all about getting away from specialization of labor as well as other aspects of corporations, but doesn't address what would happen if there was actually a major shift back to engineers doing their own building and writing their own user manuals. It never comes up that products would be significantly more expensive and the economy would tank. Not to mention that he does not suggest how reasonably complex projects would be designed or built. A good example of the lack of balance is when I made comments about creativity on this blog several people made good counterpoints and that's my personal blog - this book did nothing to address that there is more than one side to it.

Finally the size:

I really like the size of the book - it isn't a little pocket book, but still fits in a pocket so as I read through the wheel of time at home, I've been reading this book while doing laundry and hanging out on castro st. All books should be this size and if they need to be longer they can be split into multiple volumes. Also makes me wish there was a mini-kindle that bends a little.

Thursday, September 16, 2010

Time Travel

There's a particular view of time travel that seems to be preferred by tv and movies. This view is that someone can travel back in time and change something which alters the future. Let's say the character lives till 2010 then travels back to 1980 and changes stuff then travels back to 2010. In the show his time line is continuous from 1980 to 2010 then jumps to 1980 then jumps to 2010. The "first" time he is in 2010 in the past there is only one of him in 1980, the time traveling him hasn't visited that time. The "second" time he's in 2010 in the new history of the world there were two of him in 1980, one the normal and one the time traveler.

Ok, before we go further we have to allow physics to be broken in order to time travel, and even bigger we have to allow causality to be broken. It is difficult to proceed with a logical argument once we're allowing causality to be broken, but logic minus causality is one more thing we'll have to allow for this post to proceed.

It's always seemed to me that if someone time travels from 2010 to 1980, then in 1980 there are two of him and all of the resulting consequences, no matter if it is the "first" time he gets to 2010 or the "second" time, since there aren't two 1980s. (Sometimes shows touch on the idea of switching to a different universe when the time traveling occurs - that would solve the problem, but then the person is both time and universe traveling, not just time traveling*). So that's not a new idea. But what finally occurred to me is why the two different 1980s view of time travel is so natural for TV - you are following the character who time travels and time is progressing based on his view of time so it is possible to see each moment in time more than once as soon as he starts time traveling. Even in a story with many characters, the story will take the view point of only the time traveler for that part of the story. (Heros may be an exception to that rule, but Heroes' time travel rules were really wacky, remember the crazy mesh of strings they called a timeline?)

If a TV show had to draw a time line (based on the reference of a third party - or a non-time traveling character) they would be hard pressed to make it work with this view of time travel. It would be equally difficult to make this work if they also showed events from the perspective of a non-time traveling character. Especially since the time traveler's friend's memory contains one set of events during the "first" 2010 and a different set of events during the "second" 2010.

So I blame the linearity of story telling and the tendency to perceive the story through the view point of a single character for this persistent view of time travel.

Although since we've dropped causality maybe I blame this persistent view of time travel for the linearity of story telling.

(*The universe hopping version of time travel is also somewhat less satisfying since if the character goes back in time to save someone they're not actually saving the person in the original universe, but rather just choosing to live in a universe in which the person survives - that seems to make the story much more shallow. Although I guess if they're not sure how time travel works they could still be well intentioned...)

Two Ideas

Here are two ideas:

1. Trilingual travel books. Lots of people both in and out of the US speak the language of their home country and English as a second language. When they visit a foreign country it is likely they will speak English there since they will find more English speakers than speakers of their primary language. So it is useful for their tour book to have English names and descriptions. However, even if the person is very fluent in English it is likely that there will be many places in the foreign country they learned about growing up in their primary language and don't know the English for it. In addition to sites, this would likely be true for foods and other aspects of travel. So it is useful for the tour book to also include names in the reader's primary language. And of course any good tour book will include the names in the language of the destination country.

This isn't just a crazy theory - a coworker borrowed a tour book and mentioned how he had a tough time find what he's looking for because he only knows the Chinese name (and his English is approaching native speaker). When I suggested a tour book in Chinese he pointed out that he'd be speaking English in the country so a Chinese tour book wouldn't do it either.

I think the major obstacle is a company that has all the content would have to do this or give someone permission to use their content. Also tough would be that this would require the creation of a huge number of books - perhaps it is an idea better suited to a website that allows the user to pick a destination country and all the languages they want the information in - or maybe ebooks are the answer.

2. Certified store for Android apps. Any app going into the Apple app store has to be approved by apple which is both the store's biggest advantage and biggest disadvantage. My understanding is basically anything can go up on the Android store. Seems like an opportunity for someone trusted to check Android apps for security issues (and if trying to mimic apple - occasionally dismiss apps for no reason) and then put them up for sale in a special store. I was thinking that the developers might have to send them the source code, but iOS developers don't send the code to Apple so it should be possible to do the security checks with binaries only.

Semi-related idea - why isn't there an app store equivalent for desktop/laptop computers?

Tuesday, August 31, 2010

Creativity

I'm going to talk about myself for a bit, since that's what I get to observe, but I'm trying to get to a broader point not just spout off about myself.

I feel like there's a "traditional" image of the path to creativity. A bunch of somewhat wacky looking people tossing a ball around while brainstorming in an office shaped like a castle or sitting in a hot springs on some company retreat (ok, maybe that's several images all jammed together). And part of the image is that those people are part of some cross disciplinary team or each has some broad range of work and life experiences. Think of the creativity posters with pictures of an old Einstein with crazy hair.

I've filled several invention disclosures at work. Some of which are working through the process to become patents. I'll admit that while each to the best of my knowledge is an original and useful idea, none of them is going to transform an industry or anything close to that. But I like to think that to have an original useful idea in a field that has been around a while and has a decent amount of competition takes some creativity.

I was thinking about what lead up to each of these inventions. Since I've never been to a meeting where a ball was tossed around and definitely never been to a company retreat with hot springs none of those were involved in the process. In fact the common theme in each case is either independently or in collaboration with one or two other coworkers I was digging deeply into the details of some aspect of a circuit I was working on. And in each case as I reached a certain level of discovery and understanding the new idea just flowed. And it was a single clear idea, not a giant list of brainstormed ideas. Each of these situations seemed almost the exact opposite of the "traditional" image of creativity.

Going back to Einstein for a moment. The old man with crazy hair really didn't do much. It was when he was a clean cut, suit wearing, patent clerk that he came up with mind blowing advances in physics. I will admit that I don't know a ton about Einstein, but my understanding is that most of his advancements came from thought experiments on his own, not brainstorming or even collaboration.

For my own example I wonder if while I'm being creative, maybe I'm not hitting a higher level of creativity that the "traditional" example would help me achieve. The higher level could be just how new the idea is, or could be the difference between creativity on the level of circuit details vs large system changes. However, that doesn't hold together when the Einstein example is considered.

I guess the answer is probably just that creativity is a large, poorly defined concept so different types of creativity require different approaches. And different people get to creativity by different means. In addition, crazy looking Einstein makes a better poster and a multidisciplinary teams going rafting makes a better story than an engineer focusing on a computer screen late at night. So those are the images of creativity that are spread.

Was that obvious? Is there something I missed? Am I over valuing engineering creativity - is a pixar writer so much more creative than a chip designer that the comparison doesn't even make sense? Does a pixar writer actually follow the "traditional" path or is that just a false image? Is "traditional" path really more about how to get a team to collaborate than how to maximize individual creativity?

Most of my random ramblings are just that. But in this case I'm actually reevaluating which assignments at work I want based on this idea. The "traditional" image of creativity that I have says bounce from area to area picking up broad knowledge to allow cross-pollination of ideas. But now I'm thinking that while breadth shouldn't be ignored, my own path to creativity is to go further in depth.

Saturday, August 07, 2010

RFCALC

My previous post about iphone programming included some complaining about the development environment. Well I'll admit I had the expectation that I should be able to just sit down, crank out some code, and submit it (as if I was using a program instead of creating one). I realize that was expecting a bit much. Once I bothered watching a few lectures of the Stanford iPhone programming class, looking at some more example code and finding apple's class definitions I realized that apple actually makes iPhone programming very easy. And once I got into it I realized that a lot of it, especially graphics, is much easier than I anticipated.

Version 3.0 (I'm being a little generous with version numbers, but at least I started with version 1) is submitted for review now and should be on the store soon. When I first started the app several coworkers suggested I make a smith chart tool and I said that the graphics would be too much of a pain. So I'm fairly excited that version 3.0 has a smith chart tool. And, maybe it is just because I made it, but I think it is in some ways better than the smith chart tool I have on my computer at work.

I decided to try adding iAds to the app (that was added in version 2.0). So far there are just two ads that run and I'm not really making money off it. But it was kind of cool to have the first app I've seen that uses iAds. And what I like about it is I get to see how many requests for ads occur so I get some sense of if the app is just being downloaded or if people are actually running it. Based on that the number of people using it must be much smaller than the number downloading it, but there's still a decent number of people using it and in surprisingly large number of countries.

Of course now that I'm getting (somewhat) used to objective-c and have some code built up I'm running out of ideas for what to do with it next.

I've been thinking a bit about why I've been enjoying iPhone programming so much. I think part of it is that I like engineering and design and while work sometimes fulfills that role, work projects can have very long stretches between successes. On the other hand, programming, well maybe just hobbyist level programming, allows me to make something and see it work over the course of a few hours to a few days. Far faster than even hobbyist level electronics design.

This is biggest program I've worked on in quite a while, most of my coding since graduation has been limited to single page perl scripts. So it has been cool to come up with the higher level structures (even though I'm sure it is pretty basic even compared to school projects). In particular it is great when all of the underlying objects have been built up so that a few lines of code can add a ton of functionality.