Reddit -> Beehaw until I decided I didn’t like older versions of Lemmy (though it seems most things I didn’t like are better now) -> kbin.social (died) -> kbin.run (died) -> fedia.

Japan-based backend software dev.

  • 0 Posts
  • 195 Comments
Joined 2 months ago
cake
Cake day: August 14th, 2024

help-circle



  • Cool! Do you follow Japanese spaceflight at all?

    Not really. I tried interviewing as a dev on a satellite company’s site, but apparently they require that one be a citizen for various reasons. I did want to go see a launch when I first moved to Japan, but it worked out to be rather difficult and doubly so as I had no driving license at the time. I might have to look into it again as that would be pretty neat.

    Doesn’t that mean chicken or bird or something? I

    tori does mean bird, yes :)

    How do people handle the “ple”?

    プリーズ (pu ri (long vowel marker) zu). Final ‘u’ gets devoiced in most cases and, anecdotally, many who say the word a lot devoice the first one as well. So pureez with the quality of the u varying from non-existent to schwa to normal (kinda like oo in moon but shorter)



  • I live in Japan so it’s on my mind. Tri would end up like ‘tori’ or ‘turi’ though a lot of speakers might reduce the o a bit in the former and the ‘u’ might devoice in the latter being closer to “t’ri”. “Triple” is a word that is used (mostly for baseball, I think) and some people do reduce the inserted vowel quite a lot.

    I wouldn’t use ‘san’ because it doesn’t make sense outside of Japan (and, I suppose, close enough for Sinitic languages and those with loans from it). I went with ‘tri’ since it’s already a root meaning three (from Greek I think? I never remember which are Greek vs Latin).







  • I think experienced programmers may have a different route to a degree. A number of years in one language, for instance, including fairly complex production settings, etc. and having to transition to python for a new job or company or decision from someone higher up the food chain. I did it from a largely perl and PHP background for both Rust (a tiny bit of experience before, but not a super complex environment) and Go (zero to prod in a few months dropping in rewritten portions of the former PHP monolith). I can talk about memory usage, race conditions, etc. but would be completely screwed with anything internal to python or its quirks.