Seriously though, all I'm saying is that its good to define acronyms somewhere on a landing page. It can be at the bottom. In the footer even. This shouldn't re

Seriously though, all I'm saying is that its good to define acronyms somewhere on a landing page. It can be at the bottom. In the footer even. This shouldn't really be controversial. You're sortof asking how could I not know what CI is. So I'll expand on that a bit. - firstly, it doesn't matter if you think everyone knows it, the industry is deeper and wider than people think. So its polite and good practice to define acronyms. Granted part of the problem here is that this hit the front page of HN so the audience suddenly became a lot wider than the author perhaps expected. - me, personally, in my 40 years I've encountered continuous integration but not enough to see the letters CI and immediately think of CI. And when you encounter a random link on HN it could be anything. Maybe there's some new AI buzzword I havent heard of, called (say) Customizable Intelligence and its like modular AI models and its the big new thing but I havent encountered it before, and people are calling it CI. - ok so I could peruse the page and eventually figure out that they are talking about continuous integration rather than some other thing. Or I could google it. But why make me do detective work like that? To me not defining the acronyms makes it seem like the author is stuck in a little subculture and can't imagine anything outside of it. It kindof puts me off. You could think of it as the textual equivalent of a code smell. Its make me think they're just down a trendy jargon rabbithole and I've seen enough of those over the years. (I'm not saying they are in this case, just saying that to me the lack of definitions put me off) But Ok as I said above this is perhaps something that the author never expected to reach such a wide audience so I'll shut up now. But in general I believe in defining acronyms. Because there's just too damn many of them.