Job Search Dos and Don’ts

I’m sure you’ve seen one of those articles about “10 tips for job seekers”. They usually speak to some analysts or hiring managers and get some choice quotes about what they thing job seekers should do to improve their odds of finding a job. I actually had an entire college course similar to this. The problem is, hiring isn’t scientific. There’s no “best way” to hire, so different hiring managers will give different answers.

In my course it was explained that the job seeker should always ask for when a hiring decision will be made and if they haven’t heard back by then, they should call back to follow up. My instructor explained that a job seeker should never call before then, because it would be seen as needy or bothersome to the interviewer. About a month into my job search I read an article explaining the same tip. However, the article explained one should call up before the decision date, in order to remind the interviewer of their qualifications. Clearly, these two people have a different job selection process.

So, with that in mind, I’ll try to avoid specifics, and keep in mind, every interviewer is different.

Always research the company you’re interviewing with. Be informed of recent news and what their business does.

Have questions. There’s always a “do you have any questions” section of the interview. Always have a question, even if it’s “what’s it like to work here”.

Never bring up salary. Until the offer, be as vague as possible about your price. Say you have to research it.

Be timely. Arrive on time to interviews, if not early.

After an interview, send a thank you email to the interviewer. The idea is it will remind the interviewer about you. Don’t be afraid to list some of your qualifications.

Have a 2 minute ad for yourself, as short story about your qualification. In case the interviewer asks to “tell me about yourself” or another open ended question.

The Power of C in the Cloud

In my last post, I introduced you to the cloud IDE Codenvy. The primarily reason I used it is because it has a simply way to hook into Google App Engine. However, for a more robust cloud IDE, I would recommended Compilr. Compilr has support for many of the languages Codenvy does (Ruby, Java, PHP, Python) but it also has support for Objective-C and C# as well as low level languages like C and C++.

That last point leads to some interesting results. Because we have access to such low level languages, we can use the Compilr servers for general computing. From what I can tell, the Compilr servers that execute the code are running a Unix-like operating system on x86 hardware. So if you’re in a pinch and need access to a Unix like environment, Compilr can be very useful. I happened to run into such a situation while trying to make use of WoLF PSORT for a rather long sequence and lacking the necessary Linux PC to compile and run the program locally.

So, how do you execute commands on commands on Compilr’s servers? First, create your C++ project. Your program will be run in the “content” folder of your project so if you have any external files you need, place them there:

 

If you get an error message when uploading, but you also get “Upload complete”, you upload has finished. Refresh the page for the files to show up in the project panel.

The key to our program is the system function. Simply hand it commands to execute and it will do so. To untar our WoLF PSORT file execute the following:

system ("tar -zxf WoLFPSORT_package_v0.2.tar.gz");

Remember to mark the files for execution if nessessary:

system ("chmod 777 ./WoLFPSORT_package_v0.2/bin/psortModifiedForWolfFiles/psortModifiedForWoLF");

There are a few restrictions Compilr has placed on free accounts.

First, you are forced to make public project and you are restricted to 50 builds/runs. These aren’t huge problems and you can always create a new account and port code if you go over 50 builds. In fact I have noticed the build counter often reset after refreshing the page, so this never became an issue for me.

Second, you are limited to 4000 characters of output. A very simple solution, pipe output into a log file by appending > log.txt to your command:

system ("./WoLFPSORT_package_v0.2/bin/psortModifiedForWolfFiles/psortModifiedForWoLF -t ./WoLFPSORT_package_v0.2/bin/psortModifiedForWolfFiles/all.seq > log.txt");

You may also need to pipe errors and warning, in which case you can log to the same file by appending >log.txt 2>&1 to your command. Or you may wish to disable errors and warnings completely while still capturing output, in which you would append the following 1>log.txt 2>/dev/null .

Third, if your program has not accepted input in 40 seconds, it will be terminated. This requires a tricky work around. I ended up spawning a child process to accept input while the parent process was busy. The child process will send an alert for input every 30 seconds. If you choose to do something similar, remember to flush stdout before sleeping. The syntax is as follows:

fflush(stdout);

sleep(30);

Interestingly, this method triggers a security measure when one process exits before the other and will terminate the program. So make sure no process exits before your program has finished doing it’s work.

Some final points about Compilr:

Much like Codenvy, Compilr has issues with Internet Explorer. I managed to get it working in Firefox.

The first compile of every session will fail with “Lost connection to server”. Simply use a dummy application to trigger it and continue your work. If you run an application that takes a long time and it loses connection, it could block you from running further applications until it finishes.

Always backup your progress! I can’t stress this enough. If the server that stores the code loses connection to the server that runs the code while “Syncing application data”, you can lose large chunks of your work.

Finally, I’ve attached some sample code on the download website.

Programming with Java on Google App Engine

I wrote a draft post about Google App Engine many moons ago when it was Python only. As I’m not a Python man, the post isn’t very technical. Anyway, things have changed and GAE now supports Java. Albeit a customized subset of Java, which I’ll go into later.

Google App Engine is a cloud computing service: run your programs on their servers and pay by CPU usage. It’s similar to Amazon’s EC2 and Microsoft’s Azure, but unlike them in there is an absolutely free trial. You’re only required to provide a telephone number when signing up.

Step 1: Create the proper account

Sign up for a Google account here and a Google App Engine account here. After the GAE account is created, you should be prompted to create a new Google App Engine ID.

Now, if you’re like me, I won’t want to have to download and install the various SDKs and IDE to make your GAE app. So, I suggest Codenvy. Be sure your logged in to your Google account and click “Connect with Google”. Be sure you’re not using Internet Explorer, Codenvy seems to have issues with it.

Step 2: Create a project

On the welcome screen, choose “Create a New Project From Scratch”

Choose  Java Web Application (WAR) -> Google App Engine

You have to select the sample project, but you can skip using the JRebel plugin.

Use the Google App Engine ID you just created.

Step 3: Clear out the sample code

Click the project tab in the left menu (next to the Package Explorer tab)

Delete the src\main\java\com folder.

Delete the src\main\webapp\display.jsp file.

Open src\main\webapp\WEB-INF\web.xml and empty the “servlet” and “servlet-mapping” items. You can add java code to the src\main\java folder at a later time and add the proper information in these tags to specify it as a servlet.

Add the following in the “web-app” item after the “servlet-mapping” item:

<welcome-file-list>

        <welcome-file>index.jsp</welcome-file>

 </welcome-file-list>

Open src\main\webapp\WEB-INF\appengine-web.xml and make sure the “application” has enclosed your Google App Engine ID

 Customize src\main\webapp\index.jsp as you wish.

Step 4: Run your app on Codenvy servers

Make sure you save! Codenvy does not auto save changes when building.

Run -> Run Application

Step 5: Load your app into Google App Engine:

Make sure you save! Again, Codenvy does not auto save changes when building.

Go to Project -> PaaS -> Google App Engine

Select Application Update

If you get an Oath token error:

PaaS -> Google App Engine -> Logout

PaaS -> Google App Engine -> Login

Also, see this link for setting up cron jobs.

The Job Search

I’m going to be writing some new types of posts, and therefore introducing a new tag. They’ll be about the time I spent on my job search. I’m now (luckily) employed, but I was on the job market for about 9 months, not including the job searching I did while in college, and have quite a few tales to tell.

I was speaking to a friend recently about our job hunting experiences, and the one thing we immediately agreed upon is that job hunting is a soul crushing experience. Between making cold calls to doing interviews to following up, it’s all a massive time sink. The worst of it is, even if you put in all that time, you have no guarantee of success, just better odds.

The one comfort you can have is this: You have a skill. If you’re in a technical field and you’ve gotten proper training, this skill should be easily identifiable and valuable. Maybe you can program or cook well or can translate another language. And as a job seeker, this skill will be something employers are in need of. And if a business is hiring, they obviously have a need for that skill.

Technological Singularity: an Unrecognizable Future

Do you ever feel like technology just moves too fast? I’ve already posted on how technology has past me by in many ways. But there might be more to it than people falling behind current trends. There’s the idea of a technologic singularity.

The technological singularity is an event in the future when technological progress becomes so rapid that it makes the future “different”. Central to this concept is the concept of accelerated change: technologic breakthroughs allow the next technologic breakthrough to occur sooner and easier. For instance, our technologic improvements in computers have allowed us to study genetic data faster and advanced our knowledge in genetics.

(Ignore that calculations per second, they are a poor measure of intelligence)

Some interesting consequences occur. As we build faster computer and create better algorithms, it allows us to create faster computers and better algorithms. But, that’s really all just an evolutionary trend, when our computers reach a high level of AI it will become revolution. It will be a paradigm shift: a social change so large that will occur and a new generation will be created.

And after the singularity? We will be able to construct machines smarter than us. And in turn, we will become more intelligent. We will become something else.

Before I finish, I would like to recommend The Gentle Seduction by Marc Stiegler as a look at what our future may become.

Loss Leaders

I’m a big fan of Valve’s Steam service. It took me a while to come around though. Even today I still keep local copies of all my games in case of a doomsday scenario. It takes a lot of trust to buy into a Digital Distribution service. Will they respect their customers, because it’s not like you can take your library someplace else if they decide to change their Terms of Service for the worse? Will they remain competitive, or will I have to start buying from other services and fragment my library? Will I still be able to access the things I paid for in 10 years?

One of the things that push me over the edge was their amazing sales. Amazing games for just a few dollars. As someone who was unemployed at the time, or even just price conscious, it was too good to pass up. The basic idea is loss leading. Valve, or the publisher, takes a hit on the sale of a game hoping you’ll come back and buy more games from Steam or from that franchise. In the end, gaining a returning customer at the cost of a game that they may have never bought anyway.

David DeMartini Origin’s, EA’s competing DD service, boss was asked in an interview about these sales to which he responded, “We won't be doing that. Obviously they think it's the right thing to do after a certain amount of time. I just think it cheapens your intellectual property.” Take from that what you will considering partiality of the speaker.

Valve’s business development chief, Jason Holtman, responded to the criticism, “If all that were true, nobody would ever pre-purchase a game ever on Steam, ever again. You just wouldn't. You would in the back of your mind be like, okay, in six months to a year, maybe it'll be 50 per cent off on a day or a weekend or during one of our seasonal promotions. Probably true. But our pre-orders are bigger than they used to be. Tonnes of people, right? And our day one sales are bigger than they used to be. Our first week, second week, third week, all those are bigger.”

What’s underestimated in Holtman’s response is the importance of the social side of gaming. If all your friends are playing a game now, you’re more likely to buy it now to be able to discuss it with them or play it with them. Not to mention, if you happen to pick up a multiplayer game several months after launch, your libel to be greeted by many an empty server.

I’ve recently started dabbling in another Digital Distribution service, Amazon MP3. They too have been a major user of the loss leading tactic. It’s not odd to see a $10 album drop to $3 or songs drop from 99 cents to 25 cents. And boy do they give away free credit like there’s no tomorrow.

They too faced scrutiny for their tactics. One unnamed retailer is quoted in a report as saying, “I love it when they have a successful loss leader pricing deal. I can't stop laughing every time I think about how much money they must be losing”.

The problem is that music doesn’t have the same social aspect as gaming. Outside of people who are really into the technical aspects of music, most really don’t discuss it beyond “like” or “dislike”. There’s no real analog to multiplayer in music. So, there’s no pressure to buy music quickly beyond a few special circumstances like social gatherings. At the same time, this means the price of music will generally stay constant over time. What is a 99 cent song now will remain so for the remained of its life, barring sales.

While Amazon certainly has the money to keep their MP3 Digital Distribution service afloat for quite some time, I question how effective their loss leading strategy will be in the long term.

The Scorpion of Baldora Field

I’m not going to do a lot of the typing this post, this time I have a story. It’s a monolog from Night on the Galactic Railroad about the scorpion of Baldora Field:

Our father told us once about the scorpion of Baldora Field. The scorpion killed other bugs and ate them.

Then one day, a weasel found him. The scorpion fled, and fell into a deep well. He was trapped, and knew he'd die.Then, he thought to himself,"How often have l eaten other creatures? And now, the one time that l was the prey, l fled in utter terror. And look what came of that. I'll die in this well, alone."

"Life is filled with uncertainty. Why didn't l accept my fate? If l had freely given my life to the weasel, I would have given himanother day of life.But now my death will help no one. I am useless. Dear Lord, I beg of you, look into my heart and hear my prayer. In my next life, don't let me waste myself.Let me use my body for the truehappiness of everyone in the world."

And then the scorpion burst into flame: a brilliant crimson glow. And by the light of his burning body, he lit up the night forever.

How beautiful!

I always liked the story. “Put the others before yourself” is a very nice motto. Even if it has a subtle communist overtone. The world would probably be a better place if everyone thought that way. But like the story says, when death has you in its clutches, even the courageous falter.

There was a story a few months ago on 60 Minutes about the cost of end of life care to tax payers. It reminded me of this story. It’s easy for most to expect the old and sick to accept their fate and save the tax payers a few dollars, but it’s much harder to accept it when your time comes.