Aug 13 2008
Redefining scope creep
[ANYTHING is better. Try WordPress, I think it's great.]
Oooh, WordPress sounds great for our needs.
[network admin sets up WordPress blog. WordPress and FrontPage DO NOT play nice together. Much gnashing of teeth on the part of network admin and myself. Eventually find a work around. After a month.]
Oh, and can we have meaningfull URLs?
[on IIS, it’s a pain in the rear. Another few weeks go by as I look for a solution that actually works, in my copious spare time.]
Can we have various modifications to the base template?
[OK. Grrr. It is not helping that you are using pages instead of posts, you know.]
Oh, and can we have a stats counter?
[sure]
Oh, can we have one that tracks people by country?
[ummm. Sure, but not right now.]
Oh, and fix the header, please.
[low priority, guys. Just live with the fact that both your graphic and header text say the same thing.]
Oh, and some of the pages need to be in the wide format.
[NOW you tell me?]
Oh, and some of our stuff is in Greek.
[muffled scream]
How about more contrast between text and links?
[see above about low priority]
And we need a custom favicon.
[AAAARGH]
And a picture in the sidebar…
[whimper]
4 Responses to “Redefining scope creep”
eye roll. unbelievable…”oops, we just forgot to tell you we use greek <>”. That’s kinda like this week when on Monday a.m. the boss man said, “oh, and those reports you were giving to me in draft form tomorrow afternoon, I need them in final form by 1:00 today for a meeting with the government”…for real? did you just say that because I know the government doesn’t just “pop in” unexpectidly. unfreaking believable.
In other news…I see the whole “coax baby 3 out of the womb” isn’t working ;)
Baby 3.0 is being a good little baby and staying put, so Mommy can finish up some stuff :-)
Good Luck Honey
*comforts* I know how frustrating users can be.