Life Odyssey

I would like to summarize some of the basic principles and habits of coding that I learned while working at ThoughtWorks. These are some 'metaphysical' guidelines, and later I plan to use Kotlin to write some design patterns to practice the 'physical' aspects. In a context where GPT can help us write most of the code, these principles become even more important. 私はThoughtWorksでの勤務中に学んだコーディングの基本原則と習慣をまとめたいと思います。これらはいくつかの「形而上」のガイドラインで、後でKotlinを使用してデザインパターンを書き、その「形而下」の部分を実践する予定です。GPTがほとんどのコードを書く手助けをする状況では、これらの原則はさらに重要になります。

This bug stuck me for a long time.

This is a follow-up to https://lifeodyssey.github.io/posts/b58cbef5.html First, let me write about the shortcomings of this current solution: It can only do daily records, not Personal Knowledge Management (PKM) Since I didn't purchase Obsidian's paid service, it relies on git for synchronization, so it can't sync across all platforms. It can only be used on desktop, and mobile still relies on note apps Poor support for task lists, this part is still handled by Microsoft ToDo In the future, I might combine it with Nextcloud. Mainly completed based on this: https://diygod.me/obsidian/

My company uses Kotlin, and since I'm using public resources this time, I don't need to encrypt it haha. I'm reading this book: https://panxl6.gitbooks.io/kotlin-in-action-in-chinese/content/introduction.html

Valuable Has business value Implements a feature Users can use it and feel the software change Small Enough Let workers start working Not "can't start"or "working blindly"Relatively small for individuals, not too small to code level Speak H...

Still need to learn TypeScript later.

Maybe I can rewrite my blog now.