3 ms·
Well no, please let’s not be enemies. So let me start by saying I have a ton of admiration for the work you’ve done based on that resume - I agree it’s a worth
by jameshart 5y ago
Well no, please let’s not be enemies.
So let me start by saying I have a ton of admiration for the work you’ve done based on that resume - I agree it’s a worthy contribution and you should be proud.
But please don’t mistake my original reaction as being to your actual body of work, but rather to your initial characterization of a method of delivering software.
In particular you were characterizing a development approach of ‘one hard-to-replace cranky old guy’ versus ‘a team of cheap easily replaced inexperienced devs’ - as being alternatives a manager could choose between in order to get a project done. And casting your vote in favor of, it seems, the solo craftsman.
If you are going to really recommend that people who want software developed should, in general look for a highly skilled individual developer to solo the project and leave it in a state where it will take a lengthy dedicated search to find anyone capable of modifying the resulting code, then I’m sorry if my reaction to that was to (perhaps with more sarcasm than is strictly constructive, but we are all performing for a crowd when we post on the Internet) try to suggest that that might not be a particularly universal or sustainable model.
If that isn’t actually how your project operates - with a business funding the development and having the power to choose between those approaches - then my critique doesn’t even apply to your project, so you have no reason at all to take the criticism personally. I am not my code, and I am also not the examples I use in discussions on the Internet.
- ChrisMarshallNY 5y agoWell, I'll admit that "the cranky old man" trope was a bit of a deliberate goad, on my part, but that's mostly because this is pretty much how I am always perceived. It's really sad, because it's very far from the truth, and, if people spend more than thirty seconds, skimming what I write (and I know that I'm prolix), they can figure out that's not me. If you check my LinkedIn, you'll see a ton of testimonials, from folks I've worked with, over the years, saying how rewarding our relationship was. I will admit, 100%, that I'm a "Quality nut." I consider my work to be a craft, and I take tremendous personal pride in it. If it requires advanced techniques, to achieve the ends, then that is what it takes. I generally don't even bother setting up a bug tracking system for my work, as there are so few issues. GH Issues is generally fine. I will also admit, 100%, that I'm pretty appalled at what passes for "quality code," these days. I won't go ripping into the works of others; especially if it earns them money, and people are willing to pay for it, but just because everyone else does it, is no reason for me to do it; even if it means that I do it alone. The project that I'm working on now, I describe as "ambitious." That means that it is "ambitious" for me[0]. To many folks, they wouldn't even dream of a single person, writing something of this magnitude, but I do stuff like that, on a regular. I've been shipping stuff, for my entire adult life. Because it was written by one single person, from napkin sketch, to shrinkwrap, it has great integrity, and extremely high Quality. There's good people out there. There always have been. They do great work; usually orders of magnitude better than "average" work. It's worth it to track them down, and to hang onto them. I managed a guy that is "on the spectrum." He could be difficult to manage, but we worked together for almost 27 years; 25 of which, I was his boss. He was better than I will ever be, and still is (just not working for me). It was a privilege and an honor to work with him, and to have him as an employee. He had a high school diploma, and regularly stunned the Ph.Ds in Japan, with his work. It, too, was pretty inscrutable code, but it was also often 100X faster and more accurate than stuff done the "average" way. [0] https://littlegreenviper.com/miscellany/thats-not-what-ships-are-built-for/ https://littlegreenviper.com/miscellany/thats-not-what-ships...