1,975 karma · joined December 17, 2011
OSS has nothing to do with piracy. If I licensed my project MIT, sharing it is not piracy. OSS platforms do not have thriving piracy ecosystems because there is plenty of OSS software for them. In my experience, people who believe in OSS are the most likely to champion using a legal OSS alternative to pirating some widely-used proprietary software.
I would argue that the situation with Rails is analogous to the (historical) situation with Windows. There have been some design mistakes which have opened up more surface area for attacks. But the number of exploits has a lot more to do with market share.
I submit that security is typically more a function of your project than JUST the language it is written in. For example, I doubt that Haskell's focus on type safety alone will make your programs secure (particularly when you are not enjoying it and are spending more time than you want on issues other than security). You may get more bang for the buck by focusing on security as an issue within whatever language you are using?
However, most companies are smaller than Google and Amazon and have different practices. Sometimes, stupid practices, because the interviewers don't really know how to do it, just want to get it over with, or really care about things which aren't important.
But since they are in the hiring position and assume they and their company are awesome, they are not so likely to question their own technical or interviewing abilities and certainly don't want to hear what interviewees have to say about it.
You need additional insights beyond just doing the job to understand what makes someone else useful in that job. And if you don't even have that much, you are guaranteed to ask stupid questions and end up with people selected for how good they are at selling and how much you think they're cool.
If you want to become an excellent engineer or artist then you will probably be better served by getting educated, and logging many hours in progressively more difficult jobs, than procrastinating and dithering.
Anyway, most people don't have the luxury, and will only get anything interesting done if they put in serious focused effort.
So realistically I believe this is a niche idea which might be hard to make commercially viable. But it could be an interesting thing for private minecraft servers.
But this answer is unlikely to be the worst thing about you. You probably do have character flaws which affect your work. It's just that digging into them won't do anything except give the advantage to someone else who kept his mouth shut.
I submit that what this question really does is test fit to a certain corporate culture. There's a tacit understanding that you are supposed to come up with some token flaw to use. People oblivious of this will either overshare or obviously deflect the question, and people who are stubbornly honest will also not give the expected answer.
This kind of obliviousness or stubborn honesty can be a political liability. E.g.: if you are asked about your boss's or team's or company's worst weakness, you should also offer some bullshit token flaw which isn't really meaningful, because this determines their futures too.
If a culture isn't specifically built to put honesty ahead of politics, politics will quickly take the lead and honesty will be a casualty.
This is like the ancient Chinese exams which assessed applicants' suitability by their knowledge of classical poetry. Of course people who are very well prepared or smart will do better in aggregate and with certain biases, but this doesn't mean you are measuring what you claim to measure.
People have been asking this for so long that it really only gauges whether the applicant canned an answer to it which sounds bad enough that you won't think it's bullshit, but good enough that they aren't hurting their application. As with other interrogation techniques you often aren't selecting against lying, but just for plausible lying that you are unequipped to detect. It is certainly an illusion that you are selecting for honesty this way.
If you do want to hire honest people, and it isn't for an area like sales where it is important for them to project unrealistic levels of self-confidence, you will cause less needless anxiety and get more actionable information if you can get specific on what sort of disclosure you need, rather than just asking the applicant to incriminate themselves in the worst way they can imagine.
If you want to punish people with ability and integrity but lower self-esteem then this question is your ideal instrument.
To pick just one random alternative, let's take gedit. It looks simple and standard, which is nice. It's newer, that could be OK. It can be installed on more than one platform (though not necessarily simply). It has the major features, it's basically feature-complete. For fancier stuff and language-specific tools, you can write plugins with Python, which makes all kinds of things possible. On the other hand, it can get crashy when you use a few plugins - maturity issue. There are few plugins and fewer actively maintained because there's not a big community to support and build on it. A lot of its behavior is reasonable but not really customizable. Random example - if I personally want to have a simpler interface in the vein of scribes or WriteRoom, I'm SOL. Of course, gedit simply cannot be used from a terminal, so you will use another editor for that, with its own keybindings etc.
Most of the good editors have a story like this. Even if it seems to work great and be flexible enough, the community and plugins aren't there.
If your goal is only (say) to write C# for Windows, Visual Studio is probably best. If you only want to write Java, (say) IDEA is probably best. These are powerful environments. But only for certain things, and in a certain way. If you want to code on another platform, different language, really change the behavior, get around a bug, or get a fancy new capability without paying a vendor lots of money, you are just going to hit limits and have to pick up yet another tool.
If you've learned vim or emacs then you at least have a default which licks all these issues at once. In this sense they are "ultimate editors". And this is an opinion informed by broad usage of many editors.
Sharpening your tools is an investment where you trade time now for power later. Vim is very much an instance of that trade-off. It's a ridiculously flexible power tool. If you are a machine at driving nails with a rusty hammer and you are happy, then there's no reason to stop doing it that way.But if the reason you don't use vim is that you're scared of it, it's not as bad as you think. You don't have to be superior to learn it, you just need a week and an open mind.