Live data from Hacker News

Startups: Don’t Hire Frontend or Backend Webdevs

trottercashion.com

31–40 of 44 posts

Re: Startups: Don’t Hire Frontend or Backend Webdevs

#31

I'm kinda curious if his definition of "frontend" developers is the same as mine. To me, the frontend includes everything up to the purely-computational algorithms and storage of the website. That's the HTML/CSS/JS, but also the webserver/webframework, RPC system, or database API (but not the database itself). Rails is a frontend technology. I consider backend work to the computationally-intensive part. Data mining,…

> I'm wondering if his idea of a startup is the typical web 2.0 startup, where you slap a web framework on top of a database [...] I suspect that many more successful startups will start needing people who can do the algorithmic heavy lifting.

Couldn't agree more with you. Most of the current generation of start-ups is extremely boring. Quite frankly, looking at Techcrunch headlines is depressing. When you look at job requirements they post it's pretty much the same: they're looking for people to write CRUD screens in scripting languages. The current crop isn't about technology, it isn't about the people who enjoy writing non-trivial software and couldn't be happier that some one out there is willing to pay them for it (e.g., people mentioned in Graham's Great Hackers essay; reading that essay felt like music to my ears when I first read it and got me interested in the idea of startups in the first place).

This is opposed to those who see technology as just a means to wealth creation (and there is absolutely nothing wrong with that, there are plenty of "boring" problems that nonetheless benefit humanity when they're solved). That's not to say the founders aren't smart: many are coming from top schools, leaving Google etc... to start their companies; that makes it even more explicit that they're not there to solve interesting problems, they're there for something else. It looks like an awful waste of talent.

Out of the web 2.0 crowd, when you look at the successes, you'll also notice that they're ones solving non-trivial problems (machine learning/recommendation systems, graph algorithms, scalability and efficiency, etc...).

I'd love to see more technology startups emerge (i.e., those who do something technology-wise that no one else dares to try). It's a riskier route, but it's also more rewarding: you'll be able to attract more passionate people who would be more willing to actually take the risk even if the pot of gold isn't in sight (e.g., without VC funding a 100mm+ valuation).

Re: Startups: Don’t Hire Frontend or Backend Webdevs

#32

The problem with this notion - as mentioned by a few people in the article's comments - is that it is difficult to find developers with a high level of expertise for both sides of the fence. Is it worth the extra expenditure of time in the hiring process to look for two people who are good in both realms? Or is it better to spend less time looking for one front-end expert (with passable server skills) and one server-…

> If you are lucky enough to hire that person, don't pigeon hole them.

I was thinking the same thing after reading "You’d be much better off getting one of your kickass API developers to spend a little time on the website portion, which would free salary space to hire another kickass API developer.".

My immediate thought is that you'd now have a front end developer. Unfortunately, it is your former API developer turned reluctant front-end designer, who is likely annoyed that his job description changed midstream.

Re: Startups: Don’t Hire Frontend or Backend Webdevs

#34
For a consumer web app, I would split it into a Product Designer (someone who can do art, UI design, product concept, workflow, html/css/js), and a developer (who does some js, all server side work, and the related tools.

Finding the product designer is going to be the hard part -- there are a very limited number of visually oriented product designers who can also code. I think that person should either be a cofounder or hired as first employee with 1-5% of equity; on par with a later VP Engineering hire.

Re: Startups: Don’t Hire Frontend or Backend Webdevs

#35

I agree with the idea that specialists are probably not a good fit for an early stage startup. There are a lot of hats to wear. But front-end vs back-end is a false dichotomy. If you can get your hands on a brilliant illustrator who can also do pixel icon design as well as strong layout and UX , then even if their HTML skills are shakey they're going to be a strong asset. Similarly, if you have a back-end dev who wri…

Yes!

Draft for talent, not for needs.

This has been proven time and time again that people that grab the top talent in a limited talent pool (rather than trying to address their perceived needs) are the most likely to succeed.

The best analogy is sports. In (American) football, the Colts' Bill Polian regularly uses this strategy in the draft. In football, ManU's Sir Alex has a strategy to acquire what he calls "characters." While you may not like either of these teams (I love them both! :) you cannot deny that they have been among the most dominant franchises under their managers.

The real challenge is to somehow identify the best talent! :)

Re: Startups: Don’t Hire Frontend or Backend Webdevs

#36
God forbid you're grouped into a caste of skill sets based on experience and/or expertise. If you started off with a homogenous group of developers and set them to work on building an MVC app, the group would eventually split into who favors scripting, css and markup versus those who prefer writing business logic.

Hire what your team needs. If you need a duct tape dude who can do a little bit of everything, great. If you actually assemble an entire team of those guys, good luck.

Re: Startups: Don’t Hire Frontend or Backend Webdevs

#38
post #31

I'm kinda curious if his definition of "frontend" developers is the same as mine. To me, the frontend includes everything up to the purely-computational algorithms and storage of the website. That's the HTML/CSS/JS, but also the webserver/webframework, RPC system, or database API (but not the database itself). Rails is a frontend technology. I consider backend work to the computationally-intensive part. Data mining,…

> I'm wondering if his idea of a startup is the typical web 2.0 startup, where you slap a web framework on top of a database [...] I suspect that many more successful startups will start needing people who can do the algorithmic heavy lifting. Couldn't agree more with you. Most of the current generation of start-ups is extremely boring. Quite frankly, looking at Techcrunch headlines is depressing. When you look at jo…

As a founder of a startup in the "boring" category, I really disagree with your take on this.

I used to be all about the great technological breakthroughs, the really cool algorithms, all the stuff you mention. But as I got older, my interests shifted to other areas: making kickass applications that people love, designing usable interfaces, etc.

"[T]hat makes it even more explicit that they're not there to solve interesting problems, they're there for something else. It looks like an awful waste of talent."

See, that's where I disagree. I think it takes a great deal of talent to create software that helps people. It takes different talent than creating a great algorithm, but it definitely takes talent. That's why so much software has terrible interfaces and is an unusable mess.

And it takes even more talent to create something which truly shapes humanity. A lot of the companies that have made the biggest impact have no technological breakthroughs whatsoever: it's all breakthrough on all those "boring" things. Wikipedia, Facebook, Twitter, they've all done amazing things by solving "trivial" problems.

:)

Re: Startups: Don’t Hire Frontend or Backend Webdevs

#39
post #38
post #31

Earlier quoted context omitted.

> I'm wondering if his idea of a startup is the typical web 2.0 startup, where you slap a web framework on top of a database [...] I suspect that many more successful startups will start needing people who can do the algorithmic heavy lifting. Couldn't agree more with you. Most of the current generation of start-ups is extremely boring. Quite frankly, looking at Techcrunch headlines is depressing. When you look at jo…

As a founder of a startup in the "boring" category, I really disagree with your take on this. I used to be all about the great technological breakthroughs, the really cool algorithms, all the stuff you mention. But as I got older, my interests shifted to other areas: making kickass applications that people love, designing usable interfaces, etc. "[T]hat makes it even more explicit that they're not there to solve inte…

I cant agree with this comment more, even when I look at the problems that exist in my life (which is far more inclined to be technical than average), not a whole lot of them require technical breakthroughs or "exciting programming".

Music and TV streaming would be one for me that has only been solved recently for me (by spotify and tvcatchup), the streaming problems have been long solved, but convincing the stakeholders to be a part of this business took a long time with many failed attempts, even now spotify arent able to launch in the US because of these problems.

Online banking and micropayments would be another problem in that category that has not been solved as yet. while writing an online bank is hard, it is still at the core a crud system, however its impact on users lives are massive.

While I do love programming, I have come to realise it isnt the technical challenge I enjoy, its the benefits I can bring to peoples lives that I really enjoy.

Re: Startups: Don’t Hire Frontend or Backend Webdevs

#40
post #20

The problem with this notion - as mentioned by a few people in the article's comments - is that it is difficult to find developers with a high level of expertise for both sides of the fence. Is it worth the extra expenditure of time in the hiring process to look for two people who are good in both realms? Or is it better to spend less time looking for one front-end expert (with passable server skills) and one server-…

You can also just hire someone who's smart and willing to learn. I mean web development isn't that hard. I know everyone wants to hire someone who meets every single one of their many requirements (we've all seen the job ads), but realistically how long is it going to take a smart developer to pickup say Javascript + whatever APIs you're using? A few weeks? You could easily spend months trying to find the perfect hir…

lol, web development isn't that hard? Dream on.
Post reply on HN