damncabbage

Except Sally now suddenly has to retrain as a salesperson. And perhaps also try to beat out other people which already have sales experience to that sales job.

This takes effort and may be achievable with a lot of gumption, sure, but now consider the entire workforce that just got fired. Are they all going to be able to pull that off?

So... Not for anyone with a significant other. Or a family. Or an aversion to spending all day and night with your co-workers.

There's a pull request open here: https://github.com/Homebrew/homebrew/pull/26075

If you absolutely can't wait, you can run this to install it:

  $ brew install https://github.com/adnissen/homebrew/raw/110c278d3a6ce6edae6208f4033bd3508530f29d/Library/Formula/rig.rb

Voilà.

  ############################################## 100.0%
  ==> Downloading http://downloads.sourceforge.net/project/rig/rig/1.11/rig-1.11.tar.gz
  ############################################## 100.0%
  ==> make
  🍺  /usr/local/Cellar/rig/1.11: 10 files, 96K, built in 5 seconds
  $ rig
  Jewell Harrison
  984 Lowel Rd
  Galveston, TX  77553
  (409) xxx-xxxx

I'd recommend http://en.wikipedia.org/wiki/Pirates_of_Silicon_Valley if you haven't seen it already. It covers both Jobs and Gates in the period where both Apple and Microsoft began (though I'd argue that it's a little more focused on Jobs).

Well, not really. Consider the (very common) case of a PHP-based blog, forums or shop being hosted on shared hosting. The latter gets an upgrades, and the site explodes.

(I say do it anyway. It's like IE6; give it a long grace period, then tell people they need to get with the program.)

One question I haven't managed to answer yet: what happens when a Bower-bundled component needs to use and image (or a font)?

As far as I can tell, there's not asset-path() usage, and so the link breaks in production (where image assets have <assetname>-<md5hash>.jpg filenames, for example).

Scroll down.

SSNs, IPs and Phone Numbers get reused. People often have multiple email addresses.

(Bonus: Yahoo! email addresses get reused too.)

  ... while setting up huge MySQL installations with a
  dozen+ replicas ...

If you're careful about your function calls, sure. Include a UUID() or SYSDATE() in your INSERT statements, and the replication goes to pieces as the function calls are run separately on each slave (with differing results).

There's a baseline level of competency I'm willing to work with. I've had to fight for basic things (like version control) over and over again, and I'm fed up to the point of not wanting to fight those wars again every time I join another company.

The lack of testing culture, for example, was what first drove me away from PHP (to Ruby). Every PHP role interview, I'd gingerly have to ask if they knew what Automated Testing was ("Yes? Great. Have you done any yet? ... No? You don't want to? Oh."), whereas at every interview for a Ruby role I've basically gotten a "Of course we're testing. What else would you be doing?" response.

Once you get past talking about things up to the baseline, you can start the real interview.

I enjoy reading The Onion. I thank you for your sacrifice. ;)

p866:

  The level of indentation that seems to produce optimal 
  results in comprehension is between 2 and 4 spaces; as the 
  number of spaces increase, the comprehension level 
  decreases.

On the other hand, the sample program hard parts that were indented nine times (!) in places. It's an interesting read, but I'd not try to use it in a discussion.

Personally, I don't care; just pick one (hopefully one that matches what most people are using with that language, eg. 2 spaces for Ruby), and get on with it.

What happened between the 19th and the 28th? https://news.ycombinator.com/item?id=6638004

  Hi Justin. To clarify, from what I understand, October 28
  is the date MongoHQ detected this. They've provided us 
  with the logs of database access, and unfortunately the 
  queries leading to our spam attack on Saturday started as 
  early as October 19.

For the moment, yes; it's an employees' market right now.

What I hate to think about is what happen when the pendulum starts swinging back. My partner is in print design, and most companies seem to put candidates through onerous application procedures because they can.

In the US, in some places, yes.

The post's author is Australian, and is writing from that perspective. We have minimum legal notice periods from both sides (a week for the first year, evenutally going up to four weeks): http://www.fairwork.gov.au/TERMINATION/NOTICE-PERIODS/Pages/...

I was with you up until port knocking.

The problem with the implementations I've seen is that the daemons themselves can introduce vulnerabilities. Why bother compromising OpenSSH when the lesser-used port-knocking daemon is vulnerable?

My comment from the blog:

Additional point: the candidate may not be able to work (paid) at another company for a week without breaking part of their contract, such as a "devotion" clause.

(For example, something like a "the Employee must not, without the Company's prior written consent, engage in any other employment or business activity" line in the contract.)

As far as I'm Rails doesn't use secure-flag cookies by default; you need to have something like this in config/initializers/session_store.rb:

  local_env = !(Rails.env.test? || Rails.env.development?)
  MyApp::Application.config.session_store(:cookie_store, {
    key:    '_my_app_session',
    secure: local_env, # ... or just true
  })

Yes, somebody who has gone looking for this can find it, but I'd argue that Rails should at least give you the secure: ... option in a comment block. Anything less is just inviting people to get bitten by the lack of it.

  When I click log out, I know I'm logging out on this
  browser but not other browsers.

Different browsers get different sessions.

  ... it doesn't limit you from storing and checking
  things on the server-side.

Correct, but you basically end up reimplementing parts of ActiveRecord::SessionStore anyway.

  Changing session store to a database or memory store won't 
  fix it: a session id is still required on the client side, 
  then your session is still hijacked because the attacker 
  still gets the session id.

The bug specifically addresses logging out.

When you store a record of the session on the server side (with the session ID you mention), you clear that session record during logout; the session is now gone, and cookie isn't valid anymore.

(With the cookie-only approach, the server will continue to accept a cookie that you wanted to have cleared.)

7 years of PHP projects: old, messy, legacy and new and fresh. I loathe PHP and never want to use it ever again.

Most I've talked to in person (yes, plural of anecdote is not data, etc) hate PHP because they've had a wonderful first-hand experience with it. This is in Sydney (Australia), where Ruby and Node is a relatively recent phenomenon compared to SF and the like.

Your post could do without the shitty attempt at sarcasm, but you've likely figured that out already.

Thank you so very much for your efforts. We use Capistrano at Bigcommerce to deploy our apps and components, and it's saved us from an inevitable pile of shell scripts. :-)

It's "Matz Is Nice And So We Are Nice", because MINASWAN is a joke on the Japanese word for "everyone" (minasan). The -swan is like a super-cutesy suffix honorific thing.

... And yeah, it sucks that it feels like it's died a bit. But keep it up anyway; https://twitter.com/tenderlove is a great example to follow. :)

In poster form: http://www.flickr.com/photos/craftydogma/6657220791/

Ah! Oops. Thanks.

... "Paul Graham is gay"? http://i.imgur.com/UTk9DlM.png

"With this purchase, you will be activating your VIP membership" is in the sidebar. It's at body-copy writing, and you have to go looking for it.

This is a combined "Forced Continuity" and "Sneak into Basket" set of dark patterns that doesn't even given you the in-line checkbox to uncheck:

* http://darkpatterns.org/library/sneak_into_basket/

* http://darkpatterns.org/library/forced_continuity/

And what about the poor bastards who are judged to be "average" employees by whatever metric?

I agree with the model being great. The git command itself is abominably baroque in its user interface (inconsistencies and strange defaults abound), but I've gotten over that with more effort than I'd like to admit.

I love Git's plumbing; I just hate its porcelain.

  I ate better for those 7 weeks than I had all my adult
  life to that point.

I'd suggest that today's "food stamps" don't cover as much as they used to. The article does a good job of showing how little nutritious food the handouts can buy.

  Instead of heading in to town to collect our stamps...

Which costs money, particularly if you have to live a fair way outside out of town. Because you're poor.

  But having to use those colored pieces of paper in line
  at the grocery store while everyone else watched was a
  huge motivator to get out and get a job.

People are trying. Pull your head out and look at the economy. You may be fine; plenty aren't, and are stuck in a rut where they can't get out.

I know arguing with you is useless, but it's this "I worked hard, I got mine, so fuck you" attitude that's making everything worse for the poor. Have some empathy.