pshc

42 ms·

451.
by pshc 10y ago
Found it! https://youtu.be/B94lP-fZyLk?t=40s
452.
by pshc 10y ago
I assure you the "I'll never get a job again" feeling is very common but as a "Big 4" alumnus you have nothing to worry about (:
453.
by pshc 10y ago
Theory I heard: We're stuck with open plan due to the ratchet effect. The high price of office square footage in cities locks it in.
454.
by pshc 10y ago
Apply Bayesian reasoning. Weigh results appropriately.
455.
by pshc 10y ago
60 is the new 40 :)
456.
by pshc 10y ago
Occam's Razor strikes again.
457.
by pshc 10y ago
I'm curious, has anything ever improved as a result of being bought by Microsoft?
458.
by pshc 10y ago
tl;dr: use newtypes! I like using static types to avoid these sorts of problems. Modern languages like Swift, Rust and Haskell let you make zero-overhead type wrappers around other types. So here they could have defined `newtype RisingEdge(
459.
by pshc 10y ago
1. A special case could be added for `main`, but it's no big deal. 2. This seems difficult as the C arguments were mutable; the algorithm would have to start doing analysis rather than direct translation. 3. Quite difficult to "kn
460.
by pshc 10y ago
They are mostly reliable (though probably still full of security holes) despite C—made possible by the millions of person-hours thrown at the problem of maintaining large C codebases. Back then, we had no choice. We can do better.
461.
by pshc 10y ago
This seems overly pedantic. In my mind "incompressible" does not mean "there are absolutely zero situations in which the output could be shorter than the input." There will always be (compression scheme, input) combinati
462.
by pshc 10y ago
Also calls to mind a study which claimed that "thinking in a foreign language makes decisions more rational" by reducing deep-seated biases (that were formed as I grew up?) http://www.wired.com/2012/04/la
463.
by pshc 10y ago
This holds if the small functions are built around a coherent top-down design, respecting each other's invariants. Once the project is too large to fit in one's head, it is no longer sufficient for each function to be 'correc
464.
by pshc 10y ago
Java has quite a bit of memory overhead which exacerbates Minecraft's inherently high RAM requirement. That plus frequent GC pauses make Java a suboptimal choice for Minecraft long term. (But it may have been the right choice for Notch
465.
by pshc 10y ago
Right. There doesn't seem to be enough information bandwidth in or out (no touch typing, keyboard consumes half the screen, 80x24 is hardly readable) on a mobile phone to do any non-trivial coding. We may need to design a wholly differ
466.
by pshc 10y ago
Here is his very Serious LinkedIn where you may read his Serious resume, including endorsements by Serious men with suits and beards: https://ca.linkedin.com/in/mricon
467.
by pshc 10y ago
This is quite logical and I've been wondering--isn't this at odds with (future) dual SLI one-eye-per-card techniques? Would it make sense for dual SLI VR setups to go back to the old "card 1 renders the top half of the screen
468.
by pshc 10y ago
Yes. A blessing in disguise. In hindsight, global type inference seems too unstable. Too much action at a distance; it's hard to evolve a codebase when local changes cascade. Type annotations keep things grounded.
469.
by pshc 10y ago
It's just a bug. It's pretty easy to accidentally have such cases in a generic type inference algorithm, particularly one with implicit conversions. Other similar languages have had pathological cases in type inference too.
470.
by pshc 11y ago
This is in Python 3. xrange is now range, so only a generator is constructed. Agreed that 1 <= len(vals) < 5 would be more Pythonic.
471.
by pshc 11y ago
I don't expect or want to type in my username every time I unlock my phone. Nor my secure alphanumeric password. Usernames are easy to guess or find out, so in that scenario, the fingerprint scanner would go to waste unless you used a
472.
by pshc 11y ago
"Authenticates you to provide your password" meaning...?
473.
by pshc 11y ago
In short: Be specific.
474.
by pshc 11y ago
>Code that takes a full structure when it only needs to operate on a part of the structure is badly designed. I think this was a sensible statement, especially in context; I strongly agree that "this is behind a lot of long-term m
475.
by pshc 11y ago
His talk on "Present Shock" just expanded my mind a little bit. Embedded in the article: https://vimeo.com/65904419 "We recast this digital renaissance--this ability to really program our lives, to get slack
476.
by pshc 11y ago
I'm working on something slightly similar. But I'm sticking with the keyboard. And the "visuals" will still be text, with the option of other visualizations. Keyboard+text scales better than anything else.
477.
by pshc 11y ago
Perhaps unrealistic, but a brilliant concept.
478.
by pshc 11y ago
Maybe in Microsoft-land or certain circles, but anecdotally I've only started hearing "learnings" this year too.
479.
by pshc 11y ago
Anecdotally, I experienced mild depersonalization in 2014 after too many sessions in the DK2. (Other life stresses were also a factor though.) Very disorienting at the time. But I know what that dissociation feels like now and can manage it
480.
by pshc 11y ago
That's a neat analysis of what makes an artistic medium interesting! Did you come up with that breakdown?

More ›