zachsnow | 6 years ago | on: A humble guide to database schema design
zachsnow's comments
zachsnow | 6 years ago | on: A humble guide to database schema design
When paying customers / clients want to sort by last name, because “that’s how we do things”, then you sort by last name. So it’s only important when you want to make money.
Edit to add: your customers also don’t care that someone somewhere has 6 first names and no last name. “This wasn’t a problem with our old software.”
zachsnow | 6 years ago | on: Amtrak Could Turn a Profit for the First Time
zachsnow | 6 years ago | on: Trucking 'bloodbath': 4,500 truck drivers lost jobs in August
zachsnow | 6 years ago | on: America’s urban rebirth is missing actual births
zachsnow | 6 years ago | on: America’s urban rebirth is missing actual births
I think the city and the country and everywhere in between can be a wonderful or terrible place, but I would hesitate to say that any one place is right or wrong for any one person.
zachsnow | 6 years ago | on: How much money can you make on Mechanical Turk?
I imagine just about nothing is 100% fun 100% of the time. If many parts of your work are fun, it’s fair to say your work is fun. If you’d rather be doing something else, you could try that, too. Maybe you’d like it more.
zachsnow | 6 years ago | on: Ask HN: How do you deal with professional envy?
zachsnow | 6 years ago | on: Pacman in 512 bytes of x86 boot sector machine code
zachsnow | 6 years ago | on: Aphantasia
zachsnow | 6 years ago | on: San Francisco proposes “IPO tax” on eve of Uber offering
zachsnow | 6 years ago | on: Ask HN: When have you taken a decision in code outside your domain of expertise?
Yes! But there will never be a complete set of requirements — indeed if you think the requirements are complete, you spent too much time on them and you aren’t looking at the problem carefully enough.
There’s a balance between calling for more complete requirements and being able to work with less complete requirements. The more you can correctly choose to do the latter, the more you “hone this skill”, the more effective you can often be.
(As a bonus, when you do call for more complete requirements, in my experience people will be more open to doing that work. They know you wouldn’t ask if you didn’t “really need it”.)
zachsnow | 6 years ago | on: It is perfectly OK to only code at work, you can have a life too
That’s dumb. Of course you can “have a life”, regardless of whether your hobbies include something you also get paid for. Denigrating folks as not having a “life” for this reason, even as a rhetorical device, is dumb.
zachsnow | 6 years ago | on: Hackers went undetected in Citrix’s internal network for six months
zachsnow | 7 years ago | on: Redis Labs Raises a $60M Series E Round
It’s never just the product, no matter how much we builder types might like.
(No idea whether 60M is the right number for the rest though.)
zachsnow | 7 years ago | on: Why the “Self-Made” Success Story Is a Myth
As far as I understand it, most (VC-backed, tech) companies that raise millions of dollars manage to turn the money into failure.
zachsnow | 7 years ago | on: Ask HN: What's it like to work in the same company for decades?
zachsnow | 7 years ago | on: Show HN: Twiverse – Find Twitter users and get more followers
zachsnow | 7 years ago | on: What Minimum-Wage Foes Got Wrong About Seattle
Obviously in an particular case, who knows? But in general I think the expectation is that the market will decide.
zachsnow | 7 years ago | on: Identity Diversification: The Case for a Well-Balanced Sense of Self
What I found was an anecdote followed by a few hypotheticals. “What if you spend all your time sportsing and then you get hurt?” Really a minimal treatment of the idea unfortunately.
The point is that while sorting by last name (say) might not seem important to an engineer, and requiring a last name might seem outright stupid to a person filling in a form, nevertheless it is often an important requirement. Frequently folks will observe some "stupid" form, and link to some "falsehoods engineers believe about X" document, suggesting that engineering "got it wrong", when in fact they have simply misunderstood who the software is actually for.