jbrains @ jbrains @sh.itjust.works

Posts

2

Comments

503

Joined

2 yr. ago

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.

Best way block kick: no be there.

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.

Les Oulhamr fuyaient dans la nuit épouvantable. Fous de souffrance et de fatigue, tout leur semblait vain devant la calamité suprême: le Feu était mort.

Are there no prisons?

Are there no workhouses?

Plausible is more like conceivable.

It's possible that when I slam my hand on the table, it will go through the table, but it's not plausible. We can't imagine it actually happening, even though we know it can.

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. 🤷

You don't mess with the Zohran.

Visidata, maybe.

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.

Watching the fire in the hearth, no?

Icelandic: very very far top left.

The whole notion of "deserve" here is nothing more than a silly story we tell ourselves because other people teach us to believe it. It's real, but you can change it. So maybe try changing it.

Instead of "I deserve a boyfriend" or "I don't deserve a boyfriend", try thinking "This is just a dumb story. It doesn't mean anything. I either have a boyfriend or I don't. That's it." Maybe it changes something in you. Maybe it doesn't. Maybe it takes time and many repetitions. It doesn't cost much to try.

Peace.

"Sorry, I can't help you." Why? Because sometimes I hand out random favors, but not today to you.

"summation" is also related to summary. All these words are related to reducing a collection of things to a single thing. A sum reduces a collection of numbers to its total. A summary reduces a collection of thoughts to its essence. A summation is effectively a synonym for a summary.

The word multiplication describes the operation applied to each pair of numbers. The word production would refer to the act of multiplying an arbitrary collection of numbers. Just as it would be for addition and summation.

It would fit the pattern.

It looks like Russian uppercase and lowercase to me.