Live data from Hacker News

Get Shit Done: The Worst Startup Culture

whatspinksthinks.com

61–70 of 212 posts

Re: Get Shit Done: The Worst Startup Culture

#63
post #12

The whole start-up culture encourages this behaviour. The current fire fast trend, rather than trying find the root cause for example. Firing someone can completely mess up someones career, but people are being told to fire someone on a whim, if they're not right fit(I mean that could be anything). Turn it around, and put yourself in their shoes.

By the otehr side, not firing can completely mess up a small company, but nobody ever likes doing it.

People repeat a lot of "mantras" that say you should do something contrary to human nature (fire fast, get shit done, speak in a lot public, try to falsify your hipotesis). They are very important, as human nature dictates the default action every time, we need to be constantly reminded that the default may be wrong, and that we should stop and think about it.

But then, stupid people exist, even if they are stupid just a small fraction of the time. And those people will make stupid decisions. There is no procedure, environment, or technique that solves "stupid".

Re: Get Shit Done: The Worst Startup Culture

#64
post #54

> There aren’t people who are A players and C players. Just people who are performing at an A level and at a C level. That sounds very nice, like something Barney the Dinosaur would say. People who consistently perform at C level are C players. Maybe they would be A players doing something different but that's not much use to you.

Of course they are. Get them doing that other thing they are good at. People naturally gravitate to tasks they are good at. Are they're any tasks they are voluntary doing? Is there a full-time position for this?

Re: Get Shit Done: The Worst Startup Culture

#66
post #31

Earlier quoted context omitted.

I experienced "fire fast" on the receiving end once. It's the one and only time I've been let go for any cause from a job. It occurred at a shall remain unnamed big startup on the East Coast. I was hired on the merit of my portfolio and past positions (I do not have a high-snob-factor college degree), and dove in and got up to speed pretty quick. Job was to implement a lot of Java code and some .NET for a major web-b…

It's a really bad sign when people look at the end of the sprint as an absolute deadline for things needing to get done.

In this case my part of the sprint probably would have run over by one day, since I had one more feature to implement around the new core I had written and I had to spend extra time refactoring code for existing features a little (not too badly) to make them work with said new core code.

The logical thing would have been to punt that one feature, make everything else work (it was very close), then spend the rest of the sprint testing before swapping the old boat anchor out. Either that or keep the old version in place until the end of the next sprint to give time for complete unit tests to be written.

Re: Get Shit Done: The Worst Startup Culture

#67

If you are taking your management cues from a slogan on a wall, you're probably dealing with shitty management.

This.

Management by catch-phrase, one-liner, pre-packaged "management methodology," etc. is about as good as code written in the same thought-free manner. As with code, good management requires deep consideration of the actual problem at hand.

Re: Get Shit Done: The Worst Startup Culture

#70
post #31
post #12

The whole start-up culture encourages this behaviour. The current fire fast trend, rather than trying find the root cause for example. Firing someone can completely mess up someones career, but people are being told to fire someone on a whim, if they're not right fit(I mean that could be anything). Turn it around, and put yourself in their shoes.

I experienced "fire fast" on the receiving end once. It's the one and only time I've been let go for any cause from a job. It occurred at a shall remain unnamed big startup on the East Coast. I was hired on the merit of my portfolio and past positions (I do not have a high-snob-factor college degree), and dove in and got up to speed pretty quick. Job was to implement a lot of Java code and some .NET for a major web-b…

Great story, thanks for sharing.

In a way, it was for the best, isn't it ?

It is clear that you weren't a good fit for their development team and their interpretation of "agile" software ...

Post reply on HN