1,590 karma · joined July 22, 2010
CTO of Endgame.io, ex-founder of Keen.io
made @hipsterhacker, @techcrunchonion, and some other tech comedy stuff that would be more incriminating were I to share it ;)
It's not as though could be browsing one day in search of "abortions Chicago" or "genital warts" and have that auto-published to your FB page. You'd have to give an app explicit permission to share activities on your behalf.
How do you pay for it? (Do we, the users?)
Is vows-bdd like a Cucumber to vows'/jasmine's RSpec?
A QA note: The text spills offscreen and the CSS doesn't allow me to make it readable in Chrome on a 13" MacBook Air:
I've tried to tone the copy down quite a bit
What do you think now?
Seems we've hit on a real need with our solution. It's testing super well, and we've quickly turned into a very lucrative business.
No time yet for design; we're a week old and only just now put up a website.
Let me know what you think!
kw
fixed with double-hyphens, thanks
This is all I used: http://validator.w3.org/check?uri=http%3A%2F%2Fschmetrics.co...
luckily for us, those are the kinds of clients we don't want to deal with right now :)
I'd argue that the hipness of a language/tech stack is actually an important business consideration today, if only due to the short supply of good startup dev talent. Good developers have their pick of jobs right now. For instance, most of the PHP badasses I know are regularly turning down PHP work in favor of working with something newer.
After all, the smartest people like to learn more than anything else.
Under the Site misses MooTools, which is being loaded asynchronously on my site via Google Libraries API
Impressively, Built With even managed to detect that I was making an AJAX call to StackOverflow's API.
First: http://drktd.com/8Jgn
After clicking the 'Add It!' link: http://drktd.com/8Iaf
The wording on the previous page had me expecting a page for manually adding technologies to my site's stack a la Bagcheck.com.
You may be impervious to design, but I assure you, users are not.
I'll stick with Name.com for all my non-COM/ORG/NET tld's.
Lost of best practices, from the workflow methodologies you lampoon to the widespread use of (and reliance on) design patterns, only appear to exist to give bad programmers a way to contribute -- or at least to avoid them doing harm.