A RoseFactory by any other name...

November 18, 2014
development quirky computer science software engineering modeling naming
What about if you were creating new furniture pieces and putting them together? You would need some consistency in your succinct descriptions otherwise you wouldn’t be able to tell what fits with what.

For instance if you were describing the front and back leg of your couch, and the descriptions were completely different, if you changed a subtle detail in the vanir, it wouldn’t be obvious what other pieces needed to change. On the other hand, if the descriptions were identical, it wouldn’t be clear the the pieces were mirror image of each other.

How do we achieve that level of consistency without over generalizing? The answer is as you may expect, very carefully. Why do you think software engineers make so much money?

A large portion of any software engineers day is spent deciding what to call this or that, and whether a name still describes a piece that has changed. Automate the solution to that problem and you’re a great deal closer to creating a robotic software engineer.

the yin and yang of utility

August 8, 2020
development quirky life shower thoughts philosophy

coming soon: peerstate

August 6, 2020
development backstory open source

Health Pro's and Con's of Cooking with Discrete Ingredients

August 3, 2020
quirky opinion shower thoughts cooking health
comments powered by Disqus