Palm Springs is wonderful. It’s a surprising mix of ultra wealthy and general tourism. Excellent restaurants, and expensive shops line the main drag. It’s provided a wonderful outlet for the past few days. Lauren’s family has a little pool, which has been too cold to use. But we’ve made wonderful use of their hot tub thus far. We did decide to show up on probably the only rainy days of the year, but that’s a-ok. It’s still splendid compared to home.

One thing I’ve come to realize on this trip is that I’m either addicted to coding or addicted to work. I want something to work on. I crave it. I crave that engagement. Something that can occupy my time and thoughts. I guess it’s very hard for me to really relax. I think I’ve got a big part of that from my father, who at 65 built a sauna in his back yard this year. As well as still runs his own used car shop (that he started only a couple years ago). He’s always working on something, and I suspect that will be the content of my later years as well.

Perhaps by then I’ll have moved away from software and begun seeking the more tactile and hands-on forms of busy work. Fixing things around the house. Using more paint than I currently do. That sort of thing.

But until that day comes, I’ll build things with or without code.

Skeleton Key is what’s in my sights right now. Today I pushed the v0.1.0-alpha up to my fancy new private github repo. It feels kinda cool, because it is a real step towards my goals of releasing an awesome framework.

However: I’ve not worked on an application that requires this amount of detail before. When building my personal applications, I can just make things work. If I build a hacky solution only my eyes can see it, and I can ignore my shame and push it underneath the rug where it belongs.

With this, it can’t be hacky. Because hacky is hard to understand. And the purpose of this is not to be hard to understand, but to be perfectly easy.

It can’t be complicated, because I need to use it to build incredibly complicated things, quickly. I’d like to think about it sort of like a hammer. It needs to simply do it’s job.

And this draws so many questions about what to include, what to exclude, and how to build it. And it all has to work together. Flawlessly.

I think my definition of the project is morphing, too. Originally I wanted several different versions, but now I believe I’m going to have to aim a little lower. Let’s perfect the User’s framework first. With permissions, profile, image upload and styling.

Yeah. That seems like the plan.



SOURCE

LEAVE A REPLY

Please enter your comment!
Please enter your name here