thmcmahon

Definitely a thing growing up in central Victoria in the 80s/90s.

It's mentioned in the abstract: 'We deal with the potential endogeneity of the decision of how many hours to work by using the instrumental variable estimation technique.'

Essentially they use 'instruments' which are just other variables to control for this issue. Page 7 has the variables that they're using.

How'd you go with wrapping the websocket client in R? I've been putting together an R client and am stuck on how to do the websocket given the lack of R websocket libraries.

Not sure that you'd want to plant a bunch of European trees to replace native Australian forests.

I also found the r programming class to be super useful.

This is essentially how the 457 visa works in Australia. It's uncapped but you have to pay a 'market salary rate', which is either the salary of an equivalent worker in the firm, or of an equivalent worker In the industry.

This is the same economic problem that affects basic research. Open source software is a 'public good' - its usefulness is not diminished when it is used by others, and you can't prevent others from using it.

The longstanding solution to this problem is government support. This might not be a sexy solution on HN, but it is the obvious one.

Yep great article. As a beginner programmer I find functional more intuitive than OOP, there just seems to be less abstract concepts and boilerplate.

If you don't want to do it anymore just charge more. Would you be willing to do it at double the price?

The problem with cabs is the information asymmetry. You dot know before you're getting in how good their knowledge is, this means that knowledgeable drivers can't charge more and you get a 'market of lemons'. This is a classic form of market failure, and is a strong case for regulation.

Or just use snoozing (I use mailbox) and this problem is solved. I could not go back to using a mail client that doesn't have this feature.

From the preface:

Since this book is meant to provide practical advice, I think it makes sense to write with the assumption of Python 2. Specifically, I’ll be writing the book with Python 2.7 in mind. Future updates may very well change this to evolve with the Flask community, but for now 2.7 is where we stand.

I'm frustrated too, that's why we're working hard to win the next election.