[-] coaleh@lemmy.world 1 points 1 month ago

I'd be happy to take an invite code off of someone's hands (and then share the friendship some more!) :)

[-] coaleh@lemmy.world 9 points 8 months ago

Shapes 2 for the factory game!

[-] coaleh@lemmy.world 2 points 10 months ago

It's good fun! The rounds are very dynamic with all the different weapon types and destruction! Needs more modes though

[-] coaleh@lemmy.world 13 points 11 months ago

And then he hired him!

[-] coaleh@lemmy.world 2 points 1 year ago* (last edited 1 year ago)

I'd say the ideal thing to aim for is case 2-ish. Building in isolation isn't great and dog-fooding your lib (via their projects) can help reduce the amount of future breaking changes (getting things right the first time). I.e. Ideally your helping people upgrade when needed and seeing their problems. Even if your forking their projects to try your experimental changes out for them and then provide a PR? That's probably a lot easier said than done though xD

A dependecy management system to let consumers know when a new version is available could go a long way, or you pushing for them to update by talking to them (as this is all internal?).

Basically reducing the distance between teams and getting the tightest possible feedback loops should be the goal.

That's my rushed 2p while waiting for a haircut anyway ;)

[-] coaleh@lemmy.world 0 points 1 year ago* (last edited 1 year ago)

https://lemmyrs.org/c/rust@kbin.social works for me. I believe there is a generic way to link to communities that works for all sites.. but I don't know how. I know the format is something like [!rust@kbin.social](/c/rust@kbin.social) but nothing seems to convert to a link etc Edit: perhaps just relative links? /c/rust@kbin.social

coaleh

joined 1 year ago