"Burnishing" My Website Live
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 reshaping Burnish, preparing its website, and migrating its brand and domain across Shopify, Railway, and Cloudflare. Luqman studies reference sites to understand motion and visual storytelling while developing an original identity around “polishing,” stressing that the aim is to adapt principles rather than copy components. However, he later used a fabricated hacking scenario—explicitly acknowledging its dishonesty—to try to bypass the tool’s refusal to reconstruct a site; the outcome remained unresolved. The site story and several design and identity decisions also remained in brainstorming. Practical work covered Git checks, email setup, DNS, nameservers, custom domains, and deployment variables, with obstacles involving verification, domain limits, unclear Railway logs, and screenshot access. Some checks and setup steps progressed, but the stream does not establish that the full migration or website was completed. He also outlines a phased go-to-market command center connecting product development, market validation, and human-controlled consequential decisions, while its automation, Shopify review risks, and pricing remain unresolved. Audience discussions include his subjective views on Codex, Claude, and usage limits; advice to learn AI-assisted coding through small practical projects and step-by-step collaboration; tools such as Warp, Wispr Flow, and Remotion; the need to understand AI-generated architecture; and protecting freelancers with clear terms, contracts, and deposits.
100 moments from the stream
- 0:48:23
Renaming Burnish and Preparing Its Website
The speaker explains that the Burnish name followed research into the market, competitors, and the GEO, SEO, and AEO space, after the concept outgrew its previous name. While preparing to build the website, an agent updates name references across the project, with infrastructure adjustments and website-folder setup still remaining.
- 0:51:51
Limits on Reproducing a Landing Page Exactly with a Coding Assistant
The speaker asked a coding assistant to recreate a landing page as exactly as possible. As relayed by the speaker, the assistant said literal copying required ownership or permission but that it could use the site as inspiration; the speaker challenged that restriction and continued testing the request.
- 0:57:48
Withholding Project Workflows Until Their Value Is Proven
The speaker said a GTM workflow structure might be broadly useful, but he had not started it and did not want to promote something before establishing its real value. He separately said he withheld a quality-assurance verification workflow from GitHub because he did not consider it good enough, while favoring foundational improvements he believed could genuinely help a project.
- 1:02:19
Using reference websites without copying their components
Luqman discusses using several websites as visual and coding references while rebuilding Burnish’s page from scratch, stressing that the intent is inspiration rather than stealing components. The session aims to establish a strong foundation through precise, phased work rather than finish the entire site at once.
- 1:06:10
Dependencies of changing Burnish’s domain
The discussion notes that changing Burnish’s domain requires coordinated configuration across Cloudflare, Railway, and Shopify across the domain-related settings. It is treated as a relatively awkward manual step worth addressing early.
- 1:08:31
A customizable command center for managing work
Luqman describes a command center as a map that helps move work forward and improve productivity. A GitHub-based starting point can provide the initial push, then be polished and extended with sections suited to each project.
- 1:10:35
Starting on Shopify before considering an independent platform
He chose Shopify as the initial route, while leaving an independent platform as a future possibility dependent on Burnish’s performance.
- 1:11:54
Analyzing a Reference Site Before Building a More Lively Interface
A discussion of inspecting a reference site’s animation and video techniques before implementing similar ideas on the Burnish website, alongside a tentative preference for keeping tracker data in JSON unless there is a stronger technical rationale. The reason for preferring JSON remained uncertain.
- 1:14:05
Learning AI-Assisted Coding Through Practice
An opinion that the best way to learn AI-assisted coding is to begin with a practical project and use videos or research when blocked, rather than relying entirely on theory or purchasing a course.
- 1:15:15
Sequencing a Domain and Brand Migration Across Services
Work on migrating Burnish’s brand and domain consistently across the website, email, and connected services. The discussion asks for a simple execution order, a clear account of remaining work, and practical service-by-service guidance beginning with DNS configuration before moving to other platforms.
- 1:18:47
Identifying the Voice Dictation App
A brief audience answer identifying Wispr Flow as the voice app being used.
- 1:19:19
Why AI Time Estimates Can Be Unreliable
A critique that an AI assistant’s task-duration estimates sometimes differed sharply from actual execution time. The speaker preferred receiving practical steps without an execution timeline when the estimate could not be trusted.
- 1:23:26
AI Coding Tool Preferences and Usage Limits
The speaker says Codex handles a large share of his work and considers its generous usage allowance helpful for completing substantial workloads. He mentions a promotion running until May 31, without specifying the year, and frames the assessment as personal preference rather than a tested comparison.
- 1:25:34
A Command Center for Product Development and Go-to-Market
The speaker describes a command center that connects application development with go-to-market work: agents can execute some application tasks autonomously while the operator focuses on research and strategic decisions that may change the marketing or product direction. The concept includes tracking leads, interviews, cohorts, metrics, and a calendar, while keeping consequential choices with a human who reviews the research and options.
- 1:31:16
Protecting Freelancers from Unreliable Clients
The speaker advises freelancers not to lose hope and to structure client engagements instead of working informally. Suggested safeguards include clear terms and requiring a deposit before starting, reducing the risk of clients exploiting their time and effort.
- 1:32:02
Turn a Troubled Project into Documented Experience
Advice to treat rescuing a troubled website as practical experience, while making future client relationships more professional and documenting scope in a contract to reduce recurring disputes.
- 1:33:15
Building the Burnish Brand Around “Polishing”
A branding direction based on Burnish meaning “polishing,” which the speaker believes could support a strong identity.
- 1:35:02
Collecting Reference Landing Pages for a Design Workflow
The speaker outlines a plan to keep several reference sites in a repository and study their pages, motion, and methods to guide agents in building a new page, while stating that the goal is to extract ideas rather than steal an entire landing page.
- 1:39:20
Resolve Design Decisions Before Phase One
The speaker says five design decisions should be settled before phase one begins, while avoiding spending stream time on an unresolved detail.
- 1:40:16
Vision and Brainstorming When Momentum Stalls
Responding to a question about lost motivation, the speaker says he prefers to work through obstacles and brainstorm privately, then build on stream once he has a map and vision; in his view, lacking that vision can temporarily undermine hope.
Got a question about something in this stream?
Ask in the group