5,885 karma · joined April 26, 2013
These guys wrote a custom server from scratch and have hacked up the original game itself as well. It's hosted completely by the community.
Hence the adage "sir, this is a casino"
I'm always willing to work with people on code/system design - in fact it's my favorite part of my job when someone says "how can I do this beter?" - but it is excruciating to have to handhold someone through a basic diagnosis routine for or provide the same basic feedback about logging or security the nth time.
Basically my job as a staff these days, though not quite that number. I try to pair with those junior to me on some dicey parts of their code at least once a week to get some solid coding time in, and I try to do grunt work that others are not going to get to that can apply leverage to the overall productivity of the organization as a whole.
Implementing complicated sub-systems or features entire from scratch by myself though? Feels like those days are long gone for me. I might get a prototype or sketch out and have someone else implement it, but that's about it.
There are other good uses of it but it absolutely can get out of control, especially if implemented by someone whose just discovered it and wants to use it for everything.
It's equivalent to partial application.
An uninstantiated class that follows the dependency injection pattern is equivalent to a family of functions with N+Mk arguments, where Mk is the number of parameters in method k.
Upon instantiation by passing constructor arguments, you've created a family of functions each with a distinct sets of Mk parameters, and N arguments in common.
This has its own problems, obviously, but there is something to a monied-interests-unfriendly set of cultural shibboleths.
That said, it's also something I'm seeing with younger people as well.
This is how I've set it up at my current employer. It works well. We modeled it after the Terraform Plan/Apply steps, and double check that the script generated by the "apply" step matches the script generated by the "plan" step, since these can occur at significant temporal distances, and fail it if not, just so that we can be sure what we've read and approved matches what gets executed.
>they will only be expected to have basic but important measures to remove illegal content when they become aware of it. These include:
>easy-to-find, understandable terms and conditions; a complaints tool that allows users to report illegal or harmful material when they see it, backed up by a process to deal with those complaints; the ability to review content and take it down quickly if they have reason to believe it is illegal; and a specific individual responsible for compliance, who we can contact if we need to.”