henrik_w

12 ms·

91.
by henrik_w 5y ago
It didn't take long at all - maybe a day or so. I've been using one ever since, I really like them. It's a very natural grip for the hand (unlike for a regular mouse).
92.
by henrik_w 5y ago
I had similar problems. In my case, the solution was a combination of: ergonomic (split) keyboard, ergonomic mouse (a pen-mouse) and a break program. The most important component was the break program - regular breaks and stretches/exe
93.
by henrik_w 5y ago
A potential downside with consulting is that it seems to me that your pay may be lower if you are a consultant vs working as a developer at a product company (and no stock options etc).
94.
Maximising Differential Entropy to Solve Wordle(aditya-sengupta.github.io)
1 points by henrik_w 5y ago|0 comments
95.
On Code Reviews(henrikwarne.com)
1 points by henrik_w 5y ago|0 comments
96.
by henrik_w 5y ago
Still amazes me how terribly un-ergonomic most keyboards are. I had RSI, but recovered, in part because of a split keyboard (the other two components were a pen-like mouse and a pause program). https://henrikwarne.com/2012&#
97.
by henrik_w 5y ago
Also, the Lindy effect: https://en.wikipedia.org/wiki/Lindy_effect
98.
Anti-patterns when building container images(jpetazzo.github.io)
159 points by henrik_w 5y ago|31 comments
99.
by henrik_w 5y ago
I do something similar, but only for bugs that were especially tricky. I don't do it as I am debugging, but if the bug qualifies, I'll write down the steps I took debugging it, as well as the reason for it, the fix, and (most impo
100.
Selective Unit Testing – Costs and Benefits (2009)(blog.stevensanderson.com)
46 points by henrik_w 5y ago|10 comments
101.
The danger of hidden functional roles(surfingcomplexity.blog)
168 points by henrik_w 5y ago|72 comments
102.
The power of putting yourself in someone else’s shoes(timharford.com)
2 points by henrik_w 5y ago|0 comments
103.
by henrik_w 5y ago
It is mostly for my own reference. However, almost every time I come across a bug like this, I will be discussing it with people in the team. It's often hard to keep quite about it: "You wont believe what just happened..." ki
104.
by henrik_w 5y ago
Great advice! It is similar to something I have been doing for close to 20 years now: whenever I come across a really tricky bug of some kind (usually one that got all the way into production without being caught), I write down some notes o
105.
Things I Believe(gist.github.com)
3 points by henrik_w 5y ago|0 comments
106.
by henrik_w 5y ago
I was helping teaching my son's grade 8 class for about a month and a half. I was surprised at the enthusiasm from the majority of the students - most of them were really into it. It was great expericence, both for me, the other parent
107.
Root cause of failure, root cause of success(surfingcomplexity.blog)
76 points by henrik_w 5y ago|49 comments
108.
Book Review: A Philosophy of Software Design(henrikwarne.com)
2 points by henrik_w 5y ago|0 comments
109.
Polanyi's Paradox(en.wikipedia.org)
3 points by henrik_w 5y ago|0 comments
110.
by henrik_w 5y ago
+1 for https://eli.thegreenplace.net/ - very good!
111.
by henrik_w 5y ago
I interviewed with 3 companies recently, and all had some kind of coding test, although not all of them were Leetcode-style problems. But I did practise on Leetcode before, and it was useful for passing the interviews. However, in my experi
112.
by henrik_w 5y ago
Quite similar to my reasons for blogging: - To know what I think. Formulating or explaining something in writing makes me think it through really carefully. - Sharing. Sometimes there are ways of working I think are really helpful, but mayb
113.
Things I Like About Microservices(henrikwarne.com)
4 points by henrik_w 5y ago|0 comments
114.
A brief introduction to esoteric programming languages(hillelwayne.com)
143 points by henrik_w 5y ago|44 comments
115.
Assertions and Tests (2003)(vanderburg.org)
1 points by henrik_w 5y ago|0 comments
116.
Top Ten Git Tips and Tricks(honeybadger.io)
6 points by henrik_w 5y ago|0 comments
117.
by henrik_w 5y ago
I used Monte Carlo simulations to good effect analyzing the card game Set. Specifically, the odds of not finding a set among the 12 cards. More or less impossible to solve analytically (at least for me), but no problem to write a short prog
118.
by henrik_w 5y ago
I'm not sure if the post applies debugging in production systems or only when developing. For production systems it was not always possible to use a debugger, and you need logging there anyway, so finding bugs by looking at the logs ha
119.
by henrik_w 6y ago
escpae-dot (.) also works for this: "It also works to use !$ instead of escape-dot, but that is slightly harder to type, so I don’t use that anymore." Wrote about it here: https://henrikwarne.com/2018/08/
120.
Recruiting Software Developers – Coding Tests(henrikwarne.com)
1 points by henrik_w 6y ago|0 comments

More ›