Brian's Dream

April 30th, 2017 - Day #7 Setup the basic process and rendered a view (not to a phone yet, but that will come). The next problem to deal with is the problem of partial views and subviews. All it does is takes some JSON, applies the properties and renders it to HTML. Simple process to a simple problem. Of course there's more to it than that. JSON -> PARSE -> HTML "The Process" It is apparently a trivial problem, but you can really shoot yourself in the foot with it. The reason why I say this is, I need a clear separation of design and logic. Even a 99% separation is not good enough, because I'm creating a 100% data driven application. Data driven is of course arguable, but the entire point is to mass produce some solution to a certain type of problem. Laying the Foundation So, basically I would like to achieve what's here  because I want a complete separation with the model and view. But not just because I like that or want that, but because I h

April 27th, 2017 - Day #5 Didn't get a working prototype out. Didn't spend the time. That's not okay, but I will manage. Had other things to do, or not. Procrastination. But will work on it today. Need to drop it down to a repeatable pattern. Something that I can make over and over, that will make a little bit of money. Goal is to monetize as soon as possible. Make it simple and effective, just like the picture from a few days ago. Not worry too much about too many features. Next post will be a working prototype.

April 23rd, 2017 Two weeks after quitting to pursue my own hobbies and the "dream" of running my own business or making my own product, I find myself looking back at work career with fondness. So many things have happened over the past few years, people I've met and things I've done, that it's hard to make sense of it all. But in the end, it doesn't really matter. The only thing that matters is how fast I can make what I want, before my cash runs out. Time is of the essence. Starts with a simple sketch, anyone can make it... data driven business application. Better not to be pretentious and call it "engine" or "framework" because it's going to be the smallest, tiniest thing I can possibly make that works end-to-end that I can build on and expand on. How long have I thought of making this? Many months, many years. Always thought of work, responsibilities, all excuses... could have stayed to make it, but there was never the urgenc