January 13, 2007
Sometimes being a web developer actually means being a skivvy.
I’m the unlucky [insert expletive] who has to go through a 100+ page word document of copy changes, and make these changes to pages in the website.
You’d think account executives would realise that a big word document is not an effective way to communicate copy changes, and use something more effective (even a spreadsheet is better). At least tell us developers the damn filenames of the files you’re referring to rather than expecting us to just know by looking at the text.
The problem lies with the fact that agencies, clients, whoever think that developers actually care about the text we’re copying and pasting from your stupid word document. Let’s be clear: we don’t give a crap. Could be pasting latin text for all we care.
What is a web developer anyway?
A person who undertakes programming tasks for a Web site. This can include producing e-commerce applications or implementing a site search tool, for example. Occasionally used interchangeably with ‘Web designer’.
It’s a person who undertakes programming tasks for a website. We enjoy writing code. Not copying your stupid text from your word document and putting it into web pages. If you’re going to give us mundane work, at least make it clear what needs doing so we can get back to the exciting stuff quicker.
Ideally, we’d be using a CMS system, though this site was created quickly and evolved. Having said that, our agency created several websites for this client using our custom CMS product, and the account executives are way to stupid to use it. If only they would learn HTML. Or resign. Assholes.
December 16, 2006
Although the account executives are the biggest idiots you’ll work with most of the time, once in a while the people causing grief can be within the agency itself.
This is typically with freelancers. Like many companies, our agency has an internal test which candidates are required to complete before we consider interviewing them. Ironically, in excess of 50% of candidates who submit their CVs fail at this stage.
It’s not like it’s a hard test, and we even allow the candidate to choose which areas they want to be tested on, though of course, this will have to match with their CV. Anyone applying for a developer role and refusing to do the web development and database tests would not bode well and reflect negatively on them.
To be honest, even a resourceful person with two browser windows open could probably Google some of the tricky questions and answer with vaguely correct answers. A finance dude at our office once done this for fun and achieved surprisingly good marks.
So, no excuse to get the test completely wrong then. But you’d be surprised at how many crap programmers are out there, writing frikkin appaling code and putting the rest of us to shame. These people shouldn’t be allowed to work in software development.
Just over a year ago, I had the opportunity of working with such developer. He’d come from a background contracting at a large management consultancy, but scored reasonably well in the test and interview.
We found it amusing when he came to our small agency for a three week contract to cover another developer being away during a development drive to launch on time, and the first question that came out his mouth was to ask how much annual leave he gets. It’s a frikkin three week contract, dumbass. The second question? Who’s the fire warden on this floor? Everyone had a good laugh at that one.
But the funniest part, and also the saddest, was his code. After three weeks on the project, the amount of usable work he done amounted to only a few hours. The rest was built using pages of inline functions, completely ignoring all code in the business and data layers. On his last day, he said call me if you need anything else done. Dumbstruck at his comment, all I managed to splutter was “I don’t think that will be necessary”.
In an interesting twist of fate, a friend who is also a recruitment consultant came across this developer’s CV and noticed that he recently completed a contract at this agency. A short IM conversation later sealed his fate and ensured that he’d have to look to other recruitment consultants with find unsuspecting clients to hire this stupid fellow.
Although I wish he ran off (at least we wouldn’t have to pay him then), this developer stuck around and done his time. Recently heard about a story at a web agency where a developer stuck around for a week, though when other senior developers realised he done nothing and held a meeting in another room, he left a note and left the building.
Hah! Damn right you foched up. Why don’t you do us all a favour and give up programming. Go do a job where you can’t foch up, like working in a food store or something. Make the world a better place, have the common sense to realise you can’t cut code, and stop wasting your time and our money.
And damn right you won’t bill us. Hell, you should pay us for wasting our frikkin time and making our other competent developers work late on a Friday night to finish the work you were meant to do and pick up the pieces.
Do not pass Go. Do not collect $200. And don’t hit the door on your way out, dumbass.
August 18, 2006
Ever wondered what a meeting between a big agency and a client is like? This isn’t too far off the mark.
Client who was promoted to his level of incompetency some time ago and has a love-blame relationship with the agency: We need to do something new, something fresh – why aren’t we on myspace or dogster? Why aren’t people visiting our site every day for the fun and entertainment?
[Frazzled account person, thinking to herself, and worrying that she might accidentally say something true out loud: Gee, could that be because you have wildly unrealistic expectations and no consumer anywhere goes to ANY corporate Web site every day to do anything???]
Hilarious. Get the full dose at Advergirl.
June 15, 2006
Although my career to date has an agency focus, it’s by no means the only thing I’ve done, with brief stints in both a large global management consultancy and a small property company.
Despite these experiences, I’ve always found myself drifting back to agency work. In some ways, web development for the marketing sector isn’t as intense as developer roles elsewhere.
As Mark says, compared to the process at a global management consultancy, we’ve got it easy (though I don’t entirely agree with his comment, but that’s a post for another day).
There are things I love about working in a web agency (which tends to be quite small), as oposed to a 10,000+ employee global management consultancy.
A close-knit team. Everyone has one or two key areas of expertise. There’s a lot of respect within the organisation. Flat hierarchy and little or no politics. The power to innovate and bring about change.
Working in a web agency isn’t so bad. Even with dumb clients.
June 13, 2006
I’ve often wondered about a colleague notorious for their 3am e-mails. The truth only hit me recently.
“I’ve been doing email for hours.. so tired.. better get some sleep..” — one hour later — (awaking from a nightmare about a dumbass client) “aaaargh! nooooo! not more copy changes!” — 15 minutes later, unable to get back to sleep for fear of more nightmares— “let me do more email..”
This predicament is not unusual for project managers, many of whom have to endure the mental toture almost daily of dealing with stupid people. It takes a lot of patience to deal with such behaviour on a regular basis, and requires a completely different personality from developers (who tend to be ‘engineer’ type personalities as opposed to ‘sales’ type personalities).
A business where developers are client facing is almost always going to be problematic, as project managers play an important role, in that they buffer the demands of crazy clients and aggravated developers. It’s juggling. With fire. Most developers – including myself – don’t deal very well with such activity.
That’s why good project managers deserve respect from developers.
June 9, 2006
Everyone loves superheroes. They protect the good guys, fight the bad guys, and make the world a better place to live. As Pardesi Blogger says:
…our famous hero struts his stuff in tights, he faces difficulties everyday in his life, and yet he always comes out doing the *right* thing …
…Clark Kent struggles for half his life balancing his secret identity with the people he loves, facing a reality where he is constantly being tormented by villains and foes. Yet, throughout, we see him living his life trying to do good etc etc.
Remind you of anyone? Although we don’t wear tights (well, most of us), Clark Kent sounds a lot like a developer. Facing difficulties in day-to-day life dealing with badly thought out projects, struggling to keep our online identities and feelings a secret and constantly being tormented by our villains and foes, the bastard account executives.
It’s not a myth. Developers are superheroes. Except maybe those whose code is featured on The Daily WTF. Those developers shouldn’t be allowed near computers.
It’s fortunate that most developers are usually good people, because they have the potential to cause a lot of damage.
Once, a fellow developer working on the website of a (now defunct) e-commerce website showed me how the passwords for thousands of users in the database were stored in plain text, and then proceeded to randomly pick hotmail accounts and log into them using the same password. That’s why you should never use the same password for your email accounts as everything else.
Or the other e-commerce website stating it didn’t store credit card numbers, but was storing not just the credit card number and expiry date, but the CVV2 number too, as well as the cardholder’s address. My contacts in the field tell me the company has since changed this, and are now using a third-party payment provider, but I remain sceptical.
There are countless other stories. Remember what Bill Gates said, “Be nice to nerds, chances are you’ll end up working for one”. The part he forgot to add? Or they’ll be a web developer with access to the database of some e-commerce website you shopped at, and the opportunity to wreck your life.
But, those school bullies need not worry. Not only are developers generally good people, we also follow the superheroes book of ethics, taking special note of Uncle Ben’s advice to Peter Parker:
With great power comes great responsibility.
Sometimes, it’s nice to have a bit of fun though. Some years ago, when working for an agency, a young brash account executive was the repeated cause of frustration, and we decided to have a joke at his expense, with a quick script change and slight modification of a CSS file.
Logging into the admin control panel, he was presented with a completely horrid hot pink colour scheme, with dashes of yellow, and purple. Frantic with worry, he called us up begging us to help him out. We kept the poor idiot hanging for half an hour, before silently changing things back. He thought he was going crazy.
The saddest part is that all account excutives are that stupid.
June 7, 2006
It’s hard dealing with clients. By definition, they are stupid, arrogant, stubborn, clueless and have an IQ in negative numbers.
One of the agencies we deal with has a large corporate client whose homepage now looks like a cheap porn site or a dumbass kid’s myspace profile it has so many flashing animations. We tried to explain to them that having four simultaneous animating elements on a page wasn’t a good idea, but they didn’t want to know.
Can’t remember what their exact response was, but it was something like this…
“I need more pesshht peesshht chuttt chutt papapapa on this animation”
How do you argue with that? You don’t. Give them more pesshht peesshht chuttt chutt papapapa dammit. Haven’t you heard the client is always right?
Or what do you say when they say things like “Whatever you do, don’t put our phone number on the contact page”. Umm, it’s a contact page.
For more client stupidness, check out Clientcopia. It has a great selection.
June 6, 2006
One of the scariest things I’ve found in my web development career to date is how little marketing agencies selling web work actually know about the web. One of the most recent amusements was when we were supplied some designs where buttons didn’t look at all like buttons, posing some usability issues.
When this was pointed out to the account executive, they looked up with a blank look on her face, and replied “Can you send us some examples of buttons then?”. Considering that this is someone who is heavily involved in dealing with web work on a day-to-basis and forms part of a team selling web work to clients, making such a dumb statement rings alarm bells. If you’re selling web work, you should know what a button is, dumbass.
The problem is, in the land of the blind, the one-eyed man is king. Most of these large corporations have people equally stupid in their online marketing teams, so when they deal with incompetent agencies, they don’t realise that they people they are talking to aren’t giving them correct information. However, as they have so little understanding of the web and the marketing agency are master blaggers, the client awards the project to them without realising the implications of their decision. The problem is further compounded when the agency is unable to say no to the client when they make unrealistic or stupid demands, and unable to offer the client any meaningful advice due to lack of knowledge.
For example, in early 2000, I was freelancing for a small web agency, doing work for a larger marketing agency whose experience was primarily in offline media. They had a strong relationship with a massive brand, so when the client wanted to revamp their website, they turned to their account executive in this large marketing agency to get the job done.
The client also had some ideas on what they wanted on the homepage of the website – a monsterous 1.5mb flash animation, which was a digitised clip of one of their video promotions. Not understanding the implications of this, such as most people were still on 56K modems and the recommended maximum page size was 60K, the marketing agency agreed to their clients demand without a second thought, and then promptly handed this onto us with a note to get it done as soon as possible.
Despite various phone conversations and some foul language being thrown about the office in disgust at such a stupid decision, we were ultimately forced to go ahead with this and built the monsterous atrocity. When an account executive agrees to stupid ideas their clients throw at them, it’s virtually impossible to get them to go back, as they don’t want to look like idiots, even if it means delivering a half-assed solution.
When you’re an experienced web developer, the hardest thing to do is shut up and do what you’re told, but sadly, there’s often no alternative. You can only shout upon deaf ears or try to reason with a fool so many times, until your voice goes or your patience evaporates.
May 31, 2006
Part of the specification of a system we built recently was to email all global administrators whenever a user account was locked out, password reset, etc. Not the smartest idea, but the client insisted that they needed to be in on all this communication, and that it was of paramount important, so it was built.
A few months on, and one of the dumb f*ck head honchos decides he doesn’t want to receive these emails anymore and keeps moaning to the agency, who moan to us – Can’t you just code it so that he doesn’t get included in those emails? F*k no, we can’t.
There’s only a couple of emails sent out every week, and I doubt it’s clogging up his inbox. So wtf is all the fuss. Prat.
May 30, 2006
Too many marketing agencies think it’s okay to treat digital agencies simply as resources to boss around instead of asking for advice and drawing on their technical experience to do a better job and offer their clients better solutions.
What they don’t realise, is that by treating the developers like crap, they not only demotivate the team, but lose the right to ask favours, and lose the right to expect developers to do anything to help them and further their cause.
We deal with one such dumb f*k on a daily basis, who is constantly asking dumb questions, and making pathetic demands. If you ask us to do a job which we have told you is 6 hours work, don’t call us every 30 mins to ask for a status update dumbass.
For example, we get a shit design from the marketing agency (who are predominantly into print design, and don’t really get how web design is different). Rather than ask our advice, they go ahead and keep making stupid design decisions. So, we go ahead and build the rubbish they feed us, only to get comments like “Why aren’t those two boxes squared up?” – because the content inside is content controlled and you’ve put different amounts of content in each region f*cker! hahahahahhaha.
Sure, we probably could put some nice features in like character restrictions, etc. Modify the CSS to make it match their crap exactly. But, why the hell should we? It’s hard to give a job 100% when the people running the show clearly don’t know what they’re talking about, and refuse to consult with people who do.
Perhaps not an ideal analogy, given the number of rogue mechanics in this country, but generally speaking, if you go to a mechanic and ask him to fix your car, let him do his job.