For a Go service? Sure, that's easy and makes a ton of sense.
1,190 karma · joined October 9, 2011
For a Go service? Sure, that's easy and makes a ton of sense.
I think this might be a typo - we're observing X but want Y, or some similar variation. In any case, there's a bug.
Is this hypothetical guy always writing 100% correct code?
Could you say more about this? Were they technical or behavioral interviews?
How frequently do people interview in a language other than their "main" one(s)?
> - Didn't have standardized questions, which is hugely problematic (some bugs are 2 orders of magnitude harder than others)
How do you know they're not standardized? (You say in another comment where it was, and indeed that's where the blog post author works. It's described as a pretty standardized process by my reading of it.) You can pass the interview without actually solving the bug, but I get it's easier to blame the problem than admit you struggled with it.
Anki's data model is rather strange, which partly relates to its flexibility but has some unexpected downsides and trap-doors. I would love a slightly more opinionated SRS tool! (Maybe with a bit more UI polish, rather than rewriting the backend in Rust)
(Granted, most people here with an SSN should be older than that.)
In my read of the Bible quote, it's not really referring to a person as "it" in the same way.
2. Grammatical gender has nothing to do with the "vibes" of an inanimate object - it's quite arbitrary, really. The problem you're associating here is much more with gender in humans, but we were talking about the grammatical construct applied to objects (like a chair as the grandparent mentioned).
Huh? Nothing in a software project will ever be perfect – code or docs — so this doesn't seem like a reasonable expectation. It's always a process of gradual improvement, and that can be true for a change like this too.
(You seem perfectly happy distinguishing between animate/inanimate nouns and choosing "it" or "he/she/they" -- that's a difference not all languages make, but should we get rid of it in English too?)
As a product, it seems fine. I'm not entirely sure it's an area AWS really needed to have a competitor, but now that they do, /shrug
These days, I'm not sure books are much different from any other good.
I had a YAML file using `some_property_name`, which was turned into `SomePropertyName`, and it's a small annoyance. It's not a huge deal, but it adds friction where some languages have none. (Or alternately, getting reordered in a separate system like `property_name_some`.)