Re:Maslow's Hierarchy of Site Reliability Engineering Needs ...
by lukasb on Tuesday December 27, 2016 @06:39PM
(#13267271)
if you don't know what an SRE is, you're not the intended audience. probably half of the articles posted to HN are unintelligible to non-practitioners of that particular subfield, don't see why this should be different.
[ Parent
| on HN ]
Re:Maslow's Hierarchy of Site Reliability Engineering Needs ...
by closed on Tuesday December 27, 2016 @07:46PM
(#13267583)
I don't know. As a person who is part of a number of intended audiences, I still get frustrated when people (directing things at me) don't define acronyms when they're first used, since
1. it's a hinderence for people who are studying to become the intended audience.
2. sometimes I'm reading two literatures that use the same acronym, so it's momentarily stupifying.
Re:Maslow's Hierarchy of Site Reliability Engineering Needs ...
by PhasmaFelis on Tuesday December 27, 2016 @06:51PM
(#13267338)
That just makes this a problem with HN rather than with the blog. HN's audience is not narrow, and it's annoying to see so many interesting titles leading to incomprehensible articles.
It really helps when HN posters either clarify things a bit in the title, or if that's not practical, make a comment when you post the link.
Re:Maslow's Hierarchy of Site Reliability Engineering Needs ...
by moises_silva on Tuesday December 27, 2016 @09:51PM
(#13268053)
Finding a balance is hard. Should you define SQL? DB? HTTP? where do you start and stop defining acronyms.
Re:Maslow's Hierarchy of Site Reliability Engineering Needs ...
by spc476 on Tuesday December 27, 2016 @11:48PM
(#13268461)
In my blog entries [1] I use the ACRONYM [2] tag with a TITLE attribute that most browsers will show when you hover over the acronym. I don't understand why it's not used more often though.
[2] I know, ABBR is the new hotness, but I'm still using HTML 4 for my blog and old habits die hard.