343 karma · joined July 28, 2009
RewriteRule \.(asp|aspx|php|jsp)$ - [F,L,NC]
RewriteRule (w00tw00t) - [F,L,NC]
RewriteRule (phpmyadmin) - [F,L,NC]
RewriteRule (php-my-admin) - [F,L,NC]
That cuts off those requests before they hit a Rails process and suck up any additional resources.
Also, hey Jason! Still owe you a beer sometime.
The first customer that did _not_ come from my personal network was a result of posting to app directories such as feedmyapp.com and the like.
The best advice I can give on signing and keeping your first customer is to _make them happy_. Be nice. Crack jokes. When they call or email you, respond immediately. Your first customers are really important because they're vetting your business model in addition to trying your product.
Accept/understand that, as you observe your first customers interacting with your product, you're going to have to make changes. Make them quickly and reasonably.
Every company is unique, but that's how I found and retained my first customers.
They unabashedly violated two rules of logo and print media design, and it's so blatant that I can't believe it was an accident. Their logo features a gradient (print-media epic fail), and two low-contrast overlapping colors, the P and the background square (also a print-media epic fail).
I hope that the executives do not knee-jerk a reaction and demand a logo redesign, but instead play out the campaign and see how it pans out. I'm not convinced it was a mistake.
Perhaps the real redesign wasn't the logo, but their website and online presence?
As someone who's hired (good and bad) engineers in both UI/UX and back-end disciplines, my first impression of it was "Yeah, it's not pretty, but he does not allege to be a designer." At that point, I checked out the source code. It was not spectacular, but he did communicate an working grasp of the technology he professed to understand.
If this resume was judged in a biased lean towards UI/UX, my opinion is that you'd be passing up a potentially hard-working and dedicated employee. With a little help from a designer, this guy could possibly do great things.
I've employed many of the tactics he describes and have achieved >15 M/s of dynamic content through MySQL. Not Facebook, but it was fast and scalable for the market my app was geared towards.
How are your design skills?
Edit: by design I mean aesthetics and user experience
My competitors (uservoice.com, ideascale.com, and a few others) charge a similar base fee, but they both have a tier-based pricing structure. I'm shooting for more of an a-la-carte model that lets my customers choose which features they want.
If, after a few months or so, I find that my pricing is too high, it's a lot easier to lower prices than raise them:).
Thanks again!
...does anyone else have a tough time getting past that?
Example: create a document with two lines of tab-stopped text with varying lengths, and then export to HTML.
My company noticed an absolutely whopping performance boost when we dropped XML in favor of JSON for a transport format, fwiw. Ruby has quite possibly the slowest XML parsing libraries on the block (even when you wrap libxml), and we avoid parsing XML at all costs now.
Trading Error at Major Firm Blamed for Market Plunge: Sources (Story Developing)
This is some serious load...
Ha! When I started to program, everyone told me the opposite. After weeks of head scratching and spending more time learning editors than coding, I secretly switched to Pico. But man could I use the hell out of Pico.
I've reviewed hundreds of resumes, hired great people, and hired some not great people. Sometimes they leave because of you and your company, sometimes they don't. In my experience, a history of short employment can mean one of two things:
1. This candidate is extremely talented, independent, and a self-starter. Hire these people. Now. 2. This candidate leaves before he or she is truly accountable for the code they write.
2 is very dangerous. You don't want to hire an engineer who will write a subscription billing platform and quit the week after launch. It's often tough to determine the difference between 1 and 2, and it takes many pointed questions to figure it out.
The author has clearly not had to use contentEditable :)