ulrich

I was one of the 16000 protesters in Munich. The message came to me via the evening TV news about germany delayed signing ACTA. It was impressive to see how many people care about that topic. 200 attendants in London sounds like no protest at all.

If you leave aside C-extensions and libraries, CPython is a pretty bad language for number crunching. This is just not the use-case it tries to solve. I am glad they favor simplicity over execution speed.

Removing the GIL might be useful for a faster implementation with JIT compiler though.

When you are used to the SVN/CVS workflow, it takes a long time to get over it. It took me a long time to understand why the distributed approach is better, despite having read a lot about them. In my company we are using git as well, but most developers refuse to work anywhere else than on master. They probably had their share of trouble with branching in other systems.

Two weeks are quite some time for an automation. But depending on how much time you spend every day, you might want to go for it. It's not only about saving time daily, it's even more about scaling things up.

If the process is automated, it should be quite easy to use modified versions for similar problems. And you can quickly run it again and again without having to worry about making mistakes.

Whaddaya Mean, You Can't Find Programmers?

It is a give and take. If developers are in high demand, it is the companies turn to show their value to the employee in advance.

This is a very biased view and it might become invalid in different market conditions. Just think of a great inflation or any market collapse. If you own a house, you can still live in there. But you can only burn your cash for heating.

As long as our financial system works, cash is of course the best form of an asset.

I was thinking about this a lot of times. Having some person to handle the kind of work I dislike. But in the end, I guess it's too hard to realize. Headhunters are supposed to help you with it, but they never do. There had to be a different, employee-friendly incentive for them. However, I'd love to be proved wrong.

That's a good sign, but I am still waiting for it to express in the salary range of companies.

Gingerbread has a concurrent GC, so animation should not stop completely. However, on a single core system I wouldn't expect this to have a huge impact. But this is just my personal guess.

That means you can finally ship 4.x-apps without losing all the iPad owners as potential customers.

I second that. It's not the "rewrite" that is bad, but the "rewrite from scratch". You might end up with a completely different codebase if you do it incrementally.

That was exactly what I thought of when reading the name. Hotpot is great, lets see how well the recommendations will be.

That's the whole trouble about software patents, isn't it?

Maybe this is different in other parts of the world, but in Germany I have never ever been able to do nr 3. Employers over here never set the anchor for negotiating.

At least thats my impression. Prove me wrong and tell me how you were able to do it.

Another very good posting from coderoom.wordpress.com. I like it especially because this way of thinking is uncommon in the industry but very important.

The multiplayer mode of my Android game "Laska". There are just not enough active players to make it work.

But I like the feature because its based on AppEngine and XMPP, so it doesn't have any costs and will probably be available forever. (forever on the internet means sth. like 2-5 years)

I will not attend a long interview process if the salary is completely unknown. The least I do is to tell the possible employer what my expectations are and check whether this is ok for them.

Of course it would be better to make them define a salary range, but until now I was never able to do this.

You will get hired with this approach, yes. But it is the best way to destroy your own value. If someone is constantly asking for a job at this special company, he is also willing to make a lot of compromises for it.

As the author stated, this is an "employer's point of view".

What about labour costs? I am currently working for a startup that has its development office in eastern germany, with a management office near Frankfurt. Although nobody explicitly said that, but the reason is simply that wages are much lower over here.

On the other hand, afaik in Sillicon Valley salaries are very high. I'm just wondering why nobody has brought that up so far.

So you are 27 years old (same as me)?! For how long have you been working now? I'm asking, because I am also thinking about when to quit my current job and what to do next. What holds me back are just two things. First, its the paragliding course I already paid for but didn't finish yet. And second its the feeling that leaving my job would be too early right now. I have been promoted as teamleader just one year after graduating. But still I envy people like you who are able to simply quit and start a new thing.

Jena, Germany

We are currently scaling up our development team. Looking for app developers for mobile phones (Android, BlackBerry, iPhone) or good generalists.

http://www.match2blue.com/

That sounds great. Does it have any drawbacks like a high startup time?

I think the speedup is mainly because of the JIT compiler. Is there any benchmark against cPython with Psyco?

speed.pypy.org gives a timeout for me

Jogging is something I do regularly, as well as inline skating. I also picked up paragliding this year and try to do it as often as possible, but it always depends on the weather.

Today I would boot a Knoppix, backup all user data and make a full reinstall.

But a girl who has been changing boyfriends like her clothes in the past is more likely to do so in the future. Maybe that's because she doesn't fullfill her side of the equation in general.

As much as I understand the developers point of view on this, it is different as an entrepreneur. For a startup it is vital to not have half of your companys knowledge walk out the door. This article just says that there are valid reasons why job hoppers can be good employees. Mark Suster doesn't say that you should never change your job, nor does he deny young people to have some more tries for orienatation.

That was exactly my thought when seeing the website.

Too much money in very early stages is definitly a problem. I am experiencing this at my current job. The company grows very fast and you soon have a lot of people with a lot of different ideas. Problems are solved by getting more employees.