Only scored 93... One of those, "yclept" I've never ever encountered before (as a native Australian English speaker) and only lucked out by way of elimination.
I think I've been following this subconsciously as LLM artifacts reached some threshold of pervasiveness across the work I do. If I can sense (maybe eventually I won't be able to because of how capable the technology becomes?) that what I'm reading is wholly regurgitated out by an LLM, I automatically care less and feel inclined to respond in kind by generating an artificial response in return.
The last impactful one on me was Bullshit Jobs by David Graeber.
Definitely disrupted my perspective on work and the monotonous, sometimes futile, insanity that some of us subject ourselves to in order to make a living.
1. Resume seeing the world. I haven't taken a trip abroad since the tail end of 2019.
2. Cultivate a mutual and meaningful friendship with someone. A non-existent social circle and approaching my fourth decade doesn't make this any easier.
I've had not one but two turbinate resections, each time with a different ENT. From memory, neither had even bothered to really stress some of the risks others have pointed out.
I think my quality of life improved rather substantially after the first I had. To my disappointment, it didn't last. This eventually prompted me to seek out another several years later. Again, some improvement, but this time that time window was even shorter.
I'm now at the point where I've given up and just learned to live with feeling of being completely blocked through one nostril. It's frustrating.
I find the feeling affects me most when sleeping (I've tried CPAP to get restful sleep without much success) and during heavy aerobic exercise (having to constantly blow out mucous build-up as I'm running).
> Notice subtle changes in behavior: the most useful hint here is when someone who used to be very vocal about an issue stops complaining.
This point resonated greatly with my own observations, both of myself and of other colleagues with each development team I've been part of.
I think another challenge is fostering a culture where everybody genuinely cares about the output that's delivered. Not everybody will. Some people are comfortable moving tickets from triage through to a resolved state day in, day out without caring whether this process or the output can be improved.
One of my previous stints was with a small team that was building a cloud-based payroll and HR platform for the Australian market (potentially going abroad as well). It definitely opened my eyes to how complicated award rules can be.
I also remember testing being a challenge, particularly when things like multiple backpays, accruals, or one off adjustments were involved.
There was also an integration API, but I didn't stick around long enough to see it evolve enough for widespread third-party adoption.
It looks like `.git/refs/remotes/origin/HEAD` doesn't exist, which might explain why a fresh clone results in a detached HEAD (i.e. Git should default to being on the branch referenced by this entry).
As for how you can end up in such a state on the remote, I'd actually be interested to know too.
Thank you for sharing your experiences and the YouTube channel recommendation.
I've been alternating between the interactive lessons on http://learnrussian.rt.com/ and "The New Penguin Russian Course". I've been enjoying the former a lot more because there's audio to accompany written content, which helps when I try to enunciate words. There are also tests, which helps me measure retention. The latter book feels more like dry reading to me, but coverage seems very comprehensive.
I haven't been learning for all that long, but the two things that have been regularly catching me out are:
- Knowing which "o" letters in the word are stressed, in order to pronounce it correctly (I default to reading them as "o" when they should instead be "a")
- Looking up new words in sentences is a bit harder because they often occur in conjugated forms (i.e. not only verbs, but nouns too)
D3 for work, and Russian out of pure (seemingly masochistic) interest.
I'm a native English speaker and Russian would be my fourth language. Perhaps I'm simply approaching the limits of my language ability, but the grammar rules with cases that I've learnt so far are doing my head in. It's very discouraging. I don't intend on becoming completely fluent, and so I'm trying to find shortcuts to be fuzzy about the volume of grammar rules to keep in mind.
Alas, I'm in a similar situation with my current stint and looking for an exit.
The most maddening part for me is to literally sit around helpless and unable to do any development because you need to wait for your IT support ticket to be looked at. Then having to explain to your manager why work is behind schedule.
However, idle time alone doesn't seem like strong enough reason to open discussion on changing IT policies.
> I don't know if I'll ever be able to master any language anymore
Even with just a handful of languages in my toolbox, I feel this way too. A mixture of unease and anxiety.
In addition to syntactic variations, I find that the notion of writing idiomatic code in a given language amounts to more thinking overhead which eats into productivity. I'd need to be programming in the same language over a long period of time for idiomatic code to come more naturally. Can't seem to just instantly switch like some talented folk out there.
I share the sentiment about the amazing scores that many JRPGs come with. They really do help with the immersion.
Of somewhat recent JRPGs, I found NieR:Automata to be a superb masterpiece, both in the musical compositions led by Keichii Okabe and the underlying themes explored within the game itself.
The battery on my (year old) Sony Z5C running LineageOS has recently decided to start failing. I had a Z3C for two years before it too decided to start failing on touch input (you'd think I'd learn my lesson by this point).
I lament the absence of compact Android phones with long-term security updates. Maybe it's time I just bite the bullet.
The explanations breaking down the constituents of hex codes reminded me of CSS colour module level 4 and how 4 (#rgba) and 8 (#rrggbbaa) digit codes might see support.
I wonder if there's still intuition for visualising colours when involving opacity in the mix.
I've gone through not one but two turbinate reduction surgeries myself. One when I was young and another several years ago. Alas, my quality of breathing now is still pretty abysmal. It's just gotten to the point where I've come to accept having to breathe through just one nostril all the time, as much as a nuisance it is. Frustrating to have spent all that energy and funds to land back at square one.
Also went and tried CPAP for a while, which didn't really help me with breathing for restful sleep.
Where I notice this most is probably during heavy exercise. Having to breathe through the mouth during intense aerobic exercise makes me hit my limit much faster.
Made the switch earlier this year. Webmail UI might seem clunky to some, but I use IMAP so non-issue for me. Easy to set up encryption and apparently they're powered sustainably too.
One deal breaker I know of is you can't map to your own custom domains. There's something in their FAQ which explains their rationale behind this.
I view code reviews as a good opportunity for learning but I've one particular grievance with them. Specifically, when I'm asked to code review a pull request that's alarmingly huge (i.e. touches more than a dozen files, +1000 LOC changes, etc).
I've never come up with a bullet-proof way to deal with this. The situation usually ends up with me providing a rubber stamp of approval and making some caveat commentary about "uncertainties" due to my inability to devote so much time to be rigorous. I feel bad every time I've got to do this.
The problem might be exacerbated at another level too. For features, stories might not be broken down enough.