Live data from Hacker News

Failing the startup game at Unbabel

esoteric-code.blogspot.com

81–90 of 241 posts

Re: Failing the startup game at Unbabel

#81
post #65

Earlier quoted context omitted.

Facebook has a market cap of nearly 200 billion, some of the most talented engineers in the industry, a world-class AI lab , nearly unlimited perks and over a billion users. So unless this startup can start where FB is right now, no one will "clone" FB.

You'd be surprised. FB is large and that often means conservative and ossified. How long does it take for new ideas to end up on the web page? I don't see that happening much, certainly not daily. The back-end I can't see but I wonder if anybody cares; its not part of what makes FB attractive to users. So replacing FB means recruiting some niche of customers, and providing something fresh and useful. That can be done…

But that's not "cloning" it. I was in a similar position years ago when my employer decided that they wanted a piece of what AirBnb was doing - the design specs they sent me were almost exactly AirBnb, only with the logo changed.

With thinking like that you will never displace the #1 company, because you're not thinking ahead of them, you're only ever trying to catch up.

Re: Failing the startup game at Unbabel

#83

I feel for you too. It wasn't a startup and the job was local, but I took a salary drop and swapped a cosy-but-unrewarding role with a global corporate to join a 40-strong SaaS development company that wanted someone to come in and sort out their internal and customer support infrastructure - they had no strategy, procedures or hierarchy and were constantly firefighting - shuffling resources between projects accordin…

Stories like this (and my own experience) kind of sum up why I don't intend to work for another startup unless it's one I've founded. Too many people out there are taking roles with because it's a startup is always a bad idea.

Re: Failing the startup game at Unbabel

#84
post #72

There is a slight point in founders' favor - sometimes when you need to get out and just get the stuff done, you don't write test for every non-essential piece of code. You also just copy/paste that controller, because you know you will probably throw most of the code away anyway. All you want is to know if the business model works. After all, you are not building core systems for a financial institution. And you kno…

[deleted]

Re: Failing the startup game at Unbabel

#85
I agree with many of the other comments here: If this story is true, Unbabel's behavior is reprehensible. That said, look at Andreas Wild's G+[1]. He has another recently-created blog in which he spouts off some weirdness about consciousness and astrology[2]. This makes me think he is a somewhat unstable person. And it reinforces my initial feeling that we should wait for both sides of the story to emerge before forming conclusions.

1. https://plus.google.com/108299200044097592336/posts

2. http://esoteric-keys.blogspot.com/2013/12/consciousness.html

Re: Failing the startup game at Unbabel

#87
There was a great piece of advice I was given about 20 years ago by the South African guru of franchising, Eric Parker:

"Run your small business as if it was a large business", or, "Start as you mean to go on".

There is a great deal of bullshit in the tech industry; that chaos is somehow normal and that planning and the principles of good management can wait "till we're big". It should be painfully obvious that once chaos has set in, then that is the business environment and it cannot change.

If that environment includes hiring in panic and treating people badly, and the organisation survives anyway, then that organisation becomes one in which toxic relationships are rewarded indefinitely. It will be unsurprising that people like the OP will find it horrifying and be forced out.

Re: Failing the startup game at Unbabel

#88
post #83

I feel for you too. It wasn't a startup and the job was local, but I took a salary drop and swapped a cosy-but-unrewarding role with a global corporate to join a 40-strong SaaS development company that wanted someone to come in and sort out their internal and customer support infrastructure - they had no strategy, procedures or hierarchy and were constantly firefighting - shuffling resources between projects accordin…

Stories like this (and my own experience) kind of sum up why I don't intend to work for another startup unless it's one I've founded. Too many people out there are taking roles with because it's a startup is always a bad idea.

That doesn't excuse certain behaviors like breaking a contract early (we haven't seen the contract, but it's reasonable to assume there's some provision)

After seeing this and similar situations like https://news.ycombinator.com/item?id=8152933 involving YC companies, it's hard not to conclude that there may be something culturally broken at the accelerator level.

Re: Failing the startup game at Unbabel

#89
>I arrived in the final stages of a big rewrite of the core architecture that was already late. The code was a tangled mess of mindless duplication, half-implemented features and misleading comments. Of the few automated tests that existed, most didn't even run anymore.

I feel for you. But with your experience, this shouldn't be a surprise for you??

The focus in Startups is to get the code out and get a (paying) customer and the priority is not always on the quality of the code/tests. In the Enterprise world you have some more time to do more tests, code review et. al and may be you got used to it.

Re: Failing the startup game at Unbabel

#90
It comes with the startup game. What would you have done if the startup ran out of money in a month? You pack up and go home, this also happens, where sometimes they think they have money, and perhaps weren't paying enough taxes or a deal that was going to come through fails.

The reality is that if you join a startup, you should take your job day to day. You should consider it an adventure. Do not expect it to be organized like a corporate job. There is going to be a lot of GROWING PAINS, for young folks with no real world experience, they don't know better. For someone experienced in the industry, man, is it painful! But with that experience, you have to figure out how to lead, your work is not just to code, the bigger puzzle to solve is how to slowly bring about best practices, and you will get a lot of resistance.

You lead by showing. Don't worry about others, they don't wanna write tests? fine, write your own tests, write extra for others if you can. They don't want to document or use revision control? Do so, one day, someone is going to read the comments in your code and realize that it makes sense to document, or read a process document. It might take time, but they will see the light.

In a startup environment, do not complain! It helps nothing, you must wade through the garbage, that's just the way it is. I'm much older and I know this reality. I work for a big company, it's "boring", it pays great, a lot of startup's court me trying to get me to get on board for half the salary and promise of fun, but nope! I'll work more with less discipline and less pay and no stability. I know this. Should I ever join one, I can assure, I won't cry if they shut down the next day after I joined, that's the gamble. Startups fail more than they succeed.

Post reply on HN