Offshore
Video
Offshore
Photo
The Few Bets That Matter
The comments on this post are a perfect snapshot of what you can expect from X.
Everyone quotes Buffett at me like I’m a doofus.
Most of them own $RKLB, $ASTS, and $PLTR.
Guess they didn’t finish the book. Most never even started it. The irony 🍿
tweet
The comments on this post are a perfect snapshot of what you can expect from X.
Everyone quotes Buffett at me like I’m a doofus.
Most of them own $RKLB, $ASTS, and $PLTR.
Guess they didn’t finish the book. Most never even started it. The irony 🍿
If your position is down 30%+, you made a mistake. A big one.
This applies to every stock, not just $DUOL, and it doesn’t mean $DUOL is a bad company or that Antonio is a bad stock picker.
Everyone makes mistakes.
But holding a stock down 70% is not conviction. It’s ego.
It means you own a company the market refuses to reward while you insist you’re right. Millions scream at you that you are wrong, and you ignore them.
You’re still down 70%. That’s a fact. That's the definition of being wrong.
Even if $DUOL makes new highs in two or three years, you were still wrong then. You misunderstood something and paid for it with years of underperformance, likely more as you probably will DCA to the grave.
By ego, again.
The market decides who’s right and who’s wrong. A buy at $150 may be right. But the original thesis wasn’t.
You should accept being wrong. tweet
Moon Dev
I'm hiring a Head of Content. $3k/month, part-time, remote-only, no lazy Americans.
I host a daily livestream covering crypto, trading automation, and algorithmic trading.
I'm looking for someone who can:
1. Work directly with me and my team to plan stream content conducive to high quality YouTube videos, clips, & beyond. We want your expertise to assist us in the full content lifecycle.
2. Transform livestream segments into structured, narrative-driven youtube videos (Deep dives, market analysis, tutorials, etc.).
3. Create original UGC content yourself - not just repurposing, but actually making videos.
4. Build systems and processes that you will later use to manage a team under you as we scale.
5. Develop my long term content distribution strategy across all platforms and content lengths: clips, shorts, reels, TikTok, podcasts, etc.
Your KPI's will be youtube growth, and non-X virality.
How to apply:
Go into my VOD library, find a solo segment (not an interview), and edit it into a 5-10 min YouTube video.
Send that + a short bio (bullet points or a few sentences) covering your experience and why you want this job to moon@algotradecamp.com or DM here on twitter.
Requirements:
- Background in Youtube editing and growth
- Complete fluency in video editing, graphic design (thumbnails & posters), and production tools
- Knowledge of finance / crypto / trading (nice to have)
tweet
I'm hiring a Head of Content. $3k/month, part-time, remote-only, no lazy Americans.
I host a daily livestream covering crypto, trading automation, and algorithmic trading.
I'm looking for someone who can:
1. Work directly with me and my team to plan stream content conducive to high quality YouTube videos, clips, & beyond. We want your expertise to assist us in the full content lifecycle.
2. Transform livestream segments into structured, narrative-driven youtube videos (Deep dives, market analysis, tutorials, etc.).
3. Create original UGC content yourself - not just repurposing, but actually making videos.
4. Build systems and processes that you will later use to manage a team under you as we scale.
5. Develop my long term content distribution strategy across all platforms and content lengths: clips, shorts, reels, TikTok, podcasts, etc.
Your KPI's will be youtube growth, and non-X virality.
How to apply:
Go into my VOD library, find a solo segment (not an interview), and edit it into a 5-10 min YouTube video.
Send that + a short bio (bullet points or a few sentences) covering your experience and why you want this job to moon@algotradecamp.com or DM here on twitter.
Requirements:
- Background in Youtube editing and growth
- Complete fluency in video editing, graphic design (thumbnails & posters), and production tools
- Knowledge of finance / crypto / trading (nice to have)
tweet
God of Prompt
Prompting for translation tip:
tweet
Prompting for translation tip:
Prompting tip:
If you're asking AI to do a translation task, adding the line "Preserve the original register" can improve the results by A LOT
(In language, "register" means the level of formality or style you use when speaking or writing in a particular situation. For example, casual with friends vs. formal in a job interview). tweet
X (formerly Twitter)
Zara Zhang (@zarazhangrui) on X
Prompting tip:
If you're asking AI to do a translation task, adding the line "Preserve the original register" can improve the results by A LOT
(In language, "register" means the level of formality or style you use when speaking or writing in a particular…
If you're asking AI to do a translation task, adding the line "Preserve the original register" can improve the results by A LOT
(In language, "register" means the level of formality or style you use when speaking or writing in a particular…
Moon Dev
seeing so many awful takes about this
if you are a developer you should be excited about ads
until now discovery is still not solved for ai apps
having an open platform you can buy users for your app on is game changing
google and meta ads are saturated, lets go OAI ads!
tweet
seeing so many awful takes about this
if you are a developer you should be excited about ads
until now discovery is still not solved for ai apps
having an open platform you can buy users for your app on is game changing
google and meta ads are saturated, lets go OAI ads!
We are starting to test ads in ChatGPT free and Go (new $8/month option) tiers.
Here are our principles. Most importantly, we will not accept money to influence the answer ChatGPT gives you, and we keep your conversations private from advertisers.
It is clear to us that a lot of people want to use a lot of AI and don't want to pay, so we are are hopeful a business model like this can work.
(An example of ads I like are on Instagram, where I've found stuff I like that I otherwise never would have. We will try to make ads ever more useful to users.) tweet
X (formerly Twitter)
Sam Altman (@sama) on X
We are starting to test ads in ChatGPT free and Go (new $8/month option) tiers.
Here are our principles. Most importantly, we will not accept money to influence the answer ChatGPT gives you, and we keep your conversations private from advertisers.
It is…
Here are our principles. Most importantly, we will not accept money to influence the answer ChatGPT gives you, and we keep your conversations private from advertisers.
It is…
AkhenOsiris
Time for @dalibali2 Sasshitco index...all the sw shit that has been tossed in the trash, should work a year or two out no!? Few will die, but a few should also flourish
tweet
Time for @dalibali2 Sasshitco index...all the sw shit that has been tossed in the trash, should work a year or two out no!? Few will die, but a few should also flourish
tweet
God of Prompt
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 anything is unclear, a[...]
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 anything is unclear, a[...]
Offshore
Photo
God of Prompt
RT @godofprompt: Steal my Grok prompts to create a business in 2026 ✨
🔖 Bookmark for later. https://t.co/ltaW3i6P2o
tweet
RT @godofprompt: Steal my Grok prompts to create a business in 2026 ✨
🔖 Bookmark for later. https://t.co/ltaW3i6P2o
tweet
Offshore
Photo
God of Prompt
90% of the AI skills you learned in 2025 are already useless.
2026 requires a completely different playbook.
I'm breaking down what's dead vs. what's next at AI Skills'2026 on Jan 22.
4,000+ attendees. 4+ hours. Free.
Join free 👉 https://t.co/T3LxdWm0DL https://t.co/MaIDCScCdC
tweet
90% of the AI skills you learned in 2025 are already useless.
2026 requires a completely different playbook.
I'm breaking down what's dead vs. what's next at AI Skills'2026 on Jan 22.
4,000+ attendees. 4+ hours. Free.
Join free 👉 https://t.co/T3LxdWm0DL https://t.co/MaIDCScCdC
tweet
Offshore
Photo
The Few Bets That Matter
$NVO is giving me everything I want to see. Finally.
Big chances we finally found the bottom, lots of optimism on the GLP-1 pills, lots of good positive and the market is finally catching up a bid.
The retest might be an opportunity. https://t.co/8YsNcG4YDc
tweet
$NVO is giving me everything I want to see. Finally.
Big chances we finally found the bottom, lots of optimism on the GLP-1 pills, lots of good positive and the market is finally catching up a bid.
The retest might be an opportunity. https://t.co/8YsNcG4YDc
Comparing $NVO to $LLY is like comparing an air balloon to a fighter jet.
It may look good, but you're wrong.
$NVO has traded around ~5x sales for most of its history, with <10%tweet