Skip to main content

Hype on HackNews and Silicon Valley

One of the consequences of refusing to drink the in vogue kool-aid is that you remain sober and take in the full brunt of the silliness going on around you.

The technology industry overflows with such silliness, like any credible geek I spend too much time reading HackerNews even when I don't want to.

One odd phenomenon I have observed over the past few years is the fact that there is a rather peculiar writing style in Silicon Valley, seemingly meant to make writing more efficient in conveying hype.

Specifically, the desire to create emphasis when otherwise the point being made is prosaic has lead people in Silicon Valley to come up with this odd writing style where adverbs are deployed in ways that no decent writer would. Let's just say a good chunk of "influencers" in SV suffer from Hype-Nitis.

I have gleefully collected a small sample of these gems on HackerNews over the past couple of years:

atrociously bad
crucially important
astonishingly successful
growingly wants to be secular
closely involved and crucially helpful
severely unique and an incredible thing to witness
Something is dramatically wrong with her
It is an exceptionally great salary
early decline are vastly significant 
made an amazingly interesting point
It was a hugely important quarter
You just won't believe how vastly, hugely, mind-bogglingly big it is.
team massively grew
the hugely important and popular site
startup to a significantly larger organization
hugely newsworthy figure
This is insanely sad. This brilliant woman had so much left to share with us.
The OP is impressively throrough 
informatively good


Popular posts from this blog

Managing configurations with object graphs

This post is basically a pitch I send to folks whom I think will be interested in a modern approach to configuration management. I am posting it here so I can refer people to it without sending them a long email.

One of the features of the HiveMind platform is a smart object technology that solves the problem of dealing with hierarchical configuration information often represented in formats Like YAML,JSON, Java Properties,XML...etc

The smart object technology allows developers/users to directly construct object graphs of any complexity. Once you have the actual object graph you can reverse the process back to representation in any one of the formats mentioned above.

I have setup a demo instance for trying it out @

Login with login info I sent you.

Be nice, you have full system access :)

To see an example representing the AWS IP list (

Navigate to: /com/crudzilla/betaApp/web/aws/index.ins


Get out of the box sometimes

Little boxes on the Laptop, Little boxes made of Javascript stacks, Little boxes on the Laptop, Little boxes all the same. There's a green one and a pink one And a blue one and a yellow one, And they're all made out of Javascript stacks And they all look just the same. And the developers in the industry All went to the IDEs, Where they were put in boxes And they came out all the same, And there's devOps and Rubyers, And micro services, And they're all made out of Javascript stacks And they all look just the same. And they all play on the GitHub And drink their Kool-aids dry, And they all have pretty syntax And the syntax go to HackNews, And the syntax get approval stamp And then to the IDEs, Where they are put in boxes And they come out all the same. And the bros go into business And marry and raise a VC round In boxes made of Javascript stacks And they all look just the same. There's a green one and a pink one And a blue one and a yellow one, And they're a…

Your code is not a project

Language matters, just as saying the wrong word to the wrong person can leave you with one less front tooth, so too can the incorrect use of language in general create a cascade of confusion that pervades an entire industry.

One of my pet peeves about the use of language in the software arena is the use of the word "Project". This usage as far as I know goes back to IDEs grouping software artifacts as projects. The notion of a project as the top level organizing construct for software projects (see what I did there?) is now a de facto standard. One problem with this is that it is a complete misuse of the notion of a project. A project is not a thing, it is a process! A project has (or at least should have) a well defined start and end.

As a process, by its very nature, its essence is vague. So when something whose essence is precise (software) is called a project it leaves the reader wondering exactly what is being described. Whenever I come across a documentation describing…