A notch above a monkey

Facebook, web, mobile and me

Recently, for a moment, I couldn’t imagine myself working on web in ten years time. Since I am quite passionate about it and its development, the obvious question was why?

Why wouldn’t I want to be a web developer anymore?

Popularity of Facebook comes to mind. It is no secret that I am not a fan of Facebook and similar networks. Yet I do have an account there and on some of its brethren. By the way, my Facebook account is for testing purposes, so if I haven’t befriended you, it almost certainly wasn’t personal.

Anyhow, Facebook and ilk are easy to criticize. Anything of that size will certainly gain much to be critical about. I also sometimes feel nostalgic about old web, before the gold rush of last millennium. That too probably says more about my age than anything else.

After some pondering I came to conclusion that I am longing for a sense of openness, equality and control I used to have. Few of us had our own server, but in principle with investment of little time and a bit more money, you could run all services that mattered.

Few actually did, since on the whole we didn’t do much. We do more now, some of which we don’t want public. I may not like Facebook’s walled garden of information, but I would have to be mad to argue for open access to all that private information. Even with existing restrictions in place people tend to trip and reveal? information to unintended audience.

If sharing our lives is what we want to do, which clearly is the case, then rise of brokers like Facebook feels as an unavoidable consequence. However that doesn’t mean natural development of a domineering agent should also be welcomed.

If at some point Facebook becomes a conduit for most of our digital lives, what happens if they revoke our account? To whom can we appeal? Who has access to the history of all our actions and what happens to it if we do decide to leave? Is it ever really gone? How do we know that our answers to this questions are true?

It’s a clich? that technology is changing societies faster then they are able to adapt. It is a clich?, but that doesn’t make it wrong. We are changing long before we are able to understand what those changes will bring down the road. It can be argued either way, but it is your outlook on world that will largely form your opinion on desirability of end result.

I am not an optimist.

I like building things and I enjoy it even more when others use them too. I am sometimes lazy and perpetually busy, so I avoid building things which not even I asked for. I always tried to incorporate a reasonable amount of security in services I have built, but I have never added transparency and accountability to the system without outside pressure. I don’t know many who would and that pressure tends to come from legal requirements. It’s a subject too dull to care about without painful personal experience.

Another reason for uneasiness comes from the other side of web connection – web browsers. Last few years have brought an incredible amount of development and most of us aren’t well acquainted with new technologies yet. HTML5 , CSS3 and Javascript will trounce Flash and Silverlight, right?

They might, but they all might not matter. Two raising trends I find interesting are mobile web access and mobile application platforms.

iPhone and Android have more than 100 000 applications between them and my impression of these ecosystems is that many of them are not much more than platform specific clients to web services. Even if most of them might not have much to do with web (games, books…), it’s not difficult to imagine a future, where most of us would access web through mobile devices and developing native clients for a new service would have a priority over access through browser.

I can’t say this would necessarily be a bad thing, since web development can be quite messy and frustrating. It probably would be less egalitarian and less sharing environment and I would certainly miss that.

At the end of this long self-indulgent post I confess I have no answers. I barely have questions and I had to write this far to get to them. It is for me the most introspective part of the year, so I might be thinking about a non-issue. Time will tell. Eventually.

Making peanut butter

Rok requested a post about making peanut butter and since he does such a stellar job taking care of technical side of wwwh talks , I thought it would only be fair to grant his wish. My butter looks like this:

Peanut butter on a slice of bread

If this doesn’t look to you like the best peanut butter ever, look again. And again.

Before I go on describing how I make peanut butter, let me spend a moment or two talking about why. After all it can be bought in practically any grocery store in Slovenia and visiting a few will even give you a limited selection. My first reason was to limit my intake. Peanut butter is incredibly delicious, but not exactly healthy and since I noticed that how much I eat is proportional to amount available, I wanted to avoid 350g jars that would be the death of me. My second reason was to have a better control of what goes in it. Like with sausages you can’t really tell what was used and in what condition it was. I certainly didn’t want to eat hydrogenated fat [1] added to your stock? peanut butter and were suspicious of a thick layer of oil on top of organic ones too. When I got better at making it, I also found out I really dislike bought ones.

As it happens the only thing that is absolutely necessary to make peanut butter are peanuts themselves. However you will probably want to use some oil, a sweetener like sugar or maple syrup and salt.

I use roasted peanuts. You can buy already roasted (but unsalted) or roast them yourself. To do that you heat up your oven to 175? C and put them in until they are done to your liking. Turn them around every couple of minutes so they don’t get burned. Next step: chopping.

But first a side note to all my American friends. Reports that Slovenians don’t eat peanut butter are simply false. We just hide it well. It’s kind of like masonry, but instead of discreet regalia and a secret handshake, we, peanut butter connoisseurs, recognize each other by a subtle nutty odor and small brownish stains in corners of lips. Slightly crazy and distracted look in presence of a peanut butter jar might also be a hint.

So, chopping. For small amounts, 200g or less, I use a hand blender with chopper accessory. I also use it because it’s the only blender I own. It tends to overheat and since I melted its predecessor my chopping amounts to mostly waiting pierced with short chopping episodes. Bigger blenders are certainly more resilient, but they also tend to have their blades raised higher from the bottom which makes them unpractical for chopping small amounts of nuts. Spend enough time doing this and dust will turn into a fudge-like paste. Do it more and it will become more liquid. If you like to spread butter thick, it might be even liquid enough.

I don’t so I add a bit of oil. I use peanut oil , but any edible with neutral flavor will work fine, just don’t add too much. You can always add more if you find butter too thick, but it is difficult to correct too liquid one. I add about a tablespoon of oil for 200g of peanuts while they are still pulverized and rarely need to add more later.

On recent vacation in Nepal I also tried their peanut butter. It tastes very much like ours at this stage; right taste but like most food in Nepal not salty enough for western taste.

Salt is not the only thing missing. Peanut butter is like tomato sauce, it needs a bit of sugar to get a more well rounded flavor. I used powdered sugar with some success, but maple syrup recently won me over (a tip from Ale? whose many culinary talents include baking great cakes ). How much salt and sugar to use is again down to personal preference. I use about 1-2 teaspoons of maple syrup and slowly salt while mixing until I am satisfied with result. Blender warms butter and spoils tasting somewhat, so I stop spicing butter when it is a bit less sweet and slightly more salted then I would prefer. This results in just the right taste when cooled.

That’s it. You should now have peanut butter good enough for gods. A few tries, to find the right balance between ingredients and you will end up with one fit for you too. It took me longer because I also eat it with spoon, hence it’s easier to notice its mistakes and more difficult to balance different uses (I prefer more salty butter on bread).

My next goal: cashews and cocoa spread.

[1] Hydrogenated fat is used for the same reason as oil, to make butter easier to spread. Added oil doesn’t actually react with peanuts and if you leave your butter long enough, it will eventually separate and form that unwanted oily layer on top. Hydrogenation solidifes fat and prevents that from happening. Downside is that you can’t tell how much additional fat was added unless it is specified in ingredients list and it’s even more unhealthy.

Dos and Don'ts of Job Interviews

Dear job seeker,

A job opening is an odd thing, because everyone involved is a buyer and a seller. You are trying to sell yourself to my company while at the same time I am trying to sell us to you and others we might regrettably have to turn down this time.

Two months spent actively searching for a new member of our team (we found him this week) made me reflect on the whole process. I am not the only one and I sympathize with everyone going through this. In last few years I have read tens if not a hundred of job applications and interviewed tens of applicants for different Slovenian IT companies, mainly startups. Not enough to be an expert, but enough to provide me with a firm opinion that most applications sent sucked.

That doesn’t mean that you personally suck, but I feel comfortable saying that most of you do not know how to present yourselves well. Mind you most companies are failing at this too, but this post will be long enough even as I limit myself to just one side of the story. My intent is to provide a maximum amount of help with a minimum amount of venting.

I think it is a safe assumption that you sent an application because you wanted this job. It should also be obvious that we were looking for someone that we think we’ll be able to entrust with challenging tasks and has a personality that won’t turn our jobs into a punishment.

So the question you should pose yourself is: “ What kind of person is the company looking for and how do I best show to be him? ” (or her)

If you don’t know, then look for information until you do. Ask if necessary, since any company worth working for doesn’t mind answering them. But knowing this is absolutely crucial if you want to be persuasive and at the same time not needlessly wasting your time on a company that doesn’t fit you. If you still think our company is right place for you, and I hope you do, then you should make sure that everything you do when communicating with us tells us that you are THE person we want to hire.

First and foremost, read and follow job ad instructions . Seriously, you would not believe how many applications fail to follow even most basic requests. Ask a friend to double check after you if necessary so you won’t miss anything. Zemanta is an international company and much of our communication has to be in English and yet, when we asked for applications to be sent in English, majority of them weren’t.

If something is unclear, ask for clarification . Responding to a job ad is the first test of your ability to receive a task, gather missing information and perform it to expected (agreed) level. Ignoring requirements or reinterpreting instructions on your own will make us doubt you.

Send resume when asked for, but don’t think it can substitute things that were asked for. It is amazing how many people just send their resume, when ad explicitly said we would like to see examples of work above everything.

Having said that, resume ( CV ) is definitely an asset when trying to sell yourself. When you write, keep in mind that its purpose is to sell you to a company. Put yourself into my shoes and think what should you write there, that is truthful and will make me want to hire you.

Europass resume is something only a bureaucrat could love . We won’t hold it against you, since somebody probably misinformed you of its usefulness, but it does tell us almost nothing about you. Even if I knew all listed companies, I couldn’t tell from a job title what you actually did there.

Much better is to explain in couple of sentences under every job list item what you achieved there and if necessary why I should care about this (e.g. At company ACME I introduced automated testing of Javascript code that reduced bugs reported by 30% )

In a fast moving industry like IT there is probably little reason to go into details about what you did in 1999, unless you are certain it is still relevant today. I started my career in 1997 porting backup agents to new UNIX platforms, but nobody would hire me for such work today (and probably shouldn’t then either). Old job listings are mainly used as a signal for steadfastness.

Don’t embellish resume too much . It is impossible to impartially judge your skills and most reviewers expect resumes to be, well, somewhat too rosy. Still, keep things at least defensible. Think what would happen if you were invited to an interview and found out that a part of it is a lie. How much weight do you think the rest of your resume would carry afterwards? Would you trust integrity of such person?

Considering what I said so far about poor quality of most applications, you might think it is easy to get to interview, but it is not necessarily so. There can be external factors that might work against you so sometimes even otherwise promising candidates have to be turned down (e.g., it is easier to teach people who live near by).

Let’s say now that you were interesting enough that we want to conduct an interview with you. I think following tips should work well for you on most occasions. If they don’t, count yourself lucky not to work there. I am not joking.

Don’t bluff. It’s reasonable to assume that I wouldn’t ask you a question I didn’t know the answer to so it’s unlikely it would work. Good questions can’t be tersely answered so you can’t really hide anyway.

Admit when you don’t know the answer. True, knowing it would be better, but at least you are not wasting my time. It’s especially important in small companies that problems are found out as soon as possible and it is a positive sign that you are a person that we can trust to let us know about them when there is still time to do something.

Don’t just give up. We all encounter problems that we can’t solve and interview questions we don’t know answers to. Show initiative and think out loud how you see the problem and what solutions might be. Give us a chance to see how you think and persuade us that you are a tenacious problem solver that won’t unnecessarily seek help of others.

Speak to the point and be active . From my experience this is a problem more prevalent in Slovenia. It quickly becomes annoying and tiresome trying to get a direct answer to a question from a person who doesn’t want to give you one. Making me feel like I have to work to keep interview moving is probably not the best way to leave a good impression.

Skills are…needed. We all want to hire people who fit our needs perfectly. We rarely can. What happens next depends on company and people involved, but judging by my experience, we value person over his skill. If choice comes between a flaky or otherwise non-solid person with better skills and someone that couples ability to solve problems and thirst for knowledge with personal integrity and maturity, then it is likely that latter will be chosen.

Ask questions. Inquisitiveness is always a turn on, but interview is also a chance for you to find more about us. Most companies expect from you an investment of 8 hours of your life daily and if you are like me, then it should be important to you what kind of company and people are you dealing with, what work entails and how do we go about it. Personally I don’t mind questions about salary and benefits, but I do find it odd if interview starts with them.

Regretfully interview is a last stop for some candidates and we have to turn them down. I know some companies have a bad habit of turning people down without letting them know and if that happens to you, well, count yourself lucky. At Zemanta we find such behavior rude and we notify everyone. What happens afterwards is usually….nothing. No reply.

My advice to you would be to respond with a note thanking for the opportunity. It probably won’t make a difference in a short run, but it does leave a good impression. We are all more inclined to recommend (or hire in next round) people we like.

Good luck!