Doesn’t stop your manager from requiring support for the other 4%.
Doesn’t stop your manager from requiring support for the other 4%.
deleted by creator
You make it sound like this doesn’t happen frequently.
Any context on him “trashing his reputation”?
The tools will be fairly specific to the game you’re hacking. For example, a lot of tools exist for GBA Pokemon games, but something like porymap won’t work for another game.
So, the argument was that there was absolutely no way whatsoever that one could figure out they needed to depend on
mio
for a good event loop interface. It was totally an insurmountable task!
You still see this same mindset now with people making things like blessed.rs. It’s the same idea, just not wrapped into a library. I find it hilarious when it gets shared in discussions and some people go “oh wow so helpful!”, as if we all couldn’t have found serde
and rand
on crates.io without it.
I used to work at a company that held to the concept of “don’t be a hero.” Basically, if you were having to step up, work overtime, and always go out of your normal routine to “fix” stuff, then you’re actually enabling bad processes.
I think the same concept applies here. If you can’t let any code be submitted without personally reviewing it, then there is something wrong with either the review system, the onboarding system for new devs, or the continuous integration system that should be catching mistakes. Same goes for triaging: if no one is triaging because it’s too exhausting and leads to burnout, then some other system may need to be devised for handling outstanding issues.
Obviously this is much harder to deal with in an organization where most contributors are volunteers. But if we want the project to survive and not be taken over by corporations who can afford to pay people to deal with this stuff full time, I think it should be addressed in a different way.
I’m curious to see whether this survey shows that the amount of jobs programming Rust has increased.
First 1/3rd is a bit of fluff but after that, good article.
Ah yes, the Wadsworth constant.
That’s actually what the comment above was suggesting, which is why I was wondering why you couldn’t get it to work. Glad you got it working!
Can you show us your code for when you tried this suggestion?
What does “FE” stand for in this context? Sorry if it’s obvious, I just don’t see anywhere that it’s actually written out.
I sure hope this is not how most CS courses are being taught
You gonna do Rust again?
I thought problem inputs were randomized for each user?
It’s been this way for years. Really?
Diesel is well-known for having some of the worst errors in the ecosystem. This is far from the rule.
What tests? There is no hyperlink, for all I know, these are just some hidden tests that the owners of the competition run on the solutions to verify them. There is no link to Prettier at all, and at a first read it’s very unclear this is what they want you to do if you aren’t already familiar with the tool they want you to recreate.
Wow, they really did not make that clear at all on the contest description.
The const improvements are fantastic. Keep up the good work!