1,144 karma · joined August 17, 2012
Then again, I'm not an expert in this kind of thing. Would this somehow make things way more dangerous in a different way?
It would be easier to answer your question if we knew what game you were playing. Not many games share the same save file format, so there isn't a single answer which will work well for everything. Some games' save file formats do have dedicated editors made for them, and if one exists for your game, that would be the easiest and safest way to edit your file.
Even if there isn't a dedicated editor, you should be able to edit the file with a thing called a hex editor. You seem to be using Windows, so Free Hex Editor (https://frhed.sourceforge.net) may be a good place to start. This will still show you the strange characters on one side of the screen, but it will also allow you to see and edit the actual numbers, if you know where to look for them (and how to work in hexadecimal numbers).
Can you link us to the Reddit post you were talking about? That would be useful information for answering your question further.
In fact, I'm having trouble understanding how this could be interpreted as anything else. If you want to hold protests saying that the USDA ought to be paying people's personal debts, there are lots of ways to do that. They do not include filing illegitimate claims through the claim system.
It's the capitalist way: if some private company doesn't want your business, go to another company. If there isn't one, make one. It's all perfectly free-market compatible, and well in keeping with the Internet's ethos of letting anyone set up shop.
If there were norms that were actually being enforced, then existing enforcement could be brought to bear against the creepers. The problem is that there is no enforcement in the usual sense, allowing the creepers free rein to enforce, not any norms actually relating to the wider society, but their own emotional whims. In essence, rather than being proper enforcement of social norms, it is nothing but common bullying perpetrated by a vocal minority, which they get away with because there is no mechanism to bring any force to bear against the bullies. Their presence continues to be tolerated in the same way that any abusive person in a friend group is tolerated: it keeps the peace. Meanwhile, the targets leave because that's the closest thing they have to recourse.
The creeps don't mind Wheaton's Law or "Kind Communication Guidelines" much, because they know that no one with any clout will come after them for breaking the rules. Same goes for SQLite's adoption of the Rule of Saint Benedict, which they have already stated cannot be enforced for "minor" transactions. Only when the rules come with enforcement mechanisms do they actually complain, because that's the point when their targets gain a way to fight back against the bullying.
The geek community was largely formed by people who had been unfairly targeted by those who enforce social norms: picking inappropriate targets, taking things to inappropriate extremes, and the like. Our response was to create a community that didn't enforce social norms at all -Geek Social Fallacy #1, essentially- and a lot of beautiful things came from that. We changed the world for the better in a lot of ways, precisely because we refused to reject people just because they acted in ways that went against the social norm.
But there was a problem: some behaviors really shouldn't be accepted, and some people really won't change without the application of force. Unlike the people who first formed the geek communities -people we should all aspire to be like- this second group was fairly ostracized: appropriate targets, appropriate measures. They came to our community, not precisely for support, but for enablers; having been rejected from everywhere else, they fled to a group that refused to reject anybody. And that's exactly what we did, if not always enthusiastically. It's hard to find a geek circle without at least one of Those Geeks: the kind who drag things down and ruin things for everyone, but people feel a duty to put up with their crap because that's what it means to be a geek. They continue to abuse us and play us, for exactly this reason. And they aren't going to change unless they are forced to. Some of them won't change even then, but you do what you have to do.
And that's the problem with the kernel's old code of conduct, and with these "Kind Communication Guidelines". They're a step in the right direction, because they spell out unacceptable behaviors. But because they don't spell out clear and consistent consequences for those behaviors, creepers gonna creep. You might catch a few mild cases, and that's not insignificant, but the mild cases aren't at the core of the problem, so the needle isn't going to move much.
I know only too well how hard it is to lay down the law against someone who is abusing your goodwill, especially when they're valued for other reasons, and most of all when it feels so much like they're "just a little more extreme" than most. It's a horribly painful thing to have to do -if you haven't had to do it before, it hurts just as much as you might imagine, if not even worse- and I can't blame people for being reluctant to do that. But this is how you induce change in the hardcore. Guidelines like this can serve as decent warning that real change is coming, but they don't bring about that change themselves.
Still, this is a step in the right direction. It's at least an acknowledgment that there are norms, and they are to be observed. But it's not going to be the magic pill. There simply is none.
Dammit, and I'd even queued up Orff's "O Fortuna" to go with the rising crescendo of Emergency Alert System tones.
The radical inclusivity (i.e. exclude no one, for any reason) of the geek community led to some beautiful things. We took in the people nobody wanted around, and with their help, we built something special. But in our reluctance to exclude anyone, we forgot something important. We were all accused of dragging things down and ruining things for other people -it's part of what bound us together- but we neglected to address the fact that for some of us, that was true. And we became their enablers, and they did drag us down and ruin things for everybody, because that's what they do, and we did not insist that they change or leave. Many people preferred to just leave themselves, rather than confront the manchildren in our midst: a de facto exclusion, rather than mandated by any sort of rule. We were, in essence, abused and manipulated by the people we should have kicked to the curb, and because of this, they took over.
This is ending. And that scares some people to death, and not even unreasonably so: these are people who were rejected by their societies all their life before finding geekdom, which they clung to because, in its refusal to reject anyone, it could never reject them. Anyone who remembers being an outcast would be scared by the possibility of geeks beginning to cast people out, because it opens the potential that they might be cast out yet again. Who wouldn't fear that? Especially after years of growing unused to outcast status?
And yet, it has to be done. It should have been done a long time ago. Those who get cast out because of this still have the option that has been facing them since childhood: they can change. Because sometimes, the ostracizers are right.
Let's say you have 20 people in a group. At a given point in time, you might have ten people each funding one "share" in the system, two more people funding two shares each, two more funding three shares each, and six who cannot fund any shares. When the time comes to pay out, all 20 people get one share each: the ten "neutrals" get back essentially what they paid in, the four "over-funders" get less than what they paid in but still get a share each, and the six "under-funders" get more.
The following month (or whatever pay period you use), one of the people who had been funding three shares loses a lucrative job and can no longer fund any shares, but three of the former under-funders find jobs and can now fund a share each. The group still has funding for 20 shares, so everyone still gets a share when the time comes. It also demonstrates the importance of neutrals in the system: several people going neutral can make up for an over-funder who finds themselves in a bad spot.
Most polyglots are only really strong in two or three languages at a time. They may be passable in a few others, but they only remember bits and pieces of most of the languages they've worked with. They only have so much space in their head, just like you; the difference is in how they manage it. They organize their headspace differently, and there are upsides and downsides to that.
There are four main skills to being a polyglot. The first is knowing how to separate programming from coding. Your first language is always the hardest, because you're actually learning two things at once: you're learning the mindset and methods to create programs, and you're learning how to write down what you create in a particular language. When you go to relearn your second language, you don't have to relearn programming: you already know how to do that. This makes your second language, and later languages, easier than the first.
The second skill is understanding when and how it's okay to forget. There is only so much space in your head, and you forget things you aren't using. You mention this as a problem, but polyglots are no different. The trick is that almost every programming language was created because its author thought something was too difficult in the lanuages of the time, and wanted to program that thing in a way that flowed more naturally in the way they thought about it. These are the areas where you want to focus your attention: learn them as thoroughly as you can, and incorporate the concepts behind them into your general knowledge of how to program. The rest can be forgotten unless you're using the language often.
The third skill is how to draw connections between languages. As you learn new languages, focus on figuring out how to do the things you already know how to do in other languages. This will help you learn them faster, and relearn them faster (because you're going to have to relearn things you've forgotten sometimes). There's a book called "Seven Languages in Seven Weeks" which is good practice for this: you will not become an expert in any of the seven, but that's not the point. The real goal of the book is to teach you how to evaluate a new language and break it into parts that are easier to understand.
The last big skill is getting help. A polyglot is never going to have the same depth of knowledge in a language's libraries as a single-language expert will, so you need to know where to go when you don't know something. The official documentation is good. Other people are better, but not always available. You need to be able to have a sense of what you're looking for, where to get that information, and how to get it from there. You get faster at this with time.
That's most of it, really. And note that last paragraph: it's important to rememver that "polyglot" doesn't just mean "awesome". Polyglots get the job done and they look good doing it, but there's a price to pay for that. A single-language expert may or may not produce code that's any better than a very careful polyglot's. But the polyglot will take longer -sometimes much longer- to produce the same code, due to the overhead of relearning. This makes experts great, when you can find an expert that can do what you need. But sometimes, especially when your needs are very specific or demanding or the language you want to use is very new, it's not feasible to find an expert. That's where the polyglot shines: if you can't find an expert able to do what you need, the polyglot will become able to do what you need. Experts sculpt the language; polyglots sculpt themselves.
You're worried about whether or not you're cut out for this career, but I think you can succeed. If you want to become a polyglot, I think you can do that: it's a skillset you learn, not a talent you're born with. If you would rather develop as a Go expert, that's also feasible: Go is gaining a lot of popularity and seeing a lot more use than it used to, and there's a real need for experts. There are ways to branch out and carry on a good career with either path.
But in the end, it's your decision. This is a big step, and I can't tell you what's right for you. You don't have to change careers, but you can. You don't have to become a polyglot, but you can. You don't have to stick with this one language, but you can. You are not trapped.