h2s

9 ms·

1.
by h2s 12y ago
> Women are like dogs Fuck off.
2.
by h2s 12y ago
Yeah. The hand-wavey reference to advances in parallelisation and cloud runner infrastructure doesn't adequately address the drawbacks of this "post-TDD" approach.
3.
by h2s 12y ago
Worth bearing in mind that this is effectively DRM for email, with all the negative connotations that DRM brings.
4.
by h2s 13y ago
Better still, it deserves to be replaced with a better name. Comments should not be our first port of call when we notice an issue like this in code. Fix the name. If you can't fix the name, you hang your head in shame and then you w
5.
by h2s 13y ago
See this comment: https://news.ycombinator.com/item?id=7296586 Good commenting is no substitute for good naming. For a variable containing the number 1, "three" is a shitty name.
6.
by h2s 13y ago
This is a bloody clever counter-argument as well as an excellent example of the right way to use comments.
7.
by h2s 13y ago
Eagerly looking forward to the explanation for this weird juxtaposition. http://i.imgur.com/huUv09m.png
8.
by h2s 13y ago
I don't think there's enough attention on the fact that the strict MVC approach of big old school web frameworks like Rails is an increasingly glaring architectural dead-end. The "model" part of an MVC application is inv
9.
by h2s 13y ago
Rather than an exception, I think this is an example of the precise scenario in which it's most inappropriate to use comments. > visually represent logical segments of the code This is exactly the use case in which function
10.
by h2s 13y ago
Never write comments that re-state the implementation. # Try to read the configuration file. If this wasn't already obvious without the comment, then the code is a mess. Tidy the code up instead of painting over the problem wi
11.
by h2s 13y ago
Hell yes. It's a shame that this isn't just conventional wisdom. Having had a colleague recently join and then leave shortly afterwards because of factors that he could have uncovered by asking some of the questions in this list,
12.
by h2s 13y ago
That's correct, but we should still not allow them to misdirect our attention while they tighten the screws.
13.
by h2s 13y ago
Stop calling it a "porn filter". It's censorship of the internet. If it was actually a "porn filter", its purpose would be to filter pornographic material. In reality, there is a list of categories to be censored, a
14.
by h2s 13y ago
It's funny, my gut reaction to your explanation is one of technological conservatism. "This is a problem that shouldn't exist! Don't use JavaScript for that!", I want to exclaim. But I remember thinking similar thin
15.
by h2s 13y ago
I have a vague feeling of excitement about the future of JS development in general. Whether or not Meteor is going to be the bringer of that bright future is something I'm not so sure of. On the topic of constructive criticism, differe
16.
by h2s 13y ago
Couldn't agree more. I made the mistake of using Ruby to build a CLI application too, and distribution is a massive hassle. At the moment I'm still at the awkward stage of distribution via Rubygems which the article advises strong
17.
by h2s 13y ago
While I don't have any ideas, I can at least add my voice to those saying "I will send money to this man if there is a way to do so". I'm dubious of that Journalistic Source Protection Defence Fundraiser that's been
18.
by h2s 13y ago
When the first line of your article contains an Amazon referral link to buy the book and make you a quick buck, how is anybody expected to take your subsequent glowing praise of the book's contents seriously? Ending the post with a qui
19.
by h2s 13y ago
Same goes for --ignore-space-at-eol The better solution would be to teach people to stop being careless about trailing whitespace in their commits.
20.
by h2s 13y ago
There's a sliding scale of HATEOAS-ness. I've seen a much more extreme form of it described elsewhere. Mark Seemann ( http://blog.ploeh.dk/2013/05/01/rest-lesson-learned-avoid-ha... ) describes an app
21.
by h2s 13y ago
This is a great resource. Feels like the next step after Matt Gemmell's post "API Design" ( http://mattgemmell.com/2012/05/24/api-design/ ) where he called APIs "UX for developers"
22.
by h2s 13y ago
Finally, DRM for email!
23.
by h2s 13y ago
Using the right framework for the right reason is a productivity boost. I agree. The difficulty with this is in the long term. Things change: new opportunities, new technologies, new developers, new functionality. Even if you were
24.
by h2s 13y ago
I'm sad to say that I gave up reading it before it was finished because of exactly this. On a large screen, it's really disorientating.
25.
by h2s 13y ago
Apart from being based on a piece of programming terminology, the twelfth item in the list seems not to be about programming at all, but rather a flagrant plug for a book. How is this the first time I have noticed that?
26.
by h2s 13y ago
Unfortunately they are becoming more and more prevalent in the PHP community. For example, here they are in the Symfony project's coding standards: http://symfony.com/doc/current/contributing/code/st
27.
by h2s 13y ago
Personally, I'm glad I co-operated with my previous employer by delving into the specific factors that led to my decision to leave. Despite the fact that I obviously left, I really liked those people, and sometimes you go out on a limb
28.
by h2s 13y ago
That deleted one was posted by me. After I posted it I felt guilty about triggering yet another gossipy discussion about Linus, so I deleted it. Not that I was blameless, choosing such a gossipy link to submit.
29.
by h2s 13y ago
This is by far the number one API design anti-pattern in terms of how widespread it is. It's like bad kerning: once you've seen it, it's everywhere, and nobody seems to notice. It usually results from writing code with a shor
30.
by h2s 13y ago
This is standard practice. MPs receive a lot of letters from their constituents and it isn't practical to send individual responses. As well, Amber Rudd and Damien Green are conservative MPs, so they can be considered supporters of thi

More ›