henrik_w

94 ms·

961.
by henrik_w 13y ago
Absolutely hilaruous! Some good ones: Netflix Now The Largest Single Source of Internet Explorer privacy controls How one man escaped from a major statistical error. 20 lines of e-mail data Skype options turn out to be a Girl in Tech Scott
962.
$125K Job, No Degree or Experience Necessary(linkedin.com)
1 points by henrik_w 13y ago|0 comments
963.
by henrik_w 13y ago
Meetings != being at the office. I work at an office (and get lots done), but only have a one-hour meeting every other week with my team. That's it. I'm very productive at the office, and I really value all the face-to-face intera
964.
by henrik_w 13y ago
Here is another scary read: "I Was a Warehouse Wage Slave" http://www.motherjones.com/politics/2012/02/mac-mcclelland-f...
965.
You're Doing It Wrong(thecodist.com)
3 points by henrik_w 13y ago|0 comments
966.
by henrik_w 13y ago
Have you (or people on your team) done the task yourselves? It's easy to underestimate the effort required.
967.
by henrik_w 13y ago
Even "small" programming assignments take a lot of time. Several years ago, I applied for a job as a developer for a financial trading system. The take-home assignment was to build a small trading system that received buy and sell
968.
by henrik_w 13y ago
"Any sufficiently advanced incompetence is indistinguishable from malice"
969.
by henrik_w 13y ago
I find logging/tracing (that can be enabled/disabled at run time) to be very valuable for debugging, both during development and in production. I blogged about it here: http://henrikwarne.com/2013/05/05&#
970.
by henrik_w 13y ago
Exactly. Not enough developers care enough to be either good mentors or good mentees.
971.
by henrik_w 13y ago
The problem with mentoring programmers is: who is a good mentor? Looking back at when I started coding, very few of the senior people there would not have been good mentors. They simply weren't good enough. They would have taught me th
972.
3 Ways to Teach Yourself to Become Smarter(fastcompany.com)
1 points by henrik_w 13y ago|0 comments
973.
by henrik_w 13y ago
Point taken ;-) I was thinking more along the lines that you can not have a building with 100 rooms, where each room has a door to every other room. In software on the other hand, nothing (except your own sanity) stops you from having 100 c
974.
by henrik_w 13y ago
This is a good, readable paper, with clever pictures to illustrate the points. Many of the ideas in it are well known (especially if you are already familiar with XP). I like the fact that the authors recognize that the BIG BALL OF MUD arch
975.
by henrik_w 13y ago
Should be "she's right" (Kimberly)
976.
by henrik_w 13y ago
Absolutely agree! Without the deadlines, I would not have finished. That said, a 5 weeks course is a lot easier to commit to than a 10 weeks course, since it is very intense during the course. It is simply hard to find the time for it. I li
977.
Tech startups are flourishing in Montreal(montrealgazette.com)
1 points by henrik_w 13y ago|0 comments
978.
by henrik_w 13y ago
"I remember working on a number of student groups at Stanford where we might have had meetings once a week for an hour or two where we’d talk about what needed to get done, and then actually did the work on our own..." It sounds l
979.
Automatically Include Revision in Log Statement(henrikwarne.com)
1 points by henrik_w 13y ago|0 comments
980.
by henrik_w 13y ago
The book ( http://www.amazon.com/Humans-New-York-Brandon-Stanton/dp/125... ) is currently in spot 28 on Amazon's best seller list.
981.
by henrik_w 13y ago
Not all interruptions are created equal though. There are cases when interruptions should be tolerated. If someone is working on a problem (a tester, a support engineer, or another developer), and has a question I know the answer to off the
982.
by henrik_w 13y ago
There's a good article called "Bring back the 40-hour work week"[1] that seems to indicate that working more than 40 hours per week is less productive. [1] http://www.salon.com/2012/03/14/bring_
983.
A Remarkably Simple Way to Save Time(linkedin.com)
2 points by henrik_w 13y ago|0 comments
984.
by henrik_w 13y ago
I've seen this about all-employee get-together too. But when only a couple of times a year it seems purely social, not for getting actual work done. For me, the in-person collaboration takes place pretty much every day.
985.
by henrik_w 13y ago
An overwhelming majority of the people in this thread seem to favor working from home. Does anybody miss face-to-face time? I work in an office, and not a day goes by without face-to-face discussions with my co-workers. I find these discuss
986.
What can we learn from the science of high performance?(farnamstreetblog.com)
1 points by henrik_w 13y ago|0 comments
987.
The Cult of the Root Cause(reinertsenassociates.com)
1 points by henrik_w 13y ago|0 comments
988.
by henrik_w 13y ago
Well named short methods lets you read the code on a higher abstraction level. I usually jump into methods to see what they do the first time I encounter them. Later on, the name (if well named) should tell me what it does, so I don't
989.
by henrik_w 13y ago
Taking a break every hour or so is also good for avoiding RSI. I had RSI pretty bad several years ago, but have recovered completely. Part of the solution was using a break program to help me remember to take breaks for stretches. Currently
990.
by henrik_w 13y ago
Congratulations! It is nice to find your calling (if that's what it is for you). I've been programming professionally for over 20 years, and I still love it for a lot of reasons. Mostly because I get to create every day, and the p

More ›