Neil ErikssonFeb 21
Chris is.

RE: https://phpc.social/@ramsey/116104919958954997

This here; when the tools are fit for purpose and make engineers’ jobs easier, you have to pry them from our fingers. All you have to do is look at the dedication to vim/emacs adaptations you’ll see in older coders to see the lengths to which we go to use the tools we feel work best.

It is a massive quality red flag if you have to force your staff to use a tool.

Feb 20 at 11:01pmWeb
Show threadDaveOFeb 20
Which brings me back to my problem that they're useful for some things but thus far they do very little I couldn't do without them.
Show threadCarolynFeb 20
@offby1 Jack really needs to eat more.
Show threadHugo van KemenadeFeb 20

@offby1 Just imagine if the Vim project wrote this :)

"After your initial rollout, the Vim usage metrics dashboard helps you monitor how usage evolves over time. By exploring adoption, feature, model, and language trends, you can see how developers are engaging with Vim and identify areas where additional enablement or communication may drive deeper value."

Show threadJeff TriplettFeb 21
@hugovk @offby1 Chris heard my mini rant about how most tools suck but it's not cool to force tools on devs.
Show threadLawrence MillerFeb 21

@offby1 (I am not yet faced with mandatory ai usage and I am skeptical of ai)

Based on my own experience as an "older dev", I think your vim/emacs example argues the opposite of what you intend. I DEFINITELY resisted using a modern IDE for much longer than I should have, instead sticking with emacs. It wasn't until I attended a conference (maybe YAPC or LISA?) and a speaker demo'd to the room a faster way to tie one's shoes as a metaphor, that I finally gave one a try and eventually switched.