Riddle me that
-
Yes, put the poor thing out of its misery. :-) And tomorrow I will again work on a project where the customer requested a change that would require to completely replace the primary keys of most tables in order to be able to arrange all major objects (and future expansions) in a tree structure as he sees fit. But please without changing anything in the table definitions, so that the stored procedures he has written to manipulate the database (!!!) still work.
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript.Move away from SQL, just stop using databases. Move into class libraries with properties that serialize the data. Much faster Then you can have the properties bring in data from the old database seamlessly without having to rewrite the primary key system. You can also inject the value backwards into the database for the clients scripts, and as well get them to upgrade to the new system by using windows 8 xaml apps.
-
Take the fox over to the island to take care of the rabbit problem, then go back and have a nice fat roast hen for dinner...
The seed killed the chicken because it ate to much in the short 40 minutes it takes to go there and back. Also the seed was for the fields now your whole family will starve.
-
Move away from SQL, just stop using databases. Move into class libraries with properties that serialize the data. Much faster Then you can have the properties bring in data from the old database seamlessly without having to rewrite the primary key system. You can also inject the value backwards into the database for the clients scripts, and as well get them to upgrade to the new system by using windows 8 xaml apps.
That's exactly what we are doing, but unfortunately the customer has never heard of something like application logic and insists on messing around in the database with his stored procedures. The old composite primary keys are not adequate to represent the new tree structure, so we have little choice than to make those changes in the database and keep the changes to his SPs as small as possible.
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript. -
The seed killed the chicken because it ate to much in the short 40 minutes it takes to go there and back. Also the seed was for the fields now your whole family will starve.
Ah, an exercise in requirement gathering and talking to users... [oh! didn't I mention that] :)
-
Ah, an exercise in requirement gathering and talking to users... [oh! didn't I mention that] :)
If you have to ask the user what they want you're in the wrong business. You should have been able to gather the parameters of life from the fact he was a farmer and had to live more then one day. This isn't a program, even if it was, you failed. You don't need to ask the user that life goes on after one day.
-
That's exactly what we are doing, but unfortunately the customer has never heard of something like application logic and insists on messing around in the database with his stored procedures. The old composite primary keys are not adequate to represent the new tree structure, so we have little choice than to make those changes in the database and keep the changes to his SPs as small as possible.
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript.ekk
-
If you have to ask the user what they want you're in the wrong business. You should have been able to gather the parameters of life from the fact he was a farmer and had to live more then one day. This isn't a program, even if it was, you failed. You don't need to ask the user that life goes on after one day.
When it comes to users it is better not to assume anything... ... anyway what's wrong with living for the day!? :)
-
Yes, put the poor thing out of its misery. :-) And tomorrow I will again work on a project where the customer requested a change that would require to completely replace the primary keys of most tables in order to be able to arrange all major objects (and future expansions) in a tree structure as he sees fit. But please without changing anything in the table definitions, so that the stored procedures he has written to manipulate the database (!!!) still work.
The language is JavaScript. that of Mordor, which I will not utter here
I hold an A-7 computer expert classification, Commodore. I'm well acquainted with Dr. Daystrom's theories and discoveries. The basic design of all our ship's computers are JavaScript. -
You live on an island. You have a rabbit problem. You are a farmer. You have a boat that holds one item. Your task is to take a fox, a hen, and seed to the island. If you leave the fox with the hen it will eat the hen. If you leave the hen with the seed it will eat the seed. How do you get all three across to the island, when remember you can only carry one item at a time on your boat.
Club the fox to death and rip its head off. Wring the chicken's neck and cook the bird and serve with a delicious peri-peri sauce. As for the seed, throw it away and see what grows in its place the following year. In the meantime, go to the island. Rabbit pie anyone?
If there is one thing more dangerous than getting between a bear and her cubs it's getting between my wife and her chocolate.
-
When it comes to users it is better not to assume anything... ... anyway what's wrong with living for the day!? :)
I don't think you see it. If you fulfill the users needs - great you fulfilled the purpose for which they wanted. What did that have anything to do with their jobs? Are you sure they know exactly what they want? Are they even saying the right keywords in the meaning you understand them? If you program for today - today is as long as it will last. ALM - Application lifecycle management; this concept should extend beyond the memory management and into the user cases - the GUI itself. The PC is so great yet it's simplicity does not handle any one use case. So when you handle the needs of the user you are defining your own limitations.