…for a week!
Code Project survey question for the week. :)
Here’s a few random “talking points”:
Hypercard (http://en.wikipedia.org/wiki/HyperCard) – an awesome app that Apple created “in the day”, letting people create their own “knowledge stacks” and how each “card” in the stack relates to other “cards.”
NIEM (http://en.wikipedia.org/wiki/National_Information_Exchange_Model), recognizing that data is persisted in unique schemata but needs to be exchanged in a common understandable way. But rather than forcing a particular communication protocol, data exchange in NIEM is extensible by leveraging XML and XSD to essentially “define the definition.”
Semantic Structures (http://en.wikipedia.org/wiki/Semantic_technology) – “encodes meanings separately from data and content files, and separately from application code.” OK, fine, but what we need is meaning encoded WITH data, not separate from data.
So – what am I getting at?
1. People need autonomy in how they work with data and how they want to persist data.
2. However, for people to be effective, we need a way to query and exchange information meaningfully
3. “Information” has little worth. “Knowledge” has great worth, and one definition for knowledge, in my thinking is “information with meaning.” Another definition might be “knowledge is the relationship of information.”
Then, we finally get to visualization technologies, such as mapping in general and metamaps in specific as a way to explore the relationships between information. Key though, to any visualization system is that it must be “living”:
1. I need to be able to see and create the relationships that are meaningful in my context (the micro-context of my “dataset”)
2. Information and relationships need to be continually growing, in and of themselves (the macro-context of the “dataset”)
Share your thoughts!
I’m happy to announce that I am a recipient of the 2014 Code Project MVP award. Code Project is an amazing place to hang out, read articles, and of course contribute! Thank you, Code Project.
I realized today that it’s been about a year since I started working with Ruby on Rails. I ended up putting together a portfolio of the work I’ve done with Ruby / Ruby on Rails in the last year. Here it is!
Other articles on Ruby / Ruby on Rails:
Ruby on Rails Websites
personal projects implemented in Ruby on Rails
websites developed for my clients:
(these websites use significant pre-existing work from the open source community as well as other team members, so I certainly cannot take full credit for them, but I have made significant contributions to them):
The article describing the Property Grid written in Ruby on Rails and jQuery is now available. Read it on the Code Project.
An excellent real-life story of actual experience with MongoDB: http://www.sarahmei.com/blog/2013/11/11/why-you-should-never-use-mongodb/
I recommend that anyone considering a “document-based” database read this and thoroughly understand what Sarah is talking about…
…because the world IS relational.
This rebuttal was brought to my attention: http://ayende.com/blog/164483/re-why-you-should-never-use-mongodb
Personally, I find this statement: “And yes, this is a somewhat relational model.” amusing. Well, since it’s relational, doesn’t a relational database seem like the right tool? And what does “somewhat relational” mean? It either is or it isn’t, in my opinion. There’s no “somewhat” here.
Get the code: git clone https://github.com/cliftonm/property_grid_demo
I have put together is a set of classes to facilitate building the content of a property grid control on the server-side. You will note that I opted for actual classes and a “fluid” programming style, but if you don’t like the way the actual implementation looks using a “fluid” technique, I have also put together a very minimal internal Domain Specific Language (DSL) that you can use instead — basically just method calls that hide (using static data) the internal management of building the property grid instance.
As in my previous articles, I will be using Sass and Slim scripting for the CSS and HTML markup.
… The rest of this article is forthcoming!