Ai

Using AI too much, we start thinking of AI for everything – often, learning new developments is more reliable with search engines plus official project documentation. Hong Kong stocks entered on the dip, encountered a pullback, and then just randomly traded, resulting in basic losses. Strategy Trading Not necessarily to actually practice and make money, but rather to improve my own abilities through learning. I don’t believe in these trading indicators; I mostly trust the national fortune (luck) and investing in broad market indices via a buy-and-hold strategy.

Currently, no large model stands out as particularly superior; each company has its own strengths and preferred use cases. Technical Documentation For feeding code or asking IT technical questions: ChatGPT and Gemini Write Code Gather requirements and request code modifications: Claude

AI has been integrated into daily development workflows, and recent investments have shifted focus from external funds to internal stocks and ETFs. Open Source Projects Project Log Last week, I was bored and tried to obtain GitHub badges, starting to use the Issue module. Previously, when writing code, I always wanted to find a place to record the content of each AI modification, but creating a separate document to record it felt disorganized.

Cultural Propagation: Its ideological influence, subtle and pervasive. AI Programming: Not performing software design, resulting in a lot of rework. Cultural Propagation Initially, the project only supported English, Japanese, and Korean. Thinking it was just AI translation, we wondered if supporting more languages wouldn’t be a good idea. So, French, Russian, and Hindi were added. At this point, no problems were detected; when the program executed translations, formatting issues arose due to historical code problems, requiring re-translation of archived articles.

The initial design of the blog translation project was overly complex – first parsing Markdown format, then using placeholders to protect the content, and finally sending it to a large model for translation. This was entirely unnecessary; large models inherently possess the ability to recognize Markdown syntax and can directly process the original content while maintaining formatting during translation. Our work shifted from debugging code to debugging the prompting of the model.

For many years, I’ve focused on backend development, and recently started to explore AI programming while dipping my toes into some frontend-related content. However, during this period of tinkering, I gradually realized I was falling back into an old habit – being dazzled by shiny new things. I constantly try to use AI to create a frontend interface, but in reality, these attempts haven’t provided much practical benefit for my current work and are actually wasting my energy.

This site is developed using Hugo, but I’ve always used Chinese titles, which results in less friendly generated article links. In simpler terms, when shared, they don’t look as good because the Chinese characters are escaped into formats like %E4%BD%A0%E5%A5%BD within the links. While you can solve this by setting a slug, it’s tedious to do manually every time. Therefore, I decided to try using Claude4 to develop a translation assistant that automatically converts Chinese titles to English slugs and adds hyperlinks within the articles.

Since we’ve established “AI Inspiration Collision Forum,” there’s been a lot of random content being created, with people experimenting with AI to record and publish things, but thoughtful reflection is becoming increasingly scarce. Moving forward, it would be beneficial to slightly control the output of this section and consolidate it into a