This video resonates with the talk given by "Uncle" Bob Martin from the CZcams video; "The Future of Programming". We as people who write code (especially Professionally), must come up with standards and enforced Discipline. We must self regulate before non-programming bodies come in to regulate us.
44:00 "what impact is autonomous trucks (and cars and vehicles) going to have on society?" just a guess but i suspect there will not be mass unemployment from this. it will mean that there will be a lot more trucks for a lower cost, and people can move from driving to other truck-related jobs - unloading, maintaining, remotely driving around hazards, etc.
Economies while elastic, do take time to adjust. Do you know how large the number of professional drivers is? Over three million full time truckers alone, this does not count other forms of delivery.
This is a common point that a lot of people fall for. There will be new jobs created, it has always happened. That's how economy works. I enjoyed the talk though
@@driden1987 But it never happened smoothly. It takes time for an economy to adjust, and the faster a disruptive tech is implemented, the less time there is to adjust. Once the problem of self-driving cars has been solved well enough for deployment, this will go at an unprecedented pace. You can't really compare that to for example the mechanization of agriculture, which was a relatively gradual process. Phasing out jobs over a period of decades is a totally different matter to when it happens in years. And suppose many of them will get re-educated to unloading, maintenance, etc. All those software engineers working on self-driving systems are also going to switch to the next problem. So unloading too will rapidly get automated. And these systems will get increasingly advanced, so using them to solve new problems becomes increasingly easy. This means jobs will get replaced not in a linear timeframe, but exponentially. And that is certainly going to cause massive problems.
As someone in the industry who pushes for security, dependency hygiene, and testing, the value of these "cover your arse" approaches are hard to prove to management. So most of the time speed > safety, unless the organization appreciates the underlying problems. Say, industrial engineers don't have much leeway here and will easily extend a project over going at it half way in term of security. Until the software industry is treated as the above (which by then, prob will not be as much of a $$ grab), most of these mishaps will repeat
@@yankeenobonagu6411 - A buffer Overflow, in the Program, or a mixture of Bird Poop and Frozen Water, in an Angle of Attack Sensor! Or, an overlooked Bee stuck in a Static Port! Or ICE (the Frozen Water kind) fully covering the EPR Pitot (Engine Pressure Ratio Static : Dynamic Air Pressure inputs) that the Software Programmer never considered his "Fully Digital System" might need to have a Solution for! (All related to Causes of Airliner Crashes, over the Last 45+ Years! - I'm 62+ and learned to fly starting when I was 18! Many Years worth of TV News, compared to Actual Pilot Records of Accident Investigations, and Understanding that "Professional" does not necessarily mean "Perfect!" Be the Reference refer to Pilots, IR Programmers!)
Yes I know it is terrible I completely agree! This is why I loathe web development. And I call it inconsistent l, uncontrolled bloatware. I simply don’t want anything to do with it! 23K lines for an empty project, you seriously cant think that’s a good idea?! And this is why computers, that are several 1000 times faster than our old micros, run at the same speed, since most of it is limited by the user but a simple “app” (how I hate that word), is 150MB!!! Seriously?! Why?! What for?! The more code the more bugs!!!
I agree it's terrible. Minor nuance: _modern_ web development is awful. In the early days web development was fun. You had html and Javascript - which at the time was a relatively straightforward and simple scripting language. There were no "frameworks", no libraries, no nothing. I'm not even going to bother catching up anymore. These web developers nowadays don't learn to code anymore; they learn to use a framework. And then three months later they can forget about that encyclopedia of API calls to move on to the next framework.
Once again, a glitch in the Intellectual "Matrix" of understanding, between "Capitalism" (the Value of Capital, or Financial Investment) and "Greed" (or Beliefs of Never Ending Increase in Growth, and Profits)
7:20 well i completely disagree. All the stupid people are going to drink themselves to death while anyone with a little bit of sense will not get involved in this nonsense. It'd be like bringing darwin back to the human species after we did our best to save the idiots who do all manners of stupid crap and let them breed where in nature they would've died when they first decided that it was a great idea to put 4 chairs on top of each other to reach the second floor window to give it a new paintjob.
Enjoying all of your talks, thank you
This video resonates with the talk given by "Uncle" Bob Martin from the CZcams video; "The Future of Programming". We as people who write code (especially Professionally), must come up with standards and enforced Discipline. We must self regulate before non-programming bodies come in to regulate us.
This guy is a rock star, he made programming language called RockStar!
Does Dylan goes to every conference specifically to shut it down?
co-wondering. from the art of code
CDs involve software too. Magnetic tapes where the last medium that didn't.
41:40
I thought, all airplanes nowadays have two AOA sensors, but the MCAS only used the pilots side one, which happened to be faulty?
25:18 neither youtube app which is a pity!
Watching this on my 2011 ipad, b plan: open youtube in Safari, it makes the job
Goes to Russia. Talks about Apollo missions.👻
3:26 Small correction. 256 Kilobits, not Kilobytes.
44:00 "what impact is autonomous trucks (and cars and vehicles) going to have on society?" just a guess but i suspect there will not be mass unemployment from this. it will mean that there will be a lot more trucks for a lower cost, and people can move from driving to other truck-related jobs - unloading, maintaining, remotely driving around hazards, etc.
Economies while elastic, do take time to adjust. Do you know how large the number of professional drivers is? Over three million full time truckers alone, this does not count other forms of delivery.
@@JohnSmith-ox3gy technology takes time to be adopted too so i'm not sure what your point is?
This is a common point that a lot of people fall for.
There will be new jobs created, it has always happened. That's how economy works.
I enjoyed the talk though
@@driden1987 But it never happened smoothly. It takes time for an economy to adjust, and the faster a disruptive tech is implemented, the less time there is to adjust. Once the problem of self-driving cars has been solved well enough for deployment, this will go at an unprecedented pace. You can't really compare that to for example the mechanization of agriculture, which was a relatively gradual process. Phasing out jobs over a period of decades is a totally different matter to when it happens in years. And suppose many of them will get re-educated to unloading, maintenance, etc. All those software engineers working on self-driving systems are also going to switch to the next problem. So unloading too will rapidly get automated. And these systems will get increasingly advanced, so using them to solve new problems becomes increasingly easy. This means jobs will get replaced not in a linear timeframe, but exponentially. And that is certainly going to cause massive problems.
As someone in the industry who pushes for security, dependency hygiene, and testing, the value of these "cover your arse" approaches are hard to prove to management.
So most of the time speed > safety, unless the organization appreciates the underlying problems.
Say, industrial engineers don't have much leeway here and will easily extend a project over going at it half way in term of security.
Until the software industry is treated as the above (which by then, prob will not be as much of a $$ grab), most of these mishaps will repeat
;) everybody gangster untill a buffer overflow vulnerability destroys everything
keanu reves cant save you
@@yankeenobonagu6411 - A buffer Overflow, in the Program, or a mixture of Bird Poop and Frozen Water, in an Angle of Attack Sensor!
Or, an overlooked Bee stuck in a Static Port!
Or ICE (the Frozen Water kind) fully covering the EPR Pitot (Engine Pressure Ratio Static : Dynamic Air Pressure inputs) that the Software Programmer never considered his "Fully Digital System" might need to have a Solution for!
(All related to Causes of Airliner Crashes, over the Last 45+ Years! - I'm 62+ and learned to fly starting when I was 18! Many Years worth of TV News, compared to Actual Pilot Records of Accident Investigations, and Understanding that "Professional" does not necessarily mean "Perfect!" Be the Reference refer to Pilots, IR Programmers!)
@@robertweekley5926 there are multiple in the brain mind you...
@@robertweekley5926 OOOH ur a pilot?
I remember the days when people from UK had EU flag icons on twitter.
Yes I know it is terrible I completely agree! This is why I loathe web development. And I call it inconsistent l, uncontrolled bloatware. I simply don’t want anything to do with it! 23K lines for an empty project, you seriously cant think that’s a good idea?!
And this is why computers, that are several 1000 times faster than our old micros, run at the same speed, since most of it is limited by the user but a simple “app” (how I hate that word), is 150MB!!! Seriously?! Why?! What for?!
The more code the more bugs!!!
I agree it's terrible. Minor nuance: _modern_ web development is awful. In the early days web development was fun. You had html and Javascript - which at the time was a relatively straightforward and simple scripting language. There were no "frameworks", no libraries, no nothing. I'm not even going to bother catching up anymore. These web developers nowadays don't learn to code anymore; they learn to use a framework. And then three months later they can forget about that encyclopedia of API calls to move on to the next framework.
oh my god free beer last 4 years (i think might be 5 now) has destroyed my life
my sweat smells like poop pthere is poop in my blood cuz my liver is dying
and i cant shit without tearing another asshole im dying
dying i could die any minute now
13:25 It takes 6 months to draw a jpeg without using libjpeg ? Seems exagerated by a multiple times
Этот код настолько стар, что уже начал пить водку:))
В России код может начать пить водку смолоду
1:12 Проект задерфывлаофыафция
33:00 yeah, ""this is not gonna happen'" cause capitalism xD
Once again, a glitch in the Intellectual "Matrix" of understanding, between "Capitalism" (the Value of Capital, or Financial Investment) and "Greed" (or Beliefs of Never Ending Increase in Growth, and Profits)
7:20 well i completely disagree. All the stupid people are going to drink themselves to death while anyone with a little bit of sense will not get involved in this nonsense. It'd be like bringing darwin back to the human species after we did our best to save the idiots who do all manners of stupid crap and let them breed where in nature they would've died when they first decided that it was a great idea to put 4 chairs on top of each other to reach the second floor window to give it a new paintjob.
The actually leaf pathomorphologically miss because feather synthetically wrap towards a scientific fiction. voracious, bored question
GloboShlomo salesman.
I knew we picked on these kids for a reason