happytomatoe

Audit this entire codebase for materially useful simplifications in its data structures, state representation, control flow, algorithms, and ownership.

This is an audit-only exercise. Do not edit files, run tests, implement recommendations, commit, or push. Read-only inspection commands are allowed.

You are the coordinator. Continue until the complete codebase has been reviewed and the final audit is validated.

1. Establish the coverage contract

Inspect the repository and inventory every identifiable subsystem.

happytomatoe

name	explain-diff-html
description	Use when the user asks for a rich explanation of a code change, diff, branch, PR, or entire system. Produces HTML output.

Explain Diff / System

Please make a rich, interactive explanation of the specified code change, diff, or system.

First, determine the scope: is this a diff/change explanation or a system-wide explanation? Adapt the sections accordingly.

happytomatoe

This cheat sheet originated from the forum, credits to Laurent Poulain. We copied it and changed or added a few things.

Evaluation Rules

• Call by value: evaluates the function arguments before calling the function
• Call by name: evaluates the function first, and then evaluates the arguments if need be

    def example = 2      // evaluated when called
    val example = 2      // evaluated immediately

happytomatoe

Database Naming Convention and Data Warehouse Design Principles

• hackmd version: https://hackmd.io/1eeNAS1oQuSvMA0q6y_QuA?view
• gist version: https://gist.github.com/bluet/23e7697b86144561c4a3d804903d059d

[TOC]

ETL: From Data Lake to Data Warehouse

1. Extract 部份：取出要的資料、去雜訊、資料標準化、parsing...
2. Transform：aggregation、mapping 、combined、Change Data Types