The attorney calls a dispatcher first that turns the system off before connecting to the inmate. They built a system that records 70+ million calls... they can't build a feature to exclude authorized calls?
This is the shit kind of logic that messes up our society. There is no room in there to think that _maybe_ someone is locked up incorrectly. You are guilty because you are locked up, you are locked up because you are guilty. The logic assumes so much about the perfection of our justice system is or the powers that can control our lives. With that as a starting point, what margin is there to question the leaders, or the laws, or to give second chances.
Agreed. Is this really that complicated? Every field has this. "Engineer" is not usually a regulated term . So you end up with "Sanitation Engineer", "Sales Engineer", "Marketing Engineer", "HR Engineer", and "CAT Scan Engineer" (that's a technician). Companies make up stuff and muddle the waters all the time. Because they are made of people, and people need to "feel good" about their lack of accomplishment.
There are actual "Application Engineers", "DB Engineers", "Software Development Engineers" etc. But most (75%) with that title are actually "Application Admins", "Software Developer/Tester/Scripter", "Typist", "Operations technicians" etc.
I really wish we could depend on "Engineer" equaling "This level of education, expertise, capability, and job function." But we are so far over the edge on this one, there is no coming back.
REALLY? I think you are taking for granted a TON of knowledge that is considered "general" and "common sense" that the middle ages would have thought was specialization.
Your examples were Gnome, KDE, and X.org... really? Gnome gets modified by downstream supporters like RedHat and Canonical BECAUSE they went in a direction the customers didn't want. X.org is the fork because they didn't do what customers wanted. And your 3rd example, the underlying Qt framework went in the direction of what the community wanted and thus didn't get abandoned or forked.
And I disagree with the "direct financial loop" subject. In COTS, as seller you made the sale, your obligations are limited, and you have the money. That's it. Those customers may or may not buy the next version but they paid full price for this one. One payment that covers a few quarters to years. Its their problem to figure out the headaches because they already spent the money. With service and support (excluding dicks like Oracle, Cisco, and similar), you need to win the customer every quarter. They can switch other providers who provide "good enough" service. On the open source side, it is a little easier.
Sorry it sucked for you. But I personally know two people that without Obamacare's exchanges, one would probably not be talking today, and the other would have moved to another country for the same medication and medical service but 1/5 the cost. Sorry, but prior to Obamacare, there were a lot of people like them who "just got by" because they weren't chronically sick to be taken in by emergency care, but were slowly wasting away because the healthcare market felt they were unprofitable.
Obamacare is no where near perfect, but for gods sake, the US couldn't touch anything in Healthcare for over 3 decades! All those presidents and congressmen in that time were useless for the sick and needy of the US.
Healthcare affordability in the US is more about people choosing to live beyond their means..
I doubt you would still say that if you were self-employed, unemployed, or worked for a small business back in 2008. Because there, you wouldn't be able to afford the insurance, let alone the surgery. Try and get insurance or medical coverage with preexisting conditions like Parkinson, early Alzheimer, chronic blood pressure, etc. Large companies pay ~$1000 a month for employee insurance. Good luck getting that on your own.
While we "watch" them build their sphere, they would have already completed it, detected us using their advanced long range sensors, and used their FTL armada of battleships to come destroy us. Since we are still here, that is a NOT a Dyson sphere.
I read the article* and couldn't find anything that linked the measurement of fracking activity to the measurement of premature births.
There was a lot of warning verbiage about fracking and a lot of warning verbiage about premature births. They wrapped the two items together without any scientific backing and even stated that their research is still in "infancy" (pun intended?). They mention some points that it could be stress or something else, etc.
Basically its a prematurely (eh?) written article that is more emotional than factual. Clearly its meant to stir up the "Think of the children" angle for further funding into this research. Which I agree, more research needs to be done and I guess this is the only way to fight the industry and politicians. But that article had no right to be posted on Johns Hopkins website, the school just lost some credibility there.
* = I am sorry but you can't take my Slashdot card... I ummm... misplaced it.
Right, so Al Qaeda, ISIS, American revolution, French & Indian wars, Indian revolution, Peninsular War, Syrian rebels, etc. None should be able to fight because they are facing an official army using rag tag weapons.
Maybe this is different in other countries, but in the US, there is quite a large percent of the population that is trained in basic arms. The right to bear arms was given the same level of respect by the founding fathers as the right to free speech.
IEDs serve a different purpose than guns. IEDs rarely give you victory any more than bombs from airplanes. Guns give and secure victory. You don't need to fire a gun to maintain control. Just the fact you hold one and the conquered do not is enough to stop their resistance. IEDs may have scared the army, but its those AK47s that kept the population from revolting against the latest terror group for decades.
Cross pollination happens all the time and results in failure the majority of the time. Things like today's corn (pre-GMO), potato, cabbage, rice, wheat, etc would have never naturally occurred. It took humans hundreds of years of cross breeding, selective breeding, and accidents coupled with constant environment adjustments & control to produce today's crops. The veggies you see at the super market are monstrosities to their natural cousins.
This is the way Wipro was and is. InfoSys became their better replacement. Then Infosys did the same. And TCS, they started this way. I guess we should be happy that there are atleast 3 major competitors in the race to the bottom. As an another poster said, these guys are fine as low cost maintenance folks for steady state operations. But for actual development (what management calls "innovation") I see few that are happy with the result. And I don't blame them, its the management's fault for not knowing enough to make an informed decision.
With Exchange such a move is completely seamless and requires only
I am sorry. I agree with your post in general. But this is a peeve of mine. I want to slap anyone who throws up this regurgitated MS dribble about any MS product and punch any MS Consultant that states the same. We have done exactly what you said for MEGABYTE mailboxes for 20k+ instances. The project plan didn't even have a manager & service desk communication, let alone end user communications. It was all supposed to be seamless back end stuff driven by MS tools and MS environment, off hours. Our users noticed (not one offs), the SD freaked out, and we spent a good 2-3 days wasting time on "nothing broke" meetings with management.
I had to halt the project to the dismay of the head PM and MS consultants who kept telling me "No, that can't be right. Its seamless." In the end, the project was fine, communications went out, expectations set, we lost like 2% of the mailboxes and they were recoverable. We may have lost a handful of random emails, but we never know, who cares. As you said, this is all very impressive, but seamless isn't a word I would ever use again with MS products.
The situation was made worse by the fact that pilots were done, we were the 3rd batch, and 2nd largest. Just no one believed the instances that broke the "seamless" concept as real in the prior batches and no lessons learned were noted. I am sure nothing is still noted.
Single MTA doesn't mean it doesn't have redundancy. The parent is right, I work in a global shop with 60k users per regional instance. There are a lot of Exchange, domain controllers, Sharepoint, and IIS servers facing production. Not including the few backups and fail over redundancies. Lets just say a regular DSL connection wouldn't be enough for the North American _sync_ traffic.
As for pointers, MS does do a lot of testing inside their walls and covers about 70% of the real world scenarios. Well not really, they just say their way is THE way to do it. Go outside that and you are just in unsupported land. About half of those scenarios are written down by MS and it's just some admin not doing a Google for the whitepaper. The other 30%... good luck.
If there is no audit trail, shouldn't the buck stop at the top? The roles, job titles, audits, change management controls, financial approvals, etc are all business processes designed to reallocate the default responsibility who is either one of the big Cs or the board of directors. Without the approvals, audits, or whatnot the responsibility goes to the person who can't push further down. And it can't be a he said, she said thing. Need documentation.
I understand this is not how it works in the real world where companies settle or hush hush or just simply drop it because it is not worth the investigative resources but sanitizing the audit trail doesn't help anything. Misdirection, sure, and in this day and age, anyone who isn't doing enough personal CYA deserves to get the heat. Civility in business never existed.
We wanted to inform everyone so it was an educated decision...
That would be hilarious if this whole topic wasn't so sad and depressing. A law enforcement agency wanted to educate a house of knowledge on IT technology.
Basically the cops said "OMG, do you know how dangerous what you are doing is!!?!" To which the library said "Yes, we know. You clearly don't, but we do."
No, you are being too easy on them. 80% of such can have 5 years, 15% can have 10 years, and 5% can have 15 years. They can extend all they want, but can only extend 20% of outstanding orders. That way the supposed "open" government only operates 20% in the shadows. They have full freedom to choose which 20%. Our nation isn't so fragile that we need this many protections on national security. And if it was, for God's sake, let the darn thing die and be reborn stronger.
For non-disclosure & confidentiality agreements. 5 for those involving people, and 10 for those involving corporations. Extensions must be agreed by all parties.
Very well said. So many MBAs, administrators, consultants, and god forbid sales people forget... this is a "tool", not an AI. Not just in education, but in other fields, IT isn't seen as automation of some task, but as a replacement for human roles.
Everything from top to bottom of the sales pitch to acquisition to implementation of IT isn't focused on making people more efficient or effective, but rather on doing a role or parts of it. So a teacher doesn't need to "teach", they just need to follow the guide, make sure the screen is being looked at, keep order in the classroom, and click "Next". The success of these programs isn't looked at holistically or linked to actual efficiency gains, but at the number of deployments or the capital expenditure.
Technically, "doing the role" concept isn't bad itself. I think the idea that a teacher is a guide for 20% and the machine is the teaching tool for the 80% is a great concept. Unfortunately, I would say 90% of the "experts" involved in these things aren't smart enough to do the equivalent of tying their own shoes. And 99% of the user base is similarly unqualified to use these things because its all so "easy" and we saved so much by not providing any actual training.
Simply put, there are not enough true experts in the world to properly implement these things in any one district, let alone a state or country. So I think this role replacement concept shouldn't even be entertained.... we are just too stupid to do it. Lets just stick with the already difficult but achievable stuff like attendance recording, personalized testing, additional reference material, grade tracking, remote tutoring, distributed collaboration, etc. Lets get these basics down and correct before we start planning pie-in-the-sky projects.
He is actually spot on. The way it is setup, the HR procurement process would much rather hire someone working for another company or in the company over someone who recently became unemployed. Even promotions and raises go to those who show that they can easily leave to better pastures. HR seems to equate this to mean the company is undervaluing them presently. I have seen many examples where the guy who says "I have a job offer, match it or I am leaving" every two years advances by leaps compared to his peers that didn't.
Most of the younger companies in the IT industry think 5 years is a very long time to be working at any company. My last interviewers were shocked that I was at my present company for 4 years. My peers have been here for 10+. But even at my company, we have done mass firings and hired many... at the same time. Big companies tend to gravitate into thinking that the wallpaper employees are dead weights. Mostly because the wallpaper gets taken for granted and their work not documented... eventually management doesn't know what they do. The hoppers are the squeaky wheels whose "value add" is very visible to management. Their job history appears like their growth is unbounded and potential unlimited... even of that person is just sinking and jumping ships.
*Focus your testing on driving good design and executing at the UNIT level (e.g. RAM, CPU, fuckall else - no database/network/filesystem bullshit in 'unit' tests!).
That one is new and interesting. Didn't know that. Could you expand on the "no database... in unit tests" part? And honestly, #1 and #2 on your list are the hardest part:(.
Interesting? Why isn't this modded funny? Clearly the poster is tongue in cheek with all the useless statistics and pointless accomplishments. The end result of which is losing customers and firing devs. It was hilarious.
Slashdot Mirror
The attorney calls a dispatcher first that turns the system off before connecting to the inmate. They built a system that records 70+ million calls ... they can't build a feature to exclude authorized calls?
locked up
therefore
don't... deserve
This is the shit kind of logic that messes up our society. There is no room in there to think that _maybe_ someone is locked up incorrectly. You are guilty because you are locked up, you are locked up because you are guilty. The logic assumes so much about the perfection of our justice system is or the powers that can control our lives. With that as a starting point, what margin is there to question the leaders, or the laws, or to give second chances.
Agreed. Is this really that complicated? Every field has this. "Engineer" is not usually a regulated term . So you end up with "Sanitation Engineer", "Sales Engineer", "Marketing Engineer", "HR Engineer", and "CAT Scan Engineer" (that's a technician). Companies make up stuff and muddle the waters all the time. Because they are made of people, and people need to "feel good" about their lack of accomplishment.
There are actual "Application Engineers", "DB Engineers", "Software Development Engineers" etc. But most (75%) with that title are actually "Application Admins", "Software Developer/Tester/Scripter", "Typist", "Operations technicians" etc.
I really wish we could depend on "Engineer" equaling "This level of education, expertise, capability, and job function." But we are so far over the edge on this one, there is no coming back.
My apologies, I should have included a 3rd brain cell in that reading comprehension. In hindsight, that is funny.
REALLY? I think you are taking for granted a TON of knowledge that is considered "general" and "common sense" that the middle ages would have thought was specialization.
Your examples were Gnome, KDE, and X.org... really? Gnome gets modified by downstream supporters like RedHat and Canonical BECAUSE they went in a direction the customers didn't want. X.org is the fork because they didn't do what customers wanted. And your 3rd example, the underlying Qt framework went in the direction of what the community wanted and thus didn't get abandoned or forked.
And I disagree with the "direct financial loop" subject. In COTS, as seller you made the sale, your obligations are limited, and you have the money. That's it. Those customers may or may not buy the next version but they paid full price for this one. One payment that covers a few quarters to years. Its their problem to figure out the headaches because they already spent the money. With service and support (excluding dicks like Oracle, Cisco, and similar), you need to win the customer every quarter. They can switch other providers who provide "good enough" service. On the open source side, it is a little easier.
Sorry it sucked for you. But I personally know two people that without Obamacare's exchanges, one would probably not be talking today, and the other would have moved to another country for the same medication and medical service but 1/5 the cost. Sorry, but prior to Obamacare, there were a lot of people like them who "just got by" because they weren't chronically sick to be taken in by emergency care, but were slowly wasting away because the healthcare market felt they were unprofitable.
Obamacare is no where near perfect, but for gods sake, the US couldn't touch anything in Healthcare for over 3 decades! All those presidents and congressmen in that time were useless for the sick and needy of the US.
Healthcare affordability in the US is more about people choosing to live beyond their means ..
I doubt you would still say that if you were self-employed, unemployed, or worked for a small business back in 2008. Because there, you wouldn't be able to afford the insurance, let alone the surgery. Try and get insurance or medical coverage with preexisting conditions like Parkinson, early Alzheimer, chronic blood pressure, etc. Large companies pay ~$1000 a month for employee insurance. Good luck getting that on your own.
While we "watch" them build their sphere, they would have already completed it, detected us using their advanced long range sensors, and used their FTL armada of battleships to come destroy us. Since we are still here, that is a NOT a Dyson sphere.
Quoting the researcher:
“Is it air quality? Is it the stress? They’re the two leading candidates in our minds at this point.”
Its ok, just slowly take your foot out of your mouth....
I read the article* and couldn't find anything that linked the measurement of fracking activity to the measurement of premature births.
There was a lot of warning verbiage about fracking and a lot of warning verbiage about premature births. They wrapped the two items together without any scientific backing and even stated that their research is still in "infancy" (pun intended?). They mention some points that it could be stress or something else, etc.
Basically its a prematurely (eh?) written article that is more emotional than factual. Clearly its meant to stir up the "Think of the children" angle for further funding into this research. Which I agree, more research needs to be done and I guess this is the only way to fight the industry and politicians. But that article had no right to be posted on Johns Hopkins website, the school just lost some credibility there.
* = I am sorry but you can't take my Slashdot card... I ummm... misplaced it.
What could possible go wrong? Did some government police state / apocalyptic scenarios run through anyone else's minds when they read that?
...the armed forces are in the way...
Right, so Al Qaeda, ISIS, American revolution, French & Indian wars, Indian revolution, Peninsular War, Syrian rebels, etc. None should be able to fight because they are facing an official army using rag tag weapons.
Maybe this is different in other countries, but in the US, there is quite a large percent of the population that is trained in basic arms. The right to bear arms was given the same level of respect by the founding fathers as the right to free speech.
IEDs serve a different purpose than guns. IEDs rarely give you victory any more than bombs from airplanes. Guns give and secure victory. You don't need to fire a gun to maintain control. Just the fact you hold one and the conquered do not is enough to stop their resistance. IEDs may have scared the army, but its those AK47s that kept the population from revolting against the latest terror group for decades.
Cross pollination happens all the time and results in failure the majority of the time. Things like today's corn (pre-GMO), potato, cabbage, rice, wheat, etc would have never naturally occurred. It took humans hundreds of years of cross breeding, selective breeding, and accidents coupled with constant environment adjustments & control to produce today's crops. The veggies you see at the super market are monstrosities to their natural cousins.
This is the way Wipro was and is. InfoSys became their better replacement. Then Infosys did the same. And TCS, they started this way. I guess we should be happy that there are atleast 3 major competitors in the race to the bottom. As an another poster said, these guys are fine as low cost maintenance folks for steady state operations. But for actual development (what management calls "innovation") I see few that are happy with the result. And I don't blame them, its the management's fault for not knowing enough to make an informed decision.
With Exchange such a move is completely seamless and requires only
I am sorry. I agree with your post in general. But this is a peeve of mine. I want to slap anyone who throws up this regurgitated MS dribble about any MS product and punch any MS Consultant that states the same. We have done exactly what you said for MEGABYTE mailboxes for 20k+ instances. The project plan didn't even have a manager & service desk communication, let alone end user communications. It was all supposed to be seamless back end stuff driven by MS tools and MS environment, off hours. Our users noticed (not one offs), the SD freaked out, and we spent a good 2-3 days wasting time on "nothing broke" meetings with management.
I had to halt the project to the dismay of the head PM and MS consultants who kept telling me "No, that can't be right. Its seamless." In the end, the project was fine, communications went out, expectations set, we lost like 2% of the mailboxes and they were recoverable. We may have lost a handful of random emails, but we never know, who cares. As you said, this is all very impressive, but seamless isn't a word I would ever use again with MS products.
The situation was made worse by the fact that pilots were done, we were the 3rd batch, and 2nd largest. Just no one believed the instances that broke the "seamless" concept as real in the prior batches and no lessons learned were noted. I am sure nothing is still noted.
Single MTA doesn't mean it doesn't have redundancy. The parent is right, I work in a global shop with 60k users per regional instance. There are a lot of Exchange, domain controllers, Sharepoint, and IIS servers facing production. Not including the few backups and fail over redundancies. Lets just say a regular DSL connection wouldn't be enough for the North American _sync_ traffic.
As for pointers, MS does do a lot of testing inside their walls and covers about 70% of the real world scenarios. Well not really, they just say their way is THE way to do it. Go outside that and you are just in unsupported land. About half of those scenarios are written down by MS and it's just some admin not doing a Google for the whitepaper. The other 30%... good luck.
Gaming masses are still suckers and have been for quite some years. Just look at all the "best selling" titles each year.
If there is no audit trail, shouldn't the buck stop at the top? The roles, job titles, audits, change management controls, financial approvals, etc are all business processes designed to reallocate the default responsibility who is either one of the big Cs or the board of directors. Without the approvals, audits, or whatnot the responsibility goes to the person who can't push further down. And it can't be a he said, she said thing. Need documentation.
I understand this is not how it works in the real world where companies settle or hush hush or just simply drop it because it is not worth the investigative resources but sanitizing the audit trail doesn't help anything. Misdirection, sure, and in this day and age, anyone who isn't doing enough personal CYA deserves to get the heat. Civility in business never existed.
We wanted to inform everyone so it was an educated decision...
That would be hilarious if this whole topic wasn't so sad and depressing. A law enforcement agency wanted to educate a house of knowledge on IT technology.
Basically the cops said "OMG, do you know how dangerous what you are doing is!!?!" To which the library said "Yes, we know. You clearly don't, but we do."
No, you are being too easy on them. 80% of such can have 5 years, 15% can have 10 years, and 5% can have 15 years. They can extend all they want, but can only extend 20% of outstanding orders. That way the supposed "open" government only operates 20% in the shadows. They have full freedom to choose which 20%. Our nation isn't so fragile that we need this many protections on national security. And if it was, for God's sake, let the darn thing die and be reborn stronger.
For non-disclosure & confidentiality agreements. 5 for those involving people, and 10 for those involving corporations. Extensions must be agreed by all parties.
Very well said. So many MBAs, administrators, consultants, and god forbid sales people forget... this is a "tool", not an AI. Not just in education, but in other fields, IT isn't seen as automation of some task, but as a replacement for human roles.
Everything from top to bottom of the sales pitch to acquisition to implementation of IT isn't focused on making people more efficient or effective, but rather on doing a role or parts of it. So a teacher doesn't need to "teach", they just need to follow the guide, make sure the screen is being looked at, keep order in the classroom, and click "Next". The success of these programs isn't looked at holistically or linked to actual efficiency gains, but at the number of deployments or the capital expenditure.
Technically, "doing the role" concept isn't bad itself. I think the idea that a teacher is a guide for 20% and the machine is the teaching tool for the 80% is a great concept. Unfortunately, I would say 90% of the "experts" involved in these things aren't smart enough to do the equivalent of tying their own shoes. And 99% of the user base is similarly unqualified to use these things because its all so "easy" and we saved so much by not providing any actual training.
Simply put, there are not enough true experts in the world to properly implement these things in any one district, let alone a state or country. So I think this role replacement concept shouldn't even be entertained.... we are just too stupid to do it. Lets just stick with the already difficult but achievable stuff like attendance recording, personalized testing, additional reference material, grade tracking, remote tutoring, distributed collaboration, etc. Lets get these basics down and correct before we start planning pie-in-the-sky projects.
He is actually spot on. The way it is setup, the HR procurement process would much rather hire someone working for another company or in the company over someone who recently became unemployed. Even promotions and raises go to those who show that they can easily leave to better pastures. HR seems to equate this to mean the company is undervaluing them presently. I have seen many examples where the guy who says "I have a job offer, match it or I am leaving" every two years advances by leaps compared to his peers that didn't.
Most of the younger companies in the IT industry think 5 years is a very long time to be working at any company. My last interviewers were shocked that I was at my present company for 4 years. My peers have been here for 10+. But even at my company, we have done mass firings and hired many... at the same time. Big companies tend to gravitate into thinking that the wallpaper employees are dead weights. Mostly because the wallpaper gets taken for granted and their work not documented... eventually management doesn't know what they do. The hoppers are the squeaky wheels whose "value add" is very visible to management. Their job history appears like their growth is unbounded and potential unlimited... even of that person is just sinking and jumping ships.
*Focus your testing on driving good design and executing at the UNIT level (e.g. RAM, CPU, fuckall else - no database/network/filesystem bullshit in 'unit' tests!).
That one is new and interesting. Didn't know that. Could you expand on the "no database... in unit tests" part? And honestly, #1 and #2 on your list are the hardest part :(.
Interesting? Why isn't this modded funny? Clearly the poster is tongue in cheek with all the useless statistics and pointless accomplishments. The end result of which is losing customers and firing devs. It was hilarious.