Unfortunately, said small black holes often result in consuming the head attached to them, often resulting in what is colloquially referred to as rectal cranial inversion.
Agree about the certifications. The only ones that aren't immediate red flags to me are government issued ones such as Professional Engineer (PE). The reason the government certs carry more weight is they also carry legally enforced responsibility, including, but not limited to, misrepresenting your abilities or competence in a given area or discipline. There are often legally enforceable ethical codes with the law typically deferring to the the discipline's governing body, for instance, for electrical engineers, the state of Illinois defers to IEEE for the ethics code (even better that the corrupt politicians don't attempt to come up with "ethics").
For the paid certs, it feels often as if the person took a crash course on $INSERT_VENDOR_HERE just long enough to pass a test, paid the money and got the cert. A cert doesn't make up for years of hands on experience. I know more about tuning SQL than most DBAs, but I'm not now, nor will I likely ever be certified by any vendor. People that can do. People that can't... get certified, or rather, plaster their certs all over their resume.
Doing the same thing over and over and expecting a different result is insanity. 10,000 hours of practice might be better thought of 10,000 hours of experimentation. Each repetition, you try something. If that doesn't work, you vary something slightly, repeat and observe the outcome. You then take that result and make another change, and repeat the whole process. If you just dedicated 10,000 hours doing the exact same thing, the exact same way, you're insane to expect anything other than the exact same result. Athletes don't spend 10,000 hours throwing a pass the same way, taking a shot the same way or swining a bat the same way. They make adjustments based upon (usually) microexperiments. There might be film involved or coaching (for the elite, there is definitely at least those 2 things).
Point is, there is far more to the superficial "10,000 hours will make you an expert" than pure repetition.
For an athlete, once the "ideal" motion has been identified, there is value in repetition insofar as to commit that motion to muscle memory, instinct and passive response instead of actively having to "tell" your body to do some specific set of motions.
Loss to infrastructure? Why did the US interstate highway system get built? It was a direct result of the US Army's difficulty in moving troops and equipment cross country. There are also requirements that every so often they roads remain straight long enough to be used emergency runways. I don't buy loss to progress, either. A lot of technological progress has been pioneered through military research. That I'm able to even post this comment right now was a result of DARPA funded work.
I've done 2 non-trivial C++11 projects. While I also like the new shiny, there are some new gotchas in there. One is the implicit capturing of "this" in a lambda. Not a big deal if your lambda doesn't outlive the instance... Another is std::thread calling terminate in the destructor if it is for a joinable thread that hasn't been joined (far different behavior than the boost::thread it was based on). I'm sure there's more, but those are the first two gotchas that come to mind.
Mine was, too. I ended up having ICL implants, instead of laser surgery. The process wasn't exactly fun, it's basically cataract surgery, but instead of replacing your lens, they effectively add a contact lens behind your iris. The first eye they did, I was blind in for about 2 weeks due to swelling in the eye. The second eye, I could see clearly out of in about 5 mins after surgery. It's been about 4 years since I've had it done, and I don't regret it once.
I went through this at my new employer this month. I started this past December and our code signing cert expired this month. Thing is, I noticed back in around February/March timeline that this was going to happen, so I filed a ticket and added a personal reminder to tick off last month. Took us close to 2 weeks to get a new cert from our vendor (they were questioning our identity for some reason). By the time I got the new cert, it was 2 days before I went on vacation. I thought I had everything setup correctly and merrily went on my vacation. Turns out the wrong type of cert was sent and shit blew up after our old cert officially expired. Unlucky coworker had to pick up the pieces.
So, the moral here is, even if you do plan ahead an try and coordinate these things, sometimes it still blows up, and you still end up with unhappy customers.
I've used VC6, VS2003, 2005, 2008, & 2013. VS is perfectly fine & performs well for C#. 2008 and earlier absolutely sucked for C++ (I've not done C++ in VS2013), because of intellisense, which you cannot turn off. You're writing code, trying to invoke a function, and intellisense kicks in and you're stuck waiting for minutes, while the UI is hung, for it to give you suggestions on what I already know I want to do. To boot: you cannot disable it. The C# experience is quite different, and the IDE was a pleasure to use for that. The debugger, regardless of the language is still one of the best I've used. For C++, give me vim any day.
I'd assume you'd want a closed shell around the driver to reduce drag & aerodynamic disturbances. Also, I'm curious what effect this will have on the driver with only a helmet to protect them at supersonic speeds.
Its because these non-cabbies tend to drive in a safe and predictable manner, rather the the cabbies that drive erratically, changing lanes without signalling, running lights & stop signs, generally being a nuisance. Obviously not safe to mix the two. (This based on Chicago experiences, I assume CA cabbies are likewise assholes).
I used to donate every other month. I stopped donating when my work hours changed to 7a-7p, and the donor group started calling & emailing weekly asking me to come in. I told the first caller I was unable to donate due to work hours. I kept getting the calls & emails. Even after asking to be removed from their calling/email lists, it continued for years. Even now that my hours would accommodate donating, I refuse to deal with that organization over their previous harassment.
So your solution is what, exactly? Go from a phone you can root and put on a custom OS (i.e. cyanogen) that (potentially) fixes security issues to what? An iPhone? A Windows phone? A "dumb" phone?
Yes, but ancient Greeks didn't use the period, sorry, "full stop". I'd wager, however, that one would be able to find at least a few thousands of examples of "Pi" followed by a "full stop" in the multitude of scientific and mathematical journals, papers and books published in the last several centuries.
Altering the power of the assist shouldn't make this any more dangerous. Worse case, you lose power assist. Although that's bit GM hard lately with their ignition switch recall.
That's by biggest concern with this: if you engine stalls or turns off (for whatever) reason, do you completely lose steering, or you just lose power assist? There is a huge difference, even though suddenly losing assist can cause trouble.
You CANNOT change the meaning of words in advertisement. You can only advertise minimum data-rates when advertising connection speeds.
Great, this is groundbreaking. All ads now read: OFFERING 0 MBPS! Just because your ISP provides up to X Mbps, doesn't mean whomever you're talking to can actually supply it that fast. If someone connects a server to the internet on a 1200 baud modem, is it my ISP's fault that I can't download faster than several bytes a second? Or, what if I'm trying to access a site that is being DOS'd? Is that *my ISP's* fault? What you're suggesting is a step back, not forward.
I'm not advocating "fast lanes" or non-net neutrality, but what you suggest is so asinine, that when I tried to see things from your perspective, I failed, because I can't shove my head that far up my ass.
Personally, I've had days where 5-10,000 lines of C++ happened. Those are extremely few, and very far between, and the result of weeks of mental churning over how to solve a problem. What non-programmers don't realize is that 99% of development isn't the physical act of writing the code, it's identifying the problem and figuring out the solution. You can't write the code until you've done both.
LOC could be a relatively naive metric for a new code base, but if you're talking about adding onto an existing code base, immediately divide by 10 or more LOC output.
I've had days where the only commit to fix a bug was to alter 1 character. How long did that take? 8 hours. Why? No, it didn't take 8 hours to alter a character. It took 8 hours to identify which of the half-million characters to alter, make the change, build it, document it, and test it.
Another difference is that traditionally licensed Professional Engineers have to accept personal liability for designs they sign off on. Companies may accept the liability, but at the end of the day, a licensed engineer has to sign their individual name to a building or bridge design (at least of a certain significant scale). There may be a number of engineers involved, but if a structure fails or a building catches fire due to an engineering defect, you will most assuredly be able to find the engineer(s) that signed off on the design. (at least in the US).
Also, it's unclear to me what you qualify as a minor civil engineering defect. Just last week, here on/., there was an article about the possibility of skyscraper collapses in NYC if high winds and a prolonged power outage coincided. What about specifying the wrong grade of steel for a bridge (or failing to ensure proper quality) - see the Minneapolis/St Paul bridge collapse? Or failing to properly account for wind harmonics - see Tacoma Narrows Bridge?
Slashdot Mirror
Unfortunately, said small black holes often result in consuming the head attached to them, often resulting in what is colloquially referred to as rectal cranial inversion.
I think I'm allergic to Perl. Every time I see it, I have violent fits of sneezing.
Agree about the certifications. The only ones that aren't immediate red flags to me are government issued ones such as Professional Engineer (PE). The reason the government certs carry more weight is they also carry legally enforced responsibility, including, but not limited to, misrepresenting your abilities or competence in a given area or discipline. There are often legally enforceable ethical codes with the law typically deferring to the the discipline's governing body, for instance, for electrical engineers, the state of Illinois defers to IEEE for the ethics code (even better that the corrupt politicians don't attempt to come up with "ethics").
For the paid certs, it feels often as if the person took a crash course on $INSERT_VENDOR_HERE just long enough to pass a test, paid the money and got the cert. A cert doesn't make up for years of hands on experience. I know more about tuning SQL than most DBAs, but I'm not now, nor will I likely ever be certified by any vendor. People that can do. People that can't... get certified, or rather, plaster their certs all over their resume.
Enough said in the subject.
Doing the same thing over and over and expecting a different result is insanity. 10,000 hours of practice might be better thought of 10,000 hours of experimentation. Each repetition, you try something. If that doesn't work, you vary something slightly, repeat and observe the outcome. You then take that result and make another change, and repeat the whole process. If you just dedicated 10,000 hours doing the exact same thing, the exact same way, you're insane to expect anything other than the exact same result. Athletes don't spend 10,000 hours throwing a pass the same way, taking a shot the same way or swining a bat the same way. They make adjustments based upon (usually) microexperiments. There might be film involved or coaching (for the elite, there is definitely at least those 2 things).
Point is, there is far more to the superficial "10,000 hours will make you an expert" than pure repetition.
For an athlete, once the "ideal" motion has been identified, there is value in repetition insofar as to commit that motion to muscle memory, instinct and passive response instead of actively having to "tell" your body to do some specific set of motions.
Loss to infrastructure? Why did the US interstate highway system get built? It was a direct result of the US Army's difficulty in moving troops and equipment cross country. There are also requirements that every so often they roads remain straight long enough to be used emergency runways. I don't buy loss to progress, either. A lot of technological progress has been pioneered through military research. That I'm able to even post this comment right now was a result of DARPA funded work.
Yeah, and she's not biodegradable...
It's not a monopoly. It's just no one wants to learn reverse polish notation to use an HP calculator.
Naw, we just need to teach them to be vegetarians! Reminds me of this Futurama clip.
I've done 2 non-trivial C++11 projects. While I also like the new shiny, there are some new gotchas in there. One is the implicit capturing of "this" in a lambda. Not a big deal if your lambda doesn't outlive the instance... Another is std::thread calling terminate in the destructor if it is for a joinable thread that hasn't been joined (far different behavior than the boost::thread it was based on). I'm sure there's more, but those are the first two gotchas that come to mind.
Otherwise the only option is a hammer.
Only option? I beg to differ. My preferred method is thermite.
Mine was, too. I ended up having ICL implants, instead of laser surgery. The process wasn't exactly fun, it's basically cataract surgery, but instead of replacing your lens, they effectively add a contact lens behind your iris. The first eye they did, I was blind in for about 2 weeks due to swelling in the eye. The second eye, I could see clearly out of in about 5 mins after surgery. It's been about 4 years since I've had it done, and I don't regret it once.
I went through this at my new employer this month. I started this past December and our code signing cert expired this month. Thing is, I noticed back in around February/March timeline that this was going to happen, so I filed a ticket and added a personal reminder to tick off last month. Took us close to 2 weeks to get a new cert from our vendor (they were questioning our identity for some reason). By the time I got the new cert, it was 2 days before I went on vacation. I thought I had everything setup correctly and merrily went on my vacation. Turns out the wrong type of cert was sent and shit blew up after our old cert officially expired. Unlucky coworker had to pick up the pieces.
So, the moral here is, even if you do plan ahead an try and coordinate these things, sometimes it still blows up, and you still end up with unhappy customers.
I've used VC6, VS2003, 2005, 2008, & 2013. VS is perfectly fine & performs well for C#. 2008 and earlier absolutely sucked for C++ (I've not done C++ in VS2013), because of intellisense, which you cannot turn off. You're writing code, trying to invoke a function, and intellisense kicks in and you're stuck waiting for minutes, while the UI is hung, for it to give you suggestions on what I already know I want to do. To boot: you cannot disable it. The C# experience is quite different, and the IDE was a pleasure to use for that. The debugger, regardless of the language is still one of the best I've used. For C++, give me vim any day.
But, you don't get the purple heart when you pull the pin on the grenade and drop it at your feet.
I'd assume you'd want a closed shell around the driver to reduce drag & aerodynamic disturbances. Also, I'm curious what effect this will have on the driver with only a helmet to protect them at supersonic speeds.
Its because these non-cabbies tend to drive in a safe and predictable manner, rather the the cabbies that drive erratically, changing lanes without signalling, running lights & stop signs, generally being a nuisance. Obviously not safe to mix the two. (This based on Chicago experiences, I assume CA cabbies are likewise assholes).
I used to donate every other month. I stopped donating when my work hours changed to 7a-7p, and the donor group started calling & emailing weekly asking me to come in. I told the first caller I was unable to donate due to work hours. I kept getting the calls & emails. Even after asking to be removed from their calling/email lists, it continued for years. Even now that my hours would accommodate donating, I refuse to deal with that organization over their previous harassment.
So your solution is what, exactly? Go from a phone you can root and put on a custom OS (i.e. cyanogen) that (potentially) fixes security issues to what? An iPhone? A Windows phone? A "dumb" phone?
Yes, but ancient Greeks didn't use the period, sorry, "full stop". I'd wager, however, that one would be able to find at least a few thousands of examples of "Pi" followed by a "full stop" in the multitude of scientific and mathematical journals, papers and books published in the last several centuries.
Altering the power of the assist shouldn't make this any more dangerous. Worse case, you lose power assist. Although that's bit GM hard lately with their ignition switch recall.
That's by biggest concern with this: if you engine stalls or turns off (for whatever) reason, do you completely lose steering, or you just lose power assist? There is a huge difference, even though suddenly losing assist can cause trouble.
You CANNOT change the meaning of words in advertisement. You can only advertise minimum data-rates when advertising connection speeds.
Great, this is groundbreaking. All ads now read: OFFERING 0 MBPS! Just because your ISP provides up to X Mbps, doesn't mean whomever you're talking to can actually supply it that fast. If someone connects a server to the internet on a 1200 baud modem, is it my ISP's fault that I can't download faster than several bytes a second? Or, what if I'm trying to access a site that is being DOS'd? Is that *my ISP's* fault? What you're suggesting is a step back, not forward.
I'm not advocating "fast lanes" or non-net neutrality, but what you suggest is so asinine, that when I tried to see things from your perspective, I failed, because I can't shove my head that far up my ass.
Personally, I've had days where 5-10,000 lines of C++ happened. Those are extremely few, and very far between, and the result of weeks of mental churning over how to solve a problem. What non-programmers don't realize is that 99% of development isn't the physical act of writing the code, it's identifying the problem and figuring out the solution. You can't write the code until you've done both.
LOC could be a relatively naive metric for a new code base, but if you're talking about adding onto an existing code base, immediately divide by 10 or more LOC output.
I've had days where the only commit to fix a bug was to alter 1 character. How long did that take? 8 hours. Why? No, it didn't take 8 hours to alter a character. It took 8 hours to identify which of the half-million characters to alter, make the change, build it, document it, and test it.
The Plague, is that you? I haven't seen you around since '95. How's da Vinci treating you?
Another difference is that traditionally licensed Professional Engineers have to accept personal liability for designs they sign off on. Companies may accept the liability, but at the end of the day, a licensed engineer has to sign their individual name to a building or bridge design (at least of a certain significant scale). There may be a number of engineers involved, but if a structure fails or a building catches fire due to an engineering defect, you will most assuredly be able to find the engineer(s) that signed off on the design. (at least in the US).
Also, it's unclear to me what you qualify as a minor civil engineering defect. Just last week, here on /., there was an article about the possibility of skyscraper collapses in NYC if high winds and a prolonged power outage coincided. What about specifying the wrong grade of steel for a bridge (or failing to ensure proper quality) - see the Minneapolis/St Paul bridge collapse? Or failing to properly account for wind harmonics - see Tacoma Narrows Bridge?