The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions. Or if you must, use the Back Room[^] - but enter at your own risk.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen. For those discussions where you wish to be a little more frank, use the Soapbox[^]
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
Scrubbing all propriety and confidential information
So we are involved in various testing of prototype tools ( costly and all info/ datasheet not available) and time was the essence to maintain the deadline and enough pressure from people above my pay grade. The corresponding SME from product team was on vacation and not returning for next 2 weeks and my manager was vacation too. So yours truly proceeded with the test setup and execution with the knowledge I had .Was say 99.99% sure that I am doing right. I emailed my manager with my reason for starting the test and risk if I messed up.
Well to cut the long story short, the electronics in tool got destroyed as I was not in loop in recent changes in the power module. So per policy , we had a Fact finding meeting ( Whom to blame and dry his skin meeting). I presented the sequence and why tool got destroyed. So they asked me, why did I start the test with SME out of town blah, blah. Deadline cannot be a reason for not waiting etc.. Then my Manager interrupted and said verbatim ,
I approved the execution of the test and he had informed of the risk but I said , Go ahead. And please don't even dare ask me why I approved the test. In this same Room two weeks back, some of you and others lamented that Departments are slacking and often come with vacation and lack of engineers excuses for not doing the job. Mr X few minutes ago lectured on that Deadline is not a valid reason but two weeks ago you said Deadline cannot be compromised for any reason. You asked us to be proactive and take initiative and get the job done. Failure will happen sometime but you said it is part of the learning curve while changing our way of doing things here. So Please, I have real work to do and I would prefer if this meeting sticks to fact finding and lesson learnt. So My humble request is please give the engineers due respect for doing the job and lets keep the management insights away from them. My department task always has some risk and that's the cost of doing business. We would mess up once in a while when we are doing our job but don't blame us for that. Take us to cleaners for not trying but don't ever complain that we are trying too hard.
So Should we order pizza for all of us if we are going to stay longer?"
Too much of good is bad,mix some evil in it
Hi all, it struck me yesterday: when I started in IT, we built programs (systems) like we built houses: we planned the layout, had paper documentation on every routine, it took sometimes years to finish and the investment was huge but it was going to last forever. Additions followed the same guidelines if it was allowed by building regulations. It could house everything between 1 - 10 people without major issues.
Today we program like we build cars. We switch systems every 5 years, not because the current car doesn't suit our needs anymore but just because the other one has a keycard to unlock. Basically, it's just a newer version of the same. In a few years, parts will be difficult to find, cost of maintenance grows. For big parcels we need to rent a van and if we see someone with a newer version, we feel outdated.
Part of the problem is that we don't build systems like we do a house or a car: you don't have to be a professional architect to design software, you don't have to follow any building regulations, you aren't liable if the house collapses when you hand over the keys. You don't need to confirm to government legislation like you do with cars, you don't have to have any testing done at all, and test results aren't in any way public; you don't have to do recalls if there is a bug.
Instead, we have idiots throwing together lumps of code they copied from SO and QA, calling that "new software", being surprised when it doesn't do the job, and shipping it well before it's ready to meet arbitrary deadlines.
And until that changes, don't expect me to worry about feeling outdated!
Sent from my Amstrad PC 1640
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
Instead, we have idiots throwing together lumps of code they copied for SO and QA, calling that "new software", being surprised when it doesn't do the job, and shipping it well before it's ready to meet arbitrary deadlines.
Hey, hey, hey, I will not stand by and listen while you call yourself and idiot. Manager or consultant sounds much better.
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
Part of the problem is that we don't build systems like we do a house or a car
Customer: Build me a small bungalow. Programmer:(Builds small bungalow) Customer: Well that's no good! I wanted it to be twenty stories high! Fix it NOW!!!1! Programmer:(Tears down bungalow; builds twenty-storey high tower block) Customer: This is ridiculous! Where's the underground car-park and swimming pool? Programmer: You didn't ask for either of those things. We'll have to tear it down and start again. Customer: Unacceptable! You're already well over budget and past the deadline we agreed on. Don't tear it down; just add an underground car park and swimming pool! Programmer:(Face-palm; tries to meet customer demands; building collapses) Customer: You suck! My twelve-year-old nephew could have done a better job - he knows the facebooks and everything!
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
The jack-ace who made that site is a real card. And should be dealt with.
I'm pretty sure I would not like to live in a world in which I would never be offended.
I am absolutely certain I don't want to live in a world in which you would never be offended.
Freedom doesn't mean the absence of things you don't like.
Simple question: If you can build a circuit with discrete logic or simply program a cheap microcontroller and be done with it, what would you do?
Discrete logic costs next to nothing, but can very quickly hog up expensive space on your circuit board and complicate the board's layout, including problems with noise on the signals.
The microcontroller often comes in the same price category as the discrete logic chips it is supposed to replace. It's a single chip that has to be programmed to perform the function you want to have it for. It may solve the problem more elegantly than some bare bones logic could. Then again, a microcontroller with internal ROM and RAM and often diverse I/O ports seems a little wasteful for such a trivial job.
For example, I could build my interrupt control logic with discrete ICs or with a single microcontroller. The discrete logic would be simple. Interrupts that were not serviced by the time the signal becomes inactive are lost. There would be no masking and the priorities would be fixed.
The microcontroller could easily do such things, like buffering and holding interrupts until they have been acknowledged and serviced, masking interrupts or assigning different priorities.
Which way would you prefer? An 'object oriented' microcontroller where I just look at the interface and don't care how it does its job internally? Or better the minimalistic approach with discrete logic where everything is 'global'? Still, preparing a tiny computer on a chip for such a simple job seems extremely wasteful...
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
Last Visit: 31-Dec-99 18:00 Last Update: 22-Jun-18 0:34