Dyslexia doesn't wear off by 10:00 AM. You just got to bed late, didn't get enough sleep and were nodding off in class. You should have gone to a Christian private school.
Anecdote: There was a kid who was doing poorly in public school. particularly at math. So, on the advice of some neighbors, his parents enrolled him in a Catholic school. After the first semester, his grades had improved markedly, particularly in math. So his parents asked him what it was about the new surroundings that provided the newfound motivation. He replied, "On the first day, when I walked in the door and saw the statue of a guy nailed to the plus sign, I knew they took their math seriously."
I get that it can help mom and dad get to work on time, but extending the starting time an hour wouldn't put most out that much.
This article is about college. So mom and dad should be pretty much out of the picture. By 18, you should be getting up, dressing yourself, making breakfast and getting to school on your own. Most high school kids can manage this themselves. The primary reason that moving the start time back for high school is bad is that school districts have to provide bus transportation not only for high schoolers, but grade schoolers as well. And if they take you in later, they have to adjust the transportation schedules of everyone else just to pick up your entitled butt when it suits you.
their own defined business workflows are often either not the most efficient, or require so much bespoke software that it costs them a lot of money to maintain that workflow.
That might work for a plumbing repair business. But I don't think there is an item in the pull down menu to select the "commercial aircraft manufacturing" workflow. And it doesn't really cost that much if you start out with a flexible tool set. Compared to having some consultants from a Windows shop "waste the better part of last year" trying to sell you their canned solution.
The biggest part of any process re-engineering is to sit down with the customer, identify their processes and the inefficiencies therein and only then, propose a solution. And occasionally, after a cleanup, a clipboard and paper solution will work just fine.
Perhaps it's time to reinstate the '18 years or older' rule for Internet use.
The Parkland students and Florida might be onto something here. Owning guns, driving, voting, surfing the web. Maybe they need a few more years of maturity.
I'm not sure. They were looking at a lot of different products to implement DCAC/MRM when I left. This may have been one of them.
Their problems were that whatever tool suite they tried to implement on top of an NT infrastructure, it was pretty easy to go in 'underneath' the apps and fiddle with the data. And this is probably what leads to stuff like WannaCry. Once one system in a domain is cracked, it seems to be pretty easy to get into pretty much anything else.
We had a story when I worked there: A CS consultant was giving an embedded systems class to a bunch of Boeing engineers. He started the first day off by asking, "If you were on a Boeing plane taking off and you suddenly realized that your group was responsible for the avionics software, how many of you would be concerned?" Everyone raised their hands except for one lady sitting in the front row. So the instructor asked her why she wasn't worried. "If my department wrote the software, the plane wouldn't even taxi, let alone take off."
There are (at least) two parts to WannaCry: The transport mechanism, based on the NSA's EternalBlue exploit. And the payload, which does the privilege escalation and file encryption stuff. The 'kill switch' was a domain name that, when resolved by the transport mechanism, would stop it from spreading or deploying its payload on the current host.
Several different domain names appeared in the WannaCry virus, probably as its creators tried to circumvent the kill switch fix. It's possible that someone got hold of the NSA exploit source and changed the kill switch domain name yet again. Or removed it altogether.
Its also possible that Boeing didn't enter the kill domains into its internal DNS system. Or that they were deleted during some sort of cleanup*. An even funnier theory: The kill switches may have been put in by the NSA to keep their back door ware from spreading into secure government and subcontractor's systems. And Boeing just didn't rate a "friend of the government" designation in the NSA's buddy list.
*Anecdote: We had a couple of systems crash back when I worked there because some IT bigwig had asked, "What are the/tmp directories for?" And upon getting an (oversimplified) answer of "For saving garbage files", he ordered them to be deleted since "We don't store garbage on our systems."
applications which have efficient workflow the features needed for many situations
Interesting. Because it was the 'efficient workflow features' that we had to build on UNIX systems at Boeing which were simply unavailable on Windows systems. CATIA started out running on UNIX (AIX and Solaris at Boeing) and was finally ported to Windows NT when the Microsoft fanbois cried hard enough. The backend 'workflow management' was never ported to a Windows platform during my time there. We just couldn't buy enough NT servers that would handle the load a Sun system could handle.
Data integrity was (and still appears to be) a problem for Windows systems. We had a requirement to keep people from modifying datasets not a part of their scheduled workflow. The NT folks could never figure out how to implement that. And more than a decade later, this is fundamentally what the WannaCry virus does. Windows just isn't ready for enterprise use yet.
No. But they do use it on manufacturing equipment now. I was there when they got hit with the Code Red virus. Fortunately, in 2001 they were running Solaris, HP-UX and Linux on the shop floor. When management came running out in a panic about possible effects on production, we told them, "No problem. We don't run Windows."
Management's response was, "Why aren't we running Windows?" I guess now they'll find out.
Slashdot Mirror
Yeah. She wishes she looked as good as the artwork in the GTA game.
Don't forget the blackjack and hookers.
because I was dyslexic at first period
Dyslexia doesn't wear off by 10:00 AM. You just got to bed late, didn't get enough sleep and were nodding off in class. You should have gone to a Christian private school.
Anecdote: There was a kid who was doing poorly in public school. particularly at math. So, on the advice of some neighbors, his parents enrolled him in a Catholic school. After the first semester, his grades had improved markedly, particularly in math. So his parents asked him what it was about the new surroundings that provided the newfound motivation. He replied, "On the first day, when I walked in the door and saw the statue of a guy nailed to the plus sign, I knew they took their math seriously."
I get that it can help mom and dad get to work on time, but extending the starting time an hour wouldn't put most out that much.
This article is about college. So mom and dad should be pretty much out of the picture. By 18, you should be getting up, dressing yourself, making breakfast and getting to school on your own. Most high school kids can manage this themselves. The primary reason that moving the start time back for high school is bad is that school districts have to provide bus transportation not only for high schoolers, but grade schoolers as well. And if they take you in later, they have to adjust the transportation schedules of everyone else just to pick up your entitled butt when it suits you.
Will they ever really grow up?
No we won't. And you can't make us. So there! Nyah, nyah, nyah!
their own defined business workflows are often either not the most efficient, or require so much bespoke software that it costs them a lot of money to maintain that workflow.
That might work for a plumbing repair business. But I don't think there is an item in the pull down menu to select the "commercial aircraft manufacturing" workflow. And it doesn't really cost that much if you start out with a flexible tool set. Compared to having some consultants from a Windows shop "waste the better part of last year" trying to sell you their canned solution.
The biggest part of any process re-engineering is to sit down with the customer, identify their processes and the inefficiencies therein and only then, propose a solution. And occasionally, after a cleanup, a clipboard and paper solution will work just fine.
on a site where more and more minors go browsing
Perhaps it's time to reinstate the '18 years or older' rule for Internet use.
The Parkland students and Florida might be onto something here. Owning guns, driving, voting, surfing the web. Maybe they need a few more years of maturity.
Ezekiel 23:20
resolved by Teamcenter
I'm not sure. They were looking at a lot of different products to implement DCAC/MRM when I left. This may have been one of them.
Their problems were that whatever tool suite they tried to implement on top of an NT infrastructure, it was pretty easy to go in 'underneath' the apps and fiddle with the data. And this is probably what leads to stuff like WannaCry. Once one system in a domain is cracked, it seems to be pretty easy to get into pretty much anything else.
immediately result in most of the electrical grid shorting out / shutting down
I'm not worried. Our local power company put their first power plant on line in 1898. And they haven't changed much since then.
You think the US is uniquely unable to attack foes in this manner?
Russian security services use typewriters.
We had a story when I worked there: A CS consultant was giving an embedded systems class to a bunch of Boeing engineers. He started the first day off by asking, "If you were on a Boeing plane taking off and you suddenly realized that your group was responsible for the avionics software, how many of you would be concerned?" Everyone raised their hands except for one lady sitting in the front row. So the instructor asked her why she wasn't worried. "If my department wrote the software, the plane wouldn't even taxi, let alone take off."
I expect that Boeing had good defenses
You owe me a new keyboard. And a coffee refill.
There are (at least) two parts to WannaCry: The transport mechanism, based on the NSA's EternalBlue exploit. And the payload, which does the privilege escalation and file encryption stuff. The 'kill switch' was a domain name that, when resolved by the transport mechanism, would stop it from spreading or deploying its payload on the current host.
Several different domain names appeared in the WannaCry virus, probably as its creators tried to circumvent the kill switch fix. It's possible that someone got hold of the NSA exploit source and changed the kill switch domain name yet again. Or removed it altogether.
Its also possible that Boeing didn't enter the kill domains into its internal DNS system. Or that they were deleted during some sort of cleanup*. An even funnier theory: The kill switches may have been put in by the NSA to keep their back door ware from spreading into secure government and subcontractor's systems. And Boeing just didn't rate a "friend of the government" designation in the NSA's buddy list.
*Anecdote: We had a couple of systems crash back when I worked there because some IT bigwig had asked, "What are the /tmp directories for?" And upon getting an (oversimplified) answer of "For saving garbage files", he ordered them to be deleted since "We don't store garbage on our systems."
So you built something yourself?
Of course. Business rules have to be set up and workflows have to be defined.
applications which have efficient workflow the features needed for many situations
Interesting. Because it was the 'efficient workflow features' that we had to build on UNIX systems at Boeing which were simply unavailable on Windows systems. CATIA started out running on UNIX (AIX and Solaris at Boeing) and was finally ported to Windows NT when the Microsoft fanbois cried hard enough. The backend 'workflow management' was never ported to a Windows platform during my time there. We just couldn't buy enough NT servers that would handle the load a Sun system could handle.
Data integrity was (and still appears to be) a problem for Windows systems. We had a requirement to keep people from modifying datasets not a part of their scheduled workflow. The NT folks could never figure out how to implement that. And more than a decade later, this is fundamentally what the WannaCry virus does. Windows just isn't ready for enterprise use yet.
I bet wannacry will never hit an Antanov.
Yeah. But Boeing will never have to run down to Radio Shack to test vacuum tubes.
No. But they do use it on manufacturing equipment now. I was there when they got hit with the Code Red virus. Fortunately, in 2001 they were running Solaris, HP-UX and Linux on the shop floor. When management came running out in a panic about possible effects on production, we told them, "No problem. We don't run Windows."
Management's response was, "Why aren't we running Windows?" I guess now they'll find out.
FaceSpook?
Oh come on now. You're just Putin us on.
I'll finally figure out how to pronounce 'doge'.
the Terminator
Are you sure you know what you want?
people who are going to start going to the gym
Same people by the looks of them.