henrik_w

25 ms·

241.
Programming: Math or Writing?(henrikwarne.com)
1 points by henrik_w 8y ago|0 comments
242.
How well does “smooshing” shuffle cards? (2015)(quantamagazine.org)
2 points by henrik_w 8y ago|0 comments
243.
What Should a Software Engineering Course Look Like?(tomasp.net)
2 points by henrik_w 8y ago|0 comments
244.
by henrik_w 8y ago
This matches my experience too. In my opinion, the way to sell the job is to explicitly mention all the advantages - the company name, the tech stack, why it is a great place to work etc. The most annoying recruiters are the ones that have
245.
Supposedly ‘Fair’ Algorithms Can Perpetuate Discrimination(wired.com)
2 points by henrik_w 8y ago|0 comments
246.
by henrik_w 8y ago
I know. When I first read the XP book by Kent Beck it was a revelation. That was the first time I saw a methodology that I felt worked and agreed with my own experience. Planning everything out in advance is hopeless. There are two great qu
247.
by henrik_w 8y ago
This is exactly how I see bugs - a mystery to be figured out. In the process of figuring it out, you usually learn a lot about the system, and you (hopefully) become better at avoiding creating bugs yourself. https://henrikwarne.
248.
by henrik_w 8y ago
Here is a counterpoint. I worked with software development at Ericsson for about 10 years before XP and agile came out. I too had a private office, and I recognize a lot of what you describe. While it was nice, it was not a very productive
249.
by henrik_w 8y ago
"The Creeping IT Apoclypse" is on the same theme: https://news.ycombinator.com/item?id=18930781
250.
How I Choose What to Read(perell.com)
2 points by henrik_w 8y ago|1 comments
251.
by henrik_w 8y ago
I taught my son and his class (grade 8 at the time) a bit of Python programming during several weeks about a year ago. It went surprisingly well. I concentrated on basic concepts: variables, statements in sequence, conditionals and loops. I
252.
Accounting for time(hbr.org)
1 points by henrik_w 8y ago|0 comments
253.
by henrik_w 8y ago
For me it is: - the product is SW - great colleagues - challenging problems - cool technology - having users - good salary - good tools - max 40 hours a week - minimal bureaucracy - working remote when needed https://henrikwarne.
254.
by henrik_w 8y ago
Here is a looong list in a similar vein, "Best websites a programmer should visit": https://github.com/sdmg15/Best-websites-a-programmer-should-...
255.
Even Tesla Seems to Be Getting Real About Self-Driving Car Tech in 2019(jalopnik.com)
2 points by henrik_w 8y ago|0 comments
256.
How to Learn CSS(smashingmagazine.com)
3 points by henrik_w 8y ago|0 comments
257.
by henrik_w 8y ago
I think the idea is that you are somewhat a specialist in 2 areas (but not a worldclass specialist). As I recall, that advice does not apply to being a generalist.
258.
by henrik_w 8y ago
I didn't think it was that great. It was interesting, but a bit repetitive and a bit too long.
259.
by henrik_w 8y ago
+1 for Liar's Poker. Funny, revealing and really well written.
260.
by henrik_w 8y ago
I really enjoyed "Dreaming the Beatles: The Love Story of One Band and the Whole World" by Rob Sheffield
261.
by henrik_w 8y ago
If you use Goodreads to track what you read, you get some stats per year, like number of books read, number of pages read. Mine: https://www.goodreads.com/review/stats/63629672-henrik-warne
262.
by henrik_w 8y ago
+1 for Coders at Work! Excellent, long interviews with really famous developers and computer scientists.
263.
by henrik_w 8y ago
I really enjoyed it too. My main takeaways: 1. Use systems, not goals. A system lets you feel good every time you follow it, whereas a goal only makes you feel good when you reach it 2. Combination of skills. If you can be good (say top 20%
264.
by henrik_w 8y ago
I thought The Fear Index was quite disappointing, simply not believable for me.
265.
by henrik_w 8y ago
+1 for A Man Called Ove - surprisingly good.
266.
by henrik_w 8y ago
There is also the book "Exercises in Programming Style" that uses the term frequency problem to illustrate 33 different programming paradigms (including a shell solution). https://www.amazon.com/Exercises-Programmi
267.
by henrik_w 8y ago
+1 for The Martian. Excellent!
268.
Thoughts on Interviewing at Big Tech Companies(barbarianmeetscoding.com)
7 points by henrik_w 8y ago|0 comments
269.
by henrik_w 8y ago
Very good advice, I'll save that quote.
270.
by henrik_w 8y ago
Many of the reasons why I blog are for my own benefit, but it is also fun if people read what I write, so it is a mix really. My reasons in roughly order of importance: - Knowing what I think - Sharing knowledge - Venting - To learn (when I

More ›