HNHacker News
TopNewBestAskShowJobs

antonpirker

224 karma · joined June 27, 2013

Creating Maps and Services at Maptoolkit. Ex Sentry.

https://www.linkedin.com/in/antonpirker

submissionscomments
antonpirker··on Giants of IT. The giants on whose shoulders we stand. One each day
Ah, now I understand. This would be a really cool thing. With this data we could also create graphs of relationships and we also could find the Erdös of IT.

But I think for me this is to much effort to create something like this (One would need to study all the resumes of the giants to find out their relationships and so on.)

But if anyone wants to create something like this I more then willing to give them my list of giants.

antonpirker··on Giants of IT. The giants on whose shoulders we stand. One each day
What do you mean with "degree of separation". Could you elaborate?
antonpirker··on Giants of IT. The giants on whose shoulders we stand. One each day
thx!
antonpirker··on Giants of IT. The giants on whose shoulders we stand. One each day
I know :) It's a trap! (And the real authors are in the list too, but will show up later this year)
antonpirker··on Giants of IT. The giants on whose shoulders we stand. One each day
hi. indeed it is just a list of persons in no particular ordering.

The persons you name are of course on the list. Lovelace already visible the others will appear in the future. So every day one person is added.

If you have other persons you want to see on the list you can submit person with a link in the footer of the page.

antonpirker··on Giants of IT. The giants on whose shoulders we stand. One each day
on the start page (http://www.giantsofit.org/) you will be redirected to the person of today. i just posted here the first person because the person of today (jack kilby) has no image.

or do you mean more something like to have the person show on on her/his birthday or day of death?

antonpirker··on Giants of IT. The giants on whose shoulders we stand. One each day
Thanks for the link! I will add the missing persons to my list.
antonpirker··on Giants of IT. The giants on whose shoulders we stand. One each day
Hi!

It's not a best of or top 100 list or something, it is in random order. But Tim Berners Lee is of course on my list, so he will show up in the future.

antonpirker··on Ask HN: Good books on debugging?
Somewhere on the internet the book "The Medical Detective" by Bertone Roueche should be a really good read about debugging. But I did not find a place on the internet where you can buy it. Here is a link to goodreads: http://www.goodreads.com/book/show/106164.The_Medical_Detect...

Has anyone read this book and can recommend it?

antonpirker··on Ask HN: How do I become a faster programmer?
I would say:

1) get rid of distractions 2) stop creating bugs 3) get really good in debugging

This sounds a little odd bug getting rid of distractions (set all you favorite websites in /etc/hosts to points to 127.0.0.1) forces you to focus on the problem. Stop creating bugs is impossible, but you can make your best afford to test your code and write good code (read the book "clean code") But I think the biggest speed improvement is if you are really good in debugging. It can take a good debugger to find a bug in a distributed system in 15 minutes, a inexperienced developer can spend over a day and have no clue what the problem is.

antonpirker··on Lessons learned from the big rewrite
One consideration to switch from Perl to Python was that it is easier to find Python/Django developers because more young developers learn Python than Perl. Perl developers (at least in Austria) are mostly seniors and thus most of them already have a good job. (And do not want to change jobs) And a mature Perl developer is more expensive than a young Python developer.
antonpirker··on Lessons learned from the big rewrite
It's a really easy thing to do. But you need enough server resources for this. A mirror of the current production system would be the best thing. If you only have one server where the live system is running and there is not enough resources on this server you can not do this.
antonpirker··on Lessons learned from the big rewrite
'once you have understood how it should be, which results each procedure should return then coding is the most trivial part.'

I wholeheartedly agree with this! The big challenge is that you have the patience (and the patience of the management) to understand the old system thoroughly before starting to write new code.

antonpirker··on Lessons learned from the big rewrite
Yes, right! I forgot about this in the blog post. We counted the rows of some tables. Unfortunately we could not do this with all tables because we had dead data in the old database (ex: child rows without parents). But with the new database we made sure to have all the database features and checks in place to guarantee referential integrity. We also did spot tests to make sure the data is as expected.
antonpirker··on Lessons learned from the big rewrite
Sure you can attempt a rewrite! But you must make sure that you know what are getting into. It is not an easy thing to do, but once the rewrite is done your live gets way better :)
antonpirker··on Delete your code
If you have a naming convention for branches, so you see what branches are expertiments or dead maybe.

But I think having a lot of dead experiment branches is like having a huge back log. It just some place where ideas go to die.

You stumple upon them once in a while and start thinking about why you never finished them and about how this was a good idea but management killed it and so on. I think it is better to delete them and set your mind free so you can focus on the tasks at hand, not the past.

antonpirker··on Delete your code
Very cool link! Thank's for sharing!
antonpirker··on Delete your code
Why should he/she want to find out?
antonpirker··on Delete your code
I always think: the code can be found in the repository somewhere. So if we need it later, we still have it. But in the production the commented out code it is just confusing.
antonpirker··on Elance Flappy Bird jobs
You are way to late for this idea: https://itunes.apple.com/us/app/push-the-button/id294787047?...

:) A friend of mine was really hooked to the game and wanted to push more often than a fellow (drum kit playing) colluege of his.

antonpirker··on Awesome is soo lame
You are right. The world is getting more awesome. And the language changes and gets simpler.

Maybe that's just the normal run of things and should stop complaining about it :)

antonpirker··on Awesome is soo lame
Very cool! Thank's! So the eighties where not that awesome, but since about 1993 the world is getting more and more awesome :)
antonpirker··on Awesome is soo lame
Of course ;) I know there are way more important issues. But I thought I should point it out, maybe others think like me. And maybe one person uses the list to write better descriptions.
← PreviousPage 2 of 2