288 karma · joined November 14, 2018
Intuitively, we often assume that the UUID of a person is his name (for some definition of name). Then when this changes all hell breaks loose because we are mutating an ID that has been shared to 3rd parties.
Some countries don't have a UUID for its citizens. Some countries don't even have a register of its citizens.
Even those countries that have a register AND a UUID for each citizen still often make the mistake of making it derived from the "name" (thinking for example of the Italian "Codice Fiscale"), which can obviously cause confusion if you then attempt to change your name.
This is very common in a lot of IT systems even when its not names. It's windowIds VS windowNames, it's username VS userId, email VS userId, primaryKey vs ID field etc.
The hill I'll die on is the preaching of never ever ever ever using a semantical id. Sure, they are handy (humans can reason better about those than about random strings), but DON'T MAKE THEM THE ID.
A handy test to avoid this pitfall is: if tomorrow every value that represent some id-like property (i.e. foreign keys in a db) in my system (string or numeric) was replaced by a unique 1-to-1 mapping to another set of random strings, would my system still make sense? A good ID-based system would survive this. One where there are assumptions like ID = name ++ email not so much (because name <-> aaa, email <-> bbb but name ++ email <-> ccc, violating the assumption)
Right now, London salaries are easily 2x to 3x Manchester's for Software devs (yeah I know the average data is only 30% higher but you need to compare the top vs the top, not the aggregated data). As a Junior dev moving from Hertfordshire (which is 30mins from London....) to London meant my salary instantly doubled, while living cost only maybe increased 50% if we are conservative. That's going to take a long time to offset.
The threshold for "fever" as reported on all old mercury-based thermometers was exactly 37C and that was referring to the "inside" termperature.
So 36.6 outside would definitely be considered onset of mild fever, not normal. 36.6 inside would be a-ok
- This is a different game than your day to day. Those two being easy stuff means nothing if you never played the game.
- Now you moved a "unknown unknown" to the category of "known unknowns". You know you have no competence in this category, and if you wish to improve in it you can do so. Or not, it's your choice. Before, you didn't have the choice. So that's good!
- It's not about the language. You can solve these in Java, C, Assembly, Haskell. Most training website for interview questions (like these) allow you to implement in any of the major languages. If you want to play the game and get better, I recommend Hackerrank (for structure) and TopcoderArena (for variety, since they give you a bit more fuzzy spec and you also need to identify the algo for the issue at hand). The latter is slow as balls though, and offers no solution (except the best submitted, which may be cryptic).
- This stuff takes time, and if you want to learn about things you'll have to book up. Cormen's "Intro to algorithms" or Skiena's Manual are the goto texts. They are thick. Take your time. Persevere.