One AI Department Done. 3 to Go.
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 a work-in-progress automation system that organizes AI agents like connected departments for research, coordination, content production, publishing, and analytics. Luqman explains a possible progression from scheduled tasks and role-specific instructions toward shared goals and indicators, with research handed to agents that adapt posts, articles, and short videos for each platform. Practical work includes reviewing the post-stream pipeline, trimming silence and adjusting clips, and preparing operations across LinkedIn, X, Facebook, and Instagram while retaining human review initially. Speed, quality, resource use, queues, measurement, and agent autonomy still require testing and refinement; the stream does not establish a successful end-to-end system. It also discusses distribution and building in public, comparing direct outreach with SEO, social content, and advertising, alongside the speaker’s view that understanding an audience and solving a real problem matter more than selling a generic chatbot. Audience questions broaden the discussion to changing developer roles, learning and working with AI, game development, video-editing tools, background or local agent execution, community platforms, tools, and subscriptions. Other cautious, unresolved topics include AI jobs and pricing, proposed Egyptian data centers, model and hardware performance, YouTube Shorts growth, and ideas for competitions and products; these are generally presented as opinions, proposals, or open questions rather than verified findings.
171 moments from the stream
- 0:02:02
Designing an Automation System as Specialized Departments
Luqman outlines work on a mission-control-like automation system split into four departments, with the social department being finalized before choosing the community or search department as the next focus.
- 0:04:50
Connecting Research to Content Creation Across Agents
He explains a model in which a specialized research function investigates the requested topic and distributes its findings to other agents that turn them into content, describing the structure as analogous to departments in a company.
- 0:06:35
Why He Thinks Agents Will Become Essential
In response to an audience question, Luqman gives his view that agents are important and will become more central over time, while clarifying that his current focus is on marketing and traffic-related functions before technical ones.
- 0:08:17
From Scheduled Tasks to Goal-Directed Agents
Luqman distinguishes an agent that repeats a specific scheduled task from agents given a broader shared objective. He notes that each agent needs role-specific system instructions and presents this as the approach he intends to implement, not a completed result.
- 0:10:56
Confidence in High-Quality Automation After the Selim Work
The speaker says he is impressed by Selim’s work and views it as evidence that high-quality automation is possible. In his opinion, the remaining social-media automations should be less layered and mainly require focus.
- 0:14:57
Protecting Devices and Staying Connected During Power Cuts
An audience member warns that the main supply should be disconnected during an outage because returning power could damage devices. The speaker replies that he has arranged layered backup power for his equipment and separate protection for the router, giving him time to switch power sources without an immediate interruption.
- 0:17:08
Starting Manually, Then Automating the Workflow Gradually
The speaker explains that he intentionally kept parts of recording selection manual until the workflow stabilizes and gains momentum, after which they can be automated more easily. He later shows that the process remains manual and clearly identifies approving eight clips as the next step; the caption immediately before that approval is unclear.
- 0:22:34
Automatically Handing a Recording into the Processing Workflow
The speaker describes an intended workflow in which a finished stream is handed automatically to processing and then publishing. The passage expresses the plan and his confidence in the workflow, not a documented end-to-end test.
- 0:22:56
Organizing Agents to Write Multi-Platform Posts
The speaker presents a workflow under development in which multiple agents draft posts for X, LinkedIn, Instagram, and Facebook. He says the outputs still need some refinement before the process becomes routine.
- 0:23:41
Combining Programmatic SEO with Visibility in AI Answers
The speaker outlines a goal combining programmatic SEO with visibility in answers from tools such as ChatGPT, so the platform might be recommended when a user asks for a suitable solution. He says he intends to apply an existing core engine to this goal, while presenting the implementation as future work.
- 0:24:56
Distinguishing Qualitative and Quantitative Claims
The speaker distinguishes qualitative claims based on opinions or statements from quantitative claims grounded in checkable numbers. He uses an attributed prediction and an asserted software-developer wage trend from 2023 to 2026 to explain why he prefers forming views from tangible indicators; these are the speaker’s examples, not findings verified within the passage.
- 0:30:19
Organizing a Cross-Platform Content Workflow
Discusses refining a workflow where agents create posts and images for platforms such as LinkedIn, X, Facebook, and Instagram. Social publishing is prioritized for potentially faster traffic, while programmatic SEO is expected to take longer.
- 0:32:24
Repurposing Long Streams into Highlights and Short Clips
In response to a suggestion about translating videos, the speaker favors extracting highlights from a long stream into a shorter video and producing clips for platforms such as Instagram, YouTube Shorts, and TikTok. Translation is described as possible, but its value and cost remain uncertain.
- 0:36:16
Auditing the Post-Stream Pipeline End to End
Requests an end-to-end review of the post-stream process: from the recording reaching a designated folder, through inspecting the codebase and workflow, to uploading the videos, followed by a clear bullet-point explanation.
- 0:36:59
How AI Is Reshaping Software Engineering Roles
Discusses the opinion that software-engineering titles and responsibilities are shifting with AI: a software or full-stack developer may expand toward AI engineering, while the forward-deployed engineer role has regained prominence. The claims are presented tentatively, not as fixed career rules.
- 0:38:17
Reaching an International Audience Across Social Channels
Discusses using multiple channels across LinkedIn, X, Facebook, and Instagram to distribute content and reach an international audience while keeping the livestream itself in Arabic. The approach separates the live community’s language from the broader distribution strategy.
- 0:39:43
Documenting the Workflow After a Stream Ends
Notes that the detailed steps after a stream ends have been documented through to a generated workflow page, while acknowledging that parts of the process still need adjustment.
- 0:40:59
From Full-Stack Developer to Broader AI Responsibilities
A discussion of proliferating technical titles and developers taking on additional areas such as DevOps, Kubernetes, and AI. The expressed view is that the developer role is evolving and deepening rather than simply disappearing, alongside a practical question about when the title “AI engineer” is appropriate.
- 0:44:17
AI May Reshape Jobs Even If the Market Is a Bubble
The speakers argue that job requirements will change and become more demanding, so relying only on older skills may make adaptation harder. They compare a possible AI-company bubble with the dot-com bubble: companies or expectations could falter without the underlying technology disappearing, while acknowledging competing views about continued progress or a potential ceiling.
- 0:45:59
Closing Gaps in an Automated Recording Workflow
A practical review of the recording pipeline before human review. One proposed improvement is to clean the ready-recordings folder automatically after a file is picked up, preventing multiple recordings from accumulating and confusing the process.
Got a question about something in this stream?
Ask in the group