I’m in the same boat, unsure if this is outdated. I left Airbnb five years ago and haven’t followed up to ask anyone what the current state of the tech is.
I’m not trying to follow the latest Ruby dustup and don’t have a stake in it but as an Airbnb alum I did find this part particularly identifiable:
“Yet, Ruby and Rails remain the default stack at Shopify, and the only reason for that is the CEO. Every Shopify employee knows that suggesting straying away from Ruby wouldn’t fly there. And I’m convinced that if it were anyone else at the helm, Shopify would have joined the long list of companies that attempted to migrate to something else and are now stuck with both a Ruby monolith and a ton of half-migrated micro-services in Java or Go.”
A website like this is not required. It's just nice to have. Somehow we've managed to use email without this website it for the decades that email has supported HTML.
Caniuse exists too, does that mean HTML and CSS are broken? Nah, it's just a useful resource to help people decide what tradeoffs to make.
Thanks, I know I could do it in the console or the original source. But I was referring to the fact that the sentence in the post says to convert it to a getter "either in the original source code or using a conditional breakpoint."
Under the section "Debugging Property Reads": how would you convert `{configOption: true}` to `{get configOption() { debugger; return true; }}` using a conditional breakpoint?
I know Ruby != Rails but the example wasn’t mine. It was from the paragraph I quoted from the post, which conflates the two.
It may be true in Python--I don’t use it much--but I know Ruby well. It was my primary language for 13 years, at multiple companies. I taught it to over a thousand engineers at Airbnb over the course of five years. I still disagree that it is common to use exceptions for control flow.
Maybe it’s a matter of the interpretation of the word “common.” ¯\_(ツ)_/¯
> In Ruby it's common to use exceptions for control flow.
I think this is just plain incorrect. The example given later in this paragraph is the Rails `update` method--but the approach used in all canonical Rails examples and generators is the non-exception version of `update`.
I've worked as an employee and as a contractor in Silicon Valley (never at Google). While it was nice to be treated like an employee by some companies, my attitude was that it's just understood that as a contractor I'm not as much a member of the team as the employees are, and I'm the first to be let go if the money gets tight. Those were the tradeoffs of the flexibility I got. If contractors are the same as employees, why even have a distinction?
I'm confused by this article. It says "New evidence adds to work showing people made these prints [in New Mexico] sometime between 21,000 and 23,000 years ago." It supposedly contradicts experts' belief for decades that "the first people in the Americas migrated from Siberia across the Bering Strait on a land bridge exposed during the last glacial maximum, sometime between 26,500 and 19,000 years ago.
This unexpectedly reminded me of what East Berlin looked like in 1988. It looked gray and dull compared to West Berlin. I've told this story for years without realizing that lack of outdoor advertising made the difference.
It took me ten years to get back into using an RSS reader. Over that time, I found individual blog posts to read via links from Twitter. And there were a few that I subscribed to over email. But now with the whole Twitter debacle, a month ago I looked around to find a good RSS reader and installed NetNewsWire. It's nice to be back.
Even if your old one does start to go bad, I discovered it can be more effective to repair than replace for a multifunction printer/scanner. My old Brother was on the fritz a year ago. After being shocked by prices for new ones, I found a printer repair shop across the Bay from me. They fixed it for much less than the price of a new one. And they told me to keep it as long as I can because it’s such a good piece of hardware.