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…
How I Failed to Change Wasmer
11–20 of 73 posts
Re: How I Failed to Change Wasmer
#12The 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…
My reading of the article suggest the "co-founder" title was a late addition to the author's responsibilities, and not a co-founder in the "starting a company together" sense.
Re: How I Failed to Change Wasmer
#13The 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…
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 himself, asking "have you ever seen a co-founder on a free-lancer contract?".
Re: How I Failed to Change Wasmer
#14The 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 founder exit the company and air all of their dirty laundry on the way out. If there were any engineers or managers still working at Wasmer and hoping to turn the ship around, this blog post may have destroyed any chance of that. What is the alternative though? I mean this developer, at least from their telling of it, had held almost every…
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 benefit the remaining employees who are now at a company known primarily for founder drama.
Re: How I Failed to Change Wasmer
#15The 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…
Re: How I Failed to Change Wasmer
#16The 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…
It seemed to me like the author was not actually a cofounder, he was an early hire working under a freelance contract who was retroactively named a "late-cofounder", whatever that means, once the whole thing started to go off the rails. And it also sounded like he was a victim of wage theft and other abusive management behaviors. The CEO may not have displayed such toxic tendencies in the beginning when things were g…
Re: How I Failed to Change Wasmer
#17Earlier quoted context omitted.
> The only thing worse than startup leadership quarrels is watching one of the founder exit the company and air all of their dirty laundry on the way out. If there were any engineers or managers still working at Wasmer and hoping to turn the ship around, this blog post may have destroyed any chance of that. What is the alternative though? I mean this developer, at least from their telling of it, had held almost every…
> 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…
Re: How I Failed to Change Wasmer
#18After this, they wanted another interview. Sure, I guess one 3 hour interview isn't enough. They first scheduled it in the middle of the night my time, but meh time zones are hard. Most egregiously, the interview was to work on the wasmer runtime and fix a bug. Put politely, wasmer is an evolving codebase at a startup. Basically, it's not in the most clean state.
This was a bug involving a virtual file system using WASI. I was fortunate enough to be somewhat equipped to handle this bug. I've sat in on WASI meetings; I remember my file systems; and I've touched a lot of raw WebAssembly. It was still freaking hard as hell. Not to mention, the bug turned out to actually be two bugs sitting next to each other, and partially caused by an unused variable which Rust should warn you about, except for some reason they turned that warning off. Oh yeah and the CEO tried to argue with me about whether Rust warns you for unused variables. Yeah dude, anybody with half a second of experience in Rust can tell you that.
That interview took 2 hours stretching into 3.
After that fun experience, they asked me for yet another interview. I'm sorry but if you're a seed startup hiring anybody with qualifications, you do not get to give me two, 2+ hour long grueling interviews, then ask about a third. You do not get to give me a question that you only solved in the middle of the interview. Your job is to convince me to work for you as much as it is my job to convince you to hire me. Don't waste my time. If you think I'm stupid or lazy or whatever, just reject me.
Maybe it was because I was tired and irritable, but the spirit of the interview did not feel like a collaborative "let's solve this together", but more a "let's see if you're as smart as me". Which just sucks man. I want interviews to be encouraging and emotionally healthy, not just grueling beat downs.
One last petty tidbit, I find it really disingenuous how the CEO markets himself as a "mathematician". I asked about it in the interview and the dude had an undergrad degree in math. Maybe this is my elitism showing but an undergraduate degree is not enough to call yourself a mathematician. There's so much damn work that you need to do to get a PhD. I got pretty damn far in undergraduate math and I still only know a fraction of a fraction of what a PhD knows.
Re: How I Failed to Change Wasmer
#19The 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…
> 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…
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 letting someone claim the prestige of a cofounder title while disclaiming the responsibilities that come with that title.
Re: How I Failed to Change Wasmer
#20Good luck to the author, but I would just say one thing if I could meet him: never put so much energy on a job, no matter how much you love the project... it's NEVER worth it. Unless you're one of the real founders, and even then, you're always running the much higher risk of losing everything than of becoming a millionaire.
Go to work. Enjoy it, have fun, but never become emotionally involved with it. If you need social ties, try your local community, working as a volunteer at a school or whatever... at work, you're there to provide your services at a certain agreed time. After that, get out! Go home to your family. Don't let them make you think they're also your family! They're not and they'll forget you as soon as you leave (and you, them). Everyone will be better off by recognizing that.