Consumers haven't pushed back enough to stop this from happening.
The classic example of rent-seeking, according to Robert Shiller, is that of a feudal lord who installs a chain across a river that flows through his land and then hires a collector to charge passing boats a fee to lower the chain. There is nothing productive about the chain or the collector. The lord has made no improvements to the river and is not adding value in any way, directly or indirectly, except for himself. All he is doing is finding a way to make money from something that used to be free.[4]
The 'river' that manufacturers are putting a chain across is the First Sale Doctrine.
It's just rent-seeking wearing a mask. In a similar sense that the legal difference between a pyramid scheme and an MLM scheme is that the MLM scheme is accompanied by a good or service. Legally legitimate, but still morally objectionable.
It definitely feels like "big business" is working against us in this regard. Everything new is locked down because the the rent-seeking those software locks enable. It's a drag on our economy and we've got to stop letting them do this to us.
I stumbled across open source ag / construction efforts years ago, but haven't kept tabs on them since.
And thanks for spending your time on something so useful to society!
And thanks for the kind words! I have been pretty sick of working jobs that don’t broadly benefit society. I’m blessed to be working at a beautiful farm on open source tech!
I think they are still iterating a fair bit on the micro tractor. But overall it seems there was a flurry of activity around 2014 but then it has tapered off.
IMHO, I think they set their sights a bit too high, with the whole construction set. Would have been better to focus on just the tractor first, getting the documentation really hammered out. It is such an essential piece of farm equipment. But as it stands, nothing on their wiki is really viable to contribute to, because you can't really work off of it.
This one sticks out to me from a job-market POV.
Plumbers are already on par with psychiatrists in terms of pay. Sure, the work is hard, but from a supply-demand POV, the markets are saying that they do work that is of equal value (all this varies highly, but stick with me here).
Most repair work takes a LOT of experience until the employee is anywhere near proficient. Farmers will tell you that they learned the repair side in very stressful situations and that there is always something that breaks in new, and more expensive, ways each and every time. Repairing even 'simple' machines like a tractor takes a lot of experience.
So, when you add in a computer that intentionally 'breaks' the machine, and then you have the regular machine that will break, and then you have all the linkages that make the computer control the machine (all of which can break), you are requiring that the repair-person be VERY skilled at troubleshooting and repair.
Then, you eliminate most of the ways that people learn to troubleshoot and repair these machines (via these computers), and you are left with even fewer people that will be able to fix the tractors. Think something more like a bio-tech/MRI company's field-service engineers. Those people get paid bank to get sent out to malfunctioning machines and they are trained out the wazoo.
From the tractor manufacturer's perspective, yes, making machines that work for the manufacturer and not the customer, is going to really work out well for this quarter's stock price. But down the road 7 years? I think this is a poison pill.
It's also a little misleading to compare the numbers that way. It usually takes a lot longer to become a psychiatrist in the first place. Your cumulative earnings in the first ten years after graduating high school might be higher as a plumber; in fact, I suspect most people who become doctors actually lose net worth throughout those ten years due to student loans. They just don't count towards the median income for a psychiatrist because they spend much more time not being a psychiatrist.
Once the plumber and psychiatrist are both in a position where they're running their own business or practice, their income is more of a conscious choice than it is for someone who's working for an employer. Self-employed people can and do sometimes choose to earn less money in exchange for more free time, and it's a lot easier to do that when you don't have six figures of debt at the start of your career.
Plumber median pay is $54,000, while 10% make more than $94,000.
Psychiatrist median pay is $220,000, while 10% make beyond the wage cap for BLS data. https://www.bls.gov/oes/current/oes291066.htm
If the market demands it, which with the advent of computers on tractors platform this can and will be modified to allow for the maximum utility for the end user. I see nothing wrong with this.
I don't want a bridge where someone can make repairs the way we make shitty pothole repairs now. I don't trust them to get it right. I don't want to pay taxes for a bridge that tries to kill me after mandatory repairs. It's not needed, and it's a bad idea. https://en.wikipedia.org/wiki/I-35W_Mississippi_River_bridge
Here's a neat idea: maybe regulating software engineering like other engineering disciplines is actually overdue? Yet at the same time, failure rate will never be zero.
Alternatively, we should renounce all engineering regulations and let anybody with a rivet gun build bridges. and airplanes.
I realize that this kind of misquoting is a traditional "hacker" style of debate. But speaking only for myself, it really rubs me the wrong way.
If you disagree with someone, don't resort to cheap shots like that. Make your point in your own words and with your own logic. You will have a stronger argument and a better chance of informing and educating the rest of us.
Please could you describe this more? I’m intrigued.
I don’t know anything about this and what systems or mechanisms are used to regulate engineering, so any links or simple explanations are appreciated!
If you want to e.g. build a bridge it needs to be signed off on by an appropriately licensed and qualified Professional Engineer. Essentially the parent comment is saying there should be streams of software development that meet the requirements to become a Professional Engineer. Then places e.g. medical, defence, power plants could say "we need software that's been signed off by an engineer" and have assurance that the final product is of a known quality and unlikely to have any life and safety endangering defects. They are strongly incentivised to only sign off on properly engineered projects as they can be held personally liable e.g. if a bridge fails and kills someone.
An example of the level of quality that would be delivered is the software that ran on the space shuttle. See this article https://www.fastcompany.com/28121/they-write-right-stuff for an insight into how it was developed and the practises required.
I don't think all software developers should be software Engineers, but being able to lead a team to enforce quality (and not sign off on poorly thought out "MVP" crapware) would guarantee that the software that came out of that team would be reliable and well designed. It would be good for software engineering overall to be recognised as a legitimate branch of engineering. Unfortunately it seems like most of the industry does not have the sort of rigour needed for engineering tasks.
I think the only way this could happen would be if SWE only used waterfall or some similar kind of practice. Agile and the like might be able to be tweaked to work, but even there...
The problem in software is that you can basically "start in the middle" of something and work your way outward; start coding something, get the design details later and refactor.
You can't do that with a bridge or other regular engineering work. You have to plan, design, multiple sign-offs, etc - then build, and you can't build it randomly or a component here and there then fit it all together (well, you can to an extent, depending on the project and design), and if anything changes - well, in a real project it can't change much, not without a lot of money and time being lost.
Several years back there was a series of commercials on TV, I think for an insurance company, which showed (using CGI effects) "impossible building strategies" - one showed a huge scaffolding structure and cranes building something like the Great Pyramid from the top downward (for instance); I think another had some kind of skyscraper being built from the middle outward or something of that nature.
That's essentially SWE applied to regular engineering - or at least, that's how it feels at times. Now tack on Agile and other practices, and it gets 10x worse. Actual engineering is a strict discipline, starting with almost set-in-stone practices along with a lot of hard-won knowledge about materials and mechanics (books filled with tables and diagrams), that are then all used to inform an engineering design, which is then tested and retested in simulation, perhaps coupled with scale models that are also tested, and the plans changed and signed off by multiple other engineers, etc - long before it ever gets to building the thing.
And then that thing is built in a very specific and strict manner; I won't further belabor the point.
Even with all of this, sometimes things fail terribly.
Today in software, we have a ton of tools and practices we are constantly trying - and despite all of them, at least from my perspective - things really haven't gotten much better than they were 20-30 years ago. I would say that widespread use of software versioning tooling and testing frameworks, etc (plus automated build and deployment) have made some of it better - but even after all that, we still seem to be making the same number of bugs and errors that we had before (and rather than a QA department usually, we've farmed this out to the end user for the most part).
So while I'd love to see SWE become more like regular engineering practices (with the selfish request that I and others like me could be "grandfathered" in, as I don't have any kind of compsci or comparable degree, but I have been doing this for 25+ years) - I just don't see it happening for the above rational and reasons.
I could be wrong, though (and if anyone has a counter argument, please post it - I'd love to read it)...
It's a problem for a lot of reasons. First off it's the complete death of ownership. I can't fix things. At some point they will probably just lock stuff back down if I want to sell, assuming I can even sell without them getting a cut.
Second, repairability takes a nosedive. It's no longer a tough but simple piece of machinery that I can maintain indefinitely with some mostly fairly easy to teach skills. I'm an amateur, but I know enough about how cars work that I'm willing to try and fix most issues, up to the point of needing specialized tooling. Instead it's a world of more expensive parts, DRM, and things that just won't work without a dealer authorized repair.
Then we get to the part where I come off an old fuddy duddy. I don't want a car where someone can push safety critical changes the way we push shitty software updates now. I don't trust them to get it right. I don't want to be sold a car that tries to kill me after a mandatory software update. It's not needed, and it's a bad idea.