I don’t see how that can be used to make performant code though. I usually want to make my locked regions as small as possible to avoid how long other threads are blocked for.

Not a lawyer, but worked closely with them in the past. It REALLY depends on your employment contract. Changing variable names and language still makes it a derivative work, so it would depend on the original license. I’m assuming it doesn’t have a license which would mean either you or the company owns the copyright: depends on your employment contract. Whether you’re a contractor or full time also affects ownership.

Without ownership or a license, you do not have the legal right to copy the work or make a derivative of it.

I’m not clear on whether you actually wrote any code though. If that’s the case (that no code was written) then I’m not really sure how that works out. If you do post it and they find out, AND they’re mad about it, you could definitely get fired. I’m not sure if there could also be legal trouble or not.

If you need it for a resume item, you can just list it on your resume and talk about it. You could also implement it on your own time (but not share it until you’re sure you’re safe from legal action), that way you could talk about tradeoffs you’ve made, etc. in the real implementation.

In general, if you’re not sure and you’re worried about getting sued, you should ask a lawyer.

How complex are the API calls you need to make? Debugging interop mismatch can end up being more work than writing the tests if you need to deal with complex types.

The .NET languages support c interop. The documentation could use some love though.

Had a team of 10 working nights and weekends for a month because someone in sales sold a contract for an integration with a 3rd party that didn’t exist yet. In the years I was there after that project shipped, only 1 person even looked at the feature, one time. It never actually got used

Malbolge https://en.m.wikipedia.org/wiki/Malbolge

It required a cryptanalyst to write hello world.

Even worse is Windows batch scripts. The syntax also changes depending on if it’s in the terminal or run from a file

I really prefer rust’s approach. The function signature is the contract. It makes it much easier to debug compared to overly generic pure functional code or c++ templates where everything is auto and perfect forwarded.

The only time in rust where this isn’t true is with async functions. That’s because the compiler adds a ton of sugar to make it easier to write.