TDD Saves Me From Myself

I’ve gotten into TDD at least a bit over the last few months. It has a learning curve, but I’m finding that it sometimes saves me from myself (and saves me time in debugging).

Part of my problem, like a lot of people, is that I sometimes over think things or fail to see something as being multi-purpose.

A perfect example was a code kata I started yesterday. It’s a fairly simple exercise – given a file with a list of numbers, take each number, reverse it, add it to the original number, and check to see if the result is a palindrome. Repeat until the number is a palindrome.

Simple stuff, really, but it’s a nice thought exercise.

It started off well. Decided to tackle the number reversal first. Since we’re dealing with data being snagged from a file, I decide to do the reversal with strings (since the data is already in string format, I can do most of the things required by the problem without having to typecast between string and int).

I name it ReverseNumberAsString since that name says what it does fairly well (it’s not the greatest name, but it’s the first function I’ve written in the solution, and we can refactor later).

Fast forward a bit to my writing a function to test if a number is a palindrome. This is where I start to over think things (and where TDD tells me I’m an idiot).

It’s been a long day and I’m a little fried, so the first solution that comes to mind is to set pointers at the front and end of the string and just walk them toward the center, comparing, until they reach the middle or find something they don’t match.

(Hey, I spent years doing C and C++ code. Give me a break)

I test a negative case first, and the test fails. I’d set the tail pointer to string.Lengtrh instead of string.Length-1 (it happens. I was fried.) I fix it, run the test, and it passes. Yay

Try to test for a positive case and the test fails. I go to look at the code to figure out why and, after a minute or two, I realize that I’m stupid, because I’ve already written the answer somewhere else in the code.

ReverseNumberAsString reverses a number that’s in the form of a string. No it doesn’t. It reverses a string. Period. I’m a dummy.

Rename the function to ReverseString like it should have been from the beginning and use that. Compare forward to backward. If it’s a palindrome, they should be the same thing.

Look at that. It works. Who would have guessed.

Thank you, Nunit, for making me stop and see that I’m being dumb.

Current mood - calm

Current music - Dirty Vegas – A Million Ways

My Take on Professional Codes of Conduct at Conferences

 

Preface: Please keep in mind that I am not trivializing sexual harassment or sexual assault. I have loved people who have been victims of sexual harassment, sexual assault and even rape. I myself have been a victim of sexual harassment and sexual assault.

I am offering an open, honest opinion from someone who has not only the right to an opinion as a person, but a sense of perspective as the victim of and friend of victims of sexual harassment/assault. You are allowed to agree or disagree with me as your conscience so dictates.

 

Recently, there’s been a lot of push to force software development conferences to have a code of conduct.

Honestly, any code of conduct that could be adopted for a professional conference could be limited to “Be a professional” or “Don’t be an ass”. We’re all supposed to be there to learn new things, maybe to meet new people, see old friends, and generally grow as professionals and individuals (male, female, gay, straight, bi, black, white, red, yellow, green, polka dotted and everything in between).

A lot of what sparked off the recent debate was an incident that happened at a regional conference a year or so ago (and I will admit was completely unacceptable. In fact, it was horrifying, honestly).

However, a conference code of conduct wouldn’t have done anything to prevent the incident for a few reasons:

 

1) It only came to light *months* after it happened (if you don’t say anything, nothing can be done by the organizers. I know some of the organizers and you’d be hard pressed to find a better, more caring group of people. If they had known, they would have done what they could.).

2)It happened before the conference even started, and not at the venue (it occurred at a bar at the resort the conference was held).

3) Having a code of conduct doesn't stop people from doing bad things. People stepping in and saying something while it happens or before it has a chance to happen does.

 

Having a Code of Conduct that prohibits unprofessional behavior at a professional venue is the conference version of security theater. The only thing it does is make people “feel” safer (and that’s, honestly, a disservice, because *life* isn’t safe and we need to be aware of that. It lets us better prepare for when things do go wrong – and given enough time, chances are something will happen to all of us).

It’s the equivalent of a store having a sign up that says “Don’t steal stuff or we’ll call the cops.” It should be common sense and, code of conduct or not, most conference staff that I have known will deal with any problems that arise.

 

Is there a solution?

 

Yes, well more or less, but like most real solutions, it’s not easy. The best solution is to be responsible for ourselves, to be decent people, and to look out for each other.

That last item is the big one. So many people now “don’t want to get involved” when they see something bad happening. There are a lot of reasons for this – Sometimes people don’t feel like their stepping in will solve anything. Sometimes they are afraid to say anything. Some of them even think that someone in a position of power should be taking care of it.

I have news for you: You need to swallow your fear and speak up when you see it happening anyway. It’s your duty as a member of society to help each other and that includes stepping in and asking if there’s a problem if something looks fishy.

We’ve become far too isolationist as individuals and have become conditioned to “let someone else deal with it”. That needs to change.

I’m not saying to lynch someone you see doing something questionable. Step in, make sure things are okay and then respond appropriately.

Yes, I’m a fairly large (some may say frightening looking) guy. Yes, I’ve been a victim of harassment and assault. No, I don’t think a Code of Conduct will change anything. Changing ourselves will. The demands for a Code of Conduct are just another cry to make it someone else's problem.

I do my part. If I see something “off”, I see if there is a problem and work to resolve it. I ask that others do the same. It’s the only way things will get better.

 

Current mood: contemplative

Current music: Coldplay – Charlie Brown

 

Happy anniversary

Happy Birthday

The Javascript Drinking Game

 

 

The Javascript Drinking Game

 

1. Procure several bottles of your favorite liquor with a high ABV percentage (it will help the pain go away better).
2. Take a drink every time Javascript does something that a sane programming language does not.

 

 

You know what? Just open the bottle and drink until you pass out. The result is the same and this way you might stay conscious a little longer…

 

Current mood: Tired

Current music: Garbage – Run Baby Run

Cooking Time: Pizzeria Style Garlic and Herb Breadsticks

1 ½c Flour plus extra for dusting

1tsp Dry active yeast
1tsp Salt
¼c Grated Parmesan cheese
1Tbsp Italian Seasoning
1Tbsp Garlic powder
2Tbsp Olive oil plus extra for coating
Hot Water
Grated cheese (Mozzarella, Colby Jack, etc - optional)
 

• Combine dry ingredients except optional grated cheese in a large mixing bowl and mix thoroughly.
• Add 2Tbsp olive oil and enough hot water to make a pliable dough.
• Turn dough out onto floured surface and kneed dough.
• Roll dough into a ball, coat with olive oil and place in bowl covered with a towel for 1 hour so dough can rise to approximately double its original size.
• Preheat oven to 400F
• Punch down dough and roll out to a size of approximately 8”x9” and place on baking sheet, pizza pan, or cast iron skillet
• Brush surface with olive oil, cover with towel and allow to rest in a warm place for 10 minutes
• Cut dough into 8 horizontal slices, while maintaining the loaf’s shape
• Cover dough with grated cheese (if using) and place in oven for 15 minutes or until a toothpick inserted in the bread comes out clean

Your Code Sucks

 

I’ve seen a few people that I know berate people for the quality of their code and say things like they should just go and deliver pizzas.

You aren’t your code. Code is an expression of the skill, mindset, and situation facing the person who wrote it at the moment it’s made. Nothing more. In fact, it may be the chaining together of those factors from several people as the code is maintained.

There may be things about the situation that you don’t know. Maybe the person was under insane time constraints. Maybe they were thrown into a technology they had no experience with. Hell, maybe they were just having a bad day.

You may not like maintaining the code – I know I don’t, but I try not to berate the person doing it because I don’t know what lead there. (If I know the person in question and know that they just don’t care, that’s a different story)

There are a couple of appropriate responses to “your code sucks”.

• Where can I improve?
• Yes, it sucks. So does everyone else’s. I’m working to improve. Are you?

Improvement is the important part.

Yes, my code sucks. It always will, but it gets better every day.

Does yours?

 

Current mood – tired

Current music – 10,000 Maniacs – Candy Everybody Wants

Learning

After a couple of false starts, I started digging into learning ASP.NET MVC a couple of months or so ago.

First, I decided that I also wanted to learn webforms, just in case.

Don’t look at me like that. I learned the error of my ways after my eyes started to bleed and hands began reaching out of the walls for me. Though I’m not sure that was caused exclusively by webforms. That may have been caused in part by my recitation out of a book of really odd Latin poetry that I ran across…

Either way, I stopped trying to learn webforms, so mission accomplished. Now if the really creepy looking guy would stop making faces at me in the mirror when I try to shave, that’d be great. Oh, wait, that’s me. Sorry.

Next, I tried just diving in by starting with Professional ASP.NET MVC by Galloway, Haack, Wilson, and Allen.

This, for me at least, was kind of a mistake. The first couple of chapters were okay, but the first chapter on the topic of Views was full of hand waving and a sense of go screw yourself. It all kind of boiled down to “I’m not going to discuss the code. I’m just going to go off on tangents that you don’t need right now.” (This is a pet peeve of mine)

That’s not to say that the book is bad. It’s actually quite good as long as you have a rough idea of what’s going on (which I didn’t at the time). Otherwise, it got a bit frustrating. I'm going back over the book now, in fact.

I ended up going online to find the music store tutorial that was mentioned in the book and working through that first. That worked a lot better for me, but it could just be that I’m a bit slow. Who knows.

Going on the premise that I learn a lot better by playing with something once I’ve figured out the basics, I decided to rebuild my website with MVC. After all, it was just static pages, so I wouldn’t have to worry much about the M portion of things.

As a result, I got a decent grounding in the use of Controllers and spent a small mountain of time re-arranging the structure of the website to comply with the MVC principles.

Of course, I also got to do some much needed housekeeping, so that’s a plus. It just took loads of time because there were probably 40 or so pages.

In all honesty, most of my frustration was dealing with CSS3 (the site’s last incarnation used CSS2 and a lot of things have changed) and getting all of the settings right (both on my end and on my hosting provider) to get web publishing to work from Visual Studio.

The site isn’t “finished”. I’ll probably always have things that I want to do to it, but it is published. The visual changes are fairly minimal. Mostly, the menu has just moved to the top instead of running down the left side. However, things are a lot different on the back end.

Now I get to move on to more complex stuff.

Current mood: tired

Current music: David Gray – Babylon

I'm Not an Expert

 

I’m not an expert. On anything, really.

Don’t get me wrong. There are things that I’m good at, but I wouldn’t call myself an expert on them.

Part of the reason that I don’t consider myself an expert on anything is that I’ve done so many varied things. I’ve never settled into just one area of development (or anything else).

I’ve had a lot of hobbies, interests and jobs that range from martial arts, to carpentry, blacksmithing, gardening, cooking, and (obviously) software development (among many other things).

That kind of spread isn’t exactly the sort of thing that screams “I’m the greatest person in the world at one thing.” It does, however, lead to being able to look at problems from a lot of different angles and helps you come up with a solution to something you may have never seen before.

I sometimes get asked what my specialty is by people who won’t take “I don’t know” for an answer, and the only thing I can think to say is that I’ve learned to ask questions that get me the answers that I need.

I may not know a thing, but I can generally figure out a way to find the answer.

I suppose that you could say people like me specialize in being generalists, but I think we just suffer from a combination of ADD and having to take on multiple roles. Somehow, it works out, though.

Current mood: thoughtful

Current music: Goo Goo Dolls – Give a Little Bit

Motivation

It’s generally really easy for me to keep going if I’ve already got a bit of momentum, but if things have derailed me and caused me to focus elsewhere, Newton’s First Law decides that it also applies to motivation and proceeds to kick my backside.

Translation – if I stop, it takes real work to get going again.

It’s also fair to say that, for me at least, large tasks are intimidating, but breaking them into smaller chunks makes them more manageable because it lets me just consider the current step and leave subsequent steps for a little later.

Big = difficult. Little = easier. Makes sense, right? Less stuff, less to be overwhelmed by.

Or, to paraphrase my sifu a bit “Concentrate on now right now. Later will come when it is time.”

A few years ago, I found a way to motivate myself when learning something new from a book or video as well as when working on projects. Thankfully it plays into the fact that I’m a big fan of marker boards (I have several in my office to help keep myself organized and to brainstorm) so it doesn’t take any additional expense on my part.

I write the name of the book or video series on the marker board and then put down the chapter or video numbers. As I work through it, I erase the numbers for the chapters that I’ve covered.

 

This does two things:

First, it lets me keep track of where I am. This is especially helpful if I’m doing a video series or a web-based lesson plan.

Second, it lets me see that I have actually been making progress so I don’t get lost in the feeling that I’m never going to get anywhere in what I’m doing (I’m pretty sure that I’m not the only one that has this problem. It’s downright overwhelming to look at how much you have to learn, and every time you learn something, it shows you other things that you need to learn).

Some people will prefer to strike through the numbers or put a check mark next to them after they’ve finished, but I prefer to erase for one very simple reason – it lets me actually SEE the list of things I need to do shrink. If the numbers are still there, the size of the task never visually changes so my brain still says “Hey, there’s still this daunting list of things that we have to do.”

If I erase the numbers, my brain goes “Wow. We’re making progress! Maybe we can do this thing after all.”

Yes, it’s a stupid psychological trick, but in my case it works.

I guess that means it’s not so stupid after all…

 

Current mood: undecided

Current music: Adam and the Ants – Room at the Top

Product Review – Mimo 720S

A couple of weeks ago, I won a Mimo 720S (7” USB touch screen monitor) at the CONDG holiday party.

I’d seen them before online and was never really tempted because it just didn’t seem that useful. I mean, after all, a 7” screen isn’t that large. It’s okay for a tablet, but as a 2^nd or 3^rd monitor?

I’ll admit that I was wrong.

The screen’s a resistive touch screen, but it doesn’t take a lot of pressure to make it work unlike a lot of other resistive screens. That’s not to say that it doesn’t occasionally lose track of the fact that you’re doing a “click and drag”, but nothing’s perfect.

The size of the screen is just about perfect to fit on the desk under my monitor in the space where I usually put a book if I’m using it for reference. Since I have electronic copies of most of my tech books as well as paper copies, the Mimo’s primary purpose for me is as a book display.

Setting the size of the book to 120% in acrobat allows most books to be readable and take up most of the screen and since the Mimo is on an integrated stand, I don’t have to look at a book that’s lying flat like I do with its paper counterpart.

I’m also wondering how it will do as a test screen for mobile app development. Since it rotates 90 degrees, you could emulate either a phone or a tablet.

Honestly, my only complaint is that the screen isn’t a little bit bigger. I think a 10” screen would be just about perfect.

Just be sure to update to the latest drivers and calibrate the touch screen with the Calibrate program before you use it. Otherwise, you’ll be wondering why the mouse moves on your main monitor when you touch the Mimo

GPS - The Angry Wife Edition

I live in a city where I frequently have no idea how to get where I’m going. I used to use MapQuest before I got my GPS several years ago.

It’s a wonderful device, but I refer to it as “The angry little woman in the box” because the voice sounds rather annoyed when it says “recalculating” if you miss your turn or opt for another route. In fact, I think they must have multiple clips for “recalculating”, because she sounds angrier every time she says it, but that could just be my imagination.

It’s like having an irate spouse in the car with you (my girlfriend agrees).

 

 

“Turn left”

I don’t want to turn left. This road is a better option

“Recalculating. In 0.5 miles, turn left”

No, I want to stay on this road. It lets me bypass a lot of nasty intersections and is only 2 minutes slower

“If you don’t listen to me, why do you even take me along?”

I do listen to you, but in this case, I know a better route for this part of the trip

“You don’t love me anymore. I saw you looking at that other GPS in the store”

That’s a model for hiking and geocaching

“She’s a model, is she?? I bet you felt her up too! Damned skinny bitch”

Oh, now you’re just being silly

“I am NOT being silly. You don’t touch me like you used to! I catch you looking at other GPS’es and now you don’t even listen when I tell you to turn left!”

I’m just saying that this time, going straight is a better option.

“That’s it! I’m going to my mother’s! TURN RIGHT!”

 

 

Oct 31

Happy Anniversary

Oct 14

Happy Birthday

Recruiters

The tech job market in Columbus seems to be picking up quite a bit. This is a wonderful thing for a lot of people since we like to be able to pay rent and buy sandwiches.

Unfortunately, it also means an increase in the number of people that call themselves recruiters whose only purpose is to spam as many people as possible in the hope that some company will hire one of them so said “recruiter” can get a commission.

These people are not really recruiters. They’re parasites. Real recruiters are a completely different creature.

If you’re a “recruiter” and are located in an off shored call center, you aren’t really a recruiter. I’ve gotten a few calls of this sort in the last few weeks and they’re driving me up the wall – Broken English, lots of call center noise in the background, and follow up emails that say things like “I enjoyed speaking with you” when all they did was leave a voicemail.

If your “job description” is a page full of bullet points that tell me absolutely NOTHING about the position, you’re doing it wrong. I once got an email from a “recruiter” that had about 20 bullet points worth of “description” and all it really said was “write code, conform to company standards, and you won’t be supervising anyone”.

Don’t tell me that you have something you think I would be “perfect” for without telling me why. This is especially true when the job is for something I’ve never done before. This is the most common kind of resume spammer “recruiter”. Thankfully they also tend to be the least tenacious and easiest to ignore.

If you’re contacting me about a job in Ohio, but you’re located in New York, you’re doing it wrong. You can’t know about the developer community in Columbus, Ohio if you’re located in Rochester, New York. If you’re not in the geographic area that you’re hiring for, you’re probably doing it wrong (there are exceptions, but they’re not that common).

Bad recruiters leer at and hit on my girlfriend while she’s at an after users group meet-up with me (true story, sadly. Karyl almost dumped her drink on the guy).

By contrast, good recruiters generally display the following qualities:

• They work through word of mouth networks in the developer community. Referrals are the source of most of their candidates.
• They will tell you the name of the company that they are trying to put you in touch with to make sure you haven’t already submitted to them since multiple submissions basically kill your chances.
• They take some time to learn what you’re looking for instead of trying to shoehorn you into every position that comes across their desk.
• They take time to help prepare you for the interview. They will give you an idea of what to expect both in terms of interview techniques (if there are any tests, etc) and corporate culture including suggestions of how formal or casual to be in the interview.
• They do not act like a creep and hit on my girlfriend.

Good recruiters are worth their weight in gold. Bad ones only serve to make everyone’s lives difficult. Sadly, the good ones are also about as rare as gold while the bad ones abound.

Current mood: tired

Current music: The Call – Let The Day Begin

Lunch Time

 

Since some of the Devs on my twitter list seem to be in the mood for soups/stews and Bill (@sempf) suggested I place this recipe here, I present to you

Lamb Stew

• 1lb ground lamb or beef
• 6 cups beef broth (I use the beef base from Das Dutchman. It’s inexpensive and takes up much less storage space. It’s available at some area Kroger stores as well as here)
• 1 cup white wine
• 1 package beef stew seasoning
• 1 cup pearled barley
• 8-12 oz package of mushrooms (washed and diced)
• 6-8 carrots, sliced
• 2-6 whole tomatoes (about 1-1.5lb). Diced
• 1-2 medium onions, diced
• 1 can whole kernel corn (optional)
• Red pepper to taste

Brown meat in 5qt or larger pot (I use a 5qt cast iron Dutch oven)

Add remaining ingredients and bring mixture to a boil

Reduce heat, cover and allow mixture to simmer for 2-3 hours, stirring occasionally.

It may be necessary to add water to the soup as evaporation will occur

Makes 1 gallon + of stew.

Ebook Pricing

This started off as a bit of a mini rant on twitter the other day, but I thought it deserved to be fleshed out a bit as well as updated since some other information came to my attention this afternoon.

I love my Nook and take it pretty much everywhere. I consider it a great way to carry not only a book or two to read for pleasure but also a way to carry and access my programming books when I’m not near my bookshelf.

My major complaint is how much the ebooks cost in comparison to their paper counterparts. Sure, they knock a couple of dollars off of the price, but for books that cost $20-40, that’s really not much of a savings.

This isn’t just a whine on my part. Logically, ebooks should be cheaper. Think about it – they require no paper, no shelf space, no transportation costs (other than an internet connection) and can be replicated essentially forever (or at least until a publisher’s claim to the book ends and it reverts to the author)

I’m not complaining that programming and technology books are expensive. Given the amount of work that has to go into them, the limited market, and limited shelf life of most technologies (unless we’re talking about something like the K&R C book), they have to be relatively pricy in order to make a profit. I understand and accept that. We all need to make a living.

What I’m complaining about is the price difference, or rather almost lack of one, between the traditional paper books and the matching ebook. In some cases, as @jbehren pointed out, sometimes the ebook can cost more than the paper one (which is ridiculous unless, perhaps, you are paying to get a copy before the paper book even hits shelves and you just can’t wait).

The question, then, is what is a reasonable price for an ebook as compared to the paper one? Of course, the publishers would claim that their current prices are reasonable, but I disagree. Taking into account the savings caused by the lack of materials and associated costs, I’d say probably about half the price of a paper book.

Books are fairly pricy to write, but most of the cost is in the actual manufacture, shipping and storage. At half the cost of the dead tree edition, there should be enough money to still make a decent profit on the endeavor.

The half price range was sort of my gut feeling for a while, but today it was more or less confirmed by O’Reilly. For people that have an account at oreilly.com, all of their ebooks are buy one, get one free with coupon code (just look in your account under the heading Membersip).

Additionally, they will sell you an electronic copy of most of their books (bundled in multiple formats, not just PDF) for $5 if you register the paper version with them. It only applies to O’Reilly and MS Press titles so I can’t get epub copies of my Pragmatic Programmers books, but it’s a great start. (For the record, I got the PDF version of the Programming Ruby book cheaply when I bought the paper version during the Pragmatic Programmers special a while back, but PDFs don’t always scale well on smaller e-readers so availability in a variety of formats is a great plus).

I cheered when I saw the $5 electronic copy “upgrade” option, because, to me, that’s sort of the sweet spot for that service. I would gladly pay an extra $5 to have lifetime access to an ebook version of programming books that I own. In fact, I spent some time today registering my O’Reilly books so I can buy the epub copies later.

I don’t know if this is a limited time offer or one which they always have, but it is sort of telling as far as book pricing goes. It’s also something well worth taking advantage of.

Current mood: tired

Current music: Smashing Pumpkins – Cherub Rock

Oct 31

Happy Anniversary

Happy Birthday

I love you

 

When To Say No.

A lot of people that I’ve known, including clients and a previous boss, have been under the impression that we as developers (or sysadmins, or whatever else) are to do what the client (internal or external) wants. Period. They think that this is the reason why we are employed. This isn’t really true.

My old boss’s argument was that we were only a cost center and not the ones generating the revenue. This is an extremely short sighted view to take.

Our job, is to give the client what they NEED in order to do their job and for their company (and ours) to make money. There is a very large difference.

One thing we have to ask ourselves on virtually every feature of a program and even on every project is “why?”

Why are we doing this?

Does it fulfill a business need?

Does it make the company money?

Does it save the company money?

Does it make the life of people at the business easier so that they can do one of the above more effectively?

If it doesn’t fill some need, then why are we doing it? Most of the developers that I know don’t want to work on a system that nobody is really going to use, and adding features that make no sense only increases the chance of bugs in the software as well as increases the development time.

For example, say a client commissions a piece of software and one of the features, after all is said and done costs $10,000, will the value that they derive from that feature be greater than the cost? If the answer is no, then why (other than the $10,000 going into your company’s bank account) would you do it? Sure, you can keep your mouth shut and pocket the check, but chances are that the reputation may well catch up with you down the road.

Projects that come in on time and under budget tend to get you more projects. Projects that overrun on the budget and/or time don’t.

The problem is in convincing the client that they don’t need the feature (which I generally call “kitchen sink features” and a lot of people call gold plating). Sometimes the client doesn’t want to let go of a feature because they have a checklist that they want to fulfill for bragging rights/marketing material. Sometimes it’s because they don’t want to let go of *anything* and sometimes there’s some other reason.

If it turns out that you were wrong about them not needing the feature, then drop the argument and build the feature. If, however, you can deliver a better product (less bug prone, easier to maintain, etc) and do it faster without an unneeded feature, then you may want to make a business case for doing exactly that.

I’ll admit that it’s extremely difficult to make a business case against an emotional response (in this case, the desire for more more more), but it can be done.

I had a discussion with Jim Holmes on this topic at Stir Trek back in May and he had an interesting way to take care of the issue. In fact, I approve of it so wholeheartedly that it earns my Sneaky Evil Bastard Award.

He had a client that wanted far more functionality than could be delivered in the time and budget that was allocated to the project and, predictably, the client didn’t want to let go of any functionality, claiming it was all equally important.

Jim’s solution was to target one of the parts he knew they REALLY wanted as being impossible to complete given the resources since everything was equally important. Magically, the client changed their minds and decided that the unimportant functionality wasn’t vital after all, and they were able to finish the project within a reasonable time frame.

It’s funny how that works. =]

Failed projects are a bad thing. So are projects that nobody really uses. Don’t cave in to the pressure. Do the right thing when you can and work to the best of your ability. This isn’t a one-sided deal. Every piece of software involves a partnership between the craftsmen and the owners and that requires give and take from both sides. If you approach it that way, you frequently get better results.

Current Mood: thoughtful

Current Music: Jimmy Eat World – The Middle