Hate to say it but I do not think so, and this is not a criticism of these people, it just is because based on my experience working with software developers, they are subject to pretty much the same psychological thinking traps as anyone else and sometimes even more so because of the confidence bias we give to skills in domains like engineering and overextend our confidence that these skills allow us to understand everything else
@grimalkina Comparably, perhaps, I enjoy this meme but I’m not sure how true it is in general, beyond a particular sub-sub-sub-culture where I’m comfortable.
@vruba @grimalkina I do find that actual techies tend to be more focused in their new tech adoption. That is, they'll adopt the latest and greatest in one area they care about, and be adoption-shy in other areas.
For example, if you go back to 2007, I had a home network with my own email server, but I did not own a smartphone. I see that pattern a lot.
@vruba @grimalkina I have personally not perceived the AI hype as being something trying to win over technologists.
Most operators and developers I know (yeah, I am making this distinction, they're both important, and can be the same person) don't really pay attention to hype. They have goals they need to reach. Short-cuts and assistive frameworks greatly help them when under the yoke of feature development. Before AI, there was Stackoverflow.
Skepticism borne of an evidence-based, scientific process does sound like it moves towards resilience, if it is seeking out the real work that's getting done. I wonder how much of this the majority of orgs really allow workers the time to build evidence-based skepticism.
How these frameworks actually contribute to the whole notion of how the technologists are able to get their Work-As-Done also feels like a gamble. Most vendors don't want bake-offs, and a lot of orgs don't want to spend time on bake-offs. Some vendors make it extremely difficult to change once they've landed-to-expand at your company. It isn't easy to decide you've made the wrong decision, because Vendor Lock-in is a Real Thing.
I keep at it. Having trouble where I am now with this, because we get instructions like "make sure the environment supports AI code things" instead of "make sure the testing is good so that if anyone uses AI we won't care because our testing is good."