evdawg
Joined 18 years ago
Joined 18 years ago
It depends on two things:
1. Where you get your business
2. Who your competition is
For many, #2 depends on #1. We see three main sources of business: Google (we rank highly for 'Toronto web design'), Dribbble (we have the 2nd most followers in Toronto, and 8th in Canada), and of course, referrals.Dribbble leaves us with clients with the biggest budgets, who aren't afraid of 5-figure prices for web design. This is where we're competing with other high-end designers and thus our prices are more in-line with theirs.
Referrals are the strongest leads, with clients who when they don't have larger budgets are more comfortable stretching a bit because of our strong work for a friend or mutual acquaintance (and we're often happy to mark down a bit for a referral).
Leads from Google are where the clients who get really shocked come in; they don't really understand or appreciate the work that needs to go into good, iterative, considered UI/UX (and the custom development that goes along with it). The competition here includes a swath of companies who game SEO and outsource work offshore, and they can charge considerably less. Thus, our prices look unreasonably higher to the untrained eye.
There's also a phenomenon where cheaper clients expect more. If you move up in terms of positioning yourself as premium, better clients will consider you and your services-- the types of clients who aren't shocked by "high prices" for design and/or development.
So, if you find all of your clients are shocked at your prices, you're not marketing towards the right clients.
I would also highly recommend listening to patio11's podcast #3 about making more as a consultant: http://www.kalzumeus.com/2012/10/10/kalzumeus-podcast-3-grow..., and charging more http://www.kalzumeus.com/2012/09/21/ramit-sethi-and-patrick-...
Lets get real: outside of two $8 charges that he's not even asked to be reversed, this is exactly the same service that he describes as "great" in the same post.
I'm sure Instacart would have no problem at the very least waiving two $8 fees.
My advice to people calling into customer service departments? Just ask. The person on the other line can't read your mind. If you ask for what you want, you'd be surprised at how often you'll get it.
They have a design in a style that's not quite originally theirs-- they've seemingly abused the DMCA to have github remove a completely unrelated UI kit in the same style.
The two items in question are as follows: https://layervault.com/ http://designmodo.github.com/Flat-UI/
Flat UI has (seemingly) been designed and developed completely independently, having nothing to do with LayerVault. No artwork is derived, based-upon, designed by the same artist, etc.
You should care about this because the process is biased towards the accuser. Given no chance to rebut, Flat UI is removed, and disabled. Despite providing his side of the story in the commit comments https://github.com/github/dmca/commit/735e17614cca63102b8414..., the author now has to write a formal counter-takedown notification, and the repository will still be offline for up to 10 days (https://help.github.com/articles/dmca-takedown)
Furthermore, 'designers' and HN users should care because LayerVault runs a 'Hacker News' for designers at https://news.layervault.com/. LayerVault is not the right entity to run this site after these DMCA shenanigans (if in fact no infringement has taken place).
I have difficulty putting it into words but this sounds like one big excuse blaming society/parents/school for his failures rather than himself, which is where they lie.
But, why doesn't this let me pass objects to Mailer methods? I can't help but think passing ids and finding the object again on the other side is bad design.
Myself, over the past few years, instead of a job queue, I have been using a simple gem called spawn (https://github.com/tra/spawn) to fork processes to asynchronously send mail from Rails. It lets me pass objects around... I hope that this asynchronous ActionMailer gets this functionality as well!
Nintendo has released an entirely new system, while Microsoft has kept up with Nintendo's innovation by using devices you already own.
I'm not surprised the site wasn't sold; the "business" of buying and selling sites isn't exactly very "37signal"-y.
With a price now available it's much more transparent for everyone involved; I hope though that this time they are able to accommodate due diligence.
I do a lot of work in CodeIgniter as well as Rails (w/ Ruby 1.9.2 in production), and there's no doubt that my CodeIgniter apps on slower servers with little-to-no deliberate optimization are faster than my Rails apps.
For just one particular example, I have found rendering partials in Rails are such a point of poor performance that I have often found myself avoiding it.
There's this red herring (and a pet peeve) that making the framework 'less bloated' by dropping components or making them optional equals performance. You'll even see a comment on this blog post asking which components to remove to improve performance! It doesn't work that way when the core components of Rails remain slow.
While the speed of Rails had Ruby 1.8.7 to blame for a long time, now that it's being dropped I think 4.0 has a unique opportunity to optimize for 1.9 and make a big difference to the overall speed of the framework.
will_paginate may pollute Array, but it's been a great solution, that has worked for a long time. Be wary of upgrading for the sake of upgrading, especially with that kind of performance degradation.