gengwg

Enumerating objects: 19, done.
Counting objects: 100% (19/19), done.
Delta compression using up to 22 threads
Compressing objects: 100% (18/18), done.
Writing objects: 100% (18/18), 10.41 MiB | 4.59 MiB/s, done.
Total 18 (delta 2), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (2/2), completed with 1 local object.
remote: error: GH007: Your push would publish a private email address.
remote: You can make your email public or disable this protection by visiting:

gengwg

! swap left ctrl and left alt
! run xmodmap ~/.Xmodmap
clear control
clear mod1
keycode 37 = Alt_L Meta_L
keycode 64 = Control_L
add control = Control_L Control_R
add mod1 = Alt_L Meta_L

gengwg

gengwg

In Jira, an "idea" is not part of the standard project hierarchy (Project > Epic > Story/Task) but is a separate concept used for early-stage innovation and is managed in a dedicated tool called Jira Product Discovery (JPD). Ideas are for capturing and prioritizing potential work before it becomes part of the development backlog.

Here is a comparison of how ideas fit into the overall workflow:

Aspect	Jira Product Discovery (The "Idea" Space)	Jira Software (The "Development" Space)
Purpose	Capture, discuss, and prioritize opportunities and solutions.	Plan, track, and execute development work.
Unit of Work	Idea.	Issue (e.g., Epic, Story, Task, Bug).
Primary Goal	Decide what to build.	Build and deliver the selected items.
Connection	Promising ideas are sent to Jira Software as Epics or Stories.	Epics and Stories from JPD are broken down and worked on.

gengwg

Here is a breakdown of the standard Jira hierarchy for clarity:

Hierarchy Level	Description & Relationship	Common Issue Types at This Level
Project	A container for organizing all related work.	N/A
Epic	A large body of work within a project, spanning multiple sprints. It groups related Stories and Tasks.	Epic
Story / Task	An individual work item that contributes to an Epic. Stories are user-focused, while Tasks are general work. These are considered "standard-level" issues.	Story, Task, Bug
Sub-task	A small, actionable step that breaks down a Story or Task. A Sub-task must have a parent Story/Task and cannot exist on its own.	Sub-task

🔗 Important Distinctions and Limitations

gengwg

For most Site Reliability Engineering (SRE) teams, a Kanban board is generally more suitable than Scrum. Kanban’s flexibility helps manage the dynamic, interrupt-driven nature of SRE work, which often involves urgent incidents, on-call rotations, and unpredictable tasks. Scrum is typically better for projects with predictable, time-boxed work—less common for SREs.

Kanban for SRE Teams

• Focuses on continuous flow and visualizing work in progress, making it easier to respond to real-time issues.
• Allows real-time task prioritization, accommodating urgent operational demands and interruptions.
• Supports ongoing maintenance and improvement work rather than fixed-length sprints.

Scrum for SRE Teams

• Emphasizes fixed sprints, planning, and review cycles, which suit teams with predictable workloads and iterative deliverables.
• Can present challenges for SRE teams, as unplanned work (incidents, emergencies) frequently disrupts sprint commitments.

gengwg

A .gitkeep file is a convention-based placeholder file used to force Git to track an otherwise empty directory.

Why it's needed

Git doesn't track empty directories - if you commit a folder with no files, it won't be included in your repository. The .gitkeep file solves this problem.

How it works

# Without .gitkeep - empty directory won't be tracked

gengwg

From Deepseek.

1. What do "Compute-Bound" and "I/O-Bound" mean?

• Compute-Bound: A problem is compute-bound when the speed of the calculation is limited by the CPU's (or GPU's) ability to perform mathematical operations. The processors are constantly working, and the bottleneck is their processing speed. They are waiting for nothing.
• I/O-Bound: A problem is I/O-bound (Input/Output bound) when the speed of the calculation is limited by the system's ability to read data from or write data to storage (disks, SSDs) or to transfer data between parts of the system (e.g., between nodes over a network, or between RAM and a processor). The processors are often idle, waiting for data to arrive.

2. The "Why": How Supercomputing Causes the Shift

The core idea of supercomputing is to solve a big problem faster by breaking it into smaller pieces and solving those pieces simultaneously on thousands of processors (CPUs/GPUs).

gengwg

1.市场低迷时
原因是我们纳税的基础是做Roth Conversion时的投资品的市场价值。在市场下跌时，传统IRA帐户中的资产价值可能大幅缩水，此时转换，税务负担也会随之减少。转换后，等市场恢复，基金、股票回涨之时，资产在Roth IRA帐户的成长将完全免税。
举例说明：
假设老张的传统IRA帐户中有100,000，由于市场下跌，资产价值降至70,000。此时进行Roth Conversion，他只需为70,000缴纳所得税。若市场反弹，资产价值回升至12万，未来提领时无须再缴税。

2、收入相对低的时期
因为Roth conversion 会增加你的应税收入，可能会让你进入更高税率区间。如果你今年收入较低，整体税率较低，那就是个好时机。比如：
•失业或收入暂时减少的一年
•休假、创业初期或其他低收入阶段

gengwg

$ npm install -g @anthropic-ai/claude-code
npm ERR! code EACCES
npm ERR! syscall mkdir
npm ERR! path /usr/local/lib/node_modules
npm ERR! errno -13
npm ERR! Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules'
npm ERR!  [Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules'] {
npm ERR!   errno: -13,
npm ERR! code: 'EACCES',