Wednesday, October 06, 2010

I'm #2....

Read this article

I am so #2 - they could have started and finished with #2 in my opinion.

The rest of the points are not bad - but #2 hit the nail on the head!

In my "what are we still doing wrong" talk - I talk about #2 for a long time - the 'business' telling the technologist HOW to do something - not telling them WHAT they need to do. We know how to do things, they know what they need to do - the opposite is not necessarily true...


Blogger Byte64 said....

Oh yes, the world is full of customers who are teaching how to do things.

When that happens to me, i usually reply that if they know already how to do it in such detail, they just need a keyboard, not an Oracle developer.


Wed Oct 06, 05:41:00 PM EDT  

Blogger Noons said....

Ah well, Oracle - and other companies - have spent the last 10 years deriding and disparaging the dba role and claiming it can be replaced by a simple point-and-click process.

I'm not at all surprised business in general has finally learned they know a lot more about software and IT in general than a dba, so they can tell us how to do our tasks.

We reap what we sow.

Wed Oct 06, 07:49:00 PM EDT  

Anonymous Anonymous said....

Ah, where was that article when I desperately needed it? :-D

When I was a full-time developer I used to have a sign hanging in my cubicle :


Pick Any TWO.

Bill S.

Thu Oct 07, 08:23:00 AM EDT  

Anonymous David Aldridge said....

Not just a problem with businesses, this. There are too many developers who need, or think that they need, to be told exactly what to do, and need to be educated into a more active role in specification and design. I've heard frustration expressed at not being told exactly what to do.

It's certainly the case that development is much, much more than writing code -- if it's not a partnership with the business then it's not being done properly.

Thu Oct 07, 09:21:00 AM EDT  

Anonymous Anonymous said....

You are number 6.

Thu Oct 07, 10:58:00 PM EDT  

Blogger Stew Ashton said....

I would put "3. Define the users" as the second most important point. Requirements are often generated by representatives of management or other assorted bean counters, so the drones get neat dashboards and the worker bees get unusable junk.

Sat Oct 09, 06:09:00 AM EDT  

Blogger cycloscott said....

Sounds an awful lot like an argument for Agile methodologies.

Explain from a user context, what you are trying to do and why. Let IT define the solution. Iterate between IT and Business Users until the target is achieved and the business is satisfied.

Done correctly, it is a refreshing change from the waterfall style which is almost guaranteed to be out of date as soon as the documentation and use-cases are started.

Mon Oct 11, 05:39:00 PM EDT  

Anonymous Mark Brady said....

This applies not just from the business to IT but between IT groups. I work between DBA's and developers, often helping them communicate better. I had a highly volatile situation where a developer was telling the DBA's *HOW* to backup his databases. I told him to change his tack to tell them what you need. "I need to restore my database to a point in time up to two hours ago, if an install goes badly." etc.

@Dave Aldridge - That's the difference between developers and architects. Your best Java/C# guys eventually turn into architects... laying out the classes and services, and forms etc. Letting developers focus on writing the code to make each of those work. Sometimes people do both... smaller shops usually. But new developers do architecture very badly even when they can write decent code.

Mon Oct 18, 05:38:00 PM EDT  

Blogger RIHCIE said....

There is an alternative approach as I have heard this argument many times over. How about giving your business users tools to prototype and design their own applications first before talking with developers? Technology is getting close to point and click and end (business users) are now able to make their own applications with tools such as Oracle Application Express. As a business user, I often find few "partners" in the IT world. And it is most efficient for me to prototype or practice my ideas first.

Tue Oct 19, 09:09:00 PM EDT  

Blogger art100 said....

Im sorry.
Im speed testing Oracle for client.
Oracle exelent to work. This is no interesed.
I updown jock server on netbook AsusEee900SD+LinuxUbuntu10+Oracle10.
This is netbook very small screen 1024x600.
See sqlplus.
Need greate_database_examle.sql
May by we have link on tested example?
May be
And may be arhive

Past my work on WinNt4+Oracle7.33+DOS6.22 for closed commertion Belarus Belavtostrada very old. :(

Best reagards ;)
This is
Efremov Artem Alexandrovich

Tue Oct 19, 11:30:00 PM EDT  

Blogger Stew said....

RIHCIE said....

> There is an alternative approach as
> I have heard this argument many times over.
> How about giving your business users
> tools to prototype and design their
> own applications...

This would contradict the article, because then the end-user comes in with a solution, not a need. Please don't tell a systems designer or programmer how to create an app to manage your data, that's why you're paying them.

Mon Oct 25, 01:30:00 PM EDT  


<< Home