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.
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.
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.
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.
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.