The one-eyed cat has updated the latest Jujutsu Kaisen information. I really don't know how to comment on it. Adding a setting to force Gojo out.
It's not that I can't accept Gojo being taken out, I just can't accept Gojo leaving in this way!!! The previous chapter was going well, with a cool combo, but in the next chapter, it just abruptly ends??? Can't the one-eyed cat put more effort into developing Gojo's character? It feels so perfunctory.
But if you calm down and look at it, there are actually quite a few details in this chapter. First, there is the consistent theme of "a sorcerer will not have a death without regrets." Gojo intentionally mentions it, asking why he doesn't have any regrets. And why say goodbye to those dead people? Aren't you a dying person yourself, Gojo? What does it mean for Nanami to face south and Gojo to face north?
Personally, I think the one-eyed cat is playing with the audience again. Gojo was able to recover from being stabbed in the head so many times when he awakened, so it's really unreasonable for him to be defeated by such a strike.
I saw Kaiyi recommend some input methods and suddenly saw a small and beautiful input method. As a purist when it comes to input methods, I was convinced and decided to try using the WeChat input method starting today. As for why I was easily convinced...
First of all, I really like to put spaces between letters and numbers... I think it looks clearer that way. This feature is really convenient.
Secondly, I have been troubled by the native input method's word library for a long time. I always feel like when I'm using the macOS input method, I have to search for words for a long time, which is very annoying.
So, I'll give this small and beautiful input method a chance and see how it performs. The double pinyin player is ready to fight!
The WeChat input method team really understands the product. At least I haven't seen these features in other input methods.
— Kaiyi (@Kaiyi42) September 18, 2023
But I still don't understand the use case of "lightly press the / key to input" in Chinese mode. https://t.co/e7kHVIRZOE pic.twitter.com/NHBCTF1sLK
When I was at work, my project manager got really angry, but it really had nothing to do with me.
I know her well, and she's usually pretty gentle, so I don't know what happened. Of course, I still had to go put out the fire.
While I was trying to fix things, I reported all the problems to her and explained the solutions. But then, she habitually said:
"Did so-and-so make these changes? It looks like he wrote this, right? Wasn't it something he did before?"
I was shocked. The code on my screenshot, the blame on the left side, all had my name on it. Why would she suspect another colleague?
After explaining that this bug was an ancient bug and fixing it, I went to find out what the other colleague had been doing.
Oh my... three accidents in three days... constantly fixing problems... I haven't been working on this project for a long time, it's just him maintaining it, and it's really a disaster every day.
Seeing other people's predicaments, of course, I have to reflect on myself.
For example, after going live, the project manager asked him to test the simple jump function to see if it was working properly. He went to test the jump function in his own feature, not the login jump.
As a result, after going live, the login function had a problem. The implementation logic of cookies was incorrect, causing users to be unable to log in. The project manager was furious: "Didn't I ask you to click it before going live? Didn't you say you clicked it and there was no problem? Did you click it or not? Can't you understand what I'm saying? Did I ask you to click the jump function in your feature?"
The problem actually lies in "ambiguity."
The project manager is concerned about whether the functionality is stable and whether the project is running smoothly. When we release a new version, the most important things are:
- Whether there are any errors as soon as the website is accessed (meaning there shouldn't be any obvious errors after going live).
- Whether the current live functionality is working properly.
If we think from the project manager's perspective and consider what "jump" means, I would never come to the conclusion that "she wants me to test the jump function in my feature."
This seems to contradict the second point, but we need to realize that the project manager doesn't care about all the technical details like we do. She probably wouldn't specifically emphasize testing the "jump" function in today's live features! After all, it's not her implementation, so why would she think of testing that?
The problem lies here. The answer varies depending on who is listening to the sentence. If a sentence has two meanings, it must be made unambiguous! He should have thought about this and asked, "What jump should I test? The login jump or the jump in my feature?"
Of course... I wouldn't ask such a question. When I go live, I usually log in and use the system in the normal way, and only when everything is working properly do I leave work... This process definitely involves login jumps, so my approach can also avoid encountering the same problem as him.
After persisting for two days, I'm now riding my bike home after work to get some exercise...
I don't know if it's just psychological, but after exercising these two days, I don't feel as emo anymore, and I have a bit more energy at work. It feels like things are getting back on track.
I'm currently working on solving the problem of easily lying on the chair and playing with my phone when I get home. I later realized that I can install a waterproof phone case and stand in the bathroom. I can watch videos while taking a shower...
It's amazing, but when I did it today, I felt great. Taking a shower was comfortable, and I could watch videos. After I finished, I could put it down. It's really nice.
End. Let's just stop here.