Tuesday, May 19th
Sunday, May 17th
Fortune Cookies:
- "Your contributions to your community can be felt near and far."
- "You are open and honest when it comes to matters of the heart."
Saturday, May 16th
Fortune Cookies
- "Do not be impulsive where money is concerned."
Friday, May 15th
I have been reviewing how to use WebAssembly in my web projects and learning HMAC concepts and designs of Rust crypto-related traits and considerations. I'm grateful that I can utilize the open-sourced codes and LLM to accelerate my learning and information-finding process. I'm grateful that I found my previous design also used the SHA-3 algorithm family.
Fortune Cookies
- "Reward yourself with a much-deserved gift."
- "A thrilling time is in your immediate future."
- "The excitement of new romance will lift your spirits."
- "Worrying less will brighten your outlook."
- "Your life will be peaceful and fulfilling."
- "Your magnetic personality will draw people to you."
- "You have a kind and generous heart."
- "Open your heart."
- "Treasure your family and friends."
- "Set your sights high."
Thursday, May 14th
I have been mainly reviewing the Hash-based Message-Authentication-Code procedures and the bytes "IO" interface design. I have also been reviewing Rust wasm-binding generation steps.
I'm grateful that I had some time to sweep the floor. I'm grateful that the label of the canned tomato is made of paper and is fairly easy to peel off. I'm grateful that the can-opening process was smooth. I'm grateful that the cashier of the local restaurant remembered that I don't need plastic bags (I hope this request isn't too much trouble for them). I'm grateful for the chance to learn the mechanisms of SHA-3 and HMAC.
Wednesday, May 13th
Bytes Codec
- h15min58: Building tools that are both powerful and have a clean interface is somewhat difficult. I'm trying to build a codec that converts between different byte "representations", e.g., hexadecimal.
Tuesday, May 12th
Bytes Codec
-
h16min00: One thing I have been focusing on is how to make the code gadgets reusable, both as a wholesome application and as a component for other applications. I'm planning to add a collapsible piece of description or instruction.
-
h16min04: I have received a grade release email about a previous assignment. I decided to first view my grade and read the email next, but a thought popped into my mind: "What if I got a bad grade and I still need to read the email about making a regrade request?" I loaded the webpage and opened the file. It says I only got 2.5/30 for the third question. "Well, I guess I indeed need to read the regrade request submission email after all." And then, I read the email, and it says the 2.2.3 is omitted. This is indeed a somewhat emotional rollercoaster.
Monday, May 11th
Random
While reviewing course materials for authorization and authentication, I feel like there is a significant gap between users and designers in such a context. Users are expected to be somewhat less aware and less careful about choosing strong passwords and avoiding reuse. It might indeed be a sad truth. I have had this thought for a long time: if a strait separating the mainland and the island can divide the physical characteristics of birds into distinct species, the previously mentioned "virtual environment" might also have such power. People might want to be more careful.
Saturday, May 2nd
One thing I have been focusing on is investigating why the performance of my visualization webpages is starting to decay after some time. I have examined the memory snapshots and framerates, calculating the average time between frame rendering. I noticed that indeed the framerate dropped slowly as time passed. I have also chatted with LLMs, but I didn't find any "memory leaking" caused by forgetting to "dispose" or creating small objects. At the end, I tried to run the same webpage on other browsers, and the issue didn't recur. I guess there might be some problems within Firefox.
But I indeed found that the frequent "element bounding box rectangle" seems to be causing extra unnecessary computations. I redesigned the previous design to only update the "box" information after "scrolling" or "resizing" events. I have also extracted event names like "dbclick" into constants named at the top of the file. I feel that might make the file cleaner.