4 ms·
I've always enjoyed the gems that people mine from his blog. I'm big on Quality. Damn near obsessive about it. I worked for a company that was renown for Qual
by ChrisMarshallNY 5y ago
I've always enjoyed the gems that people mine from his blog.
I'm big on Quality. Damn near obsessive about it.
I worked for a company that was renown for Quality. They were (and will be, for a while), one of those brands that is basically synonymous for "Quality."
They got there by a combination of really heavy-duty, enforced process, combined with some awesome "tribal knowledge." They have been doing it for over a century.
But it was not a good fit for software development (they make hardware). Way too inflexible.
Since leaving that company, I've been trying out some ideas that I had, as I worked there. For the most part, these ideas have been working -quite well; but I haven't really had a chance to scale them.
But software quality, these days, sucks like a supermassive, galaxy-core, singularity. It's reached the point where our entire culture is acclimated to crap software, and we even punish efforts to improve it.
Something needs to be done, and I've found that small, commonsense habits can go a long way towards that.
If we watch a craftsman at work, we will see them do lots of little things, that we barely notice (and that they, themselves, barely notice, as they are habit). These little things are what makes their work "Quality."
When they have an apprentice, they are forced to inventory their habits, and articulate them. That's one reason why martial arts schools make their senior belts train junior belts. It's also why I think that today's engineering culture of "24 months, max" at corporations is pretty corrosive to Quality.
I've found that writing my code, as if I am going to be using it to train someone else, and doing it long enough to develop Quality habits, helps me to do a better job on it.
- keeganpoppen 5y agoi'm assuming from the subject matter and the capitalization of 'Q' in "Quality", that you have read Zen and the Art of Motorcycle Maintenance? (if not... let's just say you are in for a treat :^)
- ChrisMarshallNY 5y agoNo, but I think I should get around to it. Been hearing that, for ages. I capitalize “Quality,” because I consider it a Core Tenet of my personal philosophy. I picked that up from that company I mentioned. I often wanted to strangle the inflexible, stubborn bastards, but I have always been in awe of their singleminded focus on Quality.
- themodelplumber 5y agoQuality, aka other naughty things like "subjectivity" and "introversion" (Jungian). Seth is also breezy and appropriately shallow in the quantitative sense. He strikes a nice balance.
- vbtemp 5y agoWhat you wrote is really interesting. I too was in a software group at a "hardcore" engineering institution for a while and took just a bit of that rigor with me throughout my career - and have often been seen as the "quality" guy because of it. > It's also why I think that today's engineering culture of "24 months, max" at corporations is pretty corrosive to Quality. This is something I think a lot about. The problem is this is the incentive gradient that is an emergent effect. Obviously, if it was generally in organizations' interest to retain people, there would be some kind of incentive sink to keep them there (i.e., everyone would stop finding more competitive compensation at other companies).
- ChrisMarshallNY 5y ago> The problem is this is the incentive gradient that is an emergent effect. Obviously, if it was generally in organizations' interest to retain people, there would be some kind of incentive sink to keep them there (i.e., everyone would stop finding more competitive compensation at other companies). It's cultural. The tech scene has turned into a "gimmegimmegimme" culture. People have been incentivized to live a lifestyle, and hold values, that are commensurate with significant wealth. My secret is that I've lived like a pauper, my whole life. It has earned me many sneers, but I don't really care. That would not be the case for a lot of people. I'm kinda weird. In my case, I have found that shallow excess is not actually very satisfying, but no one wants to hear that. I'm told that "I'm just jealous, because I don't have it." There's also tremendous cynicism; for good reason. Corporations try to sell asceticism, so they don't need to pay their developers (so their corporate officers and shareholders can live large). I know that there are "compensation consultants" that specialize in synthesizing low salary scales, so corporations can feel justified in offering a pittance. There was that collusion thing, in SV, where all the big companies colluded to suppress salaries. That goes a long way towards earning respect and loyalty. </s> Until there is less of a cultural "pull" to excess, there will always be people using money to "keep score." The recording industry figured this out, long ago. Most of the excess that you see musicians (at least, ones getting started) living, is actually owned by their recording company. If they leave the recording company, they lose the crib and the ride. Sort of a seven-figure "company store." I think that fostering an atmosphere of simple, basic respect would go a long ways towards retaining talent. True Respect; not "pretend" respect. Most folks that run companies have very little respect for their employees, and that makes it easy for employees and applicants to justify holding their feet to the fire, compensation-wise. It's really the only leverage that a lot of folks have. They hate me anyway, so why shouldn't I make them pay for it? I think this is obvious in the ridiculous hazing rituals that masquerade as job interviews. Corporations go to drastic lengths to make it plain that they are the ones in charge of the relationship, and that applicants are, in reality, supplicants. This results in cynical people that learn to manipulate the hazing process, and extract what they want; with absolutely no respect or loyalty to the people that deliberately humiliated them, on the way in. I can't say that I blame them. No pride of ownership or craftsmanship. No loyalty. No incentive to leave a legacy. Just "smash and grab." I'll be gone in a year, so why bother writing software that's maintainable? It won't be my problem. It's a very different world, from when I had been doing the interview circuit. Also, as long as customers (including B2B customers) are happy with dreck, then dreck, they get. Why bother putting in the considerable extra cost for Quality, when the suc- um, customers, will be happy with garbage?
- kqr 5y ago> It's also why I think that today's engineering culture of "24 months, max" at corporations is pretty corrosive to Quality. There's an even simpler reason: learning requires feedback. Feedback on some meaningful decisions takes years to come back in. Without it, no learning.
- ghoward 5y ago> Something needs to be done, and I've found that small, commonsense habits can go a long way towards that. I agree, but I would like to give you an idea about what could be done: sell liability protection. This is something I am working on doing, so it's not entirely coming out of thin air. The idea is this: I am writing software to be Quality from the start. Obviously, it will be FOSS. Now, I could go the route of selling "support" (i.e., bribes to get bug fixes), but I don't like that because it incentivizes putting off fixing bugs until a customer runs into them because that will "convince" the customer that they need support. [1] Instead, with selling liability protection, including for outages, I have an incentive to make sure the customer does not run into bugs. And it doesn't matter if Amazon or some other big company starts selling my software as a service because my software is not my product. Of course, creating a quality piece of software relies on a process, as you said. My current process is at [2]. [1]: https://gavinhoward.com/2020/08/the-software-industry-is-broken/ https://gavinhoward.com/2020/08/the-software-industry-is-bro... [2]: https://gavinhoward.com/uploads/process.md https://gavinhoward.com/uploads/process.md
- ChrisMarshallNY 5y agoThat’s not a bad idea. You already have basic E&O, but that is kind of a “broad brush.” > Obviously, it will be FOSS That could cost you customers. I know the corporation that I worked at, would never agree to it. They were quite tinfoil about IP. They owned a ginormous patent portfolio, and were quite secretive in their processes. They would insist on keeping the source completely proprietary. I know that you are basically selling a personal guarantee, which is an idea I could stand behind, but that is still an individual attribute, as opposed to a standard industry one. It could be a potential personal selling point, and a competitive advantage. The real goad would be an industry-wide need for it. Basically, established precedent for suing developers (and distributors) of bad software. That’s a pretty classic Damoclean sword. Lots of claymores, buried, there.
- ghoward 5y ago> That’s not a bad idea. You already have basic E&O, but that is kind of a “broad brush.” I feel dumb, but could you tell me what "E&O" means? > That could cost you customers. I know the corporation that I worked at, would never agree to it. They were quite tinfoil about IP. They owned a ginormous patent portfolio, and were quite secretive in their processes. They would insist on keeping the source completely proprietary. Yeah, I thought that might be the case. I'm okay with that. The FOSS part is because I don't believe that customers should be in be dark about anything regarding my software. It would be like an architect not giving the plans to a building to the customer. Not professional, in my opinion. Of course, to satisfy customers like the ones you mentioned, I could just give them the source. I guess this is one point where my personal preference overrides because I believe in FOSS. To satisfy customers like that, however, maybe it would be enough if no one knows they are a customer of mine? No idea. Anyway, I'm okay with losing customers like that; I don't think I would need many customers to pay the bills. > I know that you are basically selling a personal guarantee, which is an idea I could stand behind, but that is still an individual attribute, as opposed to a standard industry one. It could be a potential personal selling point, and a competitive advantage. > The real goad would be an industry-wide need for it. Basically, established precedent for suing developers (and distributors) of bad software. > That’s a pretty classic Damoclean sword. Lots of claymores, buried, there. I agree that it needs to be an industry-wide thing. I hate the fact that EULA's basically disclaim all liability. (I'm okay with FOSS software disclaiming all liability because they don't know who is using their software, and it might just be a weekend project. Actually, my FOSS licenses disclaim liability too, so customers would actually be paying for me claiming that liability again.) But here's my hope: I hope that by doing this, and gaining a competitive advantage with it, other companies would either start to ask for it, or demand it, from their vendors, or start to do it for their software to gain a competitive advantage. In other words, I hope that I can get the ball started rolling towards becoming an industry standard. That's partly why I wrote my process down in such detail: so the industry could start to converge on standard processes like the engineering world. (Don't get me started on Agile or any of the other current "industry standard practices." Their foci are in entirely the wrong place, in my opinion.) Edit: Anyway, you're right: lots of claymores there. I need to carefully define the limits of my liability with a lawyer.