Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I understand your comment. The list is very developer friendly. But it's just meant to help companies that want to appeal a bit more to developers and get more applications.

There are great companies with great people out there who just don't know what developers are looking for. They don't have to implement all of these tips, but maybe they'll be able to mix and match them with what already works at their company.



I have to say that sometimes the sense of entitlement among developers here gets to pretty absurd levels. There's an attitude that developers are the only ones that matter, and anything that adds any kind of accountability is oppressive.

$90k+ salary, guaranteed max of 40 hours per week and a few % equity at a startup? if a sales rep or manager asked for something like that in an interview they'd be called pompous. For example, if a startup has raised $500k in funding, this would mean not only would they be spending 20% of their funding on a single developer in the first year, but they'd give up a big chunk of equity and get someone who has 3 other projects on the side they're working on. That's seems fair? that doesn't smack of an entitlement complex?

p.s. I'm a developer and run a startup.


I think if there's any sense of entitlement it comes from the people doing the hiring lamenting that they can't find qualified people.

Well, if qualified people are in short supply, you've got to give them what they want if you want one of them to work for you.

You can't on the one hand complain that developers ask for too much and then on the other complain that you can't find developers. The problem in that equation is then the person looking for developers.


I didn't complain about that. The developers I work with are amazing :)

(oh and of course they have a ton of equity)


The 90k is an example of "list the salary" and not "pay at least this much to have attention".


Salaried developer employees are different from founders or executives. I can measure a founder's performance in terms of number of users or amount of revenue. I've yet to see a meaningful numerical measure of developer output. It is possible to meaningfully grade developer output only in qualitative terms, not quantitative ones. Quantitative measures are oppressive. If you want to rate me, I want someone to pay attention to what I'm actually doing, and I want someone who is capable of understanding what's going on. That's not asking too much. But that kind of investment means one manager is capable of managing fewer people, and you have to have really talented managers, and so people don't like it.

I have no problem with accountability. Very simply, if you need to keep tabs on me (already a step down in the relationship), then I expect you to do it in a qualitative fashion, with a person capable of evaluating progress. Closed tickets and hour estimates and burndown charts and all the rest of that stuff is a fiction, and it makes an incompetent manager look real busy when he is actually doing nothing. And it wastes my time when I'm trying to do important work.

They call these metrics time saving devices, but if you don't have time to go around and peer at what's actually happening in the shop, then you aren't actually evaluating anything.

You don't need a person to track metrics. If these fictions worked you could set up a machine to track progress and send reminder emails, and even to fire people who were consistently too far behind.

To put it in a not nice way, the managers at startups I've met were experienced people who weren't skilled enough to cash out during the first bubble, or who never made it to an executive position or to starting their own company. They were untalented, and their advice was bad. If they had been genuinely capable of showing me how to perform 10% better, I would have received them as saints, or as angels from on high, and would probably have spent as much time around them as possible. That was not the case.

The other reason people like metrics is because of the squeeze. You're already operating under the assumption that I might not be working at full potential, that's why you want the additional accountability. If I am working at full potential, and you assume you can squeeze 5% more out of me, and start to press down, then maybe you do get 5% more in the short run, but in the long run you've caused a problem.

In their less guarded moments I've heard people in these positions claim their job is to improve performance by just a few percentage points, and that will justify their position. Multiplied over a department, these are huge gains. Unfortunately, that's an exceedingly difficult proposition for someone without special insight, and the only way it's going to happen is if they are in control of the results metrics. Which they are.

Maybe you can recover a few percentage points in a clunky, inefficient company. In a hot startup one overseer is not going to squeeze that much out. They're just annoying.

I doubt you can get rid of middle managers. They're there for a reason. Someone has to digest what's going on for the higher ups. But there's probably a better way for them to do their jobs than inserting themselves where they don't belong.


I guess you'll have to take my word for it that I'm not talking about the obviously silly ways of making developers accountable (like LOC or tickets closed.) I'm a developer, so I know that typically managers who don't know how to code shouldn't be managing coders.

What I'm talking about is developers who demand above market wages, and shorter hours (than lawyers, or doctors, or automotive engineers etc.) and less commitment, and more equity. There are a lot of these guys out there, and a lot of people on here who think like that. I'm saying that's a childish, entitled attitude that ignores the reality of starting and building a company. Sometimes you can't have it all.


Unless you're hiring someone fresh out of school, they've likely had some experience in the job market and base their expectations of salary and conditions on that.

It's not really a sense of entitlement if I can point to similar positions x, y, and z and ask why you're not offering the same, is it?

Expectations, whether or not you find them realistic, are not created in a vacuum. I can't pay my mortgage or feed my kids on a "pre-money equity-only" job. Taking a deep pay cut for a stake in NewCo? Been there before - at the end of the day, 5% of nothing is still nothing.

If you're looking for someone who is willing to take a big risk for very little (immediate) reward, you aren't looking for an employee, you're looking for another co-founder.


I totally agree with you. That's exactly my goal in hiring early employees - they are de facto co-founders that should get a ton of equity and a livable salary.

If someone wants 90k and 40 hour work weeks they should go work at Microsoft or IBM. That's not how successful startups are built. You need to be ultra frugal, extremely dedicated (to the point of obsession) and have lots of exposure to the up side.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: