How to demoralize your front-end developers « Two Banjos At Once: The Blog

Two Banjos At Once: The Blog

Living with standards compliance

How to demoralize your front-end developers

October 2, 2009

Stop failing at this apparently necessary chore; I’m here to help.  I can verify that all the following techniques have worked on for me.

How to Demoralize Your Front-end Developers

  1. Constantly change requirements. It’s, what, the day before the scheduled launch?  And the product doesn’t include that absolutely requisite feature you didn’t think to require until now?  Well, shoot, just demand it!  And make drastic changes to the visual and interaction design as well–where’s the glory in completion?
  2. Constantly change the visual design. You took that one-day course in CSS and remember only that it was a way you could change all of a site’s visual elements from one file.  Okay, then, let’s start by making all the blue things red, and all the red things green–but only on Tuesday–wait, change them back again, make the old red things red again–and oh, all the gray things white and the white things gray, and the grayish-white things brown, on alternate weekdays.  And all the wide things “smaller” and the narrow things “a little bigger” and the tall things “a smidge shorter” and… just marvel  how enthusiastic your front-end dev grows.
  3. Give them a lousy setup. Cram your developers into a spot at an unergonomic table in between the gal who has the obnoxious sound themes enabled on her workstation and the guy who spends his entire work day shouting into a speaker phone. Don’t let your devs use their preferred operating systems or software–point out that you’ve generously provided work computers exactly like your own, with that reliable ten-year-old OS and the proprietary groupware that cost you a bundle.
  4. Decide midway that you need pixel-perfection in IE 6 after all. So you visited your hermit, anti-consumerist brother-in-law living in a shanty with a hand-me-down Gateway 2000 accessing the Web over intermittent dial-up, and you looked like a putz because your beta site didn’t render perfectly in Internet Explorer 6.  Well, crack the whip so he can enjoy those rounded corners, PNGs with alpha transparency, and painstakingly mitered grid layouts.
  5. Critique the browser rendering against one in a different medium. Different media, you say?  Hardware?  Pshaw!  Do as I’ve actually witnessed:  hold a paper print-out of the intended design up to the monitor, and compare the rendered page unfavorably to the PDF print-out.  Remark on the differences in proportion and color.  Watch your devs writhe in either agony or amusement at your request to make the two formats identical.
  6. Assign visual design tasks to your developers. Get rid of that pesky professional, and go with a leaner team equipped with mere adequacy in Web design.  Start with vague instructions to your front-end devs (“This area of the page needs to really say ‘breathy,’ but not ‘vaporous’”), and end with your looming over them, jabbing at the display of a competitor’s site on a monitor, and shouting, “See? See?!  Like this–only different!”
  7. Pit your developers against each other. Break up that predictable day with a bout of office politics as bloody as any combat in the Colosseum!  Let one developer bully another, favor the least productive developer over the others, and disclose important project details only to the dev most likely to hoard the information.  When one dev leaves at 6pm to tend to the rest of his life, assign all his duties to the other one still in the office. Whatever you do, don’t let these people end up liking each other.
  8. Constantly interrupt with phone calls, e-mails, IMs, or in-person meetings. You know, if you give your developers the chance to concentrate, to get into the flow of working, there’s no end of disaster which could happen:  they might  finish the tasks you’ve assigned to them, or write bug-free scripts, or finish a work day with a sense of accomplishment.  Then you’d all miss an important feature of the Development Drama:  the climactic battle in which each side slays the other in murderous frenzy.
  9. Ridicule their professional opinions. Don’t listen to the nay-sayers when you describe that pop-up with autoplay Flash, animated GIFs, and blinking text you’re confident will add loads of appeal to the application.  Show them your teenaged son’s MySpace page and pointedly ask why they can’t make something like that if he can.
  10. Don’t use a bug tracking system. Sheesh, you already send all those e-mails.  Why repeat yourself in some persnickety little data entry form with those dropdown things which force you to prioritize the issue?  Just repeat: everything’s critical and of highest priority.  See, easy to remember.

Hmmm, something’s missing.  What have I left out?

4 Comments

  1. How about pay way below value because you looked at Craiglist and it looks like you can get away with it?

    Comment by Lise — October 2, 2009 @ 3:24 pm

  2. @Lise–good point. Another way to determine the below-market rate you’re offering is to query a bunch of obscure offshore development firms with short or nonexistent client lists.

    Comment by mejarc — October 2, 2009 @ 4:32 pm

  3. insist on round corners and drop downs over flash in every browser

    Comment by hrvojeb — October 16, 2009 @ 2:54 am

  4. @Hrvojeb–oh, thank you for the reminder! Yes–you must have challenging z-index situations, or else your front-end devs will retain full heads of hair.

    Comment by mejarc — October 16, 2009 @ 11:32 am

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.

Yes, I moderate comments.

Powered by WordPress

Action Against Hunger ISO Social Media & Online Marketing Intern

Like Action Against Hunger itself, the External Relations Department is constantly growing and changing to meet the new and expanding needs of the organization. Responsible for all private fundraising, press communications, corporate partnerships, social media, and major events, the External Relations Department offers a rich, fast-paced team environment with lots of opportunity to learn about the workings of a large, international humanitarian aid organization.

Essential Functions and Objectives:
The Social Media & Online Marketing Intern will work on projects designed to promote Action Against Hunger’s humanitarian work through various social media websites such as Facebook, Twitter, and YouTube. The Intern will also be the point of contact with bloggers that have offered to support the organization’s efforts. Additionally, the Intern will also work to develop and expand Action Against Hunger’s presence on various social media websites.
Tasks and Responsibilities May Include
• Updating & maintaining the current profiles and accounts on social media websites such as Facebook, Twitter & YouTube
• Developing and expanding the organization’s online presence
• Communicating with bloggers that have offered to occasionally write about the organization
• Tracking mentions of the organization on all of these social media websites and blogs
• Helping other members of the department (as needed) with the preparation of upcoming events

Readability - An Arc90 Lab Experiment

Compelling Content Worth Reading

One morning, when Gregor Samsa woke from troubled dreams, he found himself transformed in his bed into a horrible vermin. He lay on his armour-like back, and if he lifted his head a little he could see his brown belly, slightly domed and divided by arches into stiff sections.

The bedding was hardly able to cover it and seemed ready to slide off any moment. His many legs, pitifully thin compared with the size of the rest of him, waved about helplessly as he looked. "What's happened to me? " he thought. It wasn't a dream.

His room, a proper human room although a little too small, lay peacefully between its four familiar walls. A collection of textile samples lay spread out on the table - Samsa was a travelling salesman - and above it there hung a picture that he had recently cut out of an illustrated magazine and housed in a nice, gilded frame.

It showed a lady fitted out with a fur hat and fur boa who sat upright, raising a heavy fur muff that covered the whole of her lower arm towards the viewer. Gregor then turned to look out the window at the dull weather. Drops of rain could be heard hitting the pane, which made him feel quite sad.

"How about if I sleep a little bit longer and forget all this nonsense", he thought, but that was something he was unable to do because he was used to sleeping on his right, and in his present state couldn't get into that position. However hard he threw himself onto his right, he always rolled back to where he was.

He must have tried it a hundred times, shut his eyes so that he wouldn't have to look at the floundering legs, and only stopped when he began to feel a mild, dull pain there that he had never felt before. "Oh, God", he thought, "what a strenuous career it is that I've chosen! Travelling day in and day out. Doing business like this takes much more effort than doing your own business at home, and on top of that there's the curse of travelling, worries about making train connections, bad and irregular food, contact with different people all the time so that you can never get to know anyone or become friendly with them. It can all go to Hell! " He felt a slight itch

Read stuff faster online.

Turn Camino address bar into custom quick search

This is a very short tutorial explaining how you can turn the address bar of popular Mac OS X web browser Camino into a quick search bar. I know there are widgets for searching, but I'm not comfortable with continually running such widgets on my Mac. So, I decided to find an alternative...

I find myself heading over to Dictionary.com quite a bit - I need to stop talking to people who use big words. I soon got tired of typing the URL out each time i decided to visit, so I looked for an alternative. Unfortunately, Camino doesn't allow you to customize the built-in address bar search... it comes as a Google searcher and it stays as a Google searcher. Here's my solution (and in this example I will be using Dictionary.com, but anything can be in its place):

  1. Figure out the URL pattern of the site you want to search. This can be easily done by simply conducting a couple of searches and noting the similarities. With Dictionary.com, it is quite obvious. Your search results are always in this form: http://www.dictionary.com/browse/.
  2. Configure Camino. Like Firefox, to configure Camino, type about:config into your address bar. If this is your first time, it may alert you... don't worry, we're not going to kill anything.
  3. Filter the fields. You'll see a lot of fields and values which we don't need to worry about. Filter your results by typing "keyword" into the filter box. This will narrow the list down to two items.
  4. Plug in the new values. In the keyword.URL field, you will enter in the observed search pattern. In this example, the value would be "http://www.dictionary.com/browse/". Simply double click the field and type in the new value. Now you'll actually have to enable the keyword searcher. To do this, double click the keyword.enabled field to set it to true.
  5. Restart Camino. When you return - test it out! Just type a word into the address bar and hit enter, you should be taken to its result on Dictionary.com.
  6. Customize it. I know not everybody will be wanting to search a dictionary. You can even customize it to search Newsvine... whatever! Unfortunately, you can only have one quick search at a time. What I would like to do is have the ability to type "d " for searching Dictionary.com or "n " for searching Newsvine, as some other browsers do. Until then, this is the next best substitute!
  7. Currently tested (and working) on versions:

    • 1.1b
    • 1.0.3

Just as in Firefox.

Dolor Sit Amet

iTunes U: mobile learning for the next generation #mac #education #itunes

"Teachers are using iLife and iWork applications on the Mac to create customized educational materials, such as language lessons that students can listen to on the bus or at home. And with the help of tools like Podcast Producer and Wiki Server — both of which come with Mac OS X Server — IT professionals at your school can help you produce and distribute all kinds of multimedia content on iTunes U or a class wiki. Once your classroom presentations and lectures have been captured and published, students can download them from iTunes. Then they can transfer them to iPod or iPhone and take it all with them. And suddenly, any place — a café, a bus stop — can be a place to learn."

[iPhone] Ego, $2. Nice mini-review via @smokingapples.