It isn't necessary, but I decided that it didn't make sense to try and keep it under the vest. I'm pretty open about it, and even though my meds keep it under control 99% of the time, it's better for them to know that I'm not just slacking off.
I've had similar reservations on the part of employers because I'm bipolar. Thankfully, my boss decided to trust me somewhat, so I didn't get this kind of a shaft.
Not to be argumentative, but this is a fairly naive point of view. The assumption that monopolies would immediately spring up in an unregulated market proves your lack of understanding about the way the market regulates ITSELF.
The fact is, most government regulation is either not uniformly enforced, or forces affected businesses to do things that negatively impact their production, efficiency, etc. When a business is forced to gimp itself, it immediately passes the pain to the consumer in the form of lower-quality products and higher prices.
How many other laws regulate business? How many of them have completely solved the problems for which they were passed? Those attempting to further regulate are, in effect, saying, "THIS law will fix the problem!" Then, when they pass another law a year later, they say the same thing, hoping that nobody will remember what they said before.
If a business is accountable to its customers, everything else falls into place.
That's true to a point, but at some point, you risk making each line of code too dense. Content density is a tricky thing, and something that can very easily be used in a nefarious manner. A lot of the examples I've seen have done in one line what might take me ten or twenty lines of C++ or C#.
If I know the language, then extracting information from a given line is a lot easier than someone looking at it with little or no concept of the syntax. I've tried learning Haskell, so I'm not completely unexposed, but
let fibs = 1 : 1 : zipWith (+) fibs (tail fibs)
Is not trivial for me to parse. I don't think that the difficulty lies entirely on my side, either. I managed to get to the point that I could write some pet projects in Lisp, and that wasn't easy, despite Mr. Graham's protestations to the contrary. I think part of the problem is that Haskell's syntax just differs a lot more from my standard fare than other languages.
That really seems like splitting hairs to me, but maybe there's a flash of light that hasn't hit me. In both cases, you're describing the steps required to calculate something; the difference is that Haskell looks like it lets you assume or not bother with things you might have to worry about if the same thing was being written in something like C++.
I've always been fascinated with the ideas behind functional programming, but every time I try to learn it, I'm immediately struck by the complete mental disconnect needed to stop thinking about problems from an imperative or OO-based perspective. I've learned enough Python to use it for quick prototyping and testing, and I managed to get far enough into Lisp to realize it wasn't made for humans, but my one foray into Haskell was roughly equivalent to having the math team from my high school kick me repeatedly in the head while shouting, "WHY DON'T YOU GET THIS? THIS IS EASY! YOU MUST BE A RETARD!"
Slashdot Mirror
There's no such thing as a beautiful regexp.
feldicus
I'm terrified by the possible options for the Bond Girl in that film.
feldicus
How is this marked informative? Where I come from, something has to be readable to be informative. Remember kids, structure friend is your sentence!
feldicus
I'm pretty sure it's illegal to deny employment based on it, yeah. I'd just rather people know. I'm no good at making excuses.
feldicus
It isn't necessary, but I decided that it didn't make sense to try and keep it under the vest. I'm pretty open about it, and even though my meds keep it under control 99% of the time, it's better for them to know that I'm not just slacking off.
feldicus
I've had similar reservations on the part of employers because I'm bipolar. Thankfully, my boss decided to trust me somewhat, so I didn't get this kind of a shaft.
feldicus
Not to be argumentative, but this is a fairly naive point of view. The assumption that monopolies would immediately spring up in an unregulated market proves your lack of understanding about the way the market regulates ITSELF.
The fact is, most government regulation is either not uniformly enforced, or forces affected businesses to do things that negatively impact their production, efficiency, etc. When a business is forced to gimp itself, it immediately passes the pain to the consumer in the form of lower-quality products and higher prices.
How many other laws regulate business? How many of them have completely solved the problems for which they were passed? Those attempting to further regulate are, in effect, saying, "THIS law will fix the problem!" Then, when they pass another law a year later, they say the same thing, hoping that nobody will remember what they said before.
If a business is accountable to its customers, everything else falls into place.
feldicus
Don't be too proud of this technological terror you've constructed. The ability to monitor a planet is insignificant next to the power of the Force.
feldicus
I'd suggest taking at least one pass over "The Mythical Man-Month", if only for the principle of "build one to throw away".
feldicus
I don't know. The programmer in question has a lot to do with it, but it seems like some languages lend themselves to certain densities.
feldicus
That's true to a point, but at some point, you risk making each line of code too dense. Content density is a tricky thing, and something that can very easily be used in a nefarious manner. A lot of the examples I've seen have done in one line what might take me ten or twenty lines of C++ or C#.
If I know the language, then extracting information from a given line is a lot easier than someone looking at it with little or no concept of the syntax. I've tried learning Haskell, so I'm not completely unexposed, but
let fibs = 1 : 1 : zipWith (+) fibs (tail fibs)
Is not trivial for me to parse. I don't think that the difficulty lies entirely on my side, either. I managed to get to the point that I could write some pet projects in Lisp, and that wasn't easy, despite Mr. Graham's protestations to the contrary. I think part of the problem is that Haskell's syntax just differs a lot more from my standard fare than other languages.
feldicus
That really seems like splitting hairs to me, but maybe there's a flash of light that hasn't hit me. In both cases, you're describing the steps required to calculate something; the difference is that Haskell looks like it lets you assume or not bother with things you might have to worry about if the same thing was being written in something like C++.
I've always been fascinated with the ideas behind functional programming, but every time I try to learn it, I'm immediately struck by the complete mental disconnect needed to stop thinking about problems from an imperative or OO-based perspective. I've learned enough Python to use it for quick prototyping and testing, and I managed to get far enough into Lisp to realize it wasn't made for humans, but my one foray into Haskell was roughly equivalent to having the math team from my high school kick me repeatedly in the head while shouting, "WHY DON'T YOU GET THIS? THIS IS EASY! YOU MUST BE A RETARD!"
feldicus