|
The project I am working on now is pretty tough. Was wondering about some other projects that others here have worked on that were ultimately successful?
This project I am working on involves taking a C# library running on one server type machine, and interfacing it with the Micros ISLs for the Micros POS. It communicates with the C# server library using WCF (which I had not used before). Of course, Micros uses native DLLs so I had to write C++/CLI wrappers for everything else too. In addition, this C# library I wrote has to load an embedded system and put the Micros sales into our web server.
It is going to work, as I prototyped it a while ago, but now I am deep in the muck of implementation.....
I will get quite a bit of personal satisfaction when this project is working, especially since my company has paid for 2 different implementations of POS software that ultimately did not work and cost a small fortune.
|
|
|
|
|
I find any code I work on is getting harder - it sucks to get old.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
John Simmons / outlaw programmer wrote: I find any code I work on is getting harder - it sucks to get old.
That can't be good!
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
I worked real hard to eliminate any innuendo from my post.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
|
My grandmother used to have a word of advice on getting old. She said, "Don't."
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
BrainiacV wrote: She said, "Don't." She say how? (I don't want to use the one sure-fire method to do so. My sister was 20 years older than me, now I'm 9 years older than her.)
|
|
|
|
|
Unfortunately she died before passing on the secret.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
BrainiacV wrote: Unfortunately she died And that's the surefire method that my sister used so I became older than her. I do have an infantile sense of humor that I stubbornly retain despite my wife's objections. Probably a misused method of keeping the mind young.
|
|
|
|
|
Yeah, today happens to be my birthday and I've been saying fantasy or not, I plan on seeing 125.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
BrainiacV wrote: I plan on seeing 125. I'm pleased to say I am under half that age, but not by that much and unfortunately that time is approaching twice as fast. (IE, by next year, I'll have added 2 years to double my age. Of course that's true for everyone.)
When I was born the life expectancy was 72 and today it only has increased to 75. The good news is that when you live longer, your personal life expectancy increases as well. So if you make it to 124, you might reach your goal. Of course we both could snuff the candle tomorrow improving everyone else's odds of exceeding 75.
You related to that singer that bemoans the fact that we only live a 100 years? Ignoring the fact that only a few of us really reach that age and then go on and prove the singer wrong cause they just keep going, going...
|
|
|
|
|
Either that or I expect to be crossloaded into silicon by then.
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
|
Thank you. Now I don't want you running out and getting me any inexpensive gift
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
gift? I wouldn't dream of doing that to you.
|
|
|
|
|
Psychosis at 10
Film at 11
Those who do not remember the past, are doomed to repeat it.
Those who do not remember the past, cannot build upon it.
|
|
|
|
|
David Knechtges wrote: interfacing it with the Micros ISLs for the Micros POS. It communicates with the C# server library using WCF (which I had not used before).
I beg your pardon for my ignorance, how's anything "Micro" or "Embedded" to understand WCF? I'd explore just plan socket on both end (hope string/int representation be same on both ends)
dev
|
|
|
|
|
Well, Micros is the POS application - one that is used in many retail stores and restaurants. It is PC based with a way to run custom DLLs - which are native code interface DLLs.
The embedded system I am using is communicated with over a 900MHz radio. The PC communicates with it using an antenna attached to it that runs on an RS232 port on the PC.
So essentially, what I have is:
1 or more Micros POS terminals talking to my custom C# server over WCF (using C++/CLI to wrap the classes/communications)
C# server communicating with the embedded system using the antenna on the RS232 port
C# server communicating with a IIS web server on the same intranet
C# server communicating with another windows application over WCF on the same intranet
Sheesh, even me writing it out is confusing!
|
|
|
|
|
okay, clear. Thought you are saying embedded system is communicating with a windows box via WCF!!!
dev
|
|
|
|
|
Clearly what is meant is that the application that communicates uses WCF (but an existing driver probably exists to do all the low-level bits) So the application can use the higher-level functionality provided by the drivers and windows to open sockets or rawIO connections.
On the Project itself, it seems to me (Sorry if this offends) that the design of the system (not application) is flawed. It's like using a sledgehammer to whack in nails, and while it will work it may be a little over-engineered. Truely the POS equipment / software for scanners should interface to the DB already (how it gets it's prices anyway) and you could then just add-in some SQL triggers to decrement "instock" (or similar) of item. Raising a purchase ledger (should be done automatically through stock system), can then be stored online, but it should only ever be stock, prices and promo's that are read by online anyway... Just my two-cents, but might have saved you a lot of headache.
Difficult projects for me are all about difficult clients, they either have other contractors in poking about what you've done breaking things, or they change their mind about what they want (both result in a fresh bill)
|
|
|
|
|
why are you replying to me Lewis, it's not my project
dev
|
|
|
|
|
It was both a reply to you and the OP, most was for the OP but the first bit was for you
"Clearly what is meant is that the application that communicates uses WCF (but an existing driver probably exists to do all the low-level bits) So the application can use the higher-level functionality provided by the drivers and windows to open sockets or rawIO connections."
This was a reply to your comment
"okay, clear. Thought you are saying embedded system is communicating with a windows box via WCF!!!" Which was also a reply (not to the OP)
|
|
|
|
|
Lewis1986 wrote: "okay, clear. ..." Which was also a reply (not to the OP) Now I'm confused. When that was said, it was a direct reply to David Knechtges. I count him as the OP(poster,) just wasn't a reply to the original post.
|
|
|
|
|
AFAIK none of the projects I've worked on has failed, although that might be a reflection of the fact that most of them were engineering type projects (digital broadcasting, defence, marine navigation etc.) rather than internal line of business systems.
The hardest one was undoubtedly the first team I led. We were developing an automatic test system for helicopter avionics, in conjunction with our arch competitor in order to stitch up another competitor. Although it was technically tricky, the worst aspects were political in nature - and the politics went all the way down to the dev teams. Every lunchtime the team leaders were receiving faxes from their opposite numbers stating "please respond by close of play today" - and that was just the start of it. Put a foot wrong and you effectively had the management of both companies on your back.
It was horrible, but I survived and learnt a great deal from it - most notably when to stick your neck out and say "No. I don't care what they say - it cannot work this way" (I did, and although it caused a huge row which went on for months I was eventually vindicated) and when to just get on with it as best you can.
Others weren't so lucky. The software manager on my site (my immediate boss) had a nervous breakdown amid a festering pile of fantasy Gantt charts and left the project for less stressful pastures, and one of the hardware engineers on the team committed suicide.
No matter how stressful a job becomes, nothing should ever come to that.
Anna
Tech Blog | Visual Lint
"Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
|
|
|
|
|
Anna-Jayne Metcalfe wrote: Others weren't so lucky. The software manager on my site (my immediate boss) had a nervous breakdown amid a festering pile of fantasy Gantt charts and left the project for less stressful pastures, and one of the hardware engineers on the team committed suicide.
Glad I never come even close! Colleague suicide!? That's unheard of. My superior officer (luckily) has very steady mind and never breakdown (even if our system does)
dev
|
|
|
|