henrik_w

89 ms·

901.
Why you should read 100 books(jasonevanish.com)
12 points by henrik_w 13y ago|5 comments
902.
by henrik_w 13y ago
Steve McConnell makes some good points about this in Code Complete too, one of which is "small methods tend to become bigger". Even if it started out as a one-line method, it is not unusual to later find the need to add something
903.
by henrik_w 13y ago
I often end up factoring out things into common methods in the end. That's when I see what parts are common, something I don't always recognize in the beginning (or even in the middle of it).
904.
by henrik_w 13y ago
I have the same experience. I coded C++ in Emacs for many years, then switched to Java in IntelliJ IDEA. I definitely write shorter methods now in Java, than I did in C++ (and it's for the better in my opinion). Navigation in general r
905.
by henrik_w 13y ago
I completely agree - I made the same points in "7 Ways More Methods Can Improve Your Program" http://henrikwarne.com/2013/08/31/7-ways-more-methods-can-im...
906.
Session-based Logging(henrikwarne.com)
1 points by henrik_w 13y ago|0 comments
907.
by henrik_w 13y ago
For me, the fastest way of understanding code is a mix (back and forth) of reading it and running it. Some questions on how it works are more easily answered by running it and seeing what happens, while other questions are better answer
908.
by henrik_w 13y ago
I think it is understood that we all read code during a typical project. I think what the OP is referring to is code reading for the purpose of improving your skill in general, to get exposed to code that you wouldn't normally see by j
909.
by henrik_w 13y ago
From the article: "Innovation has brought great benefits to humanity. Nobody in their right mind would want to return to the world of handloom weavers. But the benefits of technological progress are unevenly distributed, especially in
910.
by henrik_w 13y ago
Previous submission: https://news.ycombinator.com/item?id=7070945
911.
by henrik_w 13y ago
Single data point: I had severe RSI problems a few years ago, but I am not completely recovered. For me, the biggest single part of the solution was to start using a break program. I also use a split keyboard and a pen mouse, but the break
912.
Why Credentials are Useless and How to Spot People Who Genuinely Love Their Jobs(linkedin.com)
1 points by henrik_w 13y ago|0 comments
913.
Living a High-DPI desktop lifestyle can be painful on Windows(hanselman.com)
188 points by henrik_w 13y ago|142 comments
914.
by henrik_w 13y ago
Another good one for (more general) programming problems is Programming Praxis: http://programmingpraxis.com/
915.
by henrik_w 13y ago
Regarding production software: I gave a talk to university students on the difference between professional software development and programming for a university course, and wrote about it in "Working as a Software Developer"[1]. I
916.
Like It Or Not, You Work in Customer Service(linkedin.com)
1 points by henrik_w 13y ago|0 comments
917.
by henrik_w 13y ago
Agreed. The Mythical Man-Month by Fred Brooks is another great book. It is famous for Brooks's law: "adding people to a late project makes it later". But for me, even better with that book was one page at the end of chapter o
918.
by henrik_w 13y ago
Even if a lot of the ideas are also present elsewhere, I still think it is a great book, especially the parts on how to actually write code. For example the chapters on naming, code lay-out, conditionals and methods/functions. I don&
919.
by henrik_w 13y ago
Yep, that's a great book, with lots of good advice. I got the first edition, which was call "My Job Went to India, and All I Got Was This Lousy Book"
920.
by henrik_w 13y ago
Coders at Work is great - easy to read (but long), with a lot of interesting information. Some sample questions the author asks: "How do you design code?", "What is the worst bug you've ever had to track down?", &qu
921.
by henrik_w 13y ago
I agree, that's an excellent reason to create a function/method. Reason 7, self-documenting code: http://henrikwarne.com/2013/08/31/7-ways-more-methods-can-im... (but of course it doesn't mean
922.
Comments should be sentences(nedbatchelder.com)
42 points by henrik_w 13y ago|49 comments
923.
SET Card Game Probabilities(henrikwarne.com)
1 points by henrik_w 13y ago|0 comments
924.
Amazon's Current Employees Raise the Bar for New Hires(online.wsj.com)
4 points by henrik_w 13y ago|1 comments
925.
Why I Love Coding(henrikwarne.com)
3 points by henrik_w 13y ago|0 comments
926.
by henrik_w 13y ago
Absolutely agree. There are many reasons why I love to program, and number one on the list is "The sheer joy of making things"! http://henrikwarne.com/2012/06/02/why-i-love-coding/
927.
Mobile payments - Swedish ambition(economist.com)
2 points by henrik_w 13y ago|0 comments
928.
Life’s Work: Salman Khan(hbr.org)
64 points by henrik_w 13y ago|5 comments
929.
by henrik_w 13y ago
Yes, it was one of the original three. The others were AI and Databases. I took the databases course, and wrote about the experience here: http://henrikwarne.com/2011/12/18/introduction-to-databases-...
930.
by henrik_w 13y ago
Yes, I'm guilty of that too. The main reason I don't take more courses is the time it takes to take them. I've taken 3 courses (databases, algorithms I & II), and they were all great, but required a lot of work. So while

More ›