that it can be turned on and off with the same click is great. double-plus good.
183 karma · joined August 7, 2008
that it can be turned on and off with the same click is great. double-plus good.
the problems i saw in the dev team across the ocean had nothing to do with their technical skill: they were for the most part technically competent. but they were by and large incapable of self-direction. there were a few exceptions, but for most of the team, once they got into a corner they didn't know how to get out of, they punted to an american developer and asked for help.
in my career i've worked with outsourced labor many times. i'd happily trade 5 butts in seats overseas for one guy locally, or even just stateside that understands initiative and can solve their own problems, even if the overseas developers are more 'technically competent'.
you can learn technical competence. you can't learn initiative. getting rid of those on the team with the most initiative can be very expensive.
put nginx in front of thin, start caching frequently used objects, and slice up your database and suddenly speed isn't a problem. php has the (perceived) advantage of running compiled in an apache module, typically. but it's a perception -- you have to do a little more tuning with your rails deployment to make it scream, but make no mistake, it can scream, even under heavy load, and without a huge server farm, at least up to 500K pages/day. i know that number because i've served it. quickly.
in radiant. (gasp! yes, with some caching.)
with one database.
it's a lesson i learned working with tomcat back in the day: defaults suck. learn your framework, learn your app server, pick the Right Thing. it's all about application tuning and app-server choice, and that goes for every language and platform in existence.
However:
Given the snarkery is in this article, and that the author is a 'digital marketing expert', I'm sensing some resentment toward programming 'rock stars'. I've never been called a 'rock star', 'ninja', or what have you in the course of my work. Since I don't currently work in the Valley, I haven't been in the kind of situation where my work environment has video games and huge parties and whatnot. (Though this might change.) As such, I've always worked with a mind toward profit, and for businesses that were like-minded. If there's no revenue at the end of the day, VC or no, the project has failed.
It doesn't take a marketing guy to figure this out, regardless of how anxious they may be prep an 'I told you so'.
No talented programmers are going to go without work, though they might expect less in the paycheck. No solid companies are going to fold, though their next VC round might be more cautious. If you're good, and if your business is good, there's no fear.
So relax or panic, as quality dictates.
also, clean up your website some. it's not awful, just looks a shade shy of professional.
anyone deciding to do this, based on this comment: i demand a beer and sammich as tribute.
now, if amazon could only stay online ...
so in our case, i have a day job, and that job helps support the crew, both of which live very lean. i have the highest expense set (and the most experience, and can generate the highest salary) so i'm the one who works.
what does this mean for the little guys? is there still money out there for people who don't need a dump truck full, but still have a phenomenal idea?
these are the questions i'm looking to have answered. someone want to write that article?
(xp)
so in our case, i have a day job, and that job helps support the crew, both of which live very lean. i have the highest expense set (and the most experience, and can generate the highest salary) so i'm the one who works.
what does this mean for the little guys? is there still money out there for people who don't need a dump truck full, but still have a phenomenal idea?
these are the questions i'm looking to have answered. someone want to write that article?
As for monetization: your target audience is fairly narrow, though if you cleaned it up somewhat, it could not only serve the needs of a given web-strategy team (who'd like the real-time stats), and it could be an effective alert method for folks who don't have that built in. I'm not sure what an annual revenue stream would look like, given the size of the target audience. If you don't have a potential revenue stream, your options for getting investment capital are limited.
(If it were me, I'd sell to interested parties.)
The most important thing is the business model. You provide a service: that of seeing real-time updates on website traffic, by page, with a clear and intuitive display, allowing a company's analysts to get an instant sense of their traffic.
That's your core business. Graphs and traffic stats are covered in the market, focus the business model on what isn't covered yet. You could do quite a bit with the display, making it more 'game-like', and even provide comparisons with other sites that you track.
Now .. a nice startup idea might be an alternate delivery method from scratch. But who has that kind of time?
Besides, I have a hard enough time keeping my iPhone connected on a call.
because we're more interested in delivering a rich experience and useful functionality to our customers than debugging someone else's code. yes, i said it. fixing bugs in IE6 amounts to working for microsoft, and if you have a complex website, it can amount to half your time or more. all this for one browser, with a declining 25% of the market.
and honestly, is that 25% the 25% that's going to be interested in our product? unlikely. so we said screw it. now we have twice as much time to work on the front end. magic.
I wasn't shooting for the poor. I was shooting for a bunch of people. It's roughly half of the households in the country. That's a lot of liquid capital to inject into the economy at once -- around 5% of our GNP.
makes an entrepreneur hope that his idea stays under the radar.
which presidential candidate is talking patent reform? there's a snippet here (http://www.industryweek.com/ReadArticle.aspx?ArticleID=17320), but it only says the obvious. whoever is serious about it, vote for that guy.
#3 - i take a little issue with this one, but not much. if it's straightforward to make something a little more flexible, the payoff is generally good. this depends on a few things: how sure are you that you'll be moving in that direction, how much work is it to add in the extra flex, how difficult will it be to connect up later?
it's worth thinking about, if only for a few minutes. the payoff could be huge, and even it's not, it's rarely wasted time.
any extra income from work (that i didn't blow on hats, mind you) would go into a managed fund, most likely an index fund. days like today though happen periodically, and individual stocks require the kind of detail work that isn't cost effective at those amounts. i make more money working than the growth i would see in the stocks having spent the same time on it.
all that said, if the current project gets picked up ...
sorry if that was unclear.
seriously though, whenever a campaign releases this kind of statement it's always clipped down to sound bite size and paraded around the seedier side of the internet. you think they'd learn.
if django-cms follows the same pattern (and the demo looks like it does) it's good for building content-based sites, brochureware, blogs and such. doubly good if you're building a site for a company who wants to manage their own content.
a few months ago i quit my full-time job to pursue a startup with only $6k in the bank. yeah, food is slim pickins, but we launch stage 1 tomorrow and it feels darn good.
none of this is to say you can't take on a few hours/week of contract work of some kind, but your startup should be your primary focus.
one man's opinion - the best source code doesn't need documentation. the code itself should be expressive.
while not everything can be as nice as rspec (example: http://pastie.org/266866), some descriptive and expressive syntactic sugar can make code more readily understood as well as convenient to write. you can be as obtuse as you want as long as you're the only person looking at the source, but the minute you add a second programmer to the project, you have to think about making their lives easier.