deadowl

Placing blame in a business setting is overvalued.

Let's all worry about blaming someone for a problem instead of fixing it. It's so much more productive.

Sounds like it could just as well be a case of a bunch of people overvalued perceived business sensibility and ignored technical sensibility, which is incredibly common.

I'm particularly infamous among my peers for asking questions, and most of the time I'm not asking on my own behalf. Asking a question because you don't understand is what you can do for yourself. Asking a question because you don't expect others to understand is something more.

This pretty much applies to all disciplines, particularly when a subgroup of people are more likely to feel intimidated by the learning environment.

I don't understand why they're calling him the last link to the Battle of Little Big Horn. He was born in 1913, well after the Battle of Little Big Horn.

I'm not saying their system of government is Muslim. I'm saying that 98% of their population is Muslim.

Well, Trump was my first thought seeing the headline. He wants to ban Muslims from the US. Turkey is a Muslim country.

I often end up writing an immutable wrapper for date/time in different programming languages.

Unless they're representing date/time or strings, then immutability is an excellent feature.

It's a fun problem to think about, but I'm just going to use the date library because it's really easy to screw up.

/\p{Lt}/.test(str) would be much more compact, but Unicode properties still aren't available in Javascript regular expressions. It doesn't look like they will be anytime soon. I guess they have some staging system and it's still at stage 0 (https://github.com/tc39/ecma262/blob/master/stage0.md), grouped with lookbehind assertions, named captures, and mode modifiers.

You have final-forms in Hebrew, although probably not at the same level of support for checking as you'd get with a script like Arabic.

typeof string == "string" && string.length && string[0] == string[0].toUpperCase() && string[0].toUpperCase() != string[0].toLowerCase();

The three cases you state aren't nearly as hairy as determining whether something is a positive integer.

Someone might do something like ~~n to truncate a float. That works fine until you go above 32 bits. Math.trunc should be used instead. Someone might do something like n >>> 0 === n, and using any bitwise operators will always bake in the assumption that the number is 32 bits. Do you treat negative 0 as a negative integer? Detecting negative 0 is hairy. So, to avoid bad patterns, it makes sense.

For is-bigger-than-5(x), x > 5 is not hairy. For add-1-to-a-number(n), n + 1 is not hairy.

For word-starts-with-capital-letter(word)? That one is actually pretty hairy. There are programmers that would write a regular expression /^[A-Z]/, or check the charCode of the first character being within the A-Z range, amongst other solutions. An appropriate solution, however, would be (typeof word == "string" && word.length && word[0] == word[0].toUpperCase() && word[0].toUpperCase() != word[0].toLowerCase()), because the toUpperCase and toLowerCase methods are unicode-aware, and presently you can't access unicode properties using Javascript's flavor of regular expressions.

Another question is whether you'd want to include negative zero as a positive integer.

x >>> 0 changes a negative integer to an unsigned (positive) 32-bit integer. You can have integers greater than 32 bits. They're represented internally as floats. Bitwise operators make 32-bit assumptions, with the top bit as a sign bit, unless you do x >>> 0, in which case you can revert a sign bit overflow back to a positive integer. If you have a positive integer that's greater than 32 bits, x >>> 0 === x fails. The expression (84294967295 >>> 0 === 84294967295) is false.

Don't even get me started on negative zero.

I like to use non-breaking spaces for that kind of thing, although they still might collapse that? At least it doesn't wrap non-breaking spaces.

Three completely unrelated things I guess.

1. Expressiveness is important? Expressiveness is why I don't like Perl.

2. You can certainly implement patterns analogous to OO in functional programming with closures and first-class functions.

3. Reading in the order of execution via chaining is definitely a lot more intuitive than reading from the inside out or right to left.

I don't know if this is how you'd do it in markdown. My text tables are generally done this way:

    +-----------+-----------+-----------+
    | label a   | label b   | label c   |
    +-----------+-----------+-----------+
    | r1f1      | r1f2      | r1f3      |
    +-----------+-----------+-----------+
    | r2f1      | r2f2      | r2f3      |
    +-----------+-----------+-----------+

I think they want to be the NSA or something.

Is there any way I can guess at my password from the Gawker leak?

It's the digital age. I am recorded on video at minimum, I would expect four times a day. I'm not a criminal. I'm commuting to work. The digital age has eroded the privacy that generations before us were able to take for granted. Does Obama want to eliminate the only guarantee to privacy that still exists in the digital age? The fourth amendment states: "The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated." I wouldn't expect to be able to exercise that right, in any sense at all in the digital age, without encryption.

Maybe he just wants people to feel how he felt when Hillary had her infamous "kitchen sink" strategy moment.

Any way to reconcile power-of-two memory structure and boundary checks? I can't imagine all code should be constrained to power-of-two memory, but if you throw in multi-threading somehow, I think it would start making more sense to have the best of both worlds.

I've seen significant script delays from loading files on the server, before ever getting to the web browser. I.e. apparently the file server was on the network, but not the same machine as the web server. I was using Smarty as a templating engine, and I had a template for a table row that loaded many times during the rendering of a particularly long table. It literally was loading the file once for every time a table row had to be generated, and it came with a lot more overhead than I would ever expect.

I switched the include directive to inline for the table row, but I was using template directives that were not supported inline by the template compiler. In the end I had to add some code to the compiler in order to get a reasonable performance time (thank you open source).

I'd actually be OK if map and filter were also in the functools package, but the only way to be consistent while maintaining backwards compatibility is going from the functools package to built-in.

Better handling of Unicode is inevitably how Python3 kills Python2. Also it's a good reason to have not supported Python2.

Aside from Unicode, I don't like some of the other changes. The overkill on the "one obvious way" bugs me in particular, e.g. the removal of reduce as a core function.

The existence of "one obvious way" isn't set in stone. It depends on context, and it's like the language developers didn't realize that when making their decision.

Even updating only 100ms at a time, you could statistically infer much smaller intervals if you're able to cross-reference timestamps.

I know someone who once bought a house built by students, but I'm not sure whether they were high school students or community college students. They didn't do any excavation work though, and it ended up being moved to the final site rather than any excavation work being involved. This was in southern Maine.

The financial aid process is horribly dysfunctional. Some loans, grants, etc, are based on financial need. There's expected family contribution (i.e. they assume your parents are going to cover part of your expenses). There's the PLUS loan that they give to parents, because of course parents should have to take out a loan to even begin to cover what the federal government expects them to pay. If your parent isn't going to pay for you to go to college, it can be unaffordable.

I got screwed in 2008 when my mom was denied the PLUS loan. I tried talking to student financial services for advice. After talking to the dean of my college, I received a large grant in order to cover my senior year. I thought I wasn't screwed anymore, but I got screwed again because nobody told me that a whole other part of my financial aid, "need-based" aid would disappear because my parents are expected to pay so much, regardless of their ability to do so. After that I was still able to pick up a few more grants and scholarships. However, I ended up having to take out private loans to cover much of the rest. I very much do not recommend taking out a private loan to pay for college.

I never really thought to do anything like .classname.classname