Hacker News Reader

angillyon The Day Series: The Day I let my first employee go

My position is that the salaries were really just our egos. We didn't have the money to pay ourselves over $100k. The $20k "example" is actually pretty close.

Ideally, take what you can to pay your mortgage. Put that on the books. Spend time getting profitable instead of balancing the books. If you become profitable, or get a nice round, it'll all work out :)

angillyon The Day Series: The Day I let my first employee go

Well this was two years ago, so by now he's doing well. Feel free to get at him @waltz though, I'll update the post. Thanks!

angillyon The Day Series: The Day I let my first employee go

I'm actually really interested in hearing anyone else's thoughts on this. In my opinion, there is no advantage.

angillyon The Day Series: The Day I let my first employee go

sweet, sweet revenge... :)

been fixed. thanks.

angillyon Ask HN: Massive vulnerability on Twitter?

... ditto. :)

angillyon Ask HN: Massive vulnerability on Twitter?

conan is following me too.

wow.

angillyon Say the unsayable: countries get the HIV epidemics they deserve

I just want to point out this has (virtually? completely?) nothing to do with "hackers" -- and that's a good thing. It's nice to have a little variety on Hacker News from time to time. Thanks for posting this.

angillyon How Google tracks clicks for backpropagation

Bingo. Explained it a bit more in a comment: http://ryanangilly.com/post/355271652/how-google-tracks-clic...

angillyon Ruby statement modifiers behave differently than conditional statements

Can a bug be by design? :)

angillyon Ruby statement modifiers behave differently than conditional statements

No, it's using unless like I intended. But your example also demonstrates the weird behavior. As a few people have pointed out here and over in the post comments, the issue at hand isn't so much about statement modifiers as it is about how Ruby 'defines' local variables.

Take this for example:

  ra:~$ irb
  a = irb(main):001:0> a = b
  NameError: undefined local variable or method `b' for main:Object
  	from (irb):1
  irb(main):002:0> defined? a
  => "local-variable"
  irb(main):003:0>

It just so happens that using statement modifiers in the way I tried using them brings this behavior to light.

angillyon Ruby statement modifiers behave differently than conditional statements

whoa. didn't see that coming.

angillyon Ruby statement modifiers behave differently than conditional statements

interesting. in ruby:

  ra:~$ irb
  irb(main):001:0> defined? a
  => nil
  irb(main):002:0> defined? b
  => nil
  irb(main):003:0> a = b
  NameError: undefined local variable or method `b' for   main:Object
  	from (irb):3
  irb(main):004:0> a
  => nil
  irb(main):005:0> b
  NameError: undefined local variable or method `b' for   main:Object
  	from (irb):5
  irb(main):006:0> defined? a
  => "local-variable"
  irb(main):007:0>

'a' gets defined.

angillyon Ruby statement modifiers behave differently than conditional statements

That makes sense, but I've never seen statement modifiers defined that way. Every explanation I've ever seen, the pickaxe included, seems to outright state, or at least imply, the former.