I work for: https://www.signalsciences.com/ and our tool is specifically designed for use cases like this. Let me know if you would like more info cody-at-signalsciences-dot-com
175 karma · joined August 21, 2014
Failed attempt in July which is being attributed as earliest work via https://twitter.com/lavados/status/948700783259811847
Even in the positions that were physically demanding your body "adjusts" to the workload and it becomes rather similar to sitting in front of a computer basically you go into periods of "auto-pilot" and then other times it was somewhat mentally demanding.
Most mining operations are heavily automated requiring at least some knowledge of I.ndustrial C.ontrol S.systems ICS/SCADA is somewhat of a programming work flow. If this valve is open turn on this other valve once this sensor is tripped turn off this motor and close this valve. From a very simplistic manner this is similar to binary logic.
At least from what I have experienced infosec is very mentally challenging, but it is not a constant demand there are definitely periods where I am in auto-pilot. The best solution for me having gone to a sedentary work life is to walk to work, drink lots of water at work (make you get up to pee alot) and to take walks at lunch.
Really my "coding" skills have helped me in other areas opening my eyes in new ways to automating my skill set. One of the best testaments to this was talked about by Zed Shaw http://learncodethehardway.org/blog/MAY_15_2012.html Basically stating that programming is a supplement to other skill sets. The majority of these programming bootcamps/workshops are geared towards onramping rapidly to jobs that would not typically qualify as engineering positions. These jobs typically require whiteboard interviews, but once you actually get on the job your programming skill set is not nearly as utilized as it was during the interview. While I cannot quantify this supposition it would be really difficult to get a company to admit or supply data stating that they interview for rock stars, but have you do "janitorial" code work in reality.
Where the Bloomberg article most failed is stating that they "cannot" learn to code. Pretending that becoming a developer/engineer/coder requires some minimal level of IQ, even the IQ standard is hotly debated, is ridiculous. Just as any other skill set it just requires dedication and commitment.
The article does state "The vuln being in recent version of Chrome should work on all Android phones;" which is factually correct.
This is a "Chrome" bug in so much as the Chrome browser uses the V8 Javascript engine. However, this particular bug could have other consequences as it is stated in this article and others that the bug in fact occurs in the V8 Javascript Engine which is used in Nodejs, Mongo and others.
So, no, none of your comments sound reasonable.
"Submit a pull request before.." The unofficial documentation and related tutorials are exactly that, unofficial, they are not meant a replacements by any stretch of the imagination for the official documentation. Rather, these forks exist to speak to many different audiences and in some cases, speaking from personal experience, attempting to document and teach others is a very useful tool for personal edification regardless if it is a distraction from the "blessed" documentation.
Motivational employees would help to significantly ease some of the social anxiety of programmers such as my self. Male or female the interaction of genuine interest is at the core of what seems to be lacking here. Typically any "collaborative" or "interest" showed by coworkers or superiors falls into two buckets.
- coworker: "oh that's cool reminds me of the time that I did x" with subtle connotations of why x is better than what you are doing.
- superior: "hmm really interesting, make sure you get this other stuff done before next week" with less subtle connotations of I have no idea what or why you are doing nor do I care as long as you get all your work done.
Side-note: Attended a BlackHat training and one of the people who works on the show (didn't catch their title) was attending one of the classes. Even saw them interracting with the offenisve security[1] cr3w. This small gesture adds an air of legitimacy in the infosec crowd.
Highly recommend any material on the main site as well. One of the few legit infosec professors I have ever interacted with.
Nearly all results of security research are given at least some metric for risk quantification. https://cve.mitre.org is a single example of an attempt to quantify risk. I'm assuming at least at some point you have run across these numbers so the statement is patently false or a complete exaggeration.
It would be a fair attribution to say that the behavior of the vehicle as viewed from another drivers perspective was none of these situations as the driver was to at least some extent still in control of the car. While I do not know the exact model of the Jeep I'm assuming that there is a mechanical emergency brake still present.
Stopping in the middle of traffic is probably very low on the metric of causes of accidents or death. Although I did not accumulate enough data to give a metric on how much risk the researchers incurred through this experiment it may be beneficial for the author to at least do some due diligence in acquiring data before labeling an industry (one the author is well known in for that matter) as having an inability to quantify risk and then immediately fail to quantify risk.
[1] Pretty ironic that the author fails in his own analysis while talking about 'proper "risk analysis"'.
Quantifying risk is a very difficult endeavor to do properly so any measure of it is done from the security researchers biased perspective. Yes infosec researchers seem to want attention for their work this is often because there is not near enough attention paid to their work. Actuarial science is an entire professional field specifically tasked with quantifying risk, at least from an insurance perspective.
The inferred statement, at least in the title, is that not only do infosec researchers now have to stay up on crypto, assembly, js[buzzword] framework and on and on, but now they must also become actuarial scientists. As a neophyte in the industry I'm having trouble getting caught up to a static point let alone that the static point is a moving and rapidly accelerating target and not in my favor. Adding to this unachievable standard I now must study and become at least somewhat proficient in actuarial sciences is maddening!
So not ALL that bad.
The lifestyle changes that would need to occur to stem California's water usage are far more extensive and could easily qualify as a scientific dilemma. Basically non-california citizens are the "problem". When you're talking about drastically altering the diet of the entire U.S. (most likely other nations as well) due to the water being consumed by Agriculture it is absolutely a scientific dilemma.
[1]http://www.scpr.org/news/2015/04/15/50941/10-things-to-know-...
,but that is because I am an unabashed infosec enthusiast that attempts to force feed everyone infosec information.