> There is nothing less productive in this world than a team of developers. Senior dev chiming in here (44yo), mainly replying to some other comments here, that claim once your team is > 1 person, your overall productivity does not increase with a person every time. I would say a good 2 person team is more productive than 2x 1 developer for the following reasons: 1. It's easier for 2 people to keep each other motivat…
If only someone told me this before my first startup
81–88 of 88 posts
Re: If only someone told me this before my first startup
#82> 6. Hire only fullstack devs. There is nothing less productive in this world than a team of developers. Huh? And those "fullstack devs" will do everything alone or what? Maybe if you are building a proof-of-concept prototype with a useful half-life of 6 months before you sell the company to someone else (and let them deal with the mess under the carpet) but not once you actually start selling the product - and mainl…
I don't disagree, because you're mostly talking about mature startups and corporations. My experinece comes from early stage startups and small saas companies. Where scrum and dev teams aren't helping and having just one dev doing the whole thing is actually very productive. But your points are good, if the reader is coming from a bigger company
The lack of some sort of formal structure very much was a problem.
Granted, some people are so self-disciplined and enlightened/experienced that they are fully capable of self-organizing and don't need the support of any formal work structure. But those are rare like hen teeth. It doesn't have to be Scrum but Scrum works, so why reinvent the wheel?
This is especially true at early stage startups when there are millions of things to take care of besides the coding. The structure/being organized is super important or things start falling through the cracks.
If it is a feature request that didn't make it that is annoying but likely no big deal. But if it is e.g. a tax declaration for the company or maybe some government paperwork that had to be done, or following up a major investment/sales lead - that could literally destroy your company overnight.
So having a structure in place to make sure everyone is constantly on the same page, everyone knows what needs to be done - and mainly who is going to do it - is super important.
The problem is that most people I have met didn't realize this. Esp. when the founders have never worked in a structured team themselves, never saw how to manage a team or had a mentor to show them the ropes. So you end up with poorly reinvented management "wheels" that don't work and the company is wasting precious capital because suddenly the founder becomes an over-stressed and overloaded bottleneck trying to juggle coding, finances, sales, filing taxes and what not. Or, worse, makes the company fail because something that had to be done wasn't.
This isn't stuff that is taught in universities or that people are somehow born with. One has to learn it with experience - and ideally see how to do it from someone more experienced.
Obviously, if your entire company is one person, you don't need Scrum. However, the moment you hire your first developer you better put some structure in place because sooner or later you will outgrow the informal "system". Only so much can be done with a single person.
And once you have more than 1 developer (or any team member - it can be graphic designer, web designer, sales, whatever) you will have problems if you keep things totally free form. It becomes super inefficient.
Re: If only someone told me this before my first startup
#83> 5. Landing page is the least important thing in a startup.
Can you elaborate on this point? I think I understand the idea of spending too much time rewriting the copy or moving pixels on a landing page, but your way of putting it is much more extreme, so I'd be glad if you can tell a bit more about your point of view.
Re: If only someone told me this before my first startup
#84> There is nothing less productive in this world than a team of developers. Senior dev chiming in here (44yo), mainly replying to some other comments here, that claim once your team is > 1 person, your overall productivity does not increase with a person every time. I would say a good 2 person team is more productive than 2x 1 developer for the following reasons: 1. It's easier for 2 people to keep each other motivat…
"good 2 person team">"one person team". - yes. however finding even 1 good dev is really difficult. Finding 2 great devs is insanely difficult for an early stage startup with no money. I've tried. In an ideal world, ofc you are right. But in real world of startups. Most got no chance finding good developers and almost none got a tiny chance finding 2 good developers
That is clearly not what I said.
Re: If only someone told me this before my first startup
#85Also, if I opened a startup and followed 10, I'd end up with a team of my wife and my dog. Which would be a wonderful company, but the revenue potential would be somewhat limited.
18 seems to me a fundamental misunderstanding how it should work. Or at least how it worked when I saw it working. It's not about managing or nagging, it's about sync Shelling point.
19 I haven't seen a single startup that could pull it off. I mean, doing their own accounting and HR and payroll management while bootstrapping? Or does it mean "outsource nothing of core product", not nothing in general? That'd make more sense, but in current componentized world, you'd be effectively "outsourcing" a lot of stuff anyway.
Re: If only someone told me this before my first startup
#8612. Get better friends
Re: If only someone told me this before my first startup
#87North America is big, and EU regulations are a bear.
You can get huge in the US alone.
Going international means i18n, which is a helluva dev task that affects nobody in the North American market.