meunierc
Vote with your dollars.
Supposing the current implementation is extremely successful, it would be the equivalent to signing up for a monthly service with Disney (or Sony Entertainment, or <insert your favorite content megacorporation name here>) : you pay the middleman, who redistributes appropriately to the content creators.
What's the problem here? This month if I want to buy 1 or 20 CD/DVD, I choose how much money I give. With the monthly service model, my entertainment disposable revenue gets converted to monthly preauthorized payments - along with all my utility bills. Not good.
Your first response was perfect IMO.
In situations like this you need to manage a person, not software nor a project. If he's in a sibling reporting branch, you may want to discuss the situation with your lead. He may decide to go ahead with the modification in the interest of good relations. If he does, you must understand this is not a judgment from your lead on the quality of your work.
Sometimes I prefer taking care of somebody's computer, precisely because they might break something. Nowadays you can still burn an LCD if you neglect the screensaver and powersave (10'000 hours backlighting MTBF can really fly), or burn a nice annoying image in your display. You can mess up your Windows installation pretty bad if you play in the wrong places. And don't get me started on giving root access to grandpa. I don't see much value for some people in learning to rebuild an OS installation from scratch. Like with kids there are times to encourage experimentation, and there are times to be cautious.
There's a whole school of thinking that value safety first. About 15 years ago there was a bold data entry clerk that wasn't afraid of fixing problems by himself. Faced with 2 waypoints called "R", he decided to encode one point as "ROZO" and the other as "R". As a consequence an aircraft turned into a mountain en route to Cali, Colombia.
Toyota, presumably because of sloppy programming in a cheap microcontroller, is learning that when you take somebody's code without looking, you get all his problems too.
It's fun to take risks sometimes, go into uncharted territory, put yourself in a situation to be exposed to new unfamiliar things.
But please, don't make it a point of being careless.
If you like attacking, Aikido is not for you though. The movements are strictly defensive.
That was 30 years ago this year, today I design aircraft simulators and automated test systems for aircraft computers. The methodology has never changed: aim high, with a goal you will enjoy a lot.
edit: to your second question, I have this to offer: there's nothing more I wish I had known when I started. I'm actually very glad I didn't consider theoretical questions too early. "Programming" is no different a language than Spanish, Japanese or Russian (maybe a tad more formal). To program you need to learn to give directives to a machine. Designing a system is something else, which uses a completely different skill set, and the entry point to that is being able to talk to the machine.
So my only advice could be: if you really want to be a hard-core computer nerd, stay with "programming" for 7-10 years, then learn (at least at overview level) all the important design principles. You'll then be able to choose according to your personality.
> someone who stares quietly into space for a few minutes
...and exactly here lies the problem. I've been fired from a job because according to an old retiree who never saw anyone programming before, "he spent his days scratching his beard and looking blankly at the screen". No mention about the job being done and the extra $1M my ideas saved. And certainly no apologies after they had to replace me by a whole external company.