[AnotherGoodName]

If it was 'just' a licensing slip up sure, but there's still a lot of integrity issues here despite that. The presentation of "we created an open source library to do X in just days" comes across as a lie right?

I feel like ycombinator leads may want to look more deeply into this one. If they are presenting it as something they've achieved that's an integrity issue right?

[rustystump]

This is the crux of it all to me. Anyone in the industry knows mistakes happen all the time but the braggadocios nature rubs me the wrong way and spits in the face to those of YC who do indeed have integrity.

[eddythompson80]

It's baffling why someone would do this tbh. It's not like the base project is some spectacular piece of engineering that would be very costly to replicate.

I'm guessing they just looked at it as a jumping point. It probably went something like:

- We know how to polish an electron app

- here is a barebone electron app with an interesting idea

- Can we build a polished UI around this, and give a demo?

The baffling part is, had they just disclosed that, no one would have given a shit. Plenty of demos begin like that: "here is a cool idea we found, here is that idea on crack". is a very common demo pattern. But of course you can't give a shout out to 'cheating-daddy' at YC demo.

It's like a fine student at a fine college, in a class they are doing fine in, then they decide to copy their friend's cover letter because "eh", then they get caught and now what? wtf would you do this?

[seanhunter]

Like the frog in the parable,[1] people with integrity often struggle when they attempt to understand the motivations of people who cheat. “Why would they cheat in this particular situation?”, they ask themselves. “It makes no sense!” Well they are cheaters. Cheaters cheat.

[1] https://en.wikipedia.org/wiki/The_Scorpion_and_the_Frog

[seanhunter]

To attach a couple of personal anecdotes to this:

1) I once was in a position where I had root on the linux boxes at a large corporation because I had been a sysadmin there and even when I changed roles, I was never removed from sudoers. Years later there was an accusation that someone had stolen source code and taken it with them to a new job. On its face this made absolutely no sense whatsoever - the system they were accused of stealing was a complete pos in the middle of a complex ecosystem so even if you had it, you couldn’t use it without all the other pieces and in any case, it was old and outdated and just total garbage. Anyway this accusation was somewhat hush—hush so the cto came to me and asked me to just look into whether or not it could be true. Sure enough, there in his bash history I could see him checking out the code and pushing it to an external repo. It made absolutely no sense, but he had indeed stolen the source code to a system that was a total piece of junk. He ended up with a criminal conviction, he lost his shiny new job, his wife left him etc. It was very said and baffling.

2)Second example, fast forward some years and I was working for a saas provider. We had won an initial proof of concept and were negotiating a 5-year, multi-million dollar contract. At the same time, our client asked us to just do a free two-week spike on something unrelated. We had to sign a (different) zero dollar contract to cover licenses, liability etc for the free spike. The same purchasing lawyer was working on both contracts. The usual contracting process is you send the contract over to the other side with some markup and comments, they make some markup and comments, you propose language, they amend it, they propose language, you amend it, eventually everyone agrees and you make a clean copy and both sides sign. While we were doing this for the big contract, we got to the point of signing the zero dollar contract. At the last moment with everything agreed, the other side said they would make the clean copy. They sent it over to us and when we did our final check before signing we found the guy on the other side had meticulously gone through and made a version which accepted all their changes and backed out all of our changes. This required a lot of extra work and could not have been an accident (think cherrypicking commits and fixing all the merge conflicts using only MS Word revision history), and it was on the zero dollar contract so there was no conceivable upside except he could say he “won” somehow by tricking us. All this while we were negotiating the multi-million dollar multiyear contract. It made absolutely no sense whatsoever to do what he did. There is no way to understand why he decided to do it, but he did it.

So yeah, don’t even try to understand why some people do the unethical things they do. Scorpions gotta sting. It’s just what they do.