How much time do you spend worrying about them?
Zero. That's the point. I'm paying to not worry; it's the farmers job to think about these things.
And as a privileged westener with the ability to pay extra for the non sustainable "organic" food. Why wouldn't I?
I dunno
So any time you purchase anything you make sure that every element from every part of the supply chain is 100% sustainably, and ethically sourced? That you own nothing that every other person in the world can not access? That every single thing you do or consume could be scaled out to every single person on the planet?
A nobel endeavour if so; but somewhat arbitrary if you're just picking and choosing when it's convenient.
I don't know enough about physics to know if there was any merit in mikael's comment that "electromagnetism" might be responsible for alignment (is it even worth considering?). Sadly the physicists only responded to the conspiracy guy, so no informative feedback. In my memory, Slashdot used to be different, but perhaps it was always thus.
I repeat, not one of these links talks about electricity in space, or plasma filaments, or whatever it is that seems to upset everyone. They just appear to be talking about some kind of galactic rotational alignment that was unexpected. Which is interesting dammit! How is that not interesting? Who cares if it's
Which is interesting.
I'm not an "electric universe" supporter, or whatever this stupid argument is about. I just saw links to an interesting cosmic phenomenon, and went "interesting!". Apology?
Your response, however, is simply condescending and adds no value.
So here's the thing. I'm not going to tell you how to do your job, but I think you may be making a mistake in your assumptions here. Software development is fundamentally different from the traditional engineering with which you would be familiar. I know this because I have done both.
If something is documented properly then actually implementing it will generally take a minority of the time.
Completely false. I have worked in both heavy and light documentation environments. Heavy waterfall style process as well as agile. The implementation is always the longest leg.
Code can be a form of documentation but the most reliable software out there spends a LOT of time on documentation that is not code.
Do you count the code you use to help run your plant? If you use PLCs or SCADA, have you thought about the companies that make that software? Chances are that I know, work with, or am the person who wrote that code. The kind of process that you are familiar with that happens inside your plant does not happen with the software on which you run your software! And it's not going to be consistent across the board from the one company either. What's required for the PLC, documentation wise, is very different from what is required in the SCADA.
The notion that you can do non-trivial tasks without having substantial proper documentation is just absurd.
My experience would suggest otherwise, its a funny old world.
FORTRAN is not a flower but a weed -- it is hardy, occasionally blooms, and grows in every computer. -- A.J. Perlis