Should be “wið”, no? 😉

I have settled into this pattern:

1. Name expands as I understand better the structural role of a thing. Duplication in names begins to become easier to spot.
2. Removing duplication in names means introducing helpful structures, resulting in shortening names again, particularly as the intent/purpose of thing becomes clearer.

Long names stay unnecessarily long when we don’t notice the patterns that suggest the missing structures.

The more examples of this kind of thing, the better!

(And my preferred name for that is rolesByEmployee. In general, “values by key”.)

Low feels more numb than dark. More like being on pause than everything is terrible. More “I’ll try again later” and less “this is never going to get better”.

I don’t remember the transition. I can’t tell you how long it took. I was only on antidepressant medication for about 18 months.

Peace.

I use Spectacle for taking screenshots and I’ve enjoyed using it for several years. After that, I’d crop it in any image editor that has a freehand selector tool. Gimp would be the first thing I tried, but I’m sure you could find something easily enough.

Good news, relatively speaking.

I’ve been where you are. Most important: don’t let yourself start to take responsibility for managerial decisions. If they want you to stand in the corner on your head and cluck like a chicken, it’s their money. 🤷 Don’t let that change how you see yourself as a programmer.

And roll your eyes in private.

Is this a problem for you or merely annoying? I mean the difference between you being blamed for their poor results and you merely being inconvenienced by doing extra work.

You might need to train yourself to accept the situation as it is and hope for someone in authority to make things better. It’s not easy, but this might be a good chance for you to build that skill. 🤷

Can you talk openly with your manager about this situation? Would it be helpful to you to propose to your manager that you help that group? Maybe your manager would appreciate your attempt at leadership.

Good luck.

This is the kind of paradox that leads us (I mean humans more generally) to look for some fundamental assumption we’re making about time that will turn out to be wrong. I assume that’s true although I wonder whether it’s literally impossible for us to even imagine how time “truly” works, let alone measure it.

I was a kak user for several years and am giving hx an honest try this year. So far, I’m quite happy.

(and yes, I’ve been both an emacs and vim user.)

hx

I meditate. Very occasionally, I still am not ready to sleep, but it still helps me to do that.

I listen to a podcast, if nothing else works.

Mostly, I don’t worry about not sleeping. It took me years to feel OK with not sleeping, but here I am.

Peace.

Dumb question: do you have a key on your keyboard that disables the microphone? I don’t have my laptop in front of me, but I know there’s a key that disables the trackpad and another that disables the camera. I realized that I’d accidentally hit those by going through something similar to this.

Good luck.

Kat.

Are there no prisons?

Are there no workhouses?

I believe the dumbness of scams conforms to the Archimedean property.

Best Practices thinking considered harmful. 🤷

I like test names that are full sentences. Doing this for its own sake is unnecessary. It’s probably wise to practise this for a year, then decide when you still need it.

For me, quite often, a combination of the test group name (often naming a behavior) and test function name (often naming a special case of that behavior) suffices, even though it is not a full sentence. (Example: test class SellOneItem, test method productNotFound. Is this not clear enough?)

Test function names that merely repeatedly duplicate details (“conversion should…” to start 12 test names) indicate a test group trying to emerge (“Conversion Tests”). Insisting on full sentences for its own sake often either masks this risk (and delays helpful refactoring) or represents redundancy (merely reiterating what has been helpfully refactored).

I have found this attention to full sentence names most helpful for tests whose audience is not programmers, since those folks are not accustomed to common source code conventions and patterns. For Programmer Tests, I think “should” turns this helpful advice into a risky overstatement.

Pump and dump of penny stock. 🤷

Everyone has to start somewhere.

I try the latest episode, then if I like it, I start from the beginning, unless it’s a current events podcast.

Icelandic: very very far top left.

Having insufficiently pale skin.