2025-01-12 Clean Code, Log, Comments, and Musings

Let's look at the world.

Economy

• Is the end of interest rate cuts this year? Growing pessimism / Will the worst-ever wildfire cause a chain of bankruptcies? / The stocks Trump is pushing that turned his enemies into loyalists / The real secret of the ant that made a 350-fold profit from long-term investment
  • US interest rate: 4.7 -> 4.76% (10-year interest rate): In the US, when the 10-year interest rate soared, the stock price was adjusted.
  • Fear & Greed Index (currently 27): Below 25 usually means a high probability of bottoming out.
  • Because of Trump, ESG is a thing of the past...
    

Outing

• Bupyeong Station Underground Shopping Center (First visit due to a friend's visit): Packed with people. It's not easy to stand still. It's huge, the prices are low, and it's good.

IT

• IT News - Developer crisis, 2025 CES, Project Digits, o1 API release, Apple eavesdropping controversy, etc.
  • By 2025, Meta will be able to replace mid-level engineers with AI.
  • Salesforce says it will no longer hire SW engineers by 2025.
  • AI agentrents GPUs and codes with pytorch
    

English Study

• I prepare English in advance and ask questions like this using ChatGPT to get satisfying answers. It seems that English teachers' jobs will be given, and it is very helpful for my writing. I am summarizing the articles I read every day and asking ChatGPT to check for better sentences.
  • Please correct the following English mistakes and indicate the mistakes separately. Please answer in markdown format. Please remove blank lines.

Code

• It's important to write clean code. Reading this article will be very helpful. This is a rewritten version focusing on what I needed: https://github.com/cheoljoo/publish/blob/main/clean-code.md

• What is the best way to use logs? I found and wrote about loggers to use in Python and Bash from open source. Python has a built-in standard module called logger, but I thought it would be better to choose loguru, which has more functions, and I added test results showing class names, etc. For Bash, I also thought it was necessary to distinguish between info/warn/critical, so I dealt with related open sources: https://github.com/cheoljoo/publish/blob/main/log.md
  

• Comments should be made as clean as possible, as discussed in clean-code, to make the code as readable as possible. However, in Python, it seems good to add comments in docstring format for class/function units because it can be automatically documented. In the case of Bash, if you write it like a docstring by simply changing the prefix to #, I think it is possible to create a tool to automatically generate documents. :https://github.com/cheoljoo/publish/blob/main/comments.md
  • In Bash, pay particular attention to the fact that all variables are global variables, so if you express them well in the comments, you can create a map using this later to see at a glance where the variables are used. (Please suggest if you have a good idea.)