onderhond

13 ms·

91.
by onderhond 15y ago
Google bases their actions on dry information harvested from people. Human science does not exist without statistics, and statistics requires you to make assumptions. Google can analyze me till kingdom come, it cannot correctly predict what
92.
Rel=next and rel=prev - how Google might be killing a spec(onderhond.com)
35 points by onderhond 15y ago|22 comments
93.
Responsive design and why it's not ready to be an industry standard(onderhond.com)
2 points by onderhond 15y ago|0 comments
94.
Using the html5 element for content type instances (exclusively)(onderhond.com)
1 points by onderhond 15y ago|0 comments
95.
Dry-htmling - writing html from wireframes(onderhond.com)
2 points by onderhond 15y ago|0 comments
96.
How to mark-up solitary, non-content links(onderhond.com)
2 points by onderhond 15y ago|0 comments
97.
The pitfalls of graceful degradation(onderhond.com)
1 points by onderhond 15y ago|0 comments
98.
The deceptive techniques of UX design(onderhond.com)
1 points by onderhond 15y ago|0 comments
99.
Html form mark-up: the big one(onderhond.com)
2 points by onderhond 15y ago|0 comments
100.
Why css restrictions suck - fighting the tr(onderhond.com)
1 points by onderhond 15y ago|0 comments
101.
How the new html 5 form attribute willingly breaks html structure(onderhond.com)
1 points by onderhond 15y ago|0 comments
102.
Why css will never catch up with design: the design axiom(onderhond.com)
2 points by onderhond 15y ago|0 comments
103.
Html5 data- attribute: use-cases and internal vs external use(onderhond.com)
1 points by onderhond 15y ago|0 comments
104.
Twitter, or how a community of 400.000 is reduced to 20 poor quality replies(onderhond.com)
23 points by onderhond 15y ago|7 comments
105.
How to hire a front-end developer: an extensive checklist(onderhond.com)
1 points by onderhond 16y ago|0 comments
106.
HTML-man: the future protector of consistency(onderhond.com)
1 points by onderhond 16y ago|0 comments
107.
How frameworks reduce the quality of your work(onderhond.com)
1 points by onderhond 16y ago|0 comments
108.
Reviving accessibility concerns: doing it right(onderhond.com)
1 points by onderhond 16y ago|0 comments
109.
The death of the one-man show web developer(onderhond.com)
2 points by onderhond 16y ago|1 comments
110.
Trying to find out how browsers render a page(onderhond.com)
1 points by onderhond 16y ago|0 comments
111.
More or LESS css - first impression(onderhond.com)
3 points by onderhond 16y ago|0 comments
112.
Css efficiency - found inefficient(onderhond.com)
2 points by onderhond 16y ago|0 comments
113.
How the web raped animation(onderhond.com)
1 points by onderhond 16y ago|1 comments
114.
Pros and cons of css variables, mixins and nestings(onderhond.com)
1 points by onderhond 16y ago|0 comments
115.
Where the css box model fails us(onderhond.com)
4 points by onderhond 16y ago|0 comments
116.
by onderhond 16y ago
It's quite funny to criticize a html-guy on worrying about semantics ... seriously, it's the core of html and the core of my every day job. If you want a more detailed explanation, check the "sad semantics" section here: http://www.onderho
117.
by onderhond 16y ago
Whatever the w3c would like to be, there is a different reality, namely what people perceive them to be. Client, back-end programmers and other non-front-end people alike look to the w3c when it comes to front-end. And seeing they've just l
118.
W3c - an embarrassment for front-end(onderhond.com)
16 points by onderhond 16y ago|12 comments
119.
How Google and Apple are fucking up the web(onderhond.com)
4 points by onderhond 16y ago|0 comments
120.
Writing about front-end: taking responsibility(onderhond.com)
2 points by onderhond 16y ago|0 comments

More ›