8 karma · joined December 25, 2015
Next, expansion. I expect expansion is a tricky proposition because it means dilution, which is both a hard sell and a risk to the workers.
We're a nimble team building brand new services in the rentals space designed to make the process of renting your home easier for renters and landlords. Or, demystifying as described by the Verge: https://www.theverge.com/2018/7/31/17634762/zillow-apartment.... We develop products to delight our users, and I think the numbers speak for themselves: 56 million visits over the last 6 months as reported by SimilarWeb.
Our stack includes Java, MySQL, Node and React. If you're interested in trying something new, apply here: https://www.zillow.com/careers/jobs/trulia/openings/?j=P1218...
Make sure to check out our reviews on Glassdoor: https://www.glassdoor.com/Reviews/Trulia-Reviews-E226815.htm More about what it's like to work here at: https://on.trulia.com/2yIpjit
Ultima IV: The Quest of the Avatar taught me about an alternative set of ethics. While too simple for real use, it was aspirational enough to get me thinking about alternatives to what I'd been taught. Ultima VI: The False Prophet led me to acknowledge good and evil typically are informed by individual (or group) point of view. Ultima VII: The Black Gate taught me to look at religion critically, to see that beyond the surface message there are often other messages that go unnoticed.
There's no question that Garriott tapped into something deep inside me that is still coming out to this day.
It's reasonable to think that in time much of it will get paid back but there are other kinds of investments that would perform better, and hence the economy would have been better off had these loans not been made and the money were spent on something else.
Also to your comment about sabbaticals and other less productive activities, is that really the common case? I believe that underemployment via career choices and local demand for skills would be more common.
This is a case where metaprogramming for tests came in handy.
I had a bug recently that involved someone making a change that violated an invariant property of a class. To codify this invariant, I was tempted to do what you did, to make a list of symbols to feed into my test to ensure the invariant was obeyed. However this bug was caused precisely by someone adding a new symbol, a method, that didn't obey this property. The test using this design wouldn't catch this failure. I instead opted to do some introspection (it's Python, so it was dead simple) on the class to ensure all of its methods obeyed this invariant. It took a little extra time to implement but in the end it worked.