Live data from Hacker News

How I Failed to Change Wasmer

mnt.io

21–30 of 73 posts

Re: How I Failed to Change Wasmer

#21
post #13

Earlier quoted context omitted.

> author appears to be a co-founder of the company despite writing much of the article from the perspective of an IC engineer who was taken advantage of. With all respect to the author, I think, from reading this, they gave him the title of co-founder to try to try to stop him from leaving earlier, given 85% of the engineering team had left (it's implied this happend before he became a co-founder). He jokes about it…

He writes further down that he was handling founder-level responsibilities. That’s actually part of his complaint about his workload. If he has the title of co-founder within the company, describes himself as co-founder in his blog, and was responsible for founder-level activities then I think it’s clear that he was, indeed, a cofounder. I sympathize with his experience, but I also think we need to be careful about l…

Not saying that he wasn't... as much as a "late" co-founder is a thing... just that the motivation for making hime that might have been a little bit sinister.

Re: How I Failed to Change Wasmer

#22

I interviewed with Wasmer a few weeks ago. It wasn't enough time to get a real inner view into the company but I saw enough to give me pause. They set up an interview for 3 hours, which stretched into 4 hours. During this interview both interviewers had to leave at points to attend other meetings. After this, they wanted another interview. Sure, I guess one 3 hour interview isn't enough. They first scheduled it in th…

Interesting perspective. Was the author of this blog post still involved at the time? Or was this after his departure?

Having the CEO try to dunk on applicants during interviews is not a great sign for any company.

Re: How I Failed to Change Wasmer

#23

The author seems to be making live changes to the article. It started as “How I failed to Change Wasmer” but it’s now titled “I’ve loved Wasmer, I still love Wasmer”. This is a tough story to read for anyone who has been passionate about a startup only to watch it decline under management quarrels. However, I have mixed feelings about this article because the author appears to be a co-founder of the company despite w…

> The only thing worse than startup leadership quarrels is watching one of the founders turn around and try to sink the company by airing all of their dirty laundry on the way out.

Wait, why is that a problem? Let all be aired and let us figure it out for ourselves. We're all adults. If the situation is indeed as the cofounder claims, a cleaned, distilled version of events is untruthful and patronizing.

And if the events aren't as claimed, startups are evaluated on their ability to hire the right people. If the CEO chose a cofounder who would lie and destroy the startup for no good reason, then that also reflects poorly on the CEO.

I, for one, appreciate the signal that Wasmer is a startup to avoid doing business with

Re: How I Failed to Change Wasmer

#25

Earlier quoted context omitted.

> if that's all true then what else could this person do other than air out the dirty laundry? Simply leaving the company quietly is a huge statement in itself. A founder who leaves an active company and tactfully announces that they’ve chosen to move on speaks volumes. Airing dirty laundry like this is politics, plain and simple. It doesn’t benefit the author to advertise his issues as a co-founder and it doesn’t be…

It might give somebody enough information to decide not to work for that CEO.

Ah, so the author of this blog is a humanitarian

Re: How I Failed to Change Wasmer

#26

I interviewed with Wasmer a few weeks ago. It wasn't enough time to get a real inner view into the company but I saw enough to give me pause. They set up an interview for 3 hours, which stretched into 4 hours. During this interview both interviewers had to leave at points to attend other meetings. After this, they wanted another interview. Sure, I guess one 3 hour interview isn't enough. They first scheduled it in th…

What an awful story, I'm sorry you had to endure that. My undergrad is in applied math and I would never even dream of calling myself a "mathematician", so, yeah, tells you a lot about the guy.

Re: How I Failed to Change Wasmer

#27
I was a very early employee at Wasmer and worked with Ivan for part of that, though I ended up leaving after roughly four months to go back to university. At the time, it didn't seem too bad but, in hindsight, it was a pretty toxic environment.

That was partly a result of a lot of pressure from larger companies that didn't want to work with Wasmer because Syrus, the founder, was publically rude to other people working on WASM (among other things).

Ivan is a really awesome guy and deserves work that values him. I wish him the best and can vouch for his technical ability.

Re: How I Failed to Change Wasmer

#29

The author seems to be making live changes to the article. It started as “How I failed to Change Wasmer” but it’s now titled “I’ve loved Wasmer, I still love Wasmer”. This is a tough story to read for anyone who has been passionate about a startup only to watch it decline under management quarrels. However, I have mixed feelings about this article because the author appears to be a co-founder of the company despite w…

> The author seems to be making live changes to the article. It started as “How I failed to Change Wasmer” but it’s now titled “I’ve loved Wasmer, I still love Wasmer”.

People second guess themselves when they write something emotionally charged and it goes semi-viral. So what? Wouldn't you? That doesn't make the article any less valid. A title change is very different from materially changing the actual events discussed, yet you imply something of this magnitude is going on (it isn't).

> The only thing worse than startup leadership quarrels is watching one of the founders turn around and try to sink the company

Maybe for you. For the rest of us, being a toxic founder who exhibits even a third of the bad behaviors mentioned in the article would be grounds for forced removal. Looking over the timeline and events that took place at Wasmer, it's pretty clear this dirty laundry needed to be aired, and everyone (the users, the employees) would benefit if this CEO is actually removed. Perhaps this idea makes you uncomfortable? It's also super disingenuous to paint this as an attempt to sink the company -- clearly it's an attempt to say the product has tons of promise but the CEO needs to go. All other options have been exercised at this point, so going to a public forum with huge industry influence is exactly the kind of thing that could solve this problem that otherwise probably has no solution other than the company floundering. The CEO could quit tomorrow, and then this entire endeavor would obviously be justified and well worth it.

> I also wish the author would have elaborated more on their original title (“How I failed to change Wasmer”) instead of laying all of the blame on the other co-founder and alluding to toxicities

In a literal sense you are right to say that the author doesn't discuss this much, but come on man, it's super obvious -- this "late co-founder" was not given enough control or say in the first place to make any of the changes that needed to be made. Heck, he couldn't even take a sick day without incurring tremendous ire. Most of the article is about that. Did we read different articles? It's like you're going way out of your way to trash this for no real reason other than it makes you feel uncomfortable. Airings of grievances like this are one of the good things about Hacker News and have a positive impact on the industry. I dare you to come up with a single example where that isn't the case. Show me an example of a startup that floundered because of disingenuous HN exposure that wasn't caught until way too late. If anything they'll have a sales bump today.

Re: How I Failed to Change Wasmer

#30

I interviewed with Wasmer a few weeks ago. It wasn't enough time to get a real inner view into the company but I saw enough to give me pause. They set up an interview for 3 hours, which stretched into 4 hours. During this interview both interviewers had to leave at points to attend other meetings. After this, they wanted another interview. Sure, I guess one 3 hour interview isn't enough. They first scheduled it in th…

Since half the purpose of an interview is to see whether you want to work for them, I'd call that interview a success.
Post reply on HN