@kotaro@kotaro.me
I'm not very familiar with the political situation in the US, but dressing like ICE is not something a respectable adult would do. This isn't Counter-Strike cosplay.
Heβs just an ordinary office worker living in Tokyo, Japan.
I'm not very familiar with the political situation in the US, but dressing like ICE is not something a respectable adult would do. This isn't Counter-Strike cosplay.
I'm Japanese, so I don't know much about the political situation in the US, but aren't ICE agents technically civil servants?
Even though they're public officials, isn't it lame how they dress like some kind of gang or terrorist group and act all tough?
The powers that be of the night are always drawn to new things and to youth, wanting to assimilate with them.
Just like Epstein.
But for some reason, I've recently started to feel revulsion towards it.
My junior colleague, the woman who leads my team, is reading self-help books and earnestly trying to figure out how to act to gain influence in the male-dominated business world.
She keeps recommending the book to us.
In Japan, women's advancement in society has only just begun.
Although, the Prime Minister, the most powerful person in the country, is now a woman.
It's because the business community feels like it's dotted with groups of women who seem to have unconsciously internalized toxic masculinity.
Today, I finally learned what asynchronous processing is all about through the firsthand experience of failure.
Now I have a story to tell. I was lucky.
I can't thank that back-end engineer enough.
I learned on MDN that event listeners themselves are asynchronous, so I didn't expect the callback to be synchronous.
However, that's something I would have realized if I had just stopped to think about it for a moment.
The reason I can usually treat an event listener's callback as if it were synchronous without giving it a second thought is that by default, it's a synchronous function.
I was under the misconception that anything with an arrow syntax like => was an asynchronous process.
I was so foolish today. It all happened in just a few hours, but itβs already become an embarrassing memory.
In JavaScript, when youβre inside an async function and want to store JSON received from a server, you assign it like this: const data = await response.json(). You do this because response.json() returns a Promise, and you canβt get the actual data without using await.
I didnβt forget that part. In fact, I was so careful that I even kept using await on the data after storing it in a variable, like selectedMonsterData = await data. I thought I had a solid grasp of JavaScript fundamentals.
But when I called the async function that contains fetch from a different buttonβs click event listener, I forgot to use await. To be precise, I forgot how to declare an event listener as async. So I never even thought to add await before calling the function that runs fetch.
Because of that, the front end didnβt wait for the necessary data after I clicked the button to send a POST request to the server, and that caused a null error.
Overconfidence can delay projects. My mistake today only cost me a day, but it made me reflect deeply.
AI can be easily manipulated by messages posted on the web.
That's why this time, I thought about the dangers of prompt injection and decided against installing Firefox AI Window.
A typical scenario where the pain occurs is when I'm lying in bed, using my smartphone with both hands while my left arm is folded underneath me.
When I do this, I put my weight on my folded left arm, and I feel the same kind of pain as when I stretch.
I'm so lazy and have a habit of using my smartphone while lying in bed, and it feels like it's putting strain on my arm.
So, maybe I'm on the fediverse too much.
WHAT IS CELL PHONE ELBOW?https://osrphysicaltherapy.com/what-is-cell-phone-elbow/