You have to integrate company A system with company B.
You look up B`s api documentation, write the necessary code, test it thoroughly. Done
__________________________________
A wild dev from B has appeared!!!
------------------------------------------------------

him > you cannot use this SDK to implement this solution. You must use a different one...

You > (coming back to him after scouring through the docs) . Ok which sdk is it then? I can't find it anywhere. Could you send it to me pls?
him > I don't kbow, my knowledge doesn't go that far. Send an email to the dev department.

After sending the email, and spending a couple of days trying to figure out which sdk was he referring to. His department answers that the sdk you should use, is the one you already used. The only one they have.

A couple of days lost, because certain smart-ass could not refrain himself from meddling in the project.

What would you do?

Note: Killing him is out of the question :)

I didn't manage to win a Hacktoberfest 2020 shirt because I don't use GitHub anymore (and they require that apparently) - but I figured I might as well have a go at it.

echo "- an amazing project" >> README.md
git add devduck.png
git commit -m "update docs"
git push devrant feed

Pls like, comment, share, and subscrieb to CodeWithCondor for moar laif hakz :3

Hey folks,

So, rust.

Has anyone any ideas on a decent way to learn it? I feel of all the languages I've ever looked into it has the least about of resources of any discernable quality available. Even the docs can be a but dodge. Would I be better off learning pure c and then migrating? (as I imagine is the pathway of the standard rust user)

Any other recommendations would be deadly!

I'm finishing up some software I designed, any tips for writing documentation for non tech people?

I do not like rust's choice to just infer something from how it is named

like if you install a package that begins with "cargo-something" then it becomes a cargo command. this feels janky

also turns out if you have a build.rs file it will build stuff for you when compiling? I just ran into this being described in the docs. well guess what. I have a build.rs file. it isn't being used for that though. I mean hasn't caused any problems, or has it?! I DON'T KNOW

config options seem more explicit than this naming nonsense. I just had to rename my project everywhere so it can be a cargo command. ffs now my git links are broken and shit.

I thought rust was verbose because it knew the merits of being explicit. can they stick to their principles pls