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.
I knew there were differences, but not that many differences. This amount of spelunking for one single API just illustrates how messed up things are, and the extent to which web developers protect us, the reader, from the vagaries of web browsers.
That was an eye opening article. I didn't know most of those differences either.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Yesterday, out of the blue, and for no particular reason, I started thinking about my old high school principle. Now it has been 39 years since I finished high school, and to suddenly start thinking of this man, remarkable as he was, is a bit odd. Anyway, I decided to do a search for him, and see what he had been up to since. I came across this article, written only that morning: RAY COLLINS: Dr Stephen Aitken | Maitland-Newcastle Catholic News[^]
My principle was (at that time) Br Stephen Aitken. Strange how I only started thinking about him on the same day as this eulogy was published.
Anyway, as I mentioned, he was a truly remarkable man. In a school of over 1700 students, he could approach any one of us, or our parents, and talk about our interests, how we were currently performing, and if we were having any issues. 10 years after I had finished, he had been given a block of land and told to turn it into a school, which he had done, I decided to pay him a visit. He saw me coming from across the yard, rushed to greet me, and started talking as if it had been only yesterday.
RIP Brother - I owe you much of who I am today.
It doesn't matter how often or hard you fall on your arse, eventually you'll roll over and land on your feet.
Kudos to your principal; let his example of caring both about the profession and the people he interacted with be an example of how professional should behave.
Engage the people around you; learn about them; care about them; invest in their lives.
"In this case, Samsung took a deliberate step towards danger," wrote Shedletsky, "and their existing test infrastructure and design validation process failed them. They shipped a dangerous product. That this is possible at one of the top consumer electronic companies in the world is humbling -- and demonstrates the need for better tools."
Nope. Nope nope nopey-no. Unless by "tools" the writer was referring to the designers, in that case I endorse his/her diagnosis. This wasn't a problem of lacking tools, as it is explicitly said,
Samsung took a deliberate step towards danger
so this is a design issue not a tooling one.
Some people will never uderstand tha no feraking tool can substitute good design and proper implementation of safety rules and good practices.
And here is me thinking the problem is some fat ass bending/squeezing the phone, or an idiot charging it while it is under their pillow/duvet etc. or buying some cheap imitation knock off charger with no/or limited protection built in......
A phone WILL bend or squeeze if put in a portable container - even if Note 7 is phreaking humongous - and its design should be tailored to that, otherwise it's simply poor design. Probably they thought that every phone would be in the same condition of the testing device, which was on a perfectly flat surface at all times.
There is a HUGE difference between understanding and caring.
There are certain countries who just don't care.
I don't mean one example, or even a few. But systemic, complete, across the board utter disregard for any life, human or otherwise, trashing the environment with lead and cadmium, tainting food products with deadly chemicals in order to get a slightly higher test result on certain factors...
I have been in that situation, over ruled by managment, thing fails dumped on my desk told make it work, take it apart, find fault, find e-mail trail relating to fault, forward email trail to supervisor. Get called into meeting "Why was X done?", "I don't know, I recomended Y as this was a possibility", "well why wasn't this brought to the attention of X", "I did send a detailed E-mail", "can you send me the e-mails", "I already forward them.", reads e-mail trail, "Oh! thank you" told I could leave finger pointing meeting. My super found me a hour later, told me I was OK and marketing had got the chop over it!
In such a place always write a message whenever you see something going down the drain, insist on a written answer when someone definitely wants it that way and archive the messges in a way that deletion from the server will not do them any good. Deletion, of course, will 'accidentally' happen by the second finger pointing session after showing your archived messages for the first time.
Don't ever let them off the hook and don't do anything until you have a written answer. They can have it any way they want, as long as they don't try to dump the responsibility as well. It also is fun to see them squirm when trying to get out of this.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.