Show HN Threads and [side] Project Naming Habits
1 - We enjoy recreating stuff for educational purposes, but whilst showing it out to the world we also should provide a premise: we’re not going to maintain it, and don’t rely upon this code/product.
That is the question we should ask ourselves in the first place as the authors of the project to see through all the excitement.
2 - Immutable data structures are important for a reason, and we as the authors of small or big packages do overwrite our knowledge by proving some “creative” names that has literally nothing to do with functionality or purpose or the problem it solves. This is not art in a sense for people to stare at an enjoy or got inspired. If a company presents a new washing machine and calls it Cosmic Debris, wouldn’t we say - it’s a damn washing machine, why do you make it so complicated? Call it what it is and get on with it. We should let our ego go, see the reality of what we’re doing, stop romanticizing and get consistent.
Kafka, Spark, Cassandra, Ruby, Pandas, Spring, Hibernate, Electron, Pig, ad infinitum.