veneratio

We use YAML, now JSON, for some of our flexibly defined data. Porting it to JSONB in Rails was filled with some interesting lessons.

A bit of an over the top title, but (disclaimer: I work at Karat) the main thesis is really interesting. Essentially, it's cool to be part of a new specialty (hiring) being born out of an industry I've worked in for a little while now (tech).

Google (as I've experienced it) is filled with normal, generally friendly folks. A few small jokes, but no cultural ousting. While I don't work in search (big company, many products), even the folks I know there recognize we need different tools for our job and sometimes Google search just isn't the way to go. I suspect if it were a more specialized company (say Tableau) then using a another company's tool for daily work might be frowned upon.

I also do this, but that's because I work at Google and got tired of explaining to coworkers why I don't usually like the results from our search engine! Also, "I duckduckgoed that" doesn't roll off of the tongue very well.

Tagging TODOs is really useful. I can always look at source control, but that's more effort than seeing a name or bug number. At Google our linters are actually configured to create errors for any TODO/FIXME that isn't immediately followed by a user id or bug number: e.g. TODO(12345) or TODO(myname). I thought it was a little annoying at first, but over time I've realized how much faster it is to have that additional context.

This is an awesome question. What sort of responses have you seen from this? Do most folks have a quick answer or do you get some thought? As an interviewer, I'm not sure I would ever expect a question like this.

Ah I thought I had seen this before.

I think the real place this device will shine is in "homely" environments: kitchens (music and getting questions answered while you cook?), study areas for your kids, maybe even hobby rooms. It's definitely a bit on the steep side, but knowing Amazon, I wouldn't be surprised if the $99 sticks around longer than a "limited time" and the $199 becomes a thing of the past early next year.

Pretty ugly.

I just started toying around with them recently, and I have the same feelings as you. In general, it seems like Derby's choice of using straight up npm makes it a bit more inter-orperable. Other than that I haven't dived in far enough.

My first brush with Node was in a class. We chose to try it for a game only about 5 months after Node's initial release. It was cool and fun to work with but ultimately a bit rough. After a year's break, I can now say I love Node. I'm glad your return was just as encouraging.

It took me a few paragraphs to gather that, but this just means it was really well done. I appreciated the "PS" components especially. I think they made the parody aspect most clear (other than the pop culture references).