3,050 karma · joined August 2, 2010
rob@robhoward.id.au
http://robhoward.id.au
http://twitter.com/damncabbage
http://github.com/damncabbage1. http://www.aec.gov.au/faqs/election_advertising.htm#blackout
Directly from the article:
“Sure, you may not be achieving much by midnight, but do you really want to be one of the first in the team to leave your desk?” George Herbert at PolicyMic asks. “If you’re always the one who leaves first will your boss question your commitment when it comes to calculating your annual bonus or deciding whether to take you onto a regular contract?”
I don't know if this leak is legitimate. Has this been covered by other sources, or has anyone downloaded the dump to see?
It's an annoying bug, it keeps getting raised as a problem, but it's never been dealt with.
APP_ROOT=`dirname "$0"`
(See http://www.tldp.org/LDP/abs/html/varassignment.html#EX16)Also, even if ^J or ^M were present in a parent directory's name, the command above would still work. Whitespace-like characters take some getting used to with Bash.
("Is it Lg, or Lrg? Err, hold on, I'll check...")
The pendulum is swung our way right now. Put yourself in the position of someone going for a job in a market that's tight and competitive.
(Like trying to rent a place in Sydney or NYC, they can discard you and there'll be plenty of people left lining up to take your place.)
For example:
# Is this some_method with an empty block, or an empty hash?
some_method {}
# Is this a regex or a comment?
#
# It depends how many arguments "whatever" takes, and you
# don't know that until you run the code that defines it.
#
# Interpretation is implementation-defined. It just so
# happens that the MRI determines that the below ISN'T a
# regex because it has a SPACE character just after the "/".
whatever / 25 ; # / ; raise SystemExit.new;I hate to break it to you, but everything you're using right now to send this information was arguably designed by nerds.
And http://cmj.io/posts/devs-make-capistrano-your-new-friend just doesn't work.
This just seems like a really poorly put-together custom blog. #-only routes, websockets for loading content, hostile error pages, etc. :(
(Telstra was government-owned until it was privatised from 1997-2000, and as such has a monopoly on most of the phone lines; the government sets the wholesale rates at which the lines are leased to other companies. Optus ran a bunch of their own cables, but the coverage isn't nearly as extensive.)
That's a myth, a pervasive one. I'll point you to one
source that debunks this, but there are many.
http://www.unlimitednovelty.com/2012/06/ruby-is-faster-than-python-php-and-perl.html
It's unfortunately compromised by some boneheaded things in the MRI implementation. Method caching is a great example: https://charlie.bz/blog/things-that-clear-rubys-method-cache(Rails startup does a lot of the mentioned things, for example, but then so do a lot of apps' controller actions unless they're careful. The OpenStruct example is particular egregious.)
The benefit everything-is-a-message is that you can swap out the implementation of sanity (or sanity=) if needed, eg.
Before:
attr_accessor :radius, :diameter
After: # Refactored radius to be the new source of truth.
def diameter
radius * 2
end
def diameter=(val)
self.radius = val / 2
end
In PHP (for example), MyClass->diameter and MyClass->diameter() are completely different things. Any existing code (including code you don't control) needs updating to change references from the former to the latter when moving logic into something that was previously static.This article is flawed by holding up those six lines in themselves as something great, but I think the point the author is trying to get across is valid.
(The article buries the link to the page with the link: https://www.healthcare.gov/developers )
I really wish they would stop using statics so much, though (eg. CHtml::activeTextField()); it's really inflexible, particularly when statics call other private statics with self::... making subclassing really tough.
(I thought "speed of light" at first, but didn't think of a way it could be applicable.)
("Use Incognito Mode when using a friend's machine or risk having your accounts stuck together"? Or maybe "Don't log into a Google account on a friend's machine without using Incognito"? It's a bit too late for me to edit, unfortunately.)
1) Use Incognito when using other machines, or
2) Don't trust Google with precious things.
(There is some mixing, eg. a few devs in Austin, a few support guys here.)