When entering new transactions, and when exporting transactions to CSV, having multiple subcategories with the same name, such as "Work Expenses", but different Parent Groups, such as "Me vs Partner" causes confusion.

I'd vote against this change. It can be really useful as-is for certain groupings. For example, I often type "inc" when categorizing to bring up the income categories. The current behavior is also how it works in YNAB: The "which are not selectable" point in the original comment is valid though. YNAB handles this by shrinking the text size of the category group names, as you can see in the above screenshot. Maybe this Issue could be modified to be a UX change (shrinking the category group name text) instead of a functionality change, such that it's clear the category group names are no selectable.

bigger game

Some frameworks call this “template inheritance”. In this example, we might say that the application layout “inherits from” or “extends” the base layout. In Rails, this is known as nested layouts, and it is a bit awkward to use. The standard Rails practice for nested layouts is complicated and involves these considerations

But what if you want to reuse one layout within another?

The result is a set of nested cascades that cover the fullorganization (figure 1-2)

嵌套事务出错回滚不会影响到主事务

The overridden core classes for Hash and Array here only handle those two types. A hash hands off a bury to an Array if it encounter a nested array. Similarly, an Array hands off a bury if it encounters a non-integer or a nested hash.

every symbol in D3 4.0 now shares a flat namespace rather than the nested one of D3 3.x. For example, d3.scale.linear is now d3.scaleLinear, and d3.layout.treemap is now d3.treemap.

patch: -> { step Destroy.method(:tidy_storage), before: :delete_model }

However, it can be a PITA if you want to customize one of those deeply nested components and add or remove a certain step, for example.

array :translations do hash do string :locale string :name end end array inputs can only have one input nested underneath them. This is because every element of the array must be the same type. And the inputs nested inside arrays cannot have names because they would never be used.

No need for DatabaseCleaner (rolling back transactions are usually faster than truncate).

The basic idea behind Zettelkasten is to build a repository of the knowledge you gain through the years. The idea is similar to what Paul Jun, of Creative Mastery, writes about keeping a Commonplace Book, or Ryan Holiday’s notecard system. Zettelkasten adds the powerful idea of linking notes to create a web of interlinked knowledge.