If you’re a programmer/gamer geek and looking for a gripping book that you won’t be able to put down then look no further than Halting State. I’ve been on a Stross kick for the past few months, having read Accelerando, Glass House and Iron Sunrise. Halting State is easily his most engaging book I’ve read so far.
It takes place in the near future where ubiquitous computing has started to take hold via mobile phone networks. This is a future where online roleplaying games and live action roleplaying games are an international past time (as we already can see happening now with the gaming industry being a bigger industry than the movie industry). The story starts off in with a bank robbery by a band of Orcs in a virtual world — a band robbery that should not have been possible because of the digital cryptography keys involved.
As much as I enjoy video games and fantasy settings, the book thankfully takes place mostly in the real world — although in the age of ubiquitous computing and common place augmented reality, who is to say what is real? It reminded me of War Games meets Cryptonomicon and World of Warcraft. Stross manages to get all the geeky elements right, and I’m not just saying that because my player character in my weekly table-top campaign is a were-bearbarian.
I don’t want to give away any spoilers, but this is a wonderful whodunit, and if this is what Charles Stross has in store for us in the future then I’m going to have to make more room on my shelf.
Favorite quote: “It’s TCP/IP over AD&D!”
Credits to Fred for introducing me to Everything Bad is Good for You: How Pop Culture is Making Us Smarter. The thesis behind the book is simple: if you look at the popular media culture over time it is becoming more and more complex. There have always been avant garde examples that wove complex stories but over time the same techniques are used in mainstream pop culture. IE: It is becoming common place to produce tv shows and movies that require multiple watchings to fully digest.
The book notes that this is in deep contrast to the old mantra of television programming where you wanted to go for the least offensive programming possible to avoid loosing market share. Johnson posits that one of the causes for change is before we didn’t have the ability to easily rewatch a tv show or movie to catch something we might have missed on first viewing.
Johnson also notes that the decline in reading books isn’t as bad as many people make it out to be because we have so much more access to written content via the Internet and more importantly people are writing more than ever before. I thought this was a good counter argument; when I look at the online presence of myself and my friends most of them are doing some form of content creation instead of passive content consumption.
The one area where I felt the book fell weak was in proving that more complex content is making us smarter. Intuitively I agree with the hypothesis, but the only proof offered was how IQ scores have been increasing in the average to above average segment of the population, but IQ scores haven’t been increasing for the ultra-smart people. It makes sense because the complexity of pop culture might be enough to increase problem solving skills in the average person but wouldn’t be enough to increase skills in the exceptionally above average.
I recommend reading this book after reading Made to Stick because Everything Bad is Good for You is a perfect example of how to convey an idea that will stay with the reader. The only downside is that some of the pop culture examples are already getting long in the tooth and I already agreed with the hypothesis without needing that much evidence. It might make for a more interesting read if it challenged your perceptions.
What Other People Have to Say
I don’t have anything against the for Dummies series (one of my friends is an author), but they’re only good when you want a very general understanding of a concept. I wouldn’t recommend the series for technical books. But my local library happened to have a copy of Ruby on Rails for Dummies, so I gave it a try.Here’s the good news: if you’ve ever used a programming language or used any HTML then you can skip the first 150 pages.
The 26 pages of how to install the software can be skipped by using InstantRails and then downloading RadRails. You’ll want to pay attention to pages 104 to 112 where the author delves into some of the ways Ruby is different than other programming languages (blocks, yielding, symbols, 0 is true).
The book uses RadRails for all of its examples; which is fine except that it takes so much longer to explain how to do something with a GUI than it does to type rails myproject or script/generate controllers ShoppingCart show. I really hate that they don’t show the one line console command as well as the four pages of GUI operations and screenshots. They don’t specifically mention which version of Rails they’re using, but the installation screenshot shows rails-1.1.2, which is a little on the old side (although the only errata I’ve seen is that require_gem doesn’t work anymore).
Thankfully once you’ve skipped ahead to chapter 8 and they start dealing with Rails in all its glory the book gets a lot better.
What The Book Covers
- Stuff to skip
- Chapter 8: view, controller, partials, helpers
- Chapter 9: model, migration
- Chapter 10: linking with image_tag, link_to, h, how ERb rolls out to HTML
- Chapter 11: uploading a file, storing binary data in database
- Chapter 12: validating input, belongs_to/has_many/many-to-many
- Chapter 13: AJAX, sending email, XML, SOAP web service
- Chapter 14: web sites (most are still alive)
- Chapter 15: lots of ruby-specific tricks with no details
- Chapter 16: Rails concepts aka “I have a job interview in 10 minutes!”
- Chapter 17: using Rails on legacy databases
What could be discussed more
- debug helper
One thing that’s pretty dang neat is that the author provides his email address and his phone number. That’s an impressive level of service. He tries a little too hard to be funny in the book, but there were some parts that made me chuckle (like when he talks about sending email reminders to his wife, but using instant messaging when he needs her urgent attention).
Unfortunately I’d recommend picking up a copy of Agile Web Development with Rails (AWDWR) instead of Ruby on Rails for Dummy (RORFD). RORFD is split into many small unrelated examples while AWDWR has more extensive example code that you could use as a skeleton for a professional site. AWDWR is much clearer to read than RORFD, which always interrupts the flow with a new figure and screenshot. One page of text may cross-reference up to ten other figures/screenshots/chapters. It feels like RORFD has ADD and it doesn’t make for an easily digestible read.
You can find a more favorable review here.
When bloggers like Gina Trapani, Mark Frauenfelder, Chris Anderson, and Phillip Lennsen are honored to be collected in New York Times’ bestselling author Michael A. Banks’ new book, Blogging Heroes: Interviews with 30 of the World’s Top Bloggers I can’t even begin to describe how exciting it is to be included in the list. “Someone must be making a mistake,” went through my head several times.
From the cover of the book you can see a list of a many of my blogging heroes: Frank Warren (PostSecret), Gina Trapani (LifeHacker), Merlin Mann (43folders), Peter Rojas (EnGadget), Chris Anderson (Wired), Michael Arrington (TechCrunch), Robert Scoble, Steve Rubel
Several other sites are posting previews from their chapters in the book, so I will as well: Blogging Heroes Preview Chapter – Internet Duct Tape
Preview the Book
Here’s a list of some of the other free chapters that are available online:
- Boing Boing’s Mark Frauenfelder
- Wired’s Chris Anderson (author of the Long Tail)
- Lifehacker’s Gina Trapani
- TechDirt’s Mike Masnick
If you spot any other chapters in the wild, drop me a comment on this blog post and I’ll add them to the list.
On Writing Blogging Heroes
Michael Banks is talking about the experience of writing Blogging Heroes.
Pick Up Your Copy
I came to a rather startling discovery in the past month: magazines are just blogs with the added luxury of being able to read them while on the toilet or in the bathtub (but hopefully not both).
I picked up the October issue of Inc. magazine because Joel Spolsky of Joel On Software has joined the magazine. I’m a Joel fan-boy. Internet Duct Tape was inspired by Joel on Software. Here are some random thoughts from spending a rainy Saturday flipping through the pages. Can this possibly be entertaining or of value to my readers? I have no idea.
I’m going to give each article a +1 or a -1 based on whether or not I found it interesting and discuss it with a short blurb. You can read along with me on the online copy. Follow the bouncing ball.
-1 Editor’s Letter, Contibutors, and Reader Mail: I can’t help but think this stuff should be at the end of a magazine instead of at the front. Below the fold, if you will. Give the reader the most useful tidbits first instead of burying it in the middle.
-1 People Who Were Inspired by Ayn Rand’s Atlas Shrugged: It didn’t sell me that the only entrepreneur’s name I recognized was the one from Doubleclick. Instead of a biographical tidbit about Ayn Rand, tell me what the book was about! How did they miss that there is a 2008 movie with Angelina Jolie in the works? Is Wikipedia the new Coles Notes? Where was the tie-in that Atlas Shrugged inspired the current hit Xbox 360 game Bioshock?
I’m getting the feeling that I’m not the core audience for this magazine.
+1 Netflix vs Blockbuster: Blockbuster proves the adage that startups are R&D for bigger companies by one upping Netflix’s business model. Bad advice from other entrepreneurs follows.
- “Netflix should court CDs” – iTunes and digital downloads are already trailblazing the future of this industry, going up against iTunes on their existing strengths isn’t going to help Netflix. Isn’t CD by mail subscription also going up against Columbia House?
- “Focus on being #1 service without lowering price” – Good, if obvious, advice.
- “Focus on obscure films” – Every company needs to have a passionate minority at their core if they hope to have any success. This would have been good advice if Netflix was starting at a grassroots level, but they already have that core smaller audience from years ago.
- “Hookup with a cable company” – I completely agree that they need to move to digital downloads. Always build the product that will kill your current product. But getting in bed with CableCos is courting the devil.
+1 Investor’s Guide to Inc 500: Bug VCs with the previous issue’s top 500 startups list. Bonus points for mentioning Massage Envy masseuse franchises that are a lawsuit waiting to happen. Bill Me Later is my pick from the list. They act as a proxy between your credit card info and other companies for people who are afraid of buying on the Internet. I also like Vocera who do star trek style voice communicators for hospitals.
+1 Even CEOs Have to Apologize for Screwing Over Workers: I appreciate the message, but felt there was a bit too much emphasis on assigning blame for why the bad decisions happened. Kudos for stepping up to the plate, admitting mistakes, and keeping the team in the loop.
+1 Applying Maslow’s Hierarchy of Needs to Companies: Someone’s written a book about the idea that companies need to fulfill more of an employee’s needs than just the paycheck. Interesting: customers are promiscuous meaning that even if they’re perfectly satisfied with service they might still switch to a competitor they’re also perfectly satisfied with. Article is fluffy, wonder if the book goes any deeper? No mention of creating fulfilling work, just increasing employees self-worth and attitudes towards themselves.
Is this like that bogus psychology from the 80s that encouraged self-confidence without merit and created a generation of self-entitled people who don’t understand why life isn’t handing them the success they deserve?
-1 Estate Planning: I pay someone to pay attention to this stuff for me. That might be stupid on my part.
+1 Is My Social Network Startup Worth Investing In? 55 Alive: Investors get to rip into a young startup. Startup wants $250k but most investors are advicing between $1 to $20 million. I love the VC who points out that common interest ties people together, not demographics like age group. We had a conversation about this last night at a dinner party discussing the people you knew in elementary school and high school that you reconnect with but it goes no where — because where you went to school is no indication of common interests. Same guy tells them to generate their own ad revenue without investors.
More good advice that they need to focus on building up local features. So true, what makes social networking sites work is if they become a communication tool for an existing friends group.
+1 Internet Video Beyond YouTube: Some good discussion on interactive webcasts, livecasting, and promotional videos. HelloWorld is officially my favorite company name ever. I’m so surprised there was no mention of Will It Blend or CommonCraft.
+1 Web Polls: Not enough information on the individual web polling companies, but the use cases of how businesses are incorporating them are phenomenal. Conclusion: don’t manage statistics gathering by hand, but be careful who you go with because it can go from $1,000 to $10,000s of dollars.
+1 Using Marketing to Improve Old Business: One man’s guerilla campaign to revitalize the NY Metropolitan Opera. My favorite example of traditional businesses embracing new media is the Brooklyn Museum’s Flickr page. I liked the idea of giving free tickets to the last dress rehearsal to create buzz and simulcasting the operas onto outside monitors.
+1 Update: An older story of a company in trouble and the advice the Inc. experts gave is updated with the results. Great proof that the magazine advice works.
+1 Questions and Answers: Inc. recommended a survey business support myspace, but ignore Second Life. Unfortunately, no mention of SL’s flying penii. They also give the sage advice that the average person sees 3,000 ads a day so advertisers have to work that much harder to be in the 1% of ads that people notice. Good advice with “do you even know who your audience is?” Huge bonus points for mentioning Made to Stick, one of the best books I’ve ever read.
How to maintain corporate culture: build stories around your brand, have bigger goals than “making money” and fire people who don’t fit with the culture you want to have.
+1 Money Management for Entrepreneurs: Good tip that you should have two financial advisors, one primary and one secondary so that if one doesn’t work out then you can transfer to the other while you look for a replacement.
0 Joel Builds a Shipping System: Reprint from Joel on Software.
-1 Entrepreneurship is Passion: all fluff, no content.
-1 Inc. Gear: hard to believe that this isn’t product placement.
+1 Pandora Story: Cover story about the Pandora music recommendation service. Turning your customers into fans will help you overcome all kinds of roadblocks. But what about your international customers?
+1 The Way I Work: The best interview question is to find out how someone copes with stress. Article focuses on stress management and using external creativity to unwind — maintaining relationships with your support network is more important than the job.
-1 Corporate Retreat: The usual on breaking down people to build a team.
+1 How I Did It: Success story in billboard advertising. Become an expert and buy advertising space that people aren’t using.
-1 Inc. Classifieds: Spam spam spam. Penis enlargement, asian brides, and buy my e-book. It’s like they have blog comments printed right in the magazine.
Overall Score: +7
After an underwhelming start I found some good content in the middle of Inc. Magazine and I’d read it again. Every blog is a self-run small business and every blogger is an entrepreneur, so it isn’t that surprising that I liked the magazine.
I’m going to celebrate Labour Day with the only book I’ve ever read that captured what it’s like to work at building integrated circuits. The Soul of a New Machine is a Pulitzer Prize winning book written in 1978 by a reporter named Tracy Kidder. Hat tip to Scott Rosenberg, or rather to James Fallows, for turning me on to this book by comparing it to Dreaming in Code. If you’ve read the book, you’ll probably find this interview with Wired (2000) interesting, as it catches up with the old team.
Rather than pontificate on what the book meant to me, I’m going to cut and paste some quotes from another reviewer on Amazon.
Review by B. Marold (Bethlehem, PA United States)
When it was first published, the book was a narrative of what was then `modern’ technology, where the central processing units (CPU) or `brains’ of commercial minicomputers and mainframe computers were built up on large circuit boards from individual, specialized integrated circuit chips, with each chip integrating dozens or hundreds of discrete components. This compares to today’s microcomputers where the entire CPU is placed on a single chip incorporating tens of thousands of discrete functions, all taking up no more room than the average credit card. Now, the book is more a history of how this technology was developed, and yet its picture of how people work in teams developing technological projects will probably never go out of date.
The irony of this book is that the computer being developed by the team described in this book, a 32 bit Eclipse computer developed by the Data General corporation, a competitor to the larger and very successful Digital Computer Corporation (Digital), did not really achieve any major breakthrough in technology. While it was intended to compete with a new generation of Digital VAX machines, it ended up being just barely faster than VAX’s in a few special tasks. In fact, in a conversation I once had with some Digital engineers, they said that when they went head to head with Data General in bidding for a computer sale, the only thing they had to do was bring out Kidder’s book to demonstrate that the Data General box was yesterday’s news. Data General may have had the last laugh, as ailing Digital was bought out by Compaq, which has since merged with H-P, further submerging the once great Digital presence in the commercial computer world. Meanwhile, Data General is still around, albeit not the presence it once had when the `minicomputer’ was the great alternative to the IBM monoliths in the glass houses.
Favorite Quotations from The Soul of a New Machine
Computer were relatively scare, and they were large and very expensive. Typically, one big machine served an entire organization. Often it lay behind a plate glass window, people in white gowns attending it, and those who wished to use it did so through intermediaries. Users were like supplicants. The process could be annoying. P14
A company was more likely to asphyxiate on its own success. Demand for its products would be soaring, and the owners would be drawing up optimistic five-year plans, when all of a sudden something would go wrong with their system of production. They wouldn’t be able to produce the machines that they had promised to deliver. Lawsuits might follow. P33
A heroic metaphor for success in the computer business: “The major thing is avoiding the big mistake. It’s like downhill ski racing: Can you stay right on that edge beside disaster?” P35
[Seymour Cray and Co.] had come to build what are generally acknowledged to be the fastest computers in the world, he quintessential number-crunchers. Cray was a legend in computers, and in the movie Cray said that he liked to hire inexperienced engineers right out of school, because they do not usually know what’s supposed to be impossible. P77
[On joining a high tech company] Going to work for the Eclipse Group could be a rough way to start out in your profession. You set out for your first real job with all the loneliness and fear that attend new beginnings, drive east from Purdue or Northwestern or Wisconsin, up from Missouri or west from MIT, and before you’ve learned to find your way to work without a road map, you’re sitting in a tiny cubicle or, even worse, in an office like the one dubbed the Micropit, along with three other new recruits, your knees practically touching theirs; and though lacking all privacy and quiet, though it’s a job you’ve never really done before, you are told that you have almost no time at all in which to master a virtual encyclopedia of technical detail and to start producing curcial pieces of a crucial new machine. And you want to make a good impression. So you don’t have any time to meet women, to help your wife buy furniture for your apartment, or to explore the unfamiliar countryside. You work. You’re told, “Don’t even mention the name Eagle outside the group.” “Don’t talk outside the group,” you’re told. You’re working at a place that looks like something psychologists build for testing the fortitude of small animals, and your boss won’t even say hello to you. P79
Wallach had now spent more than a decade working on computing equipment. He’d had a hand in the design of five computers — all good designs, in his opinion. He had worked long hours on all of them. He had put himself into those creatures of metal and silicon. And he had seen only one of them come to functional life, and in that case the customer had decided not to buy the machine. P93
That was what made it fun; he could actually touch the machine and make it obey him. “I’d run a little program and when it worked, I’d get a little high, and then I’d do another. It was neat. I loved writing programs. I could control the machine. I could make it express my own thoughts. It was an expansion of the mind to have a computer.” — Alsing, P126
There’s no such thing as a perfect design. Most experienced computer engineers I talked to agreed that absorbing this simple lesson constitutes the first step in learning how to get machines out the door. Often, they said, it is the most talented engineers who have the hardest time learning when to stop striving for perfection. West was the voice from the cave, supplying that information: “Ok. It’s right. Ship it.” P158
He would bind his team with mutual trust, he had decided. When a person signed up to do a job for him, he would in turn trust that person to accomplish it; he wouldn’t break it down into little pieces and make the task small, easy and dull. P173
“With Tom, it’s the last two percent that counts. What I now call ‘the ability to ship product’ — to get it out the door.” — Rasala P188
Above all, Rasala wanted around him engineers who took an interest in the entire computer, not just in the parts that they had designed. He said that was what was needed to get Eagle out the door on time. P199
The very word, engineer, dulled the spirit. It was something your father might be interested in.
Typically, a machine gets built and sent to market and in its first year out in public a number of small, and sometimes large, defects in its design crop up and get repaired. As the years go by, the number of bugs declines, but although no flaw in a computer’s design might appear for years, defects would probably remain in it– ones so small and occurring only under such peculiar circumstances that they might never show up before the machine became obsolete or simply stopped functioning because of dust in its chips.
“The way to stay on schedule is to make another one.” — Rasala P246
“It doesn’t matter how hard you work on something. What counts is finishing it and having it work.” — Holberger P252
[Small companies would] announce a new product and then for one reason or another they wouldn’t be able to produce it in sufficient quantities to meet their obligations. They’d asphyxiate on their own success. But a small company had to court disaster. It had to grow like a weed just to survive. P312
Almost every commentator has assured the public that the computer is bringing on a revolution. By the 1970s it should have been clear that revolution was the wrong word. And it should not have been surprising to anyone that in many cases the technology had served as a propr to the status quo. P317
Most computer companies have boasted that they aren’t just selling machines, they’re selling productivity. But that clearly isn’t always true. Sometimes they’re selling paper-producers that require new legions of workers to push that paper around.
But maybe a time would come when the computer would run every aspect of a person’s life. “Then we get tired of it. We start growing plants or something. Maybe slowly we will turn around and go away from it. If computers take something away from us, we’ll take it back. Probably a lot of people will get screwed before that happens.” — Holland P325
“I’ll stop asking questions and let you go home. You look tired.”
“It’s a long-term tiredness,” said Rasala.
“Going home won’t solve it,” said Blau. P334
“That’s the bear trap, the greatest vice. Your job. You can justify just about any behavior with it. Maybe that’s why you do it, so you don’t have to deal with all those other problems.” — West P367
Fair Use, Copyright and Digital Rights
There is a grassroots movement to make July 11th an International Fair Use Day where we all celebrate our rights to copy content in a fair manner (i.e.: backing up software/movies, quoting other sources). Copyright laws have reached the point where they stifle innovation and prevent use from standing on the shoulders of giants. Fair use of copyright is very different from piracy; copyright laws should protect the rights of the content creator but also protect the rights of the end user. Fair use is about achieving balance between the two different interests.
Copyright discussion and technology often go hand-in-hand because advances in technology make it easier and easier to cheaply reproduce what was originally hard to reproduce. Striking a balance between producers and consumers is very important. If nothing was profitable then nothing then there would be less innovation, but on the flip side what if producers held complete control over how and when their works could be used? Can you imagine a world where you weren’t legally allowed to re-sell or buy used books, CDs or DVDs? Can you imagine a world without libraries?
(photo by jbonnain)
July 11th is a great choice for the date because it is also the birthday of Canada’s own digital rights super-hero Michael Geist. Happy birthday, Michael. If you aren’t familiar with his work, then I recommend starting with a series of articles called “30 Days of DRM” that are enlightening to say the least. Another Canadian digital rights super-hero is Cory Doctorow, a science-fiction author and co-editor of the famous BoingBoing weblog.
Last night I finished reading Cory Doctorow’s new collection of short stories, Overclocked, and I was very surprised at how much I enjoyed it. I’ve read two of his other books, Eastern Standard Tribe and Down and Out in the Magic Kingdom, and found them disappointing although full of interesting ideas. Overclocked succeeds where the others failed for me because the short narrative allows for a focus on the ideas without feeling that the characters are neglected.
Common Themes in Overclocked
Cory deals with information warfare, robotic sentience, inequalities between first and third world countries and the next level of copyright infringement – when we have 3d printers that can replicate any goods. So much of our current consumer laws are based on the concept of scarcity. We’ve already entered a post-scarcity economy when it comes to entertainment goods that can be reproduced digitally. 3D printing already exists, what kind of world do we want to live in when anything — even food, clothing and electronics — can be reproduced with minimum cost and effort?
The Stories from Overclocked
All of the short stories in Overclocked are already freely available online from other sources. You can check them out by following these links.
Printcrime – the real outcome of a society where copying has been made illegal.
When Sysadmins Ruled the Earth – when a biological agent wipes out humanity the only people left standing are the sysadmins who were protecting the network in clean rooms.
Anda’s Game – a young girl learns about goldfarming and world wide inequality thanks to World of Warcraft.
I, Robot – Asimov meets Orwell in a mash-up of 1984 and I, Robot where government controlled restrictions on technology have created wars with countries that don’t follow the same restrictions.
I, Row-Boat – a sentient row boat with free will explores the nature of consciousness in a post-human society.
After the Siege – A city goes from utopia to a cesspool of human misery when other countries attack them for illegally copying the goods they need to survive.
I heard about Programmers at Work in the blog buzz surrounding the release of Founders at Work. Programmers at Work is a 20 year old book (1985) that interviews some of the top programmers of that era about the art of programming. It is not widely in print anymore, but it was easy to find a copy at my local library. When I picked it up at the library I wondered how relevant would it still be? The only constant with technology is how fast it changes.
Coding Horror has a post asking people what their favorite programming quotations are. He throws a sideways reference to Programmers at Work, a book I recently finished reading. I’m one of those annoying people who writes in the margins of books, and one of the things I like to do is collect my favorite quotations so that I can remember them down the road.
These are my favorite quotes from Programmers at Work: Interviews with 19 Programmers Who Shaped the Computer Industry. It is a collection of interviews Susan Lammers did in the early 80s. You can read my full review of the book here.
Cory Doctorow is a writer from Toronto. He is well-known for being co-author of one of the most popular blogs on the planet (BoingBoing), his association with the Electronic Frontier Foundation and for his stance against copyright. Down and Out in the Magic Kingdom was his first novel and one of the first books to be simultaneously released in published form and as an online free download.
While I could have done without the focus on Disneyland, there were several key ideas in his book I found interesting. The story takes place in a “post-death” society. Scientists have discovered how to “back-up / brain dump” the human brain so that all the experiences that make up a person can be copied into a new body — which are easily available thanks to cloning advancements. Death becomes meaningless as you only lose the time since the last back-up (days or weeks). As would be expected, medicine takes a complete nosedive; why try to heal a body when it is so much easier to grow a new one?
photo by shadowplay
Everyone is online all the time with a “heads up display / HUD” that provides them additional information about the things around them. In this post-scarcity economy where material goods are abundantly available currency has been replaced by “whuffie” — a quantitative measure of how you are viewed by society. Think of something like micropayments where if you write a popular song people can give you a small portion of their whuffie and the riches come from reaching many people.
“Whuffie recaptured the true essence of money: in the old days, if you were broke but respected, you wouldn’t starve; contrariwise, if you were rich and hated, no sum could buy you security and peace. By measuring the thing that money really represented – your personal capital with your friends and neighbors – you more accurately gauged your success”.
Whuffie is a measure of reputation, and as a blogger I saw this as a natural offshoot of the blogging microcosm. Whuffie is like attention.You write good content to get hits, links and to increase your influence. Linking to someone is like giving them whuffie. Having a high Wuffie score gets you exclusive invitations, free stuff and a general level of respect. Whuffie promotes a society where people perform actions to make them more popular.
This is where the focus on Disneyland takes place. The book is about in-fighting between several of the factions who control the rides. I felt pretty “meh” about all of the Disney stuff but I really enjoyed the concepts of this futuristic society and I’d recommend the book for that alone.
- Cory Doctorow on Building an Audience
- False idols and teacups (prose)
- Book Review: JPod by Douglas Coupland
- Book Review: Microserfs by Douglas Coupland
Write what you know. In this case, what I know about is being a geek. Over the next few days I’ll be suggesting things that I liked. I’ll be giving ball-park prices (in Canadian dollars) and at the end of each post I’ll include a link to where you can find all of the items on Amazon.
This time around I cover some of my favorite novels.
Write what you know. In this case, what I know about is being a geek. Over the next few days I’ll be suggesting things that I liked. I’ll be giving ball-park prices (in Canadian dollars) and at the end of each post I’ll include a link to where you can find all of the items on Amazon.
(photo (c) torek)
Unlike the rest of the posts in these series, I haven’t read most of these books. I’m basing the recommendations on the countless other lists on other tech websites, particularly Jeff Atwood at Coding Horror. These books are programming language independent and would make a great gift for anyone working in high tech.
Jpod is the sequel (in spirit) to Microserfs. The mid-nineties fast forwards to the mid-naughts and our protagonists switch from being monolithic Microsoft serfs in Seattle to serfs for a large game company in Vancouver. The title is a clever marketing ploy; it has nothing to do with Apple/iPod. JPod refers to the cubicle the six protagonists share. The tagline used in the marketing campaign is “Generation X-Box,” another blatant product alignment to sell more books.
Is JPod proof that Coupland has sold out?
The year is 1993 and this is the story of Daniel, a software tester at Microsoft. He lives in a geek house with his co-workers, and his relationship with them and their relationship with the software industry is the backdrop for this slice of life. It is typical Coupland fashion, strong on narrative/characters/themes and weak on plot.
It is an epistolary novel written in first person as Daniel types in his personal diary on his laptop. Flashbacks abound as we hearken back to a pre-Internet explosion era when Multimedia was the rage and everything had to be on CD-ROM. It is striking to look back and see how obvious it was to use computers for writing personal journals. Blogging is a natural evolution. (Or as Mil Millington likes to put it “nerds talking to themselves in public”).
After the break, more of my review of Microserfs.
joelonsoftware is one of the highest read programming blogs because Joel Spolsky does an excellent job of combining technical information with humour that makes his writing informative yet interesting. He was the program manager for the Microsoft Excel team and has since moved on to running his own startup. His books collects some of the best articles from his website. It’s broken into four parts, the first three of which I think are essential reading and the last of which is a comentary on Microsoft .NET which seems really unnecessary and probably won’t age as well as the rest of the book will.The book is unusual for any kind of tech book is that it’s a real page turner. Unfortunately, most of the content is already from his website so I found that for the first 70 pages or so I was just rehashing some of the best articles on there. If you’re already a regular reader of his site you might not get nearly as much out of it as someone who is picking it up fresh.
Some of my favorite parts of the book:
- 12 Steps to Better Code
- Painless Functional Specifications (and an example of a real world product spec)
- Painless Software Schedules
- Daily Builds
- Paper Prototyping
- Guerilla Guide to Interviewing
- Incentive Pay Considered Harmful
- Human Task Switching Considered Harmful
- Getting Things Done When You’re Only a Grunt
- Startup Strategy Letters
Joel’s approach to many things is so simple that even experienced programmers can find some useful nuggets of information in there (although there is strong focus on Microsoft products). I really wish someone had taken me aside with his advice on painful schedules when I’d first started. It is amazing how doing minimal time tracking every day can make you better at estimation and better at realizing where you are spending your time and focus.
After reading Paul Coelho’s the Alchemist, I thought this would be a fantastic follow up. Unfortunately, I was wrong. Where the Alchemist was a very focused tale examining a specific theme of following your dreams, TAoHaW was more of a diatribe between two people exploring a subject without a clear hypothesis. I think there is some good wisdom in this book, but so much of it is common sense that you already know.
One very interesting distinction is where the Alchemist encourages you to follow your dreams no matter what the cost, TAoHaW suggests that happiness comes from within, from accepting your circumstances and making the most out of them (although it is important to recognize when a work environment is bad).
I really wasn’t impressed with Howard Cutler (the author of the book). His writing style was very vague, and it seemed to be filled more with his own explorations and thought process without any real conclusions. Some of the facts and statistics he spouts seem a bit shoddy as well (but then again I’m part of the “all statistics are lies camp).
- Read more reviews for “The Art of Happiness at Work” at Amazon (soft cover)
- Read more reviews for “The Art of Happiness at Work” at Amazon (hard cover)
A friend from work recommended that I pick this up, and I was glad I did. This is one of those novels that everyone should read when they are at a crossroads in their life and wondering what kind of career path they should pursue. It is the tale of a young boy who decides to listen to his heart and follow his dreams instead of succumbing to life of mere contentment. Throughout this allegory, Coelho imparts the wisdom that as long as you are following your heart and your intuition, and you listen to the omens that life provides, you will find success in that which you most desire. It is one of those books that is simple yet profound and everyone should read at some point or another.
Favorite quotes / passages that I found insightful: