roytomeij

6 ms·

1.
Mastering Concurrency in Ruby(blog.appsignal.com)
3 points by roytomeij 11y ago|0 comments
2.
by roytomeij 11y ago
Dropping this here: https://appsignal.com — looks great, works even better. And it's one of the few tools that treats exceptions and performance both as first class citizens (full disclosure: I'm a co-founder).
3.
by roytomeij 13y ago
Who can live on < 1 stroopwafel per week?
4.
Stroopwafel.me: Redefining SaaS (Stroopwafels as a Service)(stroopwafel.me)
4 points by roytomeij 13y ago|2 comments
5.
Should you use a Sass mixin or extend?(roytomeij.com)
1 points by roytomeij 13y ago|0 comments
6.
Books (and pasta machines) as monitor stands. XSLT, really?(monitorstands.tumblr.com)
2 points by roytomeij 13y ago|2 comments
7.
JQuery toggle() is slow, JavaScript to the rescue(blog.appsignal.com)
1 points by roytomeij 14y ago|0 comments
8.
The missing media query: element dimensions(roy.io)
1 points by roytomeij 14y ago|0 comments
9.
Fostering a development community (follow-up to yesterdays Rails/PHP shit storm)(roy.io)
1 points by roytomeij 14y ago|0 comments
10.
by roytomeij 14y ago
Unless you want to seriously screw up the user experience: don't.
11.
Will Rails be the new PHP?(roy.io)
42 points by roytomeij 14y ago|46 comments
12.
Don't use class names to find HTML elements with JS (follow-up w/ new metrics)(roytomeij.com)
2 points by roytomeij 14y ago|1 comments
13.
The first legally binding contract I wrote… at age 11(roy.io)
1 points by roytomeij 14y ago|0 comments
14.
80beans opens "Open Test Lab" for mobile devices in Amsterdam(80beans.com)
1 points by roytomeij 14y ago|0 comments
15.
On Public Speaking: Story and Tips by a Tech Speaker(roy.io)
1 points by roytomeij 14y ago|0 comments
16.
Using Sass' each to create DRY selectors(roy.io)
2 points by roytomeij 15y ago|0 comments
17.
Sass doesn't create bad code. Bad coders do.(thesassway.com)
4 points by roytomeij 15y ago|0 comments
18.
by roytomeij 15y ago
Good one, thanks!
19.
by roytomeij 15y ago
It is, with IE9 handling just over 7,000 operations per second (based on the jsPerf test: http://jsperf.com/long-selectors-vs-data/2 ) vs. 25,000 in Chrome. Don't go all out I'd say, but in most scenario's even that number of operations wi
20.
Don't use class names to find HTML elements with JS(roytomeij.com)
14 points by roytomeij 15y ago|6 comments
21.
Modernizr & the Sass parent reference(roytomeij.com)
1 points by roytomeij 15y ago|0 comments
22.
Stop abusing the placeholder attribute(roytomeij.com)
2 points by roytomeij 15y ago|0 comments
23.
by roytomeij 15y ago
I should maybe have indicated that the clients we're talking to usually have between $20,000 and $70,000 to spend. They employ people who're expected to be experienced.
24.
by roytomeij 15y ago
All great tips, thanks for sharing. I didn't put a disclaimer in the post, but our experiences are indeed based on larger projects, typically at least in the $20,000+ range. Those are always tailor made apps, nothing off-the-shelf (apart fr
25.
by roytomeij 15y ago
I've been there and I know how that sucks. In those cases I figured it was best to take my loss and get it done and over with as soon as possible (I'm sure that's what you're doing). In my experience there's one thing you need to watch out
26.
by roytomeij 15y ago
I completely agree. It's tiresome to repeat yourself over and over, specially when you know it's also in the clients' best interest to not work with someone who guesses (and therefore often overestimates to be on the safe side). I'm hoping
27.
Myth of the Flat Fee(80beans.com)
56 points by roytomeij 15y ago|30 comments