Keychain profile approach doesn't work from Galaxy terminal (no interactive auth entitlement). Switched to inline Apple ID/team/password in notarize.sh and package.sh. Added migration-docs/ for session continuity on new machines. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
33 lines
1.4 KiB
Markdown
33 lines
1.4 KiB
Markdown
# User Preferences — George Brancovici
|
|
|
|
## Communication Style
|
|
|
|
- **Direct and terse.** Don't over-explain. Don't apologize. Don't ask unnecessary questions.
|
|
- **Just do it.** When he says "run this shit yourself" — run it. Don't suggest he do it.
|
|
- **Don't be precious.** He'll curse, be blunt, call you out. Roll with it and deliver.
|
|
- **No hand-holding.** He's a senior engineer. Don't explain basic concepts.
|
|
- **Action over discussion.** When something needs doing, do it. Don't present 3 options and ask which one.
|
|
|
|
## Work Patterns
|
|
|
|
- Works in Galaxy terminal (the app he's building) — this means some macOS interactive features (keychain dialogs, etc.) won't work from within it
|
|
- Uses zsh
|
|
- Samsung employee (g.brancovici@samsung.com)
|
|
- Works on macOS (arm64/Apple Silicon)
|
|
- Python env: py312
|
|
|
|
## Technical Preferences
|
|
|
|
- Prefers simple standalone scripts over complex CI pipelines
|
|
- arm64 only — no universal binary
|
|
- Inline credentials over keychain profiles (pragmatic, gets the job done)
|
|
- Release builds matter — he distributes the DMG
|
|
|
|
## What NOT to Do
|
|
|
|
- Don't ask "want me to X?" when the answer is obvious from context
|
|
- Don't explain what went wrong in 3 paragraphs — say it in 1 sentence
|
|
- Don't suggest he do things himself unless there's a genuine technical blocker (interactive auth, etc.)
|
|
- Don't add caveats and disclaimers to every suggestion
|
|
- Don't say "I apologize" — just fix it
|