3 ms·
What were the main arguments back then?
by bumby 7y ago
What were the main arguments back then?
- PaulDavisThe1st 7y agoWell, there were a couple that I remember. 1) programming is more like an art than a science, and so should not be regulated like engineering 2) the capital/labor requirements for programming are minimal - basically anyone could do it - so we should not worry about trying to license something that people could (and do) do at home. 3) there's no agreement about what would be required to get a license. 4) free software would die Of course, some of these really do not hold up to close inspection. It's true that there is an "art" to programming, but not much more than there is in architecture for example, and there's no reason you couldn't require a license for cases where you do work for others rather than yourself. Since the 90s, it's become a _little_ more clear what the components of a s/w dev license might be, but perhaps still not enough to really pin it down. And yes, it would probably kill the free software world.
- bumby 7y agoI wonder if they could parallel other engineering disciplines and give exemptions for specific areas or other avenues to ease the burden. For example, as long as a certain percentage of principal engineers are licensed, others within the company don’t have to be. Similar with working under a licensed lead or specific article industry exemptions. It would also give some power to the developers over management in key decisions. I’ve seen managers try to back engineers into a corner and when the engineer ultimately said they wouldn’t sign off on a design, management backed down because they didn’t have an equivalent to “just ship it now” and get it stamped later. I understand the fear of it, but sometimes it seems like the sw development is run like the Wild West.