3 ms·
I like that, but it probably won't work, as the people that jump in, out of context, are the same ones that scroll to the bottom of the Ts&Cs, and bang on "ACCE
by ChrisMarshallNY 6y ago
I like that, but it probably won't work, as the people that jump in, out of context, are the same ones that scroll to the bottom of the Ts&Cs, and bang on "ACCEPT." That's OK. I've learned the benefit of building a community by example, as opposed to fiat. The people that follow it will be the ones that don't need to read it, and they will provide the example.
I'm an "older" engineer (just turned 59. I really don't give a damn what people think of it. That's one of the benefits of being my age). I have about 40 years of experience in tech; the vast majority, writing software. Sometimes, quite badly.
Also, almost my entire career has been in "shipping" software; not just "writing" it. This has meant that I've always been pretty damn close to the end-user; sometimes, to the point of receiving personal...erm...feedback. Let's call it "feedback." I've also been responsible for delivering complete product, with polish and support. It wasn't "someone else's job" to clean things up. It was my job (it still is -even more so, these days).
I've watched (and caused) some real Jurassic-scale disasters, over the years.
That's one of the reasons I write damn good software, these days. Nothing like being given a bag and a stick, and told to clean up the mess (even if it was someone else's mess), to teach humility and caution.
So, that means that I'm often the guy that says things like "Are you sure you want to do that? I did it once, and it did not end well."
In today's "cargo" culture, that's considered "being negative," or "being timid, and only the bold survive," etc. ad nauseam.
I'm told that I'm "not a team player," or that I'm "harshing the vibe" (I actually made up the second one, but you get the picture).
This is funny, because my entire life has been ferociously dedicated to making difficult things happen. Precisely the opposite of being "too cautious to leave the starting gate." I've always been about "That's a difficult thing, and here are some of the things that might go wrong, along with a bunch we can't foresee. Let's figure out how to do it, anyway. We just need to be careful and circumspect."
That's pretty typical with experienced folks in any profession; not just tech. We often have a lot of callous and scar tissue.
Yes, we can be so timid, that we are too gun-shy to try difficult things, but we are also fairly likely to actually make it happen, if we take on the job.
For myself, I tend to look for "dreamers," who have ideas, and then help them to actually realize their dreams, as opposed to some of these Krakatoa-level explosions that we see happen, because the execution of a perfectly good idea was flawed and ill-considered.
That's what "engineering" is to me.
- BlueTemplar 6y agoThey will read it when they get kicked out of the channel for violating the rules that they haven't read.
- ChrisMarshallNY 6y agoBut it tends to work out better, when we guide them through what's needed to participate. Sometimes, their presence is something we want; just not their behavior.
- BlueTemplar 6y agoYeah, though this depends on the size of the channel - in a somewhat similar vein, see how Reddit basically gave up on parts of the netiquette by instead automating parts of it.
- rodgerd 6y ago> In today's "cargo" culture, that's considered "being negative," or "being timid, and only the bold survive," etc. ad nauseam. Frame it up as "I'm just putting on DiBono's black hat here so that we can succeed, team" and suddenly you're a Thought Leader.