From all my experience, far and away, the biggest bottleneck and ball and chain on progress in computing is bad technical writing, bad documentation, poor ability to describe technical work; one of the biggest problems here is undefined jargon; and there one of the biggest problems is undefined acronyms.
In particular, even with my decades of experience, there is no good way for me to guess that the acronym "IC" abbreviated "integrated circuits". For an audience as broad as all of Hacker News, there is NO way to know.
In particular, writing
"Homemade Integrated Circuits"
is plenty short so that there is no good reason to write
"Homemade IC"
That acronym is undefined and obscure.
Technical writing in computing is awash in undefined and obscure acronyms, and that is part of the bottleneck and ball and chain on progress.
The situation in technical writing broadly, e.g., in math, science, engineering, is clear: When jargon is used for the first time, define it or at least give a link to a definition. With the Internet, giving links to definitions is especially easy and convenient.
For the sake of progress in computing, I urge computing and the Hacker News audience (i) to minimize use of obscure acronyms and (ii) on the first use of jargon always define or link to a definition. This advice is rock solid and just technical writing 101.
In the meanwhile, indeed, I'd be more interested in homemade ice cream than homemade integrated circuits -- even for the Hacker News audience, the acronym IC more likely abbreviates "ice cream" than "integrated circuits".
Other guesses at what "IC" might abbreviate:
Internet Communications
Information Categorization
Icon Construction
or more.