3 ms·
It's general reporting by general reporters using general language for the general public. It's not a tech publication. Joe Lunchbucket doesn't care if it's h
by reaperducer 9y ago
It's general reporting by general reporters using general language for the general public. It's not a tech publication.
Joe Lunchbucket doesn't care if it's hardware that failed or software. The system failed. That's what his tax dollars pay for.
- dsfyu404ed 9y agoThere's no reason not to include the details. People who don't care can ignore them.
- nkristoffersen 9y agoBut how many details do you include? How much ram? Length of the power cords? It is the job of the writer to write for the audience, not include every single detail, no?
- adventured 9y agoEnough so that the tax payers understand the IRS isn't actually running on an IT system from 1958. That's a pretty hilariously low bar to set for a journalist to step over.
- forapurpose 9y ago> There's no reason not to include the details. People who don't care can ignore them. Based on my experience regularly communicating technical information to non-technical people, the above suggestion works out very poorly. Each technical detail is a hurdle for the listener, causing misunderstanding, frustration, feelings of inadequacy, and doubt about your competence as an advisor and communicator. Generally, they respond like most people do when confronted with something unpleasant; they tune out your message. My advice is to include the minimum possible technical details and to express them in the clearest possible non-technical language.
- DrScump 9y agoJoe Lunchbucket doesn't care if it's hardware that failed or software Unfortunately, Joe and Jane Doordash in Procurement are the ones making the big choices, and it would be nice to have them informed in detail by something other than the salesdroids that have been perpetuating the problems for decades.