4 ms·

Ozone is created by extreme events during lightningstrikes and reduced by it reacting/beeing bound otherwise. So yes, there is a natural cycle, with slight vari

Ozone is created by extreme events during lightningstrikes and reduced by it reacting/beeing bound otherwise. So yes, there is a natural cycle, with slight variances around the norm. I cant wait to see my bosses eyes- when i expand this theory of irresponsibility for everything upon bugs. There is a natural occurance rate of bugs and a natural error rate in software. To try and meddle with it- or to blame developers for it, is just plain wrong and nearly as insane as environmentalism. Sometimes in the morning, you can smell it in the air- the distinct taste of lazy.

bluejekyll 9y ago
I disagree with this analogy. As software engineers become more experienced, they start avoiding patterns or obviously flawed software constructs which they recognize as potentially creating bugs in the future. Things like marking fields of objects final/const, requiring immutability of objects, reduce bugs interior to objects. Immutable objects also reduce multithreading issues. That’s one pattern that can be used to reduce common bugs. Nature doesn’t do this. For example: Southern California has a fire season (natural) followed by a wet season (natural) which tends to cause sever mudlides. These natural processes never learn from experience that large fires before the rain is more destructive (I know I’m stretching here and fires would be smaller if we didn’t put down the small ones initially). My point is that humans, software engineers included, learn from past mistakes. Ideally we improve from those, not just throw our hands up and say bugs are a “natural” result of the software development process. Software will always have bugs, but ideally you as an engineer never make the same one twice (with the exception of off by one errors ;)

4 ms·

Ozone is created by extreme events during lightningstrikes and reduced by it reacting/beeing bound otherwise. So yes, there is a natural cycle, with slight vari

by WillReplyfFood 9y ago

bluejekyll 9y ago
I disagree with this analogy. As software engineers become more experienced, they start avoiding patterns or obviously flawed software constructs which they recognize as potentially creating bugs in the future. Things like marking fields of objects final/const, requiring immutability of objects, reduce bugs interior to objects. Immutable objects also reduce multithreading issues. That’s one pattern that can be used to reduce common bugs. Nature doesn’t do this. For example: Southern California has a fire season (natural) followed by a wet season (natural) which tends to cause sever mudlides. These natural processes never learn from experience that large fires before the rain is more destructive (I know I’m stretching here and fires would be smaller if we didn’t put down the small ones initially). My point is that humans, software engineers included, learn from past mistakes. Ideally we improve from those, not just throw our hands up and say bugs are a “natural” result of the software development process. Software will always have bugs, but ideally you as an engineer never make the same one twice (with the exception of off by one errors ;)