194 karma · joined July 4, 2012
Don't feed the trolls.
In the end not enough businesses and institutions are equipped to accurately assess skill. So rather than being hired based on skill, what you'd really be hired based on is perceived skill.
The people who can sell themselves and spin their skills will continue to thrive, the people who can't but have skills will find niches to do their work, and the people who don't have either will complain that the first two groups are being "pushy" or have an unfair advantage because they're selling themselves better.
Something like that.
Edit: even if we could measure skill... how? I don't suspect it's always an objectively measurable thing. e.g. most people who seek out psychiatric help want to find someone who is good fit for them and they can trust and talk to, not the "state's top ranked psychiatrist" (who is inherently intimidating).
http://geekfeminism.org/2009/11/29/questioning-the-merit-of-...
So, it wouldn't solve the problem... probably because it's fascistic and sexist?
How would you feel if it were the other way around, and it was insufficient white people relative to blacks, and we just killed off the excess if their employers try to shield them and replace them with white workers? You know: Apartheid?
If not then... I'm not even sure where to start with the problems in that plan.
Saying that applying a type system to an incorrect program doesn't make it correct without refactoring is like saying hanging a painting with nails doesn't work without a hammer.
It's true, but misses the point. Programmers tend to introduce implicit type information (anything from dynamic types to how you choose which functions to apply to which values). Bunches of bits have to be classified somehow to be useful.
A static type system lets you specify and define that classification explicitly, rather than implicitly.
So, if your mental model of the correctness of a program includes type information (and I assume it does in some manner or another) a static type system is invaluable for proving (re CHC) one facet of the correctness your program. Moreover, if your model isn't perfect – it rarely is – then a type system can allow you to scrutinize and analyze your model more rigorously.
These sorts of things are best left to a static type system, which is a more specialized and effective system for that portion of validating your code. On the other end of things, tests of more stateful processes or behaviors are better served by E2E testing.
There's nothing wrong with using multiple forms of testing. Different tools excel at testing different sorts of things.
Types let you codify your idea, and then make sure your implementation aligns with it as you write it.
I have found at least anecdotally that the benefits of a strong, rich type system are multiplicative with other features, not additive. For example, types in Java are largely a nuisance. The type system lacks facilities to express obvious things (I want a list of things that all have this interface) in clean ways. Instead you have to resort to "clever" hacks which ultimately just circumvent the guarantees you wanted to establish. For small projects this is a non-issue. For large projects, this is hell.
By contrast, type systems thrive in contexts with algebraic or sealed case types, or any form of pattern matching really. Or just plain old enums. In conjunction, these features enable very powerful static checks. Forcing you to handle None/Null/NONE/Nothing/nil cases everywhere encourages critical thinking. This introduces more issues, such as staircase code, but these are largely (I would personally say completely, and with a nice surplus) fixed by things like pipes, monads, computation expressions, and so forth.
This extends to libraries as well. I can't count the number of times I've used libraries which changed their API's in "non-breaking" ways, such that certain functions returned types I assumed would never be returned. Was this my fault? Yes. But if the return type had been strongly typed and I had been working in such a language as described above then:
1) I would be forced to handle every extant constructor in that type.
2) If a new one was added, I'd get a compiler warning alerting me to the fact that I hadn't handled it (this is great!).
3) If the type changed entirely, I'd get an error warning me to the fact that my code was no longer compatible with the API provided.
In the end, working with and writing libraries is about respecting contracts. Types are a tool for codifying those contracts. Strong typing and matching facilities are even more powerful tools for alerting you to violations.
The benefits are largely discoverability, enabling better tooling, improving the number of optimizations compilers can make, and guiding the programmer. These are all things we benefit pretty much unilaterally from. The trade off is having to be slightly more explicit (Java and C# haven't helped this, as they insist you sign everything in triplicate, rather than promote type inference).
For functions with sufficiently rich types, there are often only a couple ways to implement the function. Sometimes, there are few enough that a compiler can actually derive it for you.
Having switched between typed and untyped languages repeatedly, I can't emphasize enough just how much rich, strong types contribute to the readability of the code.
And on yet another front, it may only be "2%", but I'm sure most people on here know how it feels to have written a couple hundred lines of code, only to suddenly find something of the wrong type somewhere it shouldn't be... It only takes a fraction of a percentile for a program to be utterly and completely useless.
For example (hypothetically), you're asking for trouble by having a single rank of sysadmin who can clean out logs after doing whatever they please... or worse yet if you don't log accesses at all.
To me it looks like SEO/Marketing folk acting like it's the end of the world that 50% of clickthroughs are (not provided). And for them, it may be bad as they like having that data (which they certainly didn't have a little over a decade ago).
On the other hand though, if I'm using Google secure search, as a user, this seems like behavior that benefits me privacy-wise.
Am I missing some aspect here?
I'd figured out that the barcodes used on our school lunch cards were just plaintext for our ID numbers. With minor cooperation from a nice lunchlady, I discovered that there were a couple very low numbers (e.g. 00000001) that had effectively infinite funds. Presumably they had been used for testing or something.
I brought this to the attention of the schools tech guy, who thought it was very cool and said he'd go tell the administration so he could get permission to fix the issue.
Of course, being a middle schooler with access to a card printer, I also took this opportunity to reprint my lunch card with an identical design and barcode... And a Chuck Norris photo.
The administration asked to speak to me and I assumed I'd be thanked for finding an easy vulnerability that could have been losing them funds.
Instead I was told I would be expelled or at the very least suspended for a month, and that they thought this constituted a felony and identity theft. Ridiculousness of those claims aside... I ended up getting a away with weekend detention after my parents and the tech guy stood up for me.
The point of his Kickstarter is to convert that fanbase into fungible resources. Not every UReddit user is programmer, and of those, even fewer have free time or the motivation to help out. This way anyone can contribute, even indirectly. Moreover, have you ever worked on a large scale project? Having lots of people involved is horrible. Something like this shouldn't have a team of more than 3-5 people to start. Even GitHub only has 15 people on their entire website team.
Source: I work at a design firm.