5 ms·
Here's what NOT to do, from my experience in the first decade of this millennium: 1. What came first: More work or more developers? Don't stress your developme
by 734129837261 7y ago
Here's what NOT to do, from my experience in the first decade of this millennium:
1. What came first: More work or more developers? Don't stress your development team for ages without hiring new employees. They'll burn out and hate working for you.
2. Don't focus all your energy on outward appearance. Your work should speak for itself, not your amazing expensive new car and tailored suits.
3. Don't stop innovating. The developers who were there since day 1 who refuse to adopt new tech? Yeah, get rid of them. They're pulling the rest down to their level.
4. Seniority isn't a guarantee for superior knowledge; and being junior doesn't mean their opinion is invalid. Don't fall victim to playing favourites. If you hire people, then they're equal.
5. If you are one of two founders: Don't have sexual intercourse with the wife of the other founder of the company. He will find out and because you have 50/50 shares in the company, everyone needs to pick a side. This destroys the company.
6. And that also means you can no longer afford to lease that $1400/month luxury off road SUV that you only drive in a town without even a single hill in a 100 mile radius.
I was just an employee for this company, I was in my teens when I started working there, and I thought these 30-something owners of the company knew what they were doing. They didn't.
- GhettoMaestro 7y ago> 5. If you are one of two founders: Don't have sexual intercourse with the wife of the other founder of the company. He will find out and because you have 50/50 shares in the company, everyone needs to pick a side. This destroys the company. This sounds juicy...
- tonyedgecombe 7y agoIt's surprisingly common and you really don't want to get involved in any way.
- Phrenzy 7y agoUnless you are a divorce lawyer.
- bcrosby95 7y ago> 3. Don't stop innovating. The developers who were there since day 1 who refuse to adopt new tech? Yeah, get rid of them. They're pulling the rest down to their level. Sorry, but adopting new tech isn't innovating. Building new tech is. Adopting new tech may make it easier. Or it might just be that your developers are bored and need something to entertain themselves.
- djm_ 7y agoRe-read the first sentence.
- Sophistifunk 7y agoThat escalated quickly
- fizx 7y agoIt's amazing how much driving a nice car in a downturn makes your employees hate you.
- mianos 7y ago> 3. Don't stop innovating. The developers who were there since day 1 who refuse to adopt new tech? Yeah, get rid of them. They're pulling the rest down to their level. Here is one, listen to the experienced developers, stop innovating tech and focus on building what the customer actually wants/needs in a robust manner. In my experience, the focus on 'new tech' and not customers has been the death of startups I have worked in. Flakey products based on the latest and greatest tech has been another.