roytomeij
Re:Exception Monitoring and Response
on Tuesday June 16, 2015 @04:46PM (#9728583)
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).
Re:Stroopwafel.me: Redefining SaaS (Stroopwafels as a Service)
on Monday March 31, 2014 @06:11PM (#7504570)
Who can live on < 1 stroopwafel per week?
Stroopwafel.me: Redefining SaaS (Stroopwafels as a Service)
Should you use a Sass mixin or extend?
Books (and pasta machines) as monitor stands. XSLT, really?
JQuery toggle() is slow, JavaScript to the rescue
The missing media query: element dimensions
Fostering a development community (follow-up to yesterdays Rails/PHP shit storm)
Re:Disable Text Highlighting With CSS
on Sunday September 30, 2012 @10:30AM (#4592939)
Unless you want to seriously screw up the user experience: don't.
Will Rails be the new PHP?
Don't use class names to find HTML elements with JS (follow-up w/ new metrics)
The first legally binding contract I wrote… at age 11
80beans opens "Open Test Lab" for mobile devices in Amsterdam
On Public Speaking: Story and Tips by a Tech Speaker
Using Sass' each to create DRY selectors
Sass doesn't create bad code. Bad coders do.
Re:Don't use class names to find HTML elements with JS
on Wednesday January 25, 2012 @02:00AM (#3508678)
Good one, thanks!
Re:Don't use class names to find HTML elements with JS
on Wednesday January 25, 2012 @02:00AM (#3508676)
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 will be acceptable.
Don't use class names to find HTML elements with JS
Modernizr & the Sass parent reference
Stop abusing the placeholder attribute
Re:Myth of the Flat Fee
on Wednesday May 25, 2011 @11:36AM (#2584328)
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.
Re:Myth of the Flat Fee
on Wednesday May 25, 2011 @11:23AM (#2584264)
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 from the framework and all the open source components we use, but nothing like Wordpress). What we do is often pretty specific.
I think your comment, as you said, has some great insights when it comes to smaller projects.
Re:Myth of the Flat Fee
on Wednesday May 25, 2011 @10:54AM (#2584154)
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 for, and that's being a nice guy. You might start feeling sorry for your client because stuff is taking longer than planned, which makes it harder to say no to just minor changes to the scope. They will only take you 5 minutes each, and it keeps the client of your back. Those are the things that really get to you when it comes to staying motivated I think.
Re:Myth of the Flat Fee
on Wednesday May 25, 2011 @10:14AM (#2584011)
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 our prospective clients will read this blog post first and then -still- want to contact us. They are the gems you want to work with.