Really, it should be obvious that vehicle operation causes much more emissions than vehicle production. It is actually not "that obvious". The production of a simple car, like a Golf costs energy equivalent to about 30.000km driving that car. The millage varies on type of car and fuel consumption, obviously.
No idea why people fear them. Germany and Japan and Scandinavia (and probably the whole rest of Europe) already has automated nearly everything since 30 years or more.
Just compare how many people work in the car industries in Germany right now and how many it was 40 years ago. It is probably in the 10% range now.
Actually both terms never really were part of the definition:) Self learning in AI is e.g. just a small subset, albeit one that made strong improvements the last decade.
On the other hand in SF or movies AI is often set equal to self aware. However I doubt the computer in Star Trek is selfaware.
There is a misunderstanding. The code usually is sufficiently tested. However there are two reasons to not fully roll it out: there could be a glitch, especially in conjunction with other parts of the system, or simply connecting to the life data. Secondly some systems are so big (e.g. Amazon, Zalando) that it makes sense to gradually deploy the new software and gradually shut down old nodes.
As a developer myself, I think that what we're supposed to be doing is solving problems users have, not making more. And continuous delivery has nothing to do with those 'problems', I'm also pissed that the new iOS has new unwanted unneeded features. But I installed it manually, my fault.
OO models can be mapped 1:1 to relational ones. There are plenty of patterns to achieve that.
The problem comes if you already have an relational DB, which probably evolved and is no longer a pure design, and want to map that to oo.
If you know assembler well enough, you can potentially program circles around the high-level-language people. In terms of development speed, no. The amount of lines of code you write per day is nearly irrelevant regarding to the language. While I might write 100 lines assembly (which would be quite an achievement) per day, 100 lines C++ or Java implement 10 times more functionality.
And I've seen some really productive COBOLers, for example because they knew the language and shop conventions like the back of their hands. So do I with C++ and Java... so what is the point? Accessing CICS systems with COBOL is cooler than using Java and JPA/Hibernate?
It's certainly not for those poor customers who were chosen to be involuntary beta testers They are not forced to use the new functionality. And sooner or later they get it anyway, what has that to do with "continuous delivery"?
and it's also not for the rest of the customers who have to deal with software that is constantly changing underneath them. Software is constantly changing. Deal with it.
That is incorrect. The USA are not the 'most english speakers'.
From the head of my mind we have Canada, UK, Australia, Newsealand and.... India. Then there are plenty of states like Belize or Grenada that mostly speak english, or half or Kamaroun... now I could be nitpicking and point oit that basically every European below age of 50 and above 10 speaks english as a second language:)
I always sit backwards in trinas, for exact that reason:) And if I'm in the restaurant and have a beer in front of me, I prefer it not falling away from me, albeit if it would drop on me it would be more nasty. Anyway, the beer is usually secure.
Looking out if the window, I like it if I ride backward. Somehow if something catches you attention you can watch it for quite a while.
Well, 'continuous delievery' is a term with a defined meaning. And releasing phone apps with unwanted UI/functionality in rapid succession is not part of that definition. Continuous delievery basically only is the next logical step after continuous integration. You deploy the new functionallity automatically (or with a click of a button) when certain test criteria are met. Usually on a subset of your nodes so only a subset of your customers sees it. If you have crashes on those nodes or customer complaints you roll back. The level of 'how good is it tested', 'is it QA aprovedx' etc. can vary endless.
I don't see a reason why that would not work for embeded likewise. Especially when the final deployment is done via a click of a button. You automate everything and leave a manual gateway at the final step.
Acceleration is no problem. You are just pressed into the seat with a bit more than your "weight". Deceleration is however, as you will fly into the front of the cabin with more than earth gravities acceleration. So you better have safety belts.
Why should users not like it? If you shop on amazon you don't know if a specific feature you notice today came there via continuous delivery or a more traditional process.
The light detecting cells indeed get triggered by a single photon. But there are two obstacles: the photon could be absorbed by the lense or protective skin over the eye lense. Or it simplybdoes not hit cell, but fluids around it. And: usually single photon events are filtered out by the nerve system.
Ordinary trucks with drivers have the requirement to have a safety distance to the car/truck in front of them. In Germany the rule of thumb is, divide speed (in km/h) by 2 and replace km by m. So you drive 100 km/h fast, you should have a safety distance of 50m.
However the chained trucks drive in a thumbwidth distance of each other.
Slashdot Mirror
Really, it should be obvious that vehicle operation causes much more emissions than vehicle production.
It is actually not "that obvious". The production of a simple car, like a Golf costs energy equivalent to about 30.000km driving that car. The millage varies on type of car and fuel consumption, obviously.
That is exactly what a robot is.
No idea why people fear them. Germany and Japan and Scandinavia (and probably the whole rest of Europe) already has automated nearly everything since 30 years or more.
Just compare how many people work in the car industries in Germany right now and how many it was 40 years ago. It is probably in the 10% range now.
Actually both terms never really were part of the definition :)
Self learning in AI is e.g. just a small subset, albeit one that made strong improvements the last decade.
On the other hand in SF or movies AI is often set equal to self aware. However I doubt the computer in Star Trek is selfaware.
There is a misunderstanding. The code usually is sufficiently tested.
However there are two reasons to not fully roll it out: there could be a glitch, especially in conjunction with other parts of the system, or simply connecting to the life data.
Secondly some systems are so big (e.g. Amazon, Zalando) that it makes sense to gradually deploy the new software and gradually shut down old nodes.
As a developer myself, I think that what we're supposed to be doing is solving problems users have, not making more.
And continuous delivery has nothing to do with those 'problems', I'm also pissed that the new iOS has new unwanted unneeded features. But I installed it manually, my fault.
So the QA then would click the button to trigger the last step: automatic delievery/deployment.
The problem is that automated testing is no substitute for a QA team.
The QA team is supposed to provide the automatic testing.
Why don't you check out "shops" that actually do "continuous delivery" instead of boring us with your nonsense rants?
This is a long video, you will find shorter ones coming to the point of continuous delivery more quickly.
https://www.youtube.com/watch?...
Zalando is the only company I know that has realized it and is marketing, positioning itself, as an IT company, not as "a shop".
If a product manger/PO has an idea, it can be less than a day that the software is deployed in the cloud and "make money".
They actually are not doing Scrum anymore as traditional Scrum is not agile enough.
That is a misconception.
OO models can be mapped 1:1 to relational ones. There are plenty of patterns to achieve that.
The problem comes if you already have an relational DB, which probably evolved and is no longer a pure design, and want to map that to oo.
If you know assembler well enough, you can potentially program circles around the high-level-language people.
In terms of development speed, no. The amount of lines of code you write per day is nearly irrelevant regarding to the language. While I might write 100 lines assembly (which would be quite an achievement) per day, 100 lines C++ or Java implement 10 times more functionality.
And I've seen some really productive COBOLers, for example because they knew the language and shop conventions like the back of their hands. ... so what is the point? Accessing CICS systems with COBOL is cooler than using Java and JPA/Hibernate?
So do I with C++ and Java
Why do you consider this to be a good thing?
Because it is?
It's certainly not for those poor customers who were chosen to be involuntary beta testers
They are not forced to use the new functionality.
And sooner or later they get it anyway, what has that to do with "continuous delivery"?
and it's also not for the rest of the customers who have to deal with software that is constantly changing underneath them.
Software is constantly changing. Deal with it.
That is incorrect.
The USA are not the 'most english speakers'.
From the head of my mind we have Canada, UK, Australia, Newsealand and .... India. Then there are plenty of states like Belize or Grenada that mostly speak english, or half or Kamaroun ... now I could be nitpicking and point oit that basically every European below age of 50 and above 10 speaks english as a second language :)
I always sit backwards in trinas, for exact that reason :)
And if I'm in the restaurant and have a beer in front of me, I prefer it not falling away from me, albeit if it would drop on me it would be more nasty. Anyway, the beer is usually secure.
Looking out if the window, I like it if I ride backward. Somehow if something catches you attention you can watch it for quite a while.
Well,
'continuous delievery' is a term with a defined meaning. And releasing phone apps with unwanted UI/functionality in rapid succession is not part of that definition.
Continuous delievery basically only is the next logical step after continuous integration.
You deploy the new functionallity automatically (or with a click of a button) when certain test criteria are met. Usually on a subset of your nodes so only a subset of your customers sees it. If you have crashes on those nodes or customer complaints you roll back.
The level of 'how good is it tested', 'is it QA aprovedx' etc. can vary endless.
I don't see a reason why that would not work for embeded likewise. Especially when the final deployment is done via a click of a button. You automate everything and leave a manual gateway at the final step.
Acceleration is no problem. You are just pressed into the seat with a bit more than your "weight".
Deceleration is however, as you will fly into the front of the cabin with more than earth gravities acceleration.
So you better have safety belts.
The second law of thermodynamics is: entropy is increasing over time.
So your explantation is wrong.
However all laws of thermodynamics imply that you cannot recover heat energy completely.
Why should users not like it?
If you shop on amazon you don't know if a specific feature you notice today came there via continuous delivery or a more traditional process.
Your parent simply does not know how short a mile is :D
No it would not :D
A continuous delievery pipeline has as much AI as a nematode has natural inteligence ... probably even less.
I write a bit nee Java code nearly every day ;)
Dalvik is a bytecode specification and a VM, not a language.
Of course you program in Java, the language, when you code for the Dalvik VM.
Would you care to explain what the second law of thermodynamics has to do with friction?
Not finding gravity waves with LIGO would not have 'falsified' GR theory.
The light detecting cells indeed get triggered by a single photon.
But there are two obstacles: the photon could be absorbed by the lense or protective skin over the eye lense. Or it simplybdoes not hit cell, but fluids around it.
And: usually single photon events are filtered out by the nerve system.
The trucks drive behind each other with less than a hand span of distance.
Ordinary trucks with drivers have the requirement to have a safety distance to the car/truck in front of them.
In Germany the rule of thumb is, divide speed (in km/h) by 2 and replace km by m.
So you drive 100 km/h fast, you should have a safety distance of 50m.
However the chained trucks drive in a thumbwidth distance of each other.
I hope he cataloged and tagged it properly or he never finds his most favourite again.