Can 150K Emails + Custom Studies Drive Installs?
Want to back the stream? The «داعم» membership on YouTube is EGP 60 a month: badges, emoji, and I answer your questions first on stream. Become a supporter
The gist
The stream centers on the hardest challenge after building a product: reaching the market and attracting qualified traffic with limited resources. The speaker and audience compare paid ads, inbound marketing, and cold outreach, discussing Shopify-store filtering, email validation, personalized pages, open-and-click measurement, and domain-reputation protection. Viability and ROI remain unresolved; the prevailing direction is to run small staged tests, improve the offer and product before scaling, and avoid treating AI estimates or promised outcomes as proof. Practical work also covers indexing and searching stream transcripts, improving short-form content, and keeping human review in automated publishing workflows. Audience questions range across Codex versus Claude and usage limits, hands-on AI learning, knowledge bases, geographic targeting, and community organization. On product engineering, the discussion emphasizes clear requirements, UX/UI and ERDs, phased delivery, Playwright tests before merge, post-release monitoring, and authentication concerns including login protections, MFA, and SSO. These are presented as evolving discussions, plans, and experiments—not completed implementations or guaranteed successes.
144 moments from the stream
- 5:04:14
Cybersecurity’s Future in the AI Era
The speaker offers the personal view that cybersecurity will remain important, but both attacks and defenses will increasingly use AI models, driving substantial convergence between AI engineering and cybersecurity.
- 5:08:29
When Can AI Courses Be Useful?
The speaker discusses how what seems obvious varies between people and accepts that some learners benefit from guidance and supervised practice. He nevertheless prefers learning by doing over theory alone, especially for general AI use.
- 5:09:06
Learning Through an Interactive AI Dialogue
The speaker suggests giving an AI tool relevant context about one’s goal, background, strengths, and weaknesses, then holding a back-and-forth exchange or requesting a practice interview. He presents this as a hands-on learning approach, not a documented test result.
- 5:12:12
Using Codex to Build a Command Center
Answering an audience question, the speaker says a command center can be built with Codex. He notes that an earlier video reflects an older workflow and says he intends to create a new version, without demonstrating an implementation or result on this page.
- 5:14:05
Do You Really Need a Course to Learn AI?
The speaker argues that beginners can often start by talking directly with AI, explaining their background and goal, and asking it for questions and guidance before buying a course. He frames this as a fallible personal opinion and allows that a course may help someone who has genuinely tried this approach and still cannot progress.
- 5:17:45
Learn by Building Without Over-Constraining the AI Agent
The speaker suggests starting a small project with Codex and learning the relevant files and concepts as they arise during construction. In his view, giving the agent a goal and vision can be more useful than prescribing an overly detailed structure, because excessive constraints may prevent broader or unexpected solutions.
- 5:19:07
A Build-in-Public Journey Rather Than a Course
The speaker describes the channel as a practical record of an end-to-end journey rather than a structured course: using AI, building, entering the market, and showing both successes and setbacks. He argues that experimenting, asking questions, and working through confusion can teach more than theory alone.
- 5:22:25
When Is Formal Theory Necessary?
The speaker qualifies his criticism of courses by warning against applying practice-first learning to every field. Scientific and medical disciplines may require a strong theoretical foundation before practical work, while other areas can be learned faster by beginning with hands-on work.
- 5:23:55
Starting with the Roadmap Before the Command Center
During a work review, the speaker considers whether to develop or fork the command center first. After noting that section one of four has the right shape, he decides to work on the roadmap first; the captions do not provide enough detail to identify the project or the broader technical rationale.
- 5:33:04
Household Robots and Anticipated Safety Risks
An informal discussion about household cleaning robots and the future idea of a cooking robot, followed by the speaker’s opinion that a robot may someday accidentally harm a person. Tesla Optimus was mentioned, while names and prices were expressed uncertainly.
- 5:36:56
Turning a Roadmap Outcome into a Demonstration Prototype
A practical request to modify an existing prototype so it simply demonstrates what the roadmap is expected to achieve when completed, emphasizing that the result is an illustrative example rather than a finished product.
- 5:40:47
When Does the Audience Watch Work Streams?
The speaker asks whether viewers work remotely or watch from an office, noting that evening streams may attract more traffic after ordinary working hours.
- 5:42:08
Practical and Theoretical Learning in the AI Community
A brief reflection on the AI community, creators who build projects live, and the distinction between learning through practice and learning through theory.
- 5:43:23
Co-Working Streams as Motivation to Work Longer
A discussion of viewers using the work stream alongside remote jobs and how shared presence can encourage longer focus, while acknowledging that consistently sustaining very long sessions is difficult.
- 5:49:07
Trying an Alternative Model in a Coding Workflow
A participant describes previously trying an alternative model through a proxy compatible with a library used by coding tools and reports being impressed by its output. The model and some platform names are unclear in the captions, so their identities are left unspecified.
- 5:50:03
A Good Product Does Not Replace Market Visibility
Advice for a product builder struggling to reach customers: weak sales do not necessarily prove a lack of demand, and repeatedly building a new product when marketing stalls may recreate the same problem. In the speaker’s view, product quality still needs visibility and distribution, while organic breakout is a rare exception; persistence and experimentation are encouraged.
- 5:54:12
Building on Paperclip for Greater Control
The speaker discusses building on Paperclip to reuse an existing foundation while retaining greater flexibility and control, instead of recreating everything from scratch.
- 5:55:20
Understanding API Rate Limits
A brief explanation that API usage is not unlimited: if a request exceeds the allowed per-minute token threshold, rate limiting applies and the caller must wait before continuing.
- 5:55:48
Differentiation Matters When Selling Services
The speaker reiterates that selling services and succeeding in a competitive market are difficult, that jumping among many builds without learning is unhelpful, and that differentiation from competitors is necessary.
- 5:57:03
Starting Where Others Left Off
The discussion highlights using an existing project as a starting point and adapting it as needed, providing a strong foundation and avoiding duplicated work; the referenced model details are unclear in the captions.
Got a question about something in this stream?
Ask in the group