I had a question / concern / complaint about my family's @Google domain account. I contacted support. I was transferred SEVEN times before finally getting a "nobody is available to help you" message. SEVEN TIMES! "I apologize for your inconvenience. I will transfer you!" AHHHH
Sometimes I notice that not even Google has their UI act together in terms of two features conflicting. It really _is_ complicated. :)
Asked GPT why "You are a teacher" is important. Surprised to get a response which will require research before I can get meaning. Paraphrasing: "it activates submanifolds, shifting which latent concepts are relevant in the embedding space." Oh. I ... see? 🤷♀️👨💻👨🔬👨🏫
I want to post about something that seems too nerdy for LinkedIn so I'm back here. Still refuse to call it anything other than Twitter. Like some resident of NYC who is angry that buildings change name when they are bought.
I have been mentoring a junior developer. This developer is not in my team or company. It is delightful to be able to educate and encourage. And it's clear I'm proving value. 30 minutes every other week
I have just reached the pinnacle of my career. I just created a temp file called html.html. Then...
html = File.read('html.html')
I am a 10x dev.
People are "so* against classes in JavaScript but they work really well in Ruby. I'm wondering if this is a cultural issue or due to javascript classes being not-fully-baked.
Recently I have learned that one of the most important skills and qualities that you need to intentionally keep sharp as a developer and a human is CURIOSITY.
It can be easy to lose on accident. Particularly when you think you know the answers.
When I'm working in JS, I really miss Ruby. Paticulaly: mixins, array conveniences (yes, there's _some_ progress with enumerables), and, to a lesser extent, blocks (I understand arrow functions are first-class and I see that value. But blocks are just a little more intuitive.)
I'm working on a new talk on engineering and product management maturity. Tell me your worst and best experiences with engineering getting requirements from a product or upper-management team!
Here's my most recent argument against test setup outside the test. I have let statements in a test that depend on others that depend on others that depend on others. I need to change one thing but not break all the tests. Now I have technical debt **in my tests**. Not great.
In 2006 I thought it was silly that Rails had an /app folder; it had three or four children and siblings test, spec, public, and a few others. Why not just put models and controllers and such in the root? Now the root is so crowded I'm thrilled! Thanks @dhh
Just a reminder that 'else' and 'elsif' statements are idiomatic Ruby. Rubocop is apparently against them for some reason.
Wait, the C is soft in decided but hard in decoded? It's just off by one vowel... #englishIsWeird
