If your guild actually had some basic education and standards for what constitutes "professional quality code" independent and irrespective of the marketing buzzword du jour, as well as some good-quality continuing education to keep up with the technology behind the latter, it might actually benefit you, people who want to learn to code, and ultimately the employers who want to hire coders.
But as it stands now, the entire high-tech industry has acquired such a fly-by-night mentality that I don't think there's any demand for "professional quality code". The demand is "do a marketing blitz quick ship it out the door before the hype dies down and let me collect my bonus and move on to the next project." The hubris and arrogance that seems typical of developers themselves doesn't help either. Whether non-coders could or should or would code is a totally minor side-issue, given the amount of professional-quality enterprise-grade crap software out there.
I'm one of those non-coders who code -- I end up writing a few scripts in Perl or PHP or Javascript or R or whatnot for miscellaneous tasks, but I don't want to be a programmer. I'm just glad I get to put my education to use and develop my skills in a different industry, where there isn't quite so much nonsense to put up with.
Maturity is highly overrated.
Vulgar, foul language is not an indication of maturity. On the contrary, it seems to be more closely associated with the pot-smoking, meth-addled, lip-ringed, tongue-pierced, ear-stretched, purple-haired, and tattooed youth of today who can't even keep up with today's abysmally low educational standards, or hold down a job even if the world's economy depended on it.
So can you get two tickets, one for obstructing traffic and another for speeding, if you're doing both at the same time?
Yes you can, but both tickets must be tried at the same hearing, because
... [no] person [shall] be subject for the same offence to be twice put in jeopardy of life or limb;
...
Generally, that's what 'privacy' comes down to; you want to break some rules (laws, road rules, social norms, whatever) or at least to have some chance of getting away with doing so.
That's the tired old something-to-hide argument against privacy. Way too many powerful corporate and government entities know each one of us in way too intimate detail, and we know next to nothing about these entities. Nor do we need to violate any laws or social norms in order to accumulate vast quantities of private information which could easily be used against us maliciously if misappropriated. Then there is the problem that the supposedly well-meaning people or entities who snoop almost invariably meddle in some way with what they are snooping into, because such people simply aren't going to "look but not touch," (which all goes back to money and power,) and consequently the only way to avoid the meddling is to not let these busybodies know about your private affairs in the first place.
Once automated law enforcement is implemented, people will start realising just how important discretion is, or alternately, just how many laws should be fixed or repealed.
By that time it will be far too late. Try a slightly different situation on for size: do you think the people of, say, North Korea realize "how many laws should be fixed or repealed"? and would it do them any good if they did?
the marketing potential, as Darling notes, may be significant.
I'd think people were insane to discuss with a straight face such science-fiction drivel as "rights" for robots, but I can just see the greed of Apple's visionaries dreaming about this. This recent ascendency of the Apple cult is one of the most horrifying, bizarre, and sickening phenomena that I have ever witnessed. Is there no limit to how high Lucifer will elevate his throne?
Let me say, CRC32 is a very good algorithm. So good, I'll tell you how good. It is 4 bytes long, which means in theory you can change any 4 bytes of a file and get a CRC32 collision, unless the algorithm distributes them randomly, in which case you will get more or less.
I naively tried to reverse engineer a file from a known CRC32. Optimized and recursive, on a 333 mHz computer, it took 10 minutes to generate the first collision. Then every 10 minutes or so. Every 4 bytes (last 4, last 5 with the original last byte, last 6 with original last 2 bytes, etc) there was a collision.
CRC is only good for what it's designed for: to detect random bit-flipping errors due to noise. It has no cryptographic properties whatsoever. CRC is nothing more than polynomial long division mod 2. It really is nothing more than a straightforward algebra problem to modify the 4 bytes at any given position in any given file to generate any desired CRC32 checksum. Brute force is totally unnecessary.
Those who can, do; those who can't, write. Those who can't write work for the Bell Labs Record.