1. I have a strange tolerance for risk

In one of my 1st year classes, we did a test involving questions in regards to money. This was to test what is known in behavioral economics as prospect theory, which describes the way people make choices based on their perception of risk. A normal value function looks like the following, which shows that people are loss averse.

English: Value function in Prospect Theory, drawing by Marc Oliver Rieger. (Photo credit: Wikipedia)

That is, losses hurt more than gains feel good. Not me, mine was inverted. That means things that appear risky to people don’t really appear risky to me, and things that appear risky to me others don’t find risky (I am extrapolating the results and generalizing here). This explains a lot to me and was really eye opening. While others are “playing it safe” with their stable job and steady income I’m “taking a gamble” and choosing my own destiny. While to most, I’m the risk taker, in my opinion “playing it safe” is a dangerous illusion of certainty where the stakes are highest. The rat race is a game nobody can win and a game I choose not to play.

2. I am mercilessly efficient with my time

While my classmates were busy networking, practicing their interview skills, going to workshops to polish up their resumes, and spending an inordinate amount of time on homework, I was rock climbing, going to jiu jitsu, and hanging out with friends. I never went to a networking session, or an interview or resume workshop, and never spent too much time on homework. Was I worse off? Maybe a little, but I don’t think so. I was always in class on time when I showed up and usually the first to leave. I never stuck around to chit chat or kill time between classes or anything like that. In effect, I was just being efficient with my time so I could do the things that make me happy, such as hanging out with friends and heading to jiu jitsu to train. I never did more homework than I needed to. I always skipped optional homework exercises and readings. Did my grades suffer? Not really, I did well on the things I enjoyed and pretty average on the things I found boring. If I were more studious, would I have done better? Perhaps, but there is a law of diminishing returns that I just didn’t want to deal with. My time is my number one resource, and it is limited. I wanted to do the things I wanted to do and I very rarely compromised on that. I was obviously not the most popular kid in school for doing this, but I never went back to school to become popular. I made some great friends and those friendships will last a lifetime. That’s good enough for me.

3. I am good at what I love

As mentioned in point 2, I am not good at “doing school”. I was, however, very good at doing things I enjoy. If I like it, I’ll be passionate about it and take a proactive stance on it. I’ll also spend a disproportionate amount of time on it. I don’t know what the cause and effect here is (am I good at something because I like it or do I like it because I am good at it), but I did learn at MBA school that this is how I am. I did very well in certain courses (even getting an award for the highest mark in the class in one) and just didn’t care for others. There was some courses that I enjoyed but was very average in, but I never did above average in a course I disliked.

I’ve been out of school for a year now, and I must say that learning the above 3 points about myself has had the most impact on how I spend my days. Of course I learned a lot more during my time in school, but these 3 points have had the longest lasting effects on me at the moment. Who knows, maybe in the future other things that I learned about myself will emerge as more important. I definitely learned a lot about myself at school so I wouldn’t be surprised.

The lesson for you? If you learn something about yourself, use that to your advantage and don’t throw out those lessons. You’ll likely be better off for it.

Three things I learned about myself at MBA school is a post from Awesomeness Deluxe.

First bit of PR for Rentything this week is a post from Awesomeness Deluxe.

Disclaimer: This is from a newbie’s perspective who was simultaneously learning javascript through Code Academy. If you are the type who spends any time whatsoever debating whether x framework is truly MVC, or not a framework at all, or something else even remotely resembling an already formed opinion of the four frameworks in question, this post is not for you. Also note that by the time you are reading this the information is likely outdated, as these frameworks have been moving at lightning speed. And finally, I am doing this writeup largely from memories of how I felt using the frameworks from 8 months ago, and my memory is terrible. You’ve been warned.

Knockout.js
First up was Knockout. Immediately I was impressed. Their website was beautiful, well documented, and had some amazing interactive tutorials. I watched some screencasts and was very impressed. Things just worked. I had no troubles picking up the syntax at all. There was just one problem, no router (that’s the thing that takes you from /page1 to /page2 and so on)! I tried using Sammy, Davis, Pathjs and a bunch of other javascript routers out there but couldn’t quite get them to play nicely with Knockout. Rats, unfortunately it was a dealbreaker. Sigh, I was almost in love. I am not sure if Knockout has a router built in these days as I haven’t looked at it since. Knockout, you’ll always be my first.

Ember.js
Next up was Ember. It was hard. It promised all this awesome stuff and the site looked cute and I wanted to learn a little bit of templating and Handlebars sounded cool so I figured I’d love this framework, but sadly I did not. Frustrating was what it was. I spent hours just trying to get really basic stuff going that took me minutes with Knockout. The reason, I’m not sure. I think the team behind Ember came from existing open source projects and so had an opinionated way of how things should be done. And I guess that opinion didn’t fit into my pea brain. Another reason, the documentation really sucked. I mean terribly. I would literally spend hours copying and pasting documentation straight from their documents and all I got were errors that I didn’t understand and had no idea how to troubleshoot. I cursed a lot using Ember (if you could call it using). I was glad to move on.

Angular.js
Angular was awesome. I really loved using it. Pretty easy to understand, although their website left a lot to be desired (disorganized mostly). I really loved the form handling capabilities. I was like “Oh snap, that shit works and I don’t have to do a thing”. Everything was going peachy but then I hit a juggernaut of a roadblock. These things in Angular called directives. I wanted to use a Bootstrap carousel, which with every other framework or library, simply required you to declare the Bootstrap script like you would any other. Not with Angular. I didn’t understand. So I asked what the heck was going on in the forums. People replied saying I had to write a directive thingy. So I went looking into what that was. Man oh man, I was WAY in over my head. So I backed away. Dealbreaker, again. Sigh. Don’t make me go back to Ember, please God no. Only 1 framework left. Backbone, man up and do what you do, only let me understand you while you’re doing it.

Backbone.js
I didn’t know what the hell was going on. Everything was confusing to me on their website. There were no examples, there were no simple tutorials. The website was filled with jargon that I just didn’t understand. I was thinking oh man I am seriously lost. But Google to the rescue. I must had done every single tutorial that was available on the first three or four pages on Google. They all did things slightly differently. It was annoying, but I also began to see the power in the flexibility of Backbone. Slowly but surely I started to get it. I put it through the paces and I didn’t run into the roadblocks that the other frameworks did (Knockout’s lack of router, Ember’s terrible documentation, Angular’s complicated directives). Still, aside from Ember it was the least enjoyable to work with. I found it repetitive in certain tasks and lacked some of the cool things that made the other frameworks strong, such as Knockout’s two way data binding sorcery. So I started looking around to see if there were any libraries built on top of Backbone. And yes, there were a ton. I tried Knockback, which combined Knockout and Backbone, but it had its own way of doing things which was just another thing for me to learn. Then I came across Marionette, and it made my relationship with Backbone so much nicer. With Marionette, I actually started to enjoy working with Backbone.

So after all was said and done, I chose Backbone for Rentything because it had what I needed, didn’t have terrible documentation, didn’t have any deal breakers, was the most mature of the frameworks with the most plugins and largest community, and Marionette saved me a ton of time with it. Just in time, too, as I was about to give up on learning javascript completely.

So to recap, from a newbie’s perspective using terrible reconstructive memory from events that happened 8 months ago:

Best Website: Knockout.js
Worst Website: Angular.js

Best Documentation: Knockout.js
Worst Documentation: Ember.js

Most Fun: Knockout.js
Least Fun: Ember.js

Easiest to Learn: Knockout.js
Hardest to Learn: Ember.js/Backbone.js

Most Mature: Backbone.js

Largest Community: Backbone.js

Most plugins/libraries: Backbone.js

Hardest Component: Directives in Angular.js

Things have probably changed dramatically since then. I just started scanning through the frameworks websites as I am writing this, and it looks like Knockout still doesn’t have a router, Ember’s documentation still sucks and they know it (and are working on making it easier) according to http://emberjs.com/blog/2013/03/21/making-ember-easier.html , Angular now has a lot of contributors who have made tons of directives for Bootstrap and other things, and since I’m most familiar with Backbone, I know they recently released version 1.0.

I think for any projects in the near future, I’d probably give Angular another go as the community has grown drastically and it was a pleasure to work with. For smaller projects, I’d definitely go with Knockout since it was just so fun. Backbone has been great, but only after I’ve stacked it with quite a few plugins/libraries to help speed up development. I’d like to try working with a framework that just pleasantly works out of the box next time. My own javascript knowledge has grown a considerable amount since I gave these frameworks a go, so I am sure a second time around will be much less painful.

Backbone vs Ember vs Angular vs Knockout Review is a post from Awesomeness Deluxe.

I meant to write about Rentything here sooner, but I just never had the right moment to do so (I guess now is good…surprise!). It has been a tough year so far as I’ve tried to find my rhythm. I’m not there yet but definitely making improvements. Rentything has been a load of fun to make (most of the time) and something that I think has real value for some people. It’s a problem I personally had when I helped my parents move last summer and never had the abilities to borrow certain tools that we needed only temporarily. So in a way I built it for myself, and I am hoping it helps solve an issue other people run into as well. But it’s more than that. It’s access, it’s discovery (ever want to try canoeing or rock climbing or something else but didn’t have the equipment?), it’s convenience, and it’s money savings and earnings (people will earn money using stuff they already own… and rent stuff at hopefully competitive prices). In tough economic times, nothing will put a smile on my face more than knowing some family or individual was able to earn a little bit extra thanks to Rentything. If I hear that even once, I’ll consider it a huge success.

So, will it work? I don’t know. There’s a whole heck of a lot of reasons on why it will fail, and only a few reasons on why it will succeed. I’m aware of this, but I’m not too concerned about it either. I didn’t build Rentything to become an internet millionaire or something, I built it because I needed to. Rentything’s success or failure is largely irrelevant to me, but what is relevant is the skills I have picked up (javascript, what!), the skills I’m improving on (marketing, copywriting, seo, etc), the skills I’ll need to reawaken (customer support?) and the skills I will undoubtedly need soon/now/too late.

Life is short. I have my life’s mission to complete. Rentything is a great first step in that direction. Check it out at Rentything.com

P.S. With that, my blog will take on more topics now including the technical, the business, and the journey (although I was already doing that last one).

I guess I should let you know what I’ve been up to. Introducing Rentything, a peer to peer rental marketplace is a post from Awesomeness Deluxe.

Consistently doing bad things will lead to further bad things, and consistently doing good things will lead to further good things. Consistency forms habits (and habits are good and bad). Want to start becoming more awesome at something? Figure out what works, then be very consistent in doing that thing. Want to stop? Then become inconsistent at doing that thing.

Want to get good at arm bars? Find out how to do them properly, then do them. Lots of them. Every day. Consistently.

Want to get better at bouldering? Boulder. A lot. Consistently.

Want to get good at x? Find out the best way to do x, then do it. A lot. Consistently. Every day might be too much (if recovery is an issue, or if money is an issue, or time is an issue, or x is an issue). Doesn’t matter, do it at a pace you can do it at, at a schedule you can reasonably do it at. Push too hard, and it’s unsustainable. Push too light, and you won’t see the results as quickly if at all.

Consistency is not a guarantee for success (especially if you are consistently doing something incorrectly), but it is a good bet. In other words, consistency is necessary but not sufficient for success. The opposite is not also true. That is, it is virtually guaranteed that not doing something consistently will bring you results on par with not doing that thing at all.

So how do you know if you’re doing the right thing consistently? Well, that’s a bit tougher. Sometimes, it’s obvious and getting into the minutiae is unnecessary. Want to lose weight? Eat less. Forget about what you should eat, when you should eat it, and how many meals you should eat. You will know when its time to think about those things. For many, getting started is the hard part, so keeping it simple is the easiest way to start and stay at it consistently. Other times, figuring out the right thing is tough. You could ask people. If 100 people tell you to do it a certain way, it’s either conventional wisdom because it’s the correct thing to do or because nobody bothered to challenge it (one is good, one is terrible). You’ll have to decide based on gut feel what to do here. If you get 100 completely different answers, you are in “nobody knows what the eff they are talking about” territory. In that case, ignore everybody, and explore for yourself.

Usually the hardest part is just starting. That’s why I’m a fan of just doing it, observe (and measure!) obsessively, and make corrections as you go. Is P90X better than Insanity is better than blah blah blah… Stop, just stop…. If starting is the hardest part for you, then the just do it approach is a great one. If starting is not the hardest part, then I’d go with front loading the work and doing the hard and boring stuff first, like finding the right material, figuring out the annoying little details, and other deep research like you are some mad scientist with crazy hair, weird mannerisms and bad hygiene (but I’m willing to bet starting is the tough part).

Once that’s out of the way, be consistently consistent. Ready? Ok, go!

Consistently Consistent is a post from Awesomeness Deluxe.