Recent submissions

Comment · 6 years ago
Comment · 8 years ago
Barrens. General. Chat... /shudder
Comment · 10 years ago
Seriously, create a small report based on the logs that tracks visits, popular calls etc. It will do you good every morning to check it (charts and comparisons are great) and it will be an asset when promotion time comes around and you have define your "contribution" to the company :)
Comment · 10 years ago
Agree on the cognitive overhead.

People will and are arguing that "it is kernel code, it should be complicated" but I really think this is backwards. Because it is low level and debugging is really cognitively intense and difficult at this level the code should be even clearer and easier to understand.

Comment · 10 years ago
Projects should be accessible to new developers regardless of their complexity level. Even operating systems. Otherwise they will simply stagnate and die.

Also, "less skilled devs" are just people that are still learning. We've all been there.

Comment · 10 years ago
Comment · 10 years ago
I don't know why I'm even replying, this will get so much hate here, oh well...

1. Just because things aren't done "the way you would do them" doesn't mean they're "bad" or "wrong".

2. If you're not on a solo project, I've found writing correct but less "clever" code to help shorten ramp-up time for new devs and be more beneficial to future maintainability of the code-base and system.

TL;DR; Swapping values by XOR'ing may look elite and clever but hurts you in the long run.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton