In the .NET world (and beyond), data access is a cluster-fucked echo chamber of half-assed rocket engineering and cargo cultism based on decade-old cathedralized thinking and corporate naval -gazing.
And then I write them down and get in trouble...
Playing The Fool Again
I'm building a new little venture right now and, for the first time in years, I'm flipped out excited. No no not because I think it will change the world and make me stupid rich - no I'm just excited to build it because it's fun and I like to build things. And dammit I'm having a great time.
I find that when you discuss BDD or DDD a mix of jargon and definitions is thrown around until no one understands each other. This type of thing plagues software development (see REST) and makes it extremely difficult to discuss... well anything.
image from http://visual.ly/network-graph-programming-languages-influence
Saying something confuses me is no great claim - many things do. It's entirely likely that I didn't study Ember long enough, or maybe I didn't give it the "time to soak in" that it deserved. Either way I punted on my efforts to bring an Ember title to Tekpub.
In 1986 I dropped out of college. I was 2 years into a meaningless attempt at a degree without a major. I lived in Los Angeles and attended L.A. Valley College taking 12 units of meaningless general education, swimming 4000 yards from 3-5pm every day trying to get in shape for water polo tryout at UCLA.
Make You a Deal
Long story short: I hired my 10 yr. old daughter to make the artwork for my slides for my NDC 2012 talk on PostgreSQL. I bought a new iPad 3 as I read books on my iPad a lot (make that only) - a clear screen is glorious. I was going to sell my old one but thought it would make a nice educational gift for my kids.
This all started, as most stories do, on a regular day. The sun was shining, I was in a good mood all things considered. I drove to work in light traffic in my new car that I could afford because I have this job in the technical industry. I'm a programmer - which is usually quite shocking to people when I tell them.
Don't Fund It, Sell It.
Here's my premise: a lot of people have their Rails environment dialed in. The one's that are having a bit of a harder time tend to be the folks just getting started or perhaps upgrading. These are the people that might very well plunk down $5 for a tool to help them.
Up to now I've been using CoffeeScript mainly for my tests - such as they are. I find it highly descriptive and easy to read: a must when reviewing a test suite. This instantly brings up two questions: