Last week I read the new Matt Ruff novel about 9/11, an alternate history focused on examining its own premise.
On Tuesday evening, a huge billowing cloud of smoke displaced the usual traffic in photo after photo looking down Newbury Street and Boylston Street. The view from across the river showed the smoke spreading over Boston. People were evacuated from a large swath of the city, work and life were disrupted for tens of thousands of people, a number of roads and subway stations were closed, and there were early warnings that the smoke might be particularly harmful though the government was quick to dispute that (while also asking people to stay out of the area).
Then I went to a show last night. I arrived early and talked a bit with the person who was filling in as house manager since the house manager was having trouble getting to the theater. Conversations as people arrived were about trying to reach friends and colleagues, traffic disruptions, power disruptions, and cancelled performances.
This all led up to seeing the show “Recent Tragic Events” last night, which was set in an apartment the day after 9/11. The lead character is trying to reach her twin sister, who lives in New York and has not been in contact. A show set the day after the city I know was filled with smoke, which I’m watching the day after the city I know is filled with smoke. And it was absolutely creepy how easy it was for me to go back to that time. Was it all the priming and context? Was it the television on the set playing CNN from 9/12/2001 for two hours? Was it the powerful performance from Aimee Rose Ranger? Regardless, I was relieved to return home to my infant son, to my wife of more than 10 years, and to a television which is no longer tuned to CNN.
Thursday, March 15, 2012
What are the chances?
Posted by
Michael
at
11:08 AM
2
comments
Saturday, March 10, 2012
All bets are off
Back when the end of greyhound racing was being discussed in Massachusetts, it was clear that the dog tracks had no reason to stay open except in the hopes of getting broader gaming licenses for slots or full-blown casinos. I wrote to the governor back then asking that he simply let them trade in the racing licenses for slots licenses, even though I’d rather have neither around us.
The dog track owners insisted that greyhound racing was critically important for various reasons (social, economic, cultural), just as they’ve argued in other states. The same track owners had spent decades falsely insisting that greyhounds were vicious by nature and unfit as pets. Widespread public adoption of former racing greyhounds would have led to widespread public scrutiny of how the tracks were mistreating greyhounds, as it eventually did. Instead, racing dogs had routinely been killed when their racing careers were over (at one to five years old). Greyhound racing was a brutal and dishonest industry.
In Massachusetts, we closed down the dog tracks. In several other states, they gave the dog tracks broader gaming licenses on the condition that they keep racing greyhounds as much as 6 days a week. After all, the track owners had all these compelling arguments for the importance of greyhound racing. It didn’t matter that there was no longer any real audience, or that the dogs were going to continue to be mistreated, frequently injured, and sometimes killed.
Now that the dog tracks have their broader gaming licenses in those states, the track owners would like to keep their horse OTB, their slots, and their casinos, and close down the greyhound racing. Greyhound advocates who have been struggling to shut down greyhound racing are confused by having these new allies. I imagine that state officials who believed the track owners when they were passionately arguing for preserving greyhound racing are confused as well.
I’m conflicted about what the right response is. The track owners are admitting that they got their gaming licenses by lying. The lying is bad but common. Admitting it is good and uncommon. But if we don’t punish them for lying even when they admit it, then how do we convince anyone that lying is wrong? But if we punish them for admitting it while turning a blind eye to everyone else who is lying, then are we really serving the cause of greater honesty?
The one thing I’m certain of is that the wrong response, even though it’s the easy response, is to force them to keep the greyhounds racing. That just punishes the dogs along with the track owners, and the dogs deserve better. They always have.
Posted by
Michael
at
3:31 PM
0
comments
Friday, March 9, 2012
Counting noses
Two recent MBTA stories collided in my head: one story about MBTA bus drivers frequently not bothering to have passholders actually scan their passes on the bus, and another story about the MBTA doing yet another desultory crackdown on fare evaders.
The first problem isn’t directly a revenue issue for the MBTA, but it does lead to systematically undercounting ridership. That makes it hard to know how many people will actually be impacted by service cuts, hard to know where to add service, and harder to make the argument that the MBTA is worth funding because it serves a lot of people. When the MBTA says that they want to eliminate Lisa’s bus route because not enough people ride it, it’s frustrating to see the bus driver wave people onto the bus without scanning their passes.
A solution to the first problem is to count monthly passholders as a certain minimum number of rides each month. If the scanned rides on a pass are under the monthly minimum, then add the remaining rides to the ridership numbers. You can allow monthly passholders to choose a few routes and stops that they want their rides to be counted towards, and balance that with the actual pattern of scanned rides.
The second problem is a revenue issue, particularly when the fine for fare evasion is a tiny percentage of the evader’s fare savings multiplied by the evader’s chance of being caught. If adding up the occasional ticket is far less than regularly paying the fare, then fare evasion is not a surprising problem.
A couple of obvious solutions are to increase the fine for fare evasion and to increase enforcement. That way you capture both sides of the probability multiplication. But whatever level of fine and enforcement we decide on, I’d like to see one more item added to the equation: add the cost of two monthly passes and give the fare evader a pass from that date until the end of the following month. An important goal should be to change the fare evader’s habit of bypassing the fare collection system. By giving (selling) the fare evader a pass for the next 5-8 weeks, they have no excuse not to scan their pass for a while. Perhaps that will be enough to change a few habits.
Posted by
Michael
at
10:24 AM
0
comments
Maybe we should expand tipping
IRS representatives all give out their 10-digit ID numbers when they pick up the phone now. Do you think they ever google their numbers to see if anyone is mentioning them? Should we start yelp-rating individual IRS agents? Is there a market for ratemyIRSagent.com? Ok, I’ll go first.
IRS representative 1000233200 in the individual accounts department is lazy, rude, and wrong.
IRS representative 1002577699 in the tax law department is very pleasant. Not in the department I needed, sadly. She helps people who can’t read. (Well, she helps taxpayers who can’t read. I don’t know who helps 1000233200.)
Crossing the 5-hour threshold and more than 10 people for a simple tax ID number assignment is what finally got me to start writing down ID numbers. Without paying attention, my impression was that they were all terrible. I think that impression was due to some of them being terrible and none of them being able to solve the problem. When I look at the two above, terrible only describes one out of two.
Posted by
Michael
at
6:39 AM
0
comments
Labels: government, privacy
Wednesday, March 7, 2012
Monday, March 5, 2012
What I’m learning at TEDx Somerville
A quick preface: I really appreciate the opportunity to listen to every one of these people speak, and I know they put a lot of work, effort, and energy into their presentations. I could not do what any of them did. Even the talks that I personally didn’t like were undoubtedly moving and illuminating to other people who were there, and I’m glad there was a huge mix. The following is very personal reactions.
Mayor Joe Curtatone: I wish that the person who ran my city was someone like this who values his residents, who values diversity, who values information and ideas, and who believes that an evolving world requires evolving responses. I have a hard time understanding why people in my city vote for a guy whose primary skill is gladhanding and who hates progress. Lesson: my mayor really sucks by comparison.
Dan Rothstein: Asking questions is a skillset. You can learn to ask questions, to change questions from closed to open, to reframe questions with the assumption that there is a positive answer, and to prioritize questions. And this skillset empowers people. The memorable graph was one showing that reading and writing skills both increase sharply through around age 10 and then plateau with only slight increases to age 18, while question skills peak at age 4 and then decrease sharply through age 18. Lesson: What lesson would you take from this?
Georgy Cohen: Personal stories are often far more interesting to the person telling them than to their audience. Don’t make the mistake of thinking that your family is the only odd one. Lesson: an amazing title for your talk is insufficient.
Lenni Armstrong: Our combined waste and storm sewer system is old and horrible. Pavement is bad. It took 45 amateurs an entire day to remove the asphalt from a back yard, whereas it took 1 professional one day to remove the asphalt from ours (by hand). Permeable surfaces are better. Over 70% of Somerville is impermeable. Lesson: impermeable pavement sucks.
Ray Matsumiya: I’d love to hear more about his work creating personal contacts between Somerville and Morocco. It sounds extremely successful, and an inspiring story about how a couple of people can make a huge difference to hundreds of people. Lesson: Being insanely nervous makes you a less compelling speaker. I could never give a TEDx talk.
Kelly Creedon: Foreclosures suck. People are ashamed to talk about their problems, whereas solutions and peaceful revolt can only happen when people break their inclination to silence. Lesson: never doubt the power of a sufficiently mobilized populace to videotape their own suppression by the banks and the police while still being evicted.
Video of Drew Dudley: Holy crap this guy is a phenomenal speaker. Lollipop moments. Seriously, watch this video. I’m really glad I did.
Schuyler Towne: An interesting talk about ways to look at the significance and meaning of locks. One of the few talks I might go watch again on video.
Grooversity and Marcus Santos: Drumming performance, very loud, good for audience participation, bad for eardrums. Lesson: bring earplugs.
Video of Gever Tulley: He runs a camp where kids actually build things. If you give kids tools and materials and very light guidance, they can build things, enjoy building things, enjoy failing at building things, solve problems, and build more things. Lesson: kids can build more things with power tools.
Ross Lohr: This one is really complicated. Giving things (shoes, shirts) away to poor countries destroys their local economies revolving around those things. But isn’t that like arguing that single-payer health care is problematic simply because it would force all the leeches in our health insurance system to find other employment doing something else? Shirts go from here to Africa, get remade there into new shirts or bags or ties, get reimported here and sold to rich liberals at very high prices. And you should feel good about it because they pay something to poor people to do the work, which empowers them. Lesson: if you charge enough, you can call anything fair trade.
Joe Grafton: Support local businesses. Buy local efforts are good. This is very old news to me, but good to have a chance to cheer and clap in person for a local guy who’s been instrumental in supporting our local buy local campaigns at a local conference featuring local speakers, a local audience, and local organizers. Lesson: local.
Jessie Banhazl and Brendan Shea: Decent tag-team presentation dynamics about building and maintaining a rooftop farm for a restaurant. They talked a lot about their process and step-by-step experiences, rather than focusing on lessons learned. That doesn’t play well. They overwatered, they used the wrong soil mix, they didn’t figure out how to work with the restaurant well, and they did very little practical planning. Then they decided to improve the next year. Um, congrats? Lesson: don’t pay professionals at their usual rate to do new things they have no experience with.
Clarence Smith, Jr.: Cute talk about how knowledge spreads in a community, focused on the traditional barbershop culture. People who meet regularly and swap stories actually learn things that way! Lesson: molasses makes better Kool-Aid.
Brian Whitman: How do we discover new music? He’s been very involved in the efforts to find computerized approaches to discovering new music, but gave no real info or ideas. Felt like a huge missed opportunity for a fun talk. Lesson: pretend your audience wants to learn something, and see if you have something to teach them.
Jenee Halstead: Singer-songwriter performance. Must get her CD.
Video of Graham Hill: Less stuff = more happiness. Less stuff doesn’t mean no stuff. Good speaker, a little extreme in examples, nothing really new. Lesson: give away more stuff.
Daniel Hadley: Can a city government make you happy? Talked a bit about what Somerville found when surveying residents about happiness and then tried to correlate that to other factors. This has a very long way to go before being persuasive, but he’s right that an important step is to start collecting data. Lesson: you can find happy people in the strangest places, even in East Somerville. And most people claim to be pretty happy.
Ruth Allen: Open government examples from a few other places in the world. Allow citizens to participate in budget discussions (here the best we ever do is make the budget visible). Start public debate with the person who is most downtrodden (here the best we ever do is pretend to listen to empowered community groups). Give unused buildings to community groups (here the best we ever do is sell them with tons of use conditions). All of these ideas could be productively adapted to our country. It’s a shame we hate helping people. Lesson: we are nowhere near being the great democracy we pretend to be.
Erza Glenn: Interactive websites can provide an easy and interesting way for residents to contribute information about their communities. Left unaddressed: how to vet the info, and what to do with it? I’ve seen a number of these efforts over the past few years, and haven’t yet seen anything useful done with the info collected. Lesson: collecting data is a good first step, but is hardly a last step.
Sam Sommers: Great speaker, teaches at Tufts. Must find out what he teaches, consider auditing. Talked about our bad tendencies when we’re in large groups to avoid taking individual responsibility, to assume that someone else will deal with a problem, to assume that someone else would have noticed if there really were a problem. Lesson: Sam Sommers is a great speaker. Oh, and don’t be a sheep.
Alex Feldman: We need to teach and practice body language and non-verbal communication. We’re becoming more and more word-focused. He, on the other hand, is almost as entertaining a performer as he thinks he is. Lesson: make faces at your child.
Keith Fullerton Whitman: What the hell was that? Uninteresting electronic music with no explanation. And way too loud. Please, God, get me out of here. [Lisa says he was actually making her nauseous. Reminded her of stories about the military weaponizing noise.] Lesson: when your ears start telling you to throw up, don’t try to tough it out in the fourth row—just get up and leave.
Mike Norton: We much more highly value things we put effort into ourselves. Funny examples about origami and small Lego models. How can we use this to get people invested in things they might otherwise throw out, such as medical appointment reminders? Two small examples: a reminder postcard that includes areas for kids to color in, so parents have to keep it on their fridge; a reminder postcard that hides the test you need behind a scratch-off stripe. You need a ========= because that condition affects 1 out of 6 adults. This talk is the one that I came here for. Lesson: we care about things we put even a little work into, so don’t try to make everything be no work at all.
Aatish Salvi: Our public tax and financial policies favor the rich and hate the poor. That’s bad. We should change it. Numbers to back it up and horrify decent people, but I don’t think most people respond to numbers. Lesson: poor people wouldn’t all be so poor if we didn’t put so much work into keeping them poor.
Wig Zamore: Air pollution next to highways is extremely bad for health, but nobody regulates placing housing right next to a highway. Living, working, biking, walking, any activity next to a highway (or next to diesel rail) is very bad for asthma, heart damage, and heart attacks, and many other biological systems. Lesson: don’t live here.
Monica Poole: Please stop screaming into your fucking microphone! Oh, thank God, she found her inside voice. She’s actually a compelling and passionate speaker about Occupy Boston, self-empowerment, community building, horizontal democracy, open source democracy, collaborative creation when the collaborators keep changing. Best line: “No, Occupy Boston didn’t have a list of demands. By the way, neither does TED.” Lesson: we are nowhere near being the great democracy we pretend to be.
Seth Itzkan: Different livestock management practices can actually make livestock really good for land rather than really bad for land. Very hopeful. Lesson: keep your mind open.
Chris Templeman: In the future, every object in your home could be a work of art. Community-supported manufacturing, allowing us to shift our expenditures from tooling to materials, design, and production labor. Interesting resonance with the “less stuff” talk. I wish he seemed to be aware of kickstarter and similar methods for doing precisely community-supported manufacturing (and a little more aware of the lack of feedback in CSA). He really went off the rails (in a familiar and comfortable way) when he claimed that by avoiding the tooling costs for plastics manufacturing we could keep our total costs the same and pay designers and workers much more. We could, just like we could do that every time a technological advance reduces our manufacturing costs. But we don’t, and we won’t. On the other hand, he’s exactly right when he points out that people are willing to pay quite a lot more for local high-quality food, and that we can expand that model to other arenas. Lesson: support kickstarter.
Lis Pardi: Libraries have lots of interesting future directions. Rent an expert. Borrow a cake pan. Tools, car seats, pets. Maybe buildings aren’t necessary, move librarians out into the community. Librarians could be in coffee shops, maker spaces, coworking spaces, survivalist bunkers. Deconstruct the concepts of library and librarian. Really, librarians could be useful, if only you would use them! Closing line: “Thank you, and good luck with the zombies.” Lesson: libraries in other places are doing much more interesting things than our local library is.
Emperor Norton Band: Seen them too often, and running late. Time to go home.
Posted by
Michael
at
10:43 AM
1 comments
Wednesday, February 29, 2012
A little honesty would go a long way
I just received another solicitation for prize donations from a popular email list in my field that runs a fund drive every year:
“In years past, many of our supporting publishers have contributed prizes or incentives that are given to the winners of our games and challenges. This has proven to be a great way to increase donations and provide publicity for publishers. All supporting publishers are recognized by name on all Fund Drive emails, and we provide a special acknowledgment to those publishers who contribute donations as well as prizes.”
They send out over 100 Fund Drive emails to more than 20,000 subscribers, so this sounds like it could be great exposure. They also have an extensive website where they list donors, which could be even more exposure.
Sadly, it’s just not true. We give them books every year to use as prizes. Last year we gave them over 30 free books, with a retail value of over $800. We were mentioned in just 2 emails late in the fund drive, after everyone has stopped reading the messages. They don’t mention publishers in the list of donors, and they no longer show a list of prizes donated anywhere on their website.
It certainly isn’t publicity for us if they fail to publicize the donations. And it’s offensive to once again be promised specific publicity that they have no intention of providing.
We’ve supported this email list for over 15 years. We used to process credit cards for their fund drives. We advertised their services to our customers before they had a website. We give them money every year so we can post a few book announcements, even though those announcements no longer result in any obvious sales boost for us.
In mid-December, they told us that they wanted us to pay them even more money to post book announcements in the future. When I pointed out that we were already paying far more per announcement than the large publishers, their only response was that some university press had stupidly paid them a huge amount of money for a single announcement. When I asked whether our prize donations were worth anything to them, in the hopes of reaching a mutually beneficial arrangement rather than one that only benefits them, they stopped responding.
Coming just after a long blog post from a close friend where he repeatedly referred to publishers as evil, I start to wonder some days why I engage in my chosen profession. I’m apparently losing a propaganda war that I have no interest in participating in.
Posted by
Michael
at
12:38 PM
2
comments
Friday, February 24, 2012
Tuesday, February 21, 2012
Monday, February 20, 2012
Ford recall policies
I’ve never really had a problem with car recalls before Ford. My 2000 Ford Focus, however, has had around a dozen different safety recalls. Each one is a scheduling hassle, plus time to take the car to the dealer and get a ride home, and then a ride and time to pick the car back up. It would be bad enough if that were all.
Two recalls ago, the Ford dealer’s mechanic drove my car into a light pole in their parking lot. And lied about it.
One recall ago, the Ford dealer’s mechanic forgot to put the fuel evap line back in place, rigged it temporarily with a couple of zip ties, and it’s now costing me hundreds of dollars to fix.
And on the current recall, the Ford dealer claims there is no recall. The NHTSA-ordered recall 02V288000 (Ford’s recall number is 02S42) is for a battery cable that short-circuits, melts the insulation of nearby wires, melts the plastic case around the battery, and then starts a fire in the engine compartment. My engine compartment. I haven’t had a fire yet, but I’ve had all the other problems. Hard starts, check engine lights, dead batteries, melted insulation, melted plastic. Yet Ford claims that the recall never happened. When pressed, Ford says that the recall happened, but my car’s VIN wasn’t included in the recall. And since my VIN wasn’t included in the recall, there’s nothing they can do. Oddly, I get the same exact response pattern from two separate Ford dealers (Sentry Ford and Stoneham Ford): first, the recall never happened; second, my VIN wasn’t included in the recall. And I get the same exact response pattern from Ford’s warranty center, and from Ford’s customer relationship center. Though one person in Ford’s warranty center also (falsely) tells me that the reason my VIN wasn’t included in the recall is that the recall only applied to cars made in a different factory than the one that made my car.
Until I point out that I have the letter from Ford about this recall specifically for my VIN. And then, like magic, the recall did happen and my car’s VIN was included. But a dealer (Otis Ford) told Ford that they did some repair to this car related to this recall back in 2003, so a supervisor in Ford’s customer relationship center says that Ford’s policy in those circumstances is to tell the customer that their VIN was not included in the recall.
In other words, Ford lies to their customers. By policy.
I think Ford shouldn’t lie to their customers. Especially not as a policy, and certainly not about safety recalls that involve potential engine compartment fires.
It does explain why a lot of Ford Focus owners have filed formal complaints with NHTSA about this recall. Some say that Ford attempted to repair their car, but that the repair didn’t solve the problem. Many say that Ford told them their VIN wasn’t included in the recall, even though they had the precise problems described in the recall notice. And a really disturbing number of those complaints involved engine compartment fires caused by Ford’s defective battery cable.
When I pointed this out to Ford’s customer relationship center, the first Ford representative told me to sue Ford Motor Company, and the supervisor told me to sue Otis Ford (the dealership). That sort of helpful advice must be why the second person got promoted to supervisor.
And when I told Ford that I was having the car repaired by an independent repair shop that was willing to do the work that Ford’s dealers wouldn’t do to reduce the risk of an engine compartment fire, Ford told me in the strongest possible terms that they wouldn’t stand behind the work of the independent repair shop. Which I found odd, since they had just finished telling me that they wouldn’t stand behind the work of their own dealers, or their own recall notice, or their own parts.
By the way, does anyone want to buy a Ford Focus? It smells like marshmallows. And cynicism.
Posted by
Michael
at
11:49 AM
0
comments
Thursday, February 16, 2012
Friday, February 10, 2012
LPFail
Some thief paid for an Xbox using my credit card and thinks that they are going to pick it up at a Walmart in Illinois. That person is presumably going to walk into the store today or tomorrow, go to the customer service counter, present their order information for their fraudulent order, and wait for the Xbox to be retrieved from the back room.
In a sane world, the Walmart staff would keep track of the fact that this order is fraudulent, and when the thief walks into their store they would smile, walk into the back, and call the police. They would also keep the security footage, and make that available to the police. If they want to avoid trouble in the store, they could call the police, give the thief an excuse about the order being delayed a day, and have the police arrest the thief outside the store. Or the police could follow the thief and see if they learn anything more.
Instead, Walmart has given my name, email address, phone number, home address, and credit card details to the thief. And since they cancelled the order, they feel they are done. American Express will replace my card, but won’t collect any information to give to law enforcement about the attempted theft.
I called the Walmart store, told them that I was calling about a thief who was going to try to steal something from their store, and asked to speak to their store manager or head of security. They kept me on hold for a while and then disconnected me.
I called Walmart.com and told them that my account had a security breach. They refused to delete my credit card information, remove or change any of my personal information, or shut down my account. They refused to contact their own internal tech support or security department. And when I asked for a supervisor, they hung up on me.
I’m not sure that I like Walmart any better than the thief.
Posted by
Michael
at
7:44 PM
0
comments
Thursday, February 2, 2012
Content, structure, and design
A simple website has content, structure, and design. Those elements relate to each other, but you’ll have a much easier time managing a website if you treat those elements separately.
The content is the words and images on your website. The content is why people come to a particular page. It’s what Google indexes, and it’s what people search for. Good content (interesting, funny, current, informative, accurate) satisfies users. Without good content, there’s no reason to have a website.
The structure is the way the content is organized on your website. The structure is how you organize content onto individual pages and how you link those pages together. Good structure allows users who are already on your website to find more information on your website without resorting to a search. Without good structure, your website is at best an arbitrary bunch of pages and at worst a confusing or infuriating morass.
The design is how the content and structure looks. The design includes the page layout, font choices, color scheme, and navigation elements. Good design allows users to focus on the content and structure. Without good design, your website may prevent users from finding or using the content that is actually there.
The most common reasons that people want to update a simple website are because the content is stale or because the design is stale. It’s vitally important to figure out which is the primary problem that you are trying to solve. Updating the content is usually easy, no matter what the design looks like. Just find the old content and replace it with the new content (or add new content). Updating the design can be easy or hard, depending on how the site was created. CSS is useful because it allows you to have one file—a style sheet—that contains the design for many pages, so you can update the design across all of those pages just by changing the single style sheet.
Even though updating the content is easy as an isolated task, it is infinitely more difficult to do on an ongoing basis. You have to have a true continuing commitment to updating the content, with an identified person who is responsible for doing so. If the person with the technical knowledge to update your website is not the person with the content knowledge, both people have to work well together to make sure that the content is updated. A terrible and common mistake is to put the designer in charge of updating the content, which cannot succeed unless the designer has the appropriate content knowledge.
A second common mistake is to think that updating the design will somehow update the content. If your content is stale, putting resources into a new design is a distraction. A new design may be entertaining, and it may initially fool users into thinking that the content is fresh, but it cannot solve a content problem.
You can avoid both of these mistakes by clearly separating the work of updating the content from the work of updating the design. When your resources are limited, this clear separation of work becomes even more important so you can prioritize appropriately.
The content on your website can be divided into two categories: durable content and time-sensitive content. Durable content, such as your contact information or your core mission and services, does not need to be updated regularly. If you don’t have the time, resources, inclination, or commitment to update your content regularly, then limit your website to durable content.
Right now I’m watching an organization ignore all of this advice. They realized that they no longer have anyone who is willing to update any of the time-sensitive content on their website or associated blogs (or even to send a list of updates to someone with the technical knowledge to make the updates). The correct solution is a combination of: (1) finding someone who is willing to update the content, and (2) removing or archiving time-sensitive content that will not be updated. Instead, they are investing scarce resources into redesigning the website (badly, as it happens), removing much of the durable content in the process and leaving primarily time-sensitive content. At the end of this process, they will still have no plan for updating the time-sensitive content, and they will have lost most of the embedded value in the established website. It’s painful to see, but it’s very hard to look away.
Posted by
Michael
at
10:07 PM
0
comments
Labels: design
