Sudden Insights

Shared thoughts of a young thinker

Lying - The Biggest Smallest Mistakes we Make

For 23 years I have made the same stupid mistake again and again. I lied. Even though most of it was white-lies, I had no idea how badly this was influencing my life. 

A sick super power

I have a voyeuristic obsession that is both healthy and sick: I study the insufficiency and conscious wrong-doing of other people

 For some reason, as a kid, I acquired this exceptional skill to spot mistakes in the actions of other people and in the design and experience of products. Sometimes the judgements are immediate, obvious and trivial (like listening to a fat guy complaining about his weight, while watching him stuff himself with sugar and high glycemic index foods). At other times, I’m sensing the mistake but cannot explain it in words without thinking about it for some time.*

 The healthy thing about having such a habit is that it allows you to accumulate learnings and improve yourself without making the same mistakes. Unfortunately, in this case, I was already making the same mistake.

 One thing that was bugging me for a long time was how a lack of integrity impacts our life in weird ways. Politicians, bankers and other soulless people obviously cannot be trusted because of their complete lack of integrity. But even if you don’t lie on TV every day, there’s a good chance that your life quality is suffering because of the exact same thing. 

In September 2011, neuroscientist and author of several eye-opening books, Sam Harriss, made the insight about integrity very, very clear to me. Lying is deleterious and I had to stop.

Why would you stop lying?

 In his excellent essay, Sam argues that lying, even of the most innocent type, always has a negative impact on the quality of your life (and/or others). As he so elegantly puts it:

 “Lies are the social equivalent of toxic waste - everyone is potentially harmed by their spread.”

Bullshit? No. 

If you overhear a friend lying on the phone because he doesn’t want to go to some stupid dinner party, what will you think the next time he/she declines your invitation with an excuse? Even though it seems harmless, this single lie can have a undermining impact on the trust that is part of your friendship.

“Failures of integrity, once revealed, are rarely forgotten

To lie, when asked for an opinion, can also be extremely disrespectful and even damaging. Before you encourage your talentless child or friend to enroll in a reality show, please at least spend 5 seconds to consider what abusive and depressing impact it’s going to have when the person gets fried on national television. 

“False encouragement is a kind of theft: it steals time, energy, and motivation a person could put toward some other purpose”

If you want to be supportive as a friend, you should focus less on being encouraging and more on being truthful. 

A dedication never to lie and the unexpected implications

After reading Sam Harriss’ essay I was inspired in such a way, that I decided never to lie again. Like everyone else, I occasionally lied to help me on my way. It has not been more than a couple of months and the transformation is astonishing.

One effect I felt very quickly was a strengthened self-confidence. When I talk to people I get a calming feeling from knowing that I don’t have to lie, all I have to do is be myself. My improved integrity forms as a positive feedback loop, helping me easier bond with people and to establish transformative relationships.

“Vulnerability comes in pretending to be someone you are not”

Additionally, I now know that my view on things is often the most valuable around. Why? Because unlike most other people, I don’t just talk crap to avoid uncomfortable answers or appear more interesting.

This is huge. People intuitively appreciate honest answers, and If you have a history of being honest, your praise and encouragement will actually mean something. Some people will not appreciate this. If this means that they don’t return to get your opinion another time, it is not the kind of people you want to connect with anyway.  

Honesty is a prerequisite for building meaningful relationships, so no matter how much you disagree with someone, you know you are doing all you can to help the person and support a transformative relationship, just by being honest. Honest about what you think, but also honest about the stuff you don’t know.

Another thing I realized, is that lying might be a smart short-term solution to many difficult situations, but a dedication not to lie forces you to try to avoid these situations entirely.

I feel a short-term discomfort in declining to do stuff I don’t enjoy, but I know that the decision is going to pay off long-term. This might be difficult for you in the beginning. As Sam puts it:

“.. it can take practice to feel comfortable with this way of being in the world - to cancel plans, decline invitations, critique others’ work, etc. all while being honest about what one is thinking and feeling. To do this is also to hold a mirror up to one’s life - because a commitment to telling the truth requires that one pay attention to what the truth is in every moment. ”

Lastly, even though I don’t have a history as an all-time liar, it feels good to earn back the energy you would otherwise spend doing lie-accounting

“One of the great problems for the liar is that he must keep track of his lies.”

Urine

A decision to never lie is like deciding never to drink your own piss. People tell you both actions are morally incorrect, but what should be most important to you, is the life quality increase you get if you dismiss the temptation to do so.

I beg you. Please read Lying by Sam Harriss. It’s only 26 pages and the effect is life-changing.

 Also don’t drink your own urine. 

Follow me on Twitter

*If you met me at a bad time a few years ago, this would probably piss you off, since, on a bad day, I would not hesitate to share my estimate of how disappointingly little piece of your brain you seemed to be using actively. Today I try to keep most of the stuff to myself.

How to find A-team programmers on Elance

Hiring programmers doesn’t have to be a pain. I’m a programmer, and having the ability to study the quality of the code a candidate has written is obviously a great advantage. But it’s not a necessity. I recently hired a Ruby on Rails developer on Elance, and reflecting on the experience, I really don’t think it’s necessary to be a programmer to find the right guy for the job. All you need is a bit of preparation and a clear understanding of what you want.

I’ve dissected the process in 6 easy steps for you, don’t forget to pat yourself on the shoulder as you proceed.

STEP 1: Writing the Project Description

You may also find writing the project description the most cumbersome part. But it really is the place you need to invest most of your energy. Here is what it should include:

  1. 2-3 lines about who you are (company or private person) and what you do.
  2. A brief general description of what kind of person you are searching. E.g. “I’m seeking a skilled Ruby on Rails developer to put part time hours into further development of a trading/sales application used by a Swedish finance company.”
  3. A brief description of the project the selected candidate will be working on. Include technologies (if you know).
  4. Describe how the collaboration is going to work. What will a typical work day look like for the candidate? How are you going to communicate tasks (visual is good) and do you use any tools to manage the project? (AgileZen is simple and effective)
  5. In one line, emphasize on what is most important about the candidate. Feel free to copy ”I obsess about thoughtful code and only want to work with people I can trust 100%.”
  6. A list of strict requirements.
  7. A list of plusses that cannot be considered requirements
  8. An indication of how long the project will run, and what the candidate’s expectations should be.
  9. What will the hired person get besides his salary? (I don’t sit on a ton of cash, but love to help people become better at what they do)
  10. A small requirement in order to apply for the job. This will help filter out all the idiots spamming every job post. I ask candidates to provide a small code snippet and attach a sentence or two describing what is great about it. The winning candidate send me a link to a pull request he made on Github. His attached description demonstrated that he has brains and is a good personal fit:

I think it’s cool because:
- I wrote some solid unit tests to verify proper function of the feature
- I encapsulated and added the feature in a clean and non-obscure way. This is a consequence of I was able to follow and understand the source code of the anemone gem. 
- I think is cool because it shows I’ve learned Ruby ;)

Remember, it’s important that the tone of the project description reflects who you are. If you’re a dull corporate company, fine. Good luck with that. If not, make an effort to not sound as one. Make it intriguing and personal.

Thoughtful developers don't write anxious programs
Thoughtful developers don’t write anxious programs

STEP 2: Invite relevant people

This is a no brainer, but few people actually practice it. Search the elance database for programmers who you think would be a good match and kindly invite them to send a proposal for the job. This is a cheap way to signal your commitment, and will help kick-start the bidding. Don’t focus on price here.

STEP 3: Make clear expectations

Think about how you expect the ideal candidate replies, and decide on how you are going to evaluate each proposal. Doing this beforehand saves you from having weird negotiations in your head, because you get influenced on what is coming in.

What you need is an A-player. If you only get B-player replies kindly tell them why they all suck.

How are you going to judge proposals?

STEP 4: Select 3 candidates

Some of the proposals you get will probably amuse you so much, that you’ll feel your work payed off already. This is one of the small traits in hiring, so enjoy. 

If your project is interesting you should get at least 10-15 proposals. I got more than 20 and half of them was qualified. 

Use your predetermined expectations to filter the crap from the diamonds. Select 3 candidates and ask them to do a payed tryout task. Pay them the hourly rate they suggest, but limit it to a one digit maximum amount of hours billable.

STEP 5: Hire them to do a tryout task

Send the candidates a tryout task that is well-described, small in size and preferably touches upon the most important aspects of development (front-end or back-end, testing etc.)

As in step 3, it is extremely critical to have a clear understanding of what you expect of the results. Attach clear success criteria to the task description and make the entire thing as real as possible. 

Choosing the task can be difficult. I decided to pick an already implemented feature, move it to a new repository and strip away all the good stuff. That made it easy for me to judge if the implementations was good and helped me make sure that the task was not too big.

Pay the nice guys even if you don’t hire them. If you don’t you’re a dick.

STEP 6: Evaluate and select

Use your fixed expectations to judge the three implementations. If you’re not a programmer you obviously need help with this. If this is the case, I suggest you find an expert in your local Ruby group and convince him to help you with everything related to code. These guys are usually helpful, and having an advisor on the sideline can be very beneficial. 

If you followed everything above, chances are good that you just landed yourself an A-team programmer. Great job pal.

Insights

  • Don’t focus on money. If you hire cheap you get shit.
  • If you put a number on the required years of work experience, it means you don’t know a rat’s ass about software development. David at 37signals points out why.
  • From the job proposals and candidate tryout tasks I’ve seen, it’s clear that there is a direct correlation between ability to communicate clearly, personal and culture fit and code quality. Good news for all you unfortunate people in the software business who don’t know how to code. 
  • Not all great programmers have a long list of open source contributions. 

My first blog post - what do you think?

Follow me on Twitter @JonasNielsen

I would love to know what you think of this first blog post, and if you found it useful. If you think it’s just another piece of shit don’t hold back! All comments are appreciated.

What is your number one advice for hiring people online?