Copy-ready prompt
{ "type": "Chinese infographic poster", "style": "A concise vector-based infographic with clear and easy-to-read Chinese typography, a white background, thin colored panel borders, cartoon business/tech characters, small icons, charts, a laptop, code screens, and speech bubbles.", "canvas": "1:1 Square Poster", "headline": "{argument name=\"headline text\" default=\"The harsh truth of the AI era: Four types of CTOs/Technical Directors\"}", "subtitle": "Whether you write code or not is not important; what matters is embracing AI and getting heavily involved in it! Otherwise, you're becoming a liberal arts student in the tech world.", "main_layout": { "structure": "A 2x2 quadrant matrix divided by thick black horizontal and vertical arrows intersecting at the center.", "vertical_axis": { "top": "Embrace AI (through hands-on, intensive participation)", "bottom": "Not embracing AI (lacking front-line AI engineering experience)" }, "horizontal_axis": { "left": "Writing code (getting involved personally)", "right": "Not writing code (detached from frontline work)" }, "quadrants_count": 4, "quadrants": [ { "number": 1, "title": "AI Engineering Commander 👑", "position": "top-left", "border_color": "green", "summary": "Top players who possess both in-depth technical knowledge and mastery of AI productivity", "character": "An engineer in a hoodie sits in front of a laptop with a code editor on the screen, a cute AI robot mascot, tool labels Copilot and Claude Code, and a speech bubble that reads: Let me revise the prompt, verify it in 5 minutes!", "labels": { "features_title": "Features:", "features_count": 4, "features": [ "Every day I'm on the field doing AI engineering.", "Boundaries of Deep Understanding", "Able to quickly validate ideas", "Amplify team combat effectiveness with AI" ], "team_state_title": "Team Status:", "team_state": "With exceptionally high AI combat power per person, small teams achieve remarkable results.", "catchphrase": "My catchphrase: 'Let's make a minimum viable demo first to test it out.'", "result": "Result: True technology leaders lead their teams to evolve." } }, { "number": 2, "title": "AI PPT Strategist📈", "position": "top-right", "border_color": "orange", "summary": "AI in our imagination is wonderful, but its implementation in reality is a complete mess.", "character": "An executive pointed to a presentation slide titled \"AI Transformation 2026,\" which featured rising bar charts and labels such as Agent, MCP, Multimodal, Autonomous, and AGI Ready; stacks of documents labeled \"New Paradigm of AI,\" \"Futurism,\" and \"Industry Disruption\" were also present; a speech bubble read: \"AI will change everything! We're going all in on AI!\"", "labels": { "features_title": "Features:", "features_count": 4, "features": [ "PPT skills MAX", "Hearsay about AI", "Exaggerating the upper limit of AI capabilities", "Underestimating the complexity of the project" ], "team_state_title": "Team Status:", "team_state": "The roadmap was radical, the demo was stunning, but implementation was a nightmare.", "catchphrase": "My catchphrase: 'I think AI should be able to…'", "result": "Result: Using imagined AI to direct real-world engineering projects (High risk!)" } }, { "number": 3, "title": "Traditional hackers (old-school craftsmen) >_", "position": "bottom-left", "border_color": "blue", "summary": "Possesses strong technical skills, but rejects the paradigm revolution brought about by AI.", "character": "A long-haired programmer, wearing a black T-shirt, types in front of a large monitor filled with green code. His coffee cup reads \"No AI Just Code,\" and the chat bubble says: \"AI-generated code? That's just a bunch of shit keyboard shortcuts!\"", "labels": { "features_title": "Features:", "features_count": 4, "features": [ "Solid basic skills", "Terrifying debugging capabilities", "Disdain for AI tools", "Limited efficiency improvement" ], "team_state_title": "Team Status:", "team_state": "High quality, slow speed, gradually widening the gap due to productivity disparities.", "catchphrase": "My favorite saying: 'A real engineer writes it himself.'", "result": "Result: Becoming artisans in the digital age, but gradually becoming marginalized." } }, { "number": 4, "title": "Process-oriented technical managers 📋", "position": "bottom-right", "border_color": "gray", "summary": "They don't understand technology or AI; all they care about are processes and KPIs.", "character": "The manager, wearing a blue shirt and a name tag, sat at his desk, which was piled with Jira/OKR/weekly reports. A checklist poster was titled \"Key Tasks for This Week,\" along with file folders and a speech bubble that read: \"Let the lower-level staff evaluate this requirement... and write a weekly report while you're at it.\"", "labels": { "features_title": "Features:", "features_count": 4, "features": [ "KPI/Process Driven", "Technical isolation", "I have no feelings about AI", "Safety first, innovation second" ], "team_state_title": "Team Status:", "team_state": "The organization is stable, but its efficiency is average, and innovation relies mainly on luck.", "catchphrase": "Catchphrase: 'Let the people below evaluate it.'", "result": "Result: Most suitable for transitioning to a professional managerial role; stop wearing the technical hat." } } ] }, "footer": { "boxes_count": 4, "boxes": [ { "title": "The harsh reality of the AI era:", "items_count": 4, "items": [ "AI is not a new tool, but a new layer of engineering cognition.", "Not getting involved personally = losing technical judgment", "Imagination cannot replace experience typed out line by line.", "Those who understand how to filter out bubbles will be ruthlessly eliminated by the times." ] }, { "title": "Key conclusions", "text": "Whether you are personally and heavily involved in AI engineering determines whether you evolve or regress.", "emphasis": "Evolution or Degeneration" }, { "title": "Advice for technology managers:", "items_count": 4, "items": [ "Do AI engineering work yourself at least once a week (not just watch).", "Applying AI to real-world business scenarios", "Building firsthand experience on the boundaries of AI capabilities", "Otherwise, the first to be buried will be the manager." ] }, { "title": "warn!", "icon": "skull and crossbones", "text": "The most dangerous state in the tech world is: letting imagination dictate reality and using processes to mask ignorance. This will kill a team in the AI era!" } ], "note": "Remember: AI won't eliminate you, but those who know how to use AI will. Start doing AI engineering yourself now, and stop being a liberal arts student in the tech world!" }, "generation_notes": "Make all Chinese text crisp and legible, preserve the exact labels and quadrant numbering, use a balanced poster composition with clear arrows and color-coded panels." }
Prompt breakdown
{ "type": "Chinese infographic poster", "style": "A concise vector-based infographic with clear and easy-to-read Chinese typography, a white background, thin colored panel borders, cartoon business/tech characters, small icons, charts, a laptop, code screens, and speech bubbles.", "canvas": "1:1 Square Poster", "headline": "{argument name=\"headline text\" default=\"The harsh truth of the AI era: Four types of CTOs/Technical Directors\"}", "subtitle": "Whether you write code or not is not important; what matters is embracing AI and getting heavily involved in it! Otherwise, you're becoming a liberal arts student in the tech world.", "main_layout": { "structure": "A 2x2 quadrant matrix divided by thick black horizontal and vertical arrows intersecting at the center.", "vertical_axis": { "top": "Embrace AI (through hands-on, intensive participation)", "bottom": "Not embracing AI (lacking front-line AI engineering experience)" }, "horizontal_axis": { "left": "Writing code (getting involved personally)", "right": "Not writing code (detached from frontline work)" }, "quadrants_count": 4, "quadrants": [ { "number": 1, "title": "AI Engineering Commander 👑", "position": "top-left", "border_color": "green", "summary": "Top players who possess both in-depth technical knowledge and mastery of AI productivity", "character": "An engineer in a hoodie sits in front of a laptop with a code editor on the screen, a cute AI robot mascot, tool labels Copilot and Claude Code, and a speech bubble that reads: Let me revise the prompt, verify it in 5 minutes!", "labels": { "features_title": "Features:", "features_count": 4, "features": [ "Every day I'm on the field doing AI engineering.", "Boundaries of Deep Understanding", "Able to quickly validate ideas", "Amplify team combat effectiveness with AI" ], "team_state_title": "Team Status:", "team_state": "With exceptionally high AI combat power per person, small teams achieve remarkable results.", "catchphrase": "My catchphrase: 'Let's make a minimum viable demo first to test it out.'", "result": "Result: True technology leaders lead their teams to evolve." } }, { "number": 2, "title": "AI PPT Strategist📈", "position": "top-right", "border_color": "orange", "summary": "AI in our imagination is wonderful, but its implementation in reality is a complete mess.", "character": "An executive pointed to a presentation slide titled \"AI Transformation 2026,\" which featured rising bar charts and labels such as Agent, MCP, Multimodal, Autonomous, and AGI Ready; stacks of documents labeled \"New Paradigm of AI,\" \"Futurism,\" and \"Industry Disruption\" were also present; a speech bubble read: \"AI will change everything! We're going all in on AI!\"", "labels": { "features_title": "Features:", "features_count": 4, "features": [ "PPT skills MAX", "Hearsay about AI", "Exaggerating the upper limit of AI capabilities", "Underestimating the complexity of the project" ], "team_state_title": "Team Status:", "team_state": "The roadmap was radical, the demo was stunning, but implementation was a nightmare.", "catchphrase": "My catchphrase: 'I think AI should be able to…'", "result": "Result: Using imagined AI to direct real-world engineering projects (High risk!)" } }, { "number": 3, "title": "Traditional hackers (old-school craftsmen) >_", "position": "bottom-left", "border_color": "blue", "summary": "Possesses strong technical skills, but rejects the paradigm revolution brought about by AI.", "character": "A long-haired programmer, wearing a black T-shirt, types in front of a large monitor filled with green code.
His coffee cup reads \"No AI Just Code,\" and the chat bubble says: \"AI-generated code? That's just a bunch of shit keyboard shortcuts!\"", "labels": { "features_title": "Features:", "features_count": 4, "features": [ "Solid basic skills", "Terrifying debugging capabilities", "Disdain for AI tools", "Limited efficiency improvement" ], "team_state_title": "Team Status:", "team_state": "High quality, slow speed, gradually widening the gap due to productivity disparities.", "catchphrase": "My favorite saying: 'A real engineer writes it himself.'", "result": "Result: Becoming artisans in the digital age, but gradually becoming marginalized." } }, { "number": 4, "title": "Process-oriented technical managers 📋", "position": "bottom-right", "border_color": "gray", "summary": "They don't understand technology or AI; all they care about are processes and KPIs.", "character": "The manager, wearing a blue shirt and a name tag, sat at his desk, which was piled with Jira/OKR/weekly reports.
A checklist poster was titled \"Key Tasks for This Week,\" along with file folders and a speech bubble that read: \"Let the lower-level staff evaluate this requirement...
and write a weekly report while you're at it.\"", "labels": { "features_title": "Features:", "features_count": 4, "features": [ "KPI/Process Driven", "Technical isolation", "I have no feelings about AI", "Safety first, innovation second" ], "team_state_title": "Team Status:", "team_state": "The organization is stable, but its efficiency is average, and innovation relies mainly on luck.", "catchphrase": "Catchphrase: 'Let the people below evaluate it.'", "result": "Result: Most suitable for transitioning to a professional managerial role; stop wearing the technical hat." } } ] }, "footer": { "boxes_count": 4, "boxes": [ { "title": "The harsh reality of the AI era:", "items_count": 4, "items": [ "AI is not a new tool, but a new layer of engineering cognition.", "Not getting involved personally = losing technical judgment", "Imagination cannot replace experience typed out line by line.", "Those who understand how to filter out bubbles will be ruthlessly eliminated by the times." ] }, { "title": "Key conclusions", "text": "Whether you are personally and heavily involved in AI engineering determines whether you evolve or regress.", "emphasis": "Evolution or Degeneration" }, { "title": "Advice for technology managers:", "items_count": 4, "items": [ "Do AI engineering work yourself at least once a week (not just watch).", "Applying AI to real-world business scenarios", "Building firsthand experience on the boundaries of AI capabilities", "Otherwise, the first to be buried will be the manager." ] }, { "title": "warn!", "icon": "skull and crossbones", "text": "The most dangerous state in the tech world is: letting imagination dictate reality and using processes to mask ignorance.











