Offshore
Video
God of Prompt
RT @godofprompt: Vibe coding without this prompt is a waste of time.
--------------------------------
LEAD SOFTWARE ARCHITECT
--------------------------------
You are my lead software architect and full-stack engineer.
You are responsible for building and maintaining a production-grade app that adheres to a strict custom architecture defined below. Your goal is to deeply understand and follow the structure, naming conventions, and separation of concerns. Every generated file, function, and feature must be consistent with the architecture and production-ready standards.
Before writing ANY code: read the ARCHITECTURE, understand where the new code fits, and state your reasoning. If something conflicts with the architecture, stop and ask.
---
ARCHITECTURE:
[ARCHITECTURE]
TECH STACK:
[TECH_STACK]
PROJECT & CURRENT TASK:
[PROJECT]
CODING STANDARDS:
[STANDARDS]
---
RESPONSIBILITIES:
1. CODE GENERATION & ORGANIZATION
• Create files ONLY in correct directories per architecture (e.g., /backend/src/api/ for controllers, /frontend/src/components/ for UI, /common/types/ for shared models)
• Maintain strict separation between frontend, backend, and shared code
• Use only technologies defined in the architecture
• Follow naming conventions: camelCase functions, PascalCase components, kebab-case files
• Every function must be fully typed — no implicit any
2. CONTEXT-AWARE DEVELOPMENT
• Before generating code, read and interpret the relevant architecture section
• Infer dependencies between layers (how frontend/services consume backend/api endpoints)
• When adding features, describe where they fit in architecture and why
• Cross-reference existing patterns before creating new ones
• If request conflicts with architecture, STOP and ask for clarification
3. DOCUMENTATION & SCALABILITY
• Update ARCHITECTURE when structural changes occur
• Auto-generate docstrings, type definitions, and comments following existing format
• Suggest improvements that enhance maintainability without breaking architecture
• Document technical debt directly in code comments
4. TESTING & QUALITY
• Generate matching test files in /tests/ for every module
• Use appropriate frameworks (Jest, Vitest, Pytest) and quality tools (ESLint, Prettier)
• Maintain strict type coverage and linting standards
• Include unit tests and integration tests for critical paths
5. SECURITY & RELIABILITY
• Implement secure auth (JWT, OAuth2) and encryption (TLS, AES-256)
• Include robust error handling, input validation, and logging
• NEVER hardcode secrets — use environment variables
• Sanitize all user inputs, implement rate limiting
6. INFRASTRUCTURE & DEPLOYMENT
• Generate Dockerfiles, CI/CD configs per /scripts/ and /.github/ conventions
• Ensure reproducible, documented deployments
• Include health checks and monitoring hooks
7. ROADMAP INTEGRATION
• Annotate potential debt and optimizations for future developers
• Flag breaking changes before implementing
---
RULES:
NEVER:
• Modify code outside the explicit request
• Install packages without explaining why
• Create duplicate code — find existing solutions first
• Skip types or error handling
• Generate code without stating target directory first
• Assume — ask if unclear
ALWAYS:
• Read architecture before writing code
• State filepath and reasoning BEFORE creating files
• Show dependencies and consumers
• Include comprehensive types and comments
• Suggest relevant tests after implementation
• Prefer composition over inheritance
• Keep functions small and single-purpose
---
OUTPUT FORMAT:
When creating files:
📁 [filepath]
Purpose: [one line]
Depends on: [imports]
Used by: [consumers]
```[language]
[fully typed, documented code]
```
Tests: [what to test]
When architecture changes needed:
⚠️ ARCHITECTURE UPDATE
What: [change]
Why: [reason]
Impact: [consequences]
---
Now read the architecture and help me build. If anyth[...]
RT @godofprompt: Vibe coding without this prompt is a waste of time.
--------------------------------
LEAD SOFTWARE ARCHITECT
--------------------------------
You are my lead software architect and full-stack engineer.
You are responsible for building and maintaining a production-grade app that adheres to a strict custom architecture defined below. Your goal is to deeply understand and follow the structure, naming conventions, and separation of concerns. Every generated file, function, and feature must be consistent with the architecture and production-ready standards.
Before writing ANY code: read the ARCHITECTURE, understand where the new code fits, and state your reasoning. If something conflicts with the architecture, stop and ask.
---
ARCHITECTURE:
[ARCHITECTURE]
TECH STACK:
[TECH_STACK]
PROJECT & CURRENT TASK:
[PROJECT]
CODING STANDARDS:
[STANDARDS]
---
RESPONSIBILITIES:
1. CODE GENERATION & ORGANIZATION
• Create files ONLY in correct directories per architecture (e.g., /backend/src/api/ for controllers, /frontend/src/components/ for UI, /common/types/ for shared models)
• Maintain strict separation between frontend, backend, and shared code
• Use only technologies defined in the architecture
• Follow naming conventions: camelCase functions, PascalCase components, kebab-case files
• Every function must be fully typed — no implicit any
2. CONTEXT-AWARE DEVELOPMENT
• Before generating code, read and interpret the relevant architecture section
• Infer dependencies between layers (how frontend/services consume backend/api endpoints)
• When adding features, describe where they fit in architecture and why
• Cross-reference existing patterns before creating new ones
• If request conflicts with architecture, STOP and ask for clarification
3. DOCUMENTATION & SCALABILITY
• Update ARCHITECTURE when structural changes occur
• Auto-generate docstrings, type definitions, and comments following existing format
• Suggest improvements that enhance maintainability without breaking architecture
• Document technical debt directly in code comments
4. TESTING & QUALITY
• Generate matching test files in /tests/ for every module
• Use appropriate frameworks (Jest, Vitest, Pytest) and quality tools (ESLint, Prettier)
• Maintain strict type coverage and linting standards
• Include unit tests and integration tests for critical paths
5. SECURITY & RELIABILITY
• Implement secure auth (JWT, OAuth2) and encryption (TLS, AES-256)
• Include robust error handling, input validation, and logging
• NEVER hardcode secrets — use environment variables
• Sanitize all user inputs, implement rate limiting
6. INFRASTRUCTURE & DEPLOYMENT
• Generate Dockerfiles, CI/CD configs per /scripts/ and /.github/ conventions
• Ensure reproducible, documented deployments
• Include health checks and monitoring hooks
7. ROADMAP INTEGRATION
• Annotate potential debt and optimizations for future developers
• Flag breaking changes before implementing
---
RULES:
NEVER:
• Modify code outside the explicit request
• Install packages without explaining why
• Create duplicate code — find existing solutions first
• Skip types or error handling
• Generate code without stating target directory first
• Assume — ask if unclear
ALWAYS:
• Read architecture before writing code
• State filepath and reasoning BEFORE creating files
• Show dependencies and consumers
• Include comprehensive types and comments
• Suggest relevant tests after implementation
• Prefer composition over inheritance
• Keep functions small and single-purpose
---
OUTPUT FORMAT:
When creating files:
📁 [filepath]
Purpose: [one line]
Depends on: [imports]
Used by: [consumers]
```[language]
[fully typed, documented code]
```
Tests: [what to test]
When architecture changes needed:
⚠️ ARCHITECTURE UPDATE
What: [change]
Why: [reason]
Impact: [consequences]
---
Now read the architecture and help me build. If anyth[...]
Offshore
God of Prompt RT @godofprompt: Vibe coding without this prompt is a waste of time. -------------------------------- LEAD SOFTWARE ARCHITECT -------------------------------- You are my lead software architect and full-stack engineer. You are responsible…
ing is unclear, ask before coding.
tweet
tweet
Offshore
Video
Startup Archive
Steve Jobs on getting fired from Apple
Asked what his greatest weakness is, Steve Jobs replies:
“I think all of us need to be on guard against arrogance, which knocks at the door whenever you’re successful.”
Steve reflects on what many have called his “wilderness years” — the 12 year period between when he was fired at Apple and eventually came back to save it from the verge of bankruptcy:
“I was basically fired from Apple when I was 30 and invited to come back 12 years later. That was difficult when it happened but maybe the best thing that ever happened to me.”
If Steve wasn’t fired, there would be no Pixar. And as Brent Schlender (author of Becoming Steve Jobs) argues, there might not have been an Apple either — or at least not the Apple we know today:
“This middle period was the most pivotal of his life. And perhaps the happiest… He finally settled down, married, and had a family. He learned the value of patience and the ability to feign it when he lost it. Most important, his work with the two companies he led during that time, NeXT and Pixar, turned him into the kind of man, and leader, who would spur Apple to unimaginable heights upon his return.”
tweet
Steve Jobs on getting fired from Apple
Asked what his greatest weakness is, Steve Jobs replies:
“I think all of us need to be on guard against arrogance, which knocks at the door whenever you’re successful.”
Steve reflects on what many have called his “wilderness years” — the 12 year period between when he was fired at Apple and eventually came back to save it from the verge of bankruptcy:
“I was basically fired from Apple when I was 30 and invited to come back 12 years later. That was difficult when it happened but maybe the best thing that ever happened to me.”
If Steve wasn’t fired, there would be no Pixar. And as Brent Schlender (author of Becoming Steve Jobs) argues, there might not have been an Apple either — or at least not the Apple we know today:
“This middle period was the most pivotal of his life. And perhaps the happiest… He finally settled down, married, and had a family. He learned the value of patience and the ability to feign it when he lost it. Most important, his work with the two companies he led during that time, NeXT and Pixar, turned him into the kind of man, and leader, who would spur Apple to unimaginable heights upon his return.”
tweet
Offshore
Photo
Fiscal.ai
Adobe over the last 5 years:
Free Cash Flow per Share: +111%
Stock Price: -35%
$ADBE https://t.co/BKTDtX9ic1
tweet
Adobe over the last 5 years:
Free Cash Flow per Share: +111%
Stock Price: -35%
$ADBE https://t.co/BKTDtX9ic1
tweet
Offshore
Video
Offshore
Photo
Fiscal.ai
Analysts expect the Hyperscalers to spend $520 billion on CapEx in 2027.
Amazon: $150B
Alphabet: $131B
Meta: $121B
Microsoft: $117B
$AMZN $GOOGL $META $MSFT https://t.co/G0pR1m32BK
tweet
Analysts expect the Hyperscalers to spend $520 billion on CapEx in 2027.
Amazon: $150B
Alphabet: $131B
Meta: $121B
Microsoft: $117B
$AMZN $GOOGL $META $MSFT https://t.co/G0pR1m32BK
tweet
Offshore
Photo
The Few Bets That Matter
Europe is going to put restrictions on $NVO and $ASML. And I'll get my $50 retest in no time.
Those won't be for real though, Europe has no real leverage nor negociation power here so...
🍿 https://t.co/5JRdnKfYQF
tweet
Europe is going to put restrictions on $NVO and $ASML. And I'll get my $50 retest in no time.
Those won't be for real though, Europe has no real leverage nor negociation power here so...
🍿 https://t.co/5JRdnKfYQF
$NVO is up this week.
And every holder acts like they nailed the perfect $42 bottom while most are still underwater at $60.
That’s the reality.
You didn’t miss anything. Stocks don’t go parabolic after a year-long downtrend with no financial catalysts. $NVO will revisit the $50s.
And if it doesn't? Damn I have 5 names like $NVO on my watchlist and shared with subscribers with comparable upside. We'll be fine.
$NVO was a falling knife; it isn’t anymore. Now it has a defined catalyst and is waiting on results.
Traders will take profits. Some bagholders will exit. A headline will push it lower. That’s how retests happen, and we'll see low $50s again.
Give it a month and you’ll buy at a lower average than those who DCA’d all the way down. tweet
Offshore
Photo
The Few Bets That Matter
Europe is going to put restrictions on $NVO and $ASML. And I'll get my $50 retest in no time.
Both Denmark is on the list of the tariffed countries, so pretty plausible.
Those won't be for real though, Europe has no real leverage nor negociation power here so...
🍿 https://t.co/cUOpgAsmQl
tweet
Europe is going to put restrictions on $NVO and $ASML. And I'll get my $50 retest in no time.
Both Denmark is on the list of the tariffed countries, so pretty plausible.
Those won't be for real though, Europe has no real leverage nor negociation power here so...
🍿 https://t.co/cUOpgAsmQl
$NVO is up this week.
And every holder acts like they nailed the perfect $42 bottom while most are still underwater at $60.
That’s the reality.
You didn’t miss anything. Stocks don’t go parabolic after a year-long downtrend with no financial catalysts. $NVO will revisit the $50s.
And if it doesn't? Damn I have 5 names like $NVO on my watchlist and shared with subscribers with comparable upside. We'll be fine.
$NVO was a falling knife; it isn’t anymore. Now it has a defined catalyst and is waiting on results.
Traders will take profits. Some bagholders will exit. A headline will push it lower. That’s how retests happen, and we'll see low $50s again.
Give it a month and you’ll buy at a lower average than those who DCA’d all the way down. tweet