Allan & Steve are the chubby founders of LessEverything. This is their blog, hear them rant, praise, give advice and talk about Just Stuff, Less Accounting, Lovd by Less, More Honey, Less Memories, Code, Business, Design, Marketing
These two blogs are the killeriet blogs on the tubes, if you don’t have them in your rss reader you’re seriously losing out. I promise, read them for a week and see if your mind doesn’t explode.
I was a hell of a kid, not a bad kid, but it seemed I was always doing really dumb things. When I was 10 my Dad told me something that really stuck. He said "You can obey me out of fear or out of love but you're going to obey me". Rarely does 10 year-old boy remember anything let alone something that makes them think. I've always thought about this and observed people in authoritative positions to me.
What makes a good day for you?
Taken from an email written by a good friend of mine about the number of downloads for our open source social network platform, Lovd By Less:
Talking to you on Thursday it was obvious that you were genuinely surprised by the success of LovdByLess. The fact that you were surprised is shocking to me. Take the single-most sought out feature in one of the hottest languages of today and have one of the best Rails shops in the country build the functionality, design the site, and bundle it all together for no cost.
Obviously flattering, but from our perspective very far from the mark. We have been genuinely surprised by the number of people who have tried, downloaded and contributed code back to Lovd. There is no guarantee of success. We had an interesting idea have executed well.
Our recipe for success is:We have been blessed with a lot of good ideas, a really strong work ethic, the ability to see what’s important and stick to it, very understanding families, and luck. Our parents have always supported our careers and have guided, mentored and inspired us. We have occasionally been called arrogant or self-promoting, but truly what we have is a fear of failure. We self-promote because we don’t have any expectation that someone will do it for us. We succeed or our families don’t eat. Just like the rest of you.
Last year I worked over 4000 hours. This year I am trying to keep the number close to 3000.
We work hard. We participate in open source. We blog a lot. We write and act honestly. We try to make things easy for our users and ourselves. Any measure of success that we have or will have comes from these things. We don’t expect to succeed. We just keep trying.
And we are grateful. We are overjoyed that people enjoy our opinions enough to read and subscribe to our blog. That people like our work enough to use our products and ask us to work on their products. That people download our software and contribute back.
Thank you all for allowing us to share ourselves with you. And while we don’t expect it, we do appreciate it.
I wanted to jot down some things we (less everything) work towards to keep our personal lives in balance with our work. Our industry is unique in the fact we love what we do and sometimes we feel it's acceptable to work 80+ hours. While some weeks you must kick out some work, overall it's not a positive thing to be that unbalanced. In the past months, we have added a few company rules.
5) Try to do something to get the blood pumping. I'm fat and lazy but I try to ride my bike around the neighborhood while pulling my son in his baby trailer. This is a time that I can have complete silence and clear my thoughts, plus sweat a little.
I am sure you've heard the expression, "he's a jack of all trades and the master of none". Fast food restaurants are "jacks," they carry everything under the sun, salads, burgers, shakes, pies, ice cream, coffees, breakfast burritos etc. And it's all crap... "Five Guys Burgers" is a franchise burger joint that has a great product, unique setting and a business model that screams less. They have burgers (cheese, bacon or plain) and they have fries (cajun or regular); I believe you can get a hot dog too. But that's it, they know they can make a killer hamburger loaded with the toppings and they can do it fast and well. Because their menu is small, the ordering is fast, the cooks have less to learn, less to prepare and less food inventory to store.
There are a lot of people who are really good programmers who never reach that “top .1%,” or whatever, level. Of late I have been thinking of one of the things that sets the best programmers apart: Discernment. I’m not talking about discerning a good technology from a bad one, but rather the ability to discern a good choice from a bad one. To be able to see the consequences of this path versus that one. In short, to know which rabbits to chase.

When writing software we face a million billion choices every day. Having the talent to make good choices is crucial to being productive. It’s the reason we can launch a product in seven hours.
Here is an example: Recently, one of my guys was refactoring some bad controller code we inherited. He was very excited to show me how he had abstracted and cleaned some of the bad controller code into a library so all of the controllers could call these methods instead of duplicating this bad code all over the place. At first glance it was clear to me that this abstraction was the beginnings of a new library that would be almost identical to Make Resourceful. Once I showed him where his path was leading he agreed that this was probably not the right time to write a Make Resourceful clone, especially when what was really called for was just making the bad code proper, not writing a support structure for it. This reminds me of what Malcom Gladwell was talking about in Blink: The ability to know instantly. (Perhaps to know truth instantly.)
I’m not talking about syntax here. Obie Fernandez and I have fairly different coding styles. He prefers to have the code be more explicit and readable while I prefer my code to be more terse and succinct. Neither is right or wrong, and neither is the reason we are both able to look at a problem and immediately prune it to its core and see clearly where the different paths take us.
This isn’t just true of code, I have seen Allan do the same thing with design. We were working with a designer who was very headstrong and really thought Allan was lacking in something (I’ll save the “why were you working with someone like that” story for another time). This person was doing the html/css for a website and using some popular grid-css-template-thing (I believe that is the technical term for it). When Allan first looked at the code, he just started ripping parts out, not because it was bad in and of itself, but because it was clear that was way too complicated. Using this framework did not buy the simplicity and maintainability of what has come to be known as “The Allan Way™.” (It is amazing to watch Allan take a 7000 line css file and without changing the way the site looks, trim the file to 300 lines.) The other designer made a fuss until Allan was done. Once he saw the difference, he was converted to “The Allan Way™.”
It’s easy to say, “that is just a product of experience.” And although experience certainly plays a part, I think it goes way beyond that. I think this discernment might also be called wisdom. Wisdom basically boils down to how well can you predict the future. When one approaches the wise old sage, the sage immediately knows the outcome of all the paths presented.
So how does one get this discernment/wisdom? I am not sure. I do believe one can learn it, and I think one of the requirements is to know that that is what one is trying to learn. When you play chess, do you only think about your strategy, or do you constantly think “why did my opponent make that move?” Acquiring wisdom might require applying that mental discipline to every part of life: Why did my wife/boss/client/adversary say that? Was it planned or just careless? How does my action affect others? And not just in dealing with others: If I do this, what will I do next? And then what? What paths am I forcing myself into later, if I make this choice now? How deep is this rabbit hole?
Maybe this is the difference between success and mediocrity, between satisfaction and melancholy. Or maybe not.
Jason Fried of 37signals says meetings are unproductive and I can't agree more. I would even go as far as saying most conference calls are a waste of time. Here my reasoning, it never fails someone will talk and talk and have no idea what they are talking about. You'll listen to their 10-minute ego speech using vague buzz words and then you'll disprove their "theory" in half a sentence. So please, if you don't know what you are talking about don't pretend to know. You don't see me with a blog about dieting do you? If someone asks a question and you don't know, don't pretend you know the answer. Save us all the agony of listening to you ramble around the wrong answer.