That's not the same project
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
loctrice wrote:
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening?
Yes, several times.
loctrice wrote:
Now they want the program to actually do something different.
Can I get fries with that also? :)
New version: WinHeist Version 2.1.0 Beta There's a fine line between crazy and free spirited and it's usually a prescription.
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
loctrice wrote:
Ever been so frustrated that you wanted to make a post
No, but I have been so frustrated that I wanted to take up cage fighting. :)
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
loctrice wrote:
I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Here lies danger!
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
loctrice wrote:
Ever been so frustrated that you wanted to make a post
No, but I have been so frustrated that I wanted to take up cage fighting. :)
Slacker007 wrote:
I wanted to take up cage fighting.
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
This calls for introducing the Bongo-Bongo-Man [aka Sales] to my [patent pending] "Sh!tty St!ck" with the award winning "where the sun don't shine" attachment.
-
loctrice wrote:
I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Here lies danger!
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
-
Slacker007 wrote:
I wanted to take up cage fighting.
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
:laugh: :laugh: :laugh: :laugh: :laugh: :laugh: Oh, man, I needed a good laugh. Thanks.
Colin Mullikin wrote:
Is that you?
I can not tell a lie....yes, that is me. :-\
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
-
I'm not really sure what you mean by that. I googled the term, but I got a bunch of drop down box related links. Nothing useful.
Elephant elephant elephant, sunshine sunshine sunshine
I used to have a boss, who would introduce major system changes and extensions by starting with: "Ok if we add here a drop-down with "... (all the things it is supposed to do), then they just select the option, it is just a drop-down. I call this the drop-down methodology.
-
It's a recent one, but it's one of my all-time favorites.
The United States invariably does the right thing, after having exhausted every other alternative. -Winston Churchill America is the only country that went from barbarism to decadence without civilization in between. -Oscar Wilde Wow, even the French showed a little more spine than that before they got their sh*t pushed in.[^] -Colin Mullikin
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
Been there. :( Make sure you keep track on everything written, because if the shit hits the fan it's gonna be your fault.
Wrong is evil and must be defeated. - Jeff Ello Any organization is like a tree full of monkeys. The monkeys on top look down and see a tree full of smiling faces. The monkeys on the bottom look up and see nothing but assholes.
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
At this point, if I were you, I would introduce your management to the project triangle. This is a triangle that balances Scope, Cost and Time to deliver. In other words, if one of those items changes, then the other two parts have to be adjusted to compensate - so, the scope of your application has changed, then the time to deliver changes as does the cost. This is project management 101, and if they don't understand this, they need to be pushed.
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
Maybe just be honest and blunt with them. Say you will do it, but it isn't nearly the same, and there is no guarantee it will be done in a month. And if they pressure you for overtime, they will be paying you more, because of their failure to do their job properly.
My CodeProject Articles :: Our forgotten astronomic heritage :: My website.
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
I rarely explain any of the refactoring or maintenance that I have to do to keep a code base sane. No matter how you do it, it's just going to sound over complicated and excessive to them. So, figure out how to change the architecture and keep the system sane, and do that, and it takes as long as it takes.
Curvature of the Mind now with 3D
-
I rarely explain any of the refactoring or maintenance that I have to do to keep a code base sane. No matter how you do it, it's just going to sound over complicated and excessive to them. So, figure out how to change the architecture and keep the system sane, and do that, and it takes as long as it takes.
Curvature of the Mind now with 3D
Andy Brummer wrote:
So, figure out how to change the architecture and keep the system sane, and do that, and it takes as long as it takes
That's where I'm at with it. I've been watching plural sight videos for an upcoming project most of the morning so that I could think about this one. I wasn't going to start coding until I had a solution that was not a hack. I've come up with something that is going to fit nicely into the program, and shouldn't take too long for me to put in place.
Andy Brummer wrote:
I rarely explain any of the refactoring or maintenance that I have to do to keep a code base sane. No matter how you do it, it's just going to sound over complicated and excessive to them.
I'm in an interesting position with that here. The boss and one of the processors were programmers. They are from an old script hack breed though. They don't get why an object is different than a code module, they don't know what design patterns are or how they are useful, and they don't see the need to plan before you start coding. So I end up having to explain myself, but they don't understand in the end anyway.
Elephant elephant elephant, sunshine sunshine sunshine
-
Ever been so frustrated that you wanted to make a post, but then couldn't really explain what was happening? I made a web based file checker for one of our clients as per request of the boss. It worked great, so much that we expanded it to work for more companies. No big deal, I had anticipated that so I set it up with nice design patterns to allow flexibility. Had a factory and command pattern. Not to bad. Now they want the program to actually do something different. I can't seem to explain to them that it's something that needs a good conversation and some dev time. They want it to be persistent and have complex rules, which is something I hadn't anticipated. There's now way, in the way the project is laid out, to do that. It was never meant to perform those sorts of tasks. They don't want a new program though, "just add this one thing onto it". So , like, if they just say it different and treat it like no big deal it will become easy enough for me to say ok. They just keep pressuring. We had been discussing other similar items, and then I guess they found an item that was "easy enough to do". As soon as it was brought up, everyone else is like "but you said you couldn't do that with my thing. If you do that, then we can do my thing too". Of coarse I don't have a choice. They already "sold" it to the client. At least I have until the end of the month. I just need to insert a specific one off into a generic system without breaking anything that works for the other companies.
Elephant elephant elephant, sunshine sunshine sunshine
