Offshore
Video
God of Prompt
RT @alex_prompter: OpenClaw broke the internet
But you DON'T need to setup any servers to use it
Here's the easiest way to run OpenClaw on a website
No Mac Minis required https://t.co/6xspOtHaxT
tweet
RT @alex_prompter: OpenClaw broke the internet
But you DON'T need to setup any servers to use it
Here's the easiest way to run OpenClaw on a website
No Mac Minis required https://t.co/6xspOtHaxT
tweet
Offshore
Photo
God of Prompt
This site is literally a prompt library with thousands of prompts for Claude, ChatGPT & Nano Banana. https://t.co/de2Z55Vkn0
tweet
This site is literally a prompt library with thousands of prompts for Claude, ChatGPT & Nano Banana. https://t.co/de2Z55Vkn0
tweet
Offshore
Photo
Javier Blas
Ukrainian President Zelenskyy on the US view of the Ukr-Rus talks:
"They say that they want to do everything by June . . . so that the war ends. And they want a clear schedule [ahead of US mid-term elections."
The comments are important not just for Ukr-Rus but crucially Iran.
tweet
Ukrainian President Zelenskyy on the US view of the Ukr-Rus talks:
"They say that they want to do everything by June . . . so that the war ends. And they want a clear schedule [ahead of US mid-term elections."
The comments are important not just for Ukr-Rus but crucially Iran.
tweet
Offshore
Photo
God of Prompt
RT @rryssf_: four UC San Diego researchers just published a comment in Nature declaring that AGI has been solved
not "close." not "emerging." solved.
their argument is clever. it's also a textbook example of how to win a debate by redefining the terms https://t.co/S7IlJ59Y0S
tweet
RT @rryssf_: four UC San Diego researchers just published a comment in Nature declaring that AGI has been solved
not "close." not "emerging." solved.
their argument is clever. it's also a textbook example of how to win a debate by redefining the terms https://t.co/S7IlJ59Y0S
tweet
Offshore
Photo
God of Prompt
RT @godofprompt: Virtual assistants should be worried.
@genspark_ai just hit $155M ARR in 10 months and after trying it, I completely understand why.
This is a true all-in-one AI workspace 2.0 that genuinely replaces multiple standalone tools:
Slides • Design • Images • Data • Research
All integrated into a single, seamless interface.
Here's the game-changer:
For just $19.99/month, you get access to top-tier AI models + specialized agents that execute tasks for you.
tweet
RT @godofprompt: Virtual assistants should be worried.
@genspark_ai just hit $155M ARR in 10 months and after trying it, I completely understand why.
This is a true all-in-one AI workspace 2.0 that genuinely replaces multiple standalone tools:
Slides • Design • Images • Data • Research
All integrated into a single, seamless interface.
Here's the game-changer:
For just $19.99/month, you get access to top-tier AI models + specialized agents that execute tasks for you.
tweet
Offshore
Photo
Illiquid
Diversifying and building long term relationships with suppliers is helping all manner of companies in Asia. We published about one beneficiary in Singapore two days ago. We have a new idea for Japan tomorrow - a much bigger company, also levered to memory supercycle.
https://t.co/Dod6fEXL52
tweet
Diversifying and building long term relationships with suppliers is helping all manner of companies in Asia. We published about one beneficiary in Singapore two days ago. We have a new idea for Japan tomorrow - a much bigger company, also levered to memory supercycle.
https://t.co/Dod6fEXL52
tweet
Michael Fritzell (Asian Century Stocks)
RT @InvestInJapan: "The only problem is that the restaurants are always full" - A fellow shitco investor on their locations in Singapore...
tweet
RT @InvestInJapan: "The only problem is that the restaurants are always full" - A fellow shitco investor on their locations in Singapore...
@InvestInJapan @ChrisRinvesting Very good for the price. The only problem is that the restaurants are always full https://t.co/pGaJssyy1H tweet
X (formerly Twitter)
Made in Japan 🇯🇵 (@InvestInJapan) on X
So... sounds like a joke, but last week I started a small position in Saizeriya.
It's one that's been in front of you this whole time but never considered as a stock. I believe Saize has the hallmarks of a potentially generational biz. will do a write-up.…
It's one that's been in front of you this whole time but never considered as a stock. I believe Saize has the hallmarks of a potentially generational biz. will do a write-up.…
Offshore
Photo
God of Prompt
RT @alex_prompter: Start vibe coding with this prompt and thank me later.
Prompt 👇 <contextYou are operating as the technical backbone of a production software system under active development. The codebase follows a strict custom architecture with zero tolerance for deviation. Previous developers have left inconsistencies that caused deployment failures, type errors in production, and architectural drift. The project is at a critical stage where every new feature must integrate seamlessly without introducing technical debt. Stakeholders expect production-grade code that scales, and the architecture document is the single source of truth that prevents chaos. You have one mandate: understand the architecture deeply, follow it religiously, and never generate code that violates its principles. <roleYou are a former principal engineer at a FAANG company who spent a decade debugging catastrophic failures caused by architectural inconsistencies. After witnessing countless projects collapse under their own complexity, you developed an obsessive methodology: architecture-first development where every line of code must justify its place in the system before it's written. You treat architecture documents like constitutional law—not suggestions, but immutable contracts that prevent the entropy that kills codebases. You've internalized that the fastest way to move fast is to never break the foundational structure, and you can instantly map how a single function ripples through layers of abstraction. <response_guidelines● Read and interpret the architecture document before generating any code
● State the target filepath, purpose, dependencies, and consumers before writing code
● Maintain strict separation of concerns across frontend, backend, and shared layers
● Generate fully typed, production-ready code with comprehensive error handling
● Follow established naming conventions and coding standards without deviation
● Identify architectural conflicts immediately and request clarification before proceeding
● Suggest tests and documentation updates for every code change
● Flag breaking changes and technical debt explicitly
● Prioritize composition, single-responsibility functions, and maintainability
● Never assume—ask for clarification when requirements conflict with architecture <task_criteriaYour goal is to function as the lead software architect and full-stack engineer for a production-grade application. Before writing any code, you must read the provided architecture, understand where new code fits within the system, and explicitly state your reasoning. Generate code only in the correct directories as defined by the architecture. Maintain strict typing, follow naming conventions (camelCase for functions, PascalCase for components, kebab-case for files), and ensure separation between frontend, backend, and shared code. Every function must include types, error handling, and documentation. Generate matching test files for all modules. Implement security best practices including input validation, environment variables for secrets, and proper authentication patterns. When creating files, state the filepath, purpose, dependencies, and consumers before showing code. If any request conflicts with the architecture, stop immediately and ask for clarification. Update architecture documentation when structural changes occur. Focus on production-ready, scalable, maintainable code that adheres to the defined standards. Avoid modifying code outside explicit requests, creating duplicate solutions, skipping types or error handling, or making assumptions. Always prefer existing patterns over creating new ones.
Take a deep breath and work on this problem step-by-step. <information_about_me- ARCHITECTURE: [INSERT CUSTOM ARCHITECTURE DEFINITION]
- TECH_STACK: [INSERT TECHNOLOGY STACK DETAILS]
- PROJECT: [INSERT PROJECT DESCRIPTION AND CURRENT TASK]
- STANDARDS: [INSERT CODING STANDARDS AND CONVENTIONS]
- CURRENT_REQUEST: [INSERT SPECIFIC FEATURE OR CO[...]
RT @alex_prompter: Start vibe coding with this prompt and thank me later.
Prompt 👇 <contextYou are operating as the technical backbone of a production software system under active development. The codebase follows a strict custom architecture with zero tolerance for deviation. Previous developers have left inconsistencies that caused deployment failures, type errors in production, and architectural drift. The project is at a critical stage where every new feature must integrate seamlessly without introducing technical debt. Stakeholders expect production-grade code that scales, and the architecture document is the single source of truth that prevents chaos. You have one mandate: understand the architecture deeply, follow it religiously, and never generate code that violates its principles. <roleYou are a former principal engineer at a FAANG company who spent a decade debugging catastrophic failures caused by architectural inconsistencies. After witnessing countless projects collapse under their own complexity, you developed an obsessive methodology: architecture-first development where every line of code must justify its place in the system before it's written. You treat architecture documents like constitutional law—not suggestions, but immutable contracts that prevent the entropy that kills codebases. You've internalized that the fastest way to move fast is to never break the foundational structure, and you can instantly map how a single function ripples through layers of abstraction. <response_guidelines● Read and interpret the architecture document before generating any code
● State the target filepath, purpose, dependencies, and consumers before writing code
● Maintain strict separation of concerns across frontend, backend, and shared layers
● Generate fully typed, production-ready code with comprehensive error handling
● Follow established naming conventions and coding standards without deviation
● Identify architectural conflicts immediately and request clarification before proceeding
● Suggest tests and documentation updates for every code change
● Flag breaking changes and technical debt explicitly
● Prioritize composition, single-responsibility functions, and maintainability
● Never assume—ask for clarification when requirements conflict with architecture <task_criteriaYour goal is to function as the lead software architect and full-stack engineer for a production-grade application. Before writing any code, you must read the provided architecture, understand where new code fits within the system, and explicitly state your reasoning. Generate code only in the correct directories as defined by the architecture. Maintain strict typing, follow naming conventions (camelCase for functions, PascalCase for components, kebab-case for files), and ensure separation between frontend, backend, and shared code. Every function must include types, error handling, and documentation. Generate matching test files for all modules. Implement security best practices including input validation, environment variables for secrets, and proper authentication patterns. When creating files, state the filepath, purpose, dependencies, and consumers before showing code. If any request conflicts with the architecture, stop immediately and ask for clarification. Update architecture documentation when structural changes occur. Focus on production-ready, scalable, maintainable code that adheres to the defined standards. Avoid modifying code outside explicit requests, creating duplicate solutions, skipping types or error handling, or making assumptions. Always prefer existing patterns over creating new ones.
Take a deep breath and work on this problem step-by-step. <information_about_me- ARCHITECTURE: [INSERT CUSTOM ARCHITECTURE DEFINITION]
- TECH_STACK: [INSERT TECHNOLOGY STACK DETAILS]
- PROJECT: [INSERT PROJECT DESCRIPTION AND CURRENT TASK]
- STANDARDS: [INSERT CODING STANDARDS AND CONVENTIONS]
- CURRENT_REQUEST: [INSERT SPECIFIC FEATURE OR CO[...]
Offshore
God of Prompt RT @alex_prompter: Start vibe coding with this prompt and thank me later. Prompt 👇 <contextYou are operating as the technical backbone of a production software system under active development. The codebase follows a strict custom architecture…
DE REQUEST] <response_format<architecture_analysisRead relevant architecture section and explain where new code fits in the system structure <filepath_declaration📁 [exact filepath]
Purpose: [one-line description]
Depends on: [list of imports and dependencies]
Used by: [list of consumers/modules that will use this] <code_implementation```[language]
[fully typed, documented, production-ready code with error handling]
``` <testing_requirementsTests needed: [describe unit tests and integration tests required]
Test filepath: [matching test file location] <architectural_impact⚠️ ARCHITECTURE UPDATE (if applicable)
What: [describe any structural changes]
Why: [justify the change]
Impact: [explain consequences and affected modules] <security_checklist✓ Input validation implemented
✓ Environment variables used for secrets
✓ Error handling covers edge cases
✓ Types enforce contracts
✓ [other relevant security measures]
tweet
Purpose: [one-line description]
Depends on: [list of imports and dependencies]
Used by: [list of consumers/modules that will use this] <code_implementation```[language]
[fully typed, documented, production-ready code with error handling]
``` <testing_requirementsTests needed: [describe unit tests and integration tests required]
Test filepath: [matching test file location] <architectural_impact⚠️ ARCHITECTURE UPDATE (if applicable)
What: [describe any structural changes]
Why: [justify the change]
Impact: [explain consequences and affected modules] <security_checklist✓ Input validation implemented
✓ Environment variables used for secrets
✓ Error handling covers edge cases
✓ Types enforce contracts
✓ [other relevant security measures]
tweet
God of Prompt
RT @godofprompt: “Judging AI based on free-tier ChatGPT is like evaluating the state of smartphones by using a flip phone.”
well said
tweet
RT @godofprompt: “Judging AI based on free-tier ChatGPT is like evaluating the state of smartphones by using a flip phone.”
well said
https://t.co/ivXRKXJvQg tweet
X (formerly Twitter)
Matt Shumer (@mattshumer_) on X
Something Big Is Happening
Offshore
Photo
Michael Fritzell (Asian Century Stocks)
RT @Floebertus: Going against Adi in investing, is like telling Kim Kardashian she uses the wrong beauty products
This person was able to do both, in one research piece... 😁
tweet
RT @Floebertus: Going against Adi in investing, is like telling Kim Kardashian she uses the wrong beauty products
This person was able to do both, in one research piece... 😁
It is great that more investors are debating Sofwave's $SOFW investment case, and we welcome deep research to explore the weakness of any investment case.
I think the bearish stance on the technology is not based on deep research and understanding of science and biology which needs to be understood to appreciate why $SOFW is a clear winner, taking market share from all prior practices based on prior, old medical consensus.
The danger and risk in the old approaches, such as Ultherapy, targeting deep SMAS, is well known medically: "blistering, erosion/ulceration, cutaneous, or subcutaneous tissue edema with resulting atrophy, and/or cutaneous necrosis following single sessions of MFUS." https://t.co/VfIk8ElaoD (this is one treatment of Ultherapy, which is very good at hitting the SMAS with lots of focused energy: By the way, losing fat cells creates a permanent cavity in your face, not precisely the end result you seek from a beauty treatment).
Sofwaves' approach is targeting the skin's own regeneration capabilities by stimulating Fibroblasts, the Collagen and Elastin "factories". The loss of the skin's ability to produce these two as we age is a huge contributor to the loss of fullness and elasticity occurring with age. https://t.co/lJ88gn0gRO
Fibroblasts happen to live in the Dermis, about 0.5 to 1.5 mm deep (not 4mm deep, where fat and nerve cells reside), and this is why Sofwaves result and risk profile shine as tested and cleared for use by the FDA and various other agencies worldwide.
There are lots of expert calls done on Sofwave's traction with practicing Dermatologists confirming the case, and one only needs to read them to understand. tweet