Inside the Core Engine
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 developing the Burnish Shopify app, especially refining its multi-step onboarding so it feels native and consistent with Shopify, communicates merchant value clearly, and improves copy, cards, navigation, and pricing using visual references. The work remained unfinished: content and design revisions, backend wiring, deep-link behavior, and onboarding’s dependency on database state still required attention. In parallel, Luqman explores a safer Git workflow for multiple coding agents—cleaning the repository, isolating tasks with branches and worktrees, detecting conflicts before merge, validating development servers and URLs, and maintaining a living diagnostic log of difficult problems and fixes. Audience questions and broader discussions cover SEO and GEO, AI-driven product discovery, using funnel signals to assess demand, and practical advice for learning while building a SaaS product. The stream also contains personal, qualified impressions of Codex, Claude, Gemini, GPT, and coding benchmarks, stressing that outcomes depend partly on how tools are used and that informal comparisons do not support firm conclusions.
109 moments from the stream
- 0:04:32
Balancing Speed and Organization Across Multiple Coding Agents
A practical comparison of Warp, Claude, and Codex: multiple terminal sessions can accelerate parallel work, but may consume more resources and make it harder to track worktrees, branches, and pull requests, increasing the risk of overlapping changes during merges.
- 0:07:05
Studying a Competitor’s Onboarding When Its Frame Is Hard to Inspect
An attempt to understand a competitor’s onboarding design by exploring its interface, with the observation that right-clicking an element inside a frame only offered “open frame,” not “inspect.” No confirmed solution appears on this page.
- 0:07:52
Designing a Simpler Git Workflow for Parallel Development
A request to review the current branches and worktrees and propose a concise, simpler workflow for a website, landing page, and Shopify app, allowing multiple sessions and agents to work in separate areas without overlapping or losing changes.
- 0:09:21
Growing Interest in SEO in the Arab World
A general audience-discussion observation that interest in search engine optimization was growing among people in the Arab world at the time.
- 0:10:38
The Evolving Relationship Between SEO and GEO
The speaker argues that demand for SEO continues to grow alongside AI, while SEO and GEO overlap only partially. Blogging and product FAQs are discussed as examples, with the qualification that the market is still determining what specifically benefits GEO.
- 0:11:24
Comparing AI Coding Tool Workflows
A practical comparison favors Claude Code's interface while crediting another tool with notably fast work and the ability to open its UI inside a desktop coding environment. Some tool names in the captions are unclear.
- 0:14:10
Inspecting a Shopify UI Button in Safari
The speaker investigates how a competitor implemented a button that appears native to Shopify after documentation and research did not reveal the full approach. Safari Web Inspector is used to inspect attributes and copy the element, while whether it is ordinary HTML or a native implementation remains unresolved.
- 0:17:06
Organizing a Codex Workflow and Usage Limits
An audience discussion considers how much work Codex can handle and uncertainty about future usage limits after a temporary offer ending May 31. The speaker describes consulting one assistant before handing final work to Codex, then asks for a simplified workflow involving a fresh main branch, cleanup, and squash-merge or rebase decisions.
- 0:21:25
Must an App Follow BFS from Day One?
A question about whether an app should be designed around BFS requirements from day one or can be realigned before applying once eligible. The discussion mentions install and review thresholds, but gives conflicting install counts, so no specific number should be treated as reliable.
- 0:24:39
Preferring the Codex Experience While Struggling with Worktrees
A practical opinion favoring the cleaner Codex experience while describing worktree management in another workflow as a source of friction. This is a personal impression, not a benchmarked tool comparison.
- 0:28:16
Branches and Worktrees for Parallel Coding Sessions
A discussion of why a solo developer may initially work on one branch, yet need branches, worktrees, and pull requests when publishing or running several sessions and models against one project. Isolating each session lets GitHub surface merge conflicts, though the speaker stresses the workflow’s complexity and recounts previously losing part of the interface work after an incorrect merge.
- 0:30:53
Organizing Work with Git Branches and Worktrees
A discussion of working on a development branch, using a release branch and worktrees, then pushing changes to the release branch once the work is ready.
- 0:37:21
Forking a Claude Conversation While Preserving Context
An explanation of forking a long conversation when it reaches a point with multiple possible directions, allowing each new conversation to inherit the prior context and receive separate instructions.
- 0:40:04
Matching a Primary Button to Shopify’s Style
Design feedback calling for a black, full-width button that resembles Shopify’s native primary button as closely as possible, using an attached reference for guidance.
- 0:41:26
Reviewing Task Scope Before Implementation
The discussion decides not to alter onboarding, requests deletion of task 001, and asks for a brief purpose statement for each remaining task before implementation continues.
- 0:44:39
Comparing a Button with Shopify’s UI Pattern
A button’s appearance and hover effect are compared with Shopify’s primary button pattern. The current implementation appears not to match the reference, though the cause remains unresolved.
- 0:47:26
Building a Living Diagnostic Log of Problems and Fixes
The speaker proposes recording time-consuming problems, why they were difficult, and how they were resolved in a document that grows into a reference for future sessions. Its scope should include design, database work, and development-startup issues rather than design alone.
- 0:51:41
Tracking Development Work with Branches and Worktrees
The discussion examines how hard it becomes to locate changes and know whether they are tracked or committed. It argues for doing each piece of work in an appropriate branch or worktree so changes remain recoverable and easier to follow, while acknowledging the workflow takes effort to learn.
- 0:55:51
Safely Cleaning a Git Repository Without Losing Work
After repeated uncommitted changes on the main branch and lost work during merges, the speaker asks for an inventory of branches, worktrees, and unpushed changes before any cleanup. The discussion emphasizes using Git as a recoverable source, avoiding guesswork, and cleaning the repository before new work begins while reviewing branches and worktrees methodically.
- 1:01:20
Balancing Stream Quality and Chat Latency
The speaker explains that normal latency was selected to preserve stream quality, which delayed chat responses, and considers trying low latency later to improve interaction.
Got a question about something in this stream?
Ask in the group