Dev community drama took over the Mano Rage Show: devs attacking devs, a Power BI identity fight, a live hospital hack, and an audit-log story worth studying.
What happened on the Mano Rage Show this week
Episode 263 of the Mano Rage Show, the weekly live stream by Brazilian creator Mano Deyvin, aired on Wednesday, August 26, 2026, and centered on one thesis: the Brazilian developer bubble attacks itself. The host argued that the loudest critics of programmers are programmers, and he built the episode around four examples from X, a Reddit post, and a live hacking demo.
The episode is entertainment first. The host repeatedly reminds viewers it is a humor show and tells the audience to check sources rather than trust YouTubers, so every story below should be read as the host's commentary on community events, not as verified reporting. Even so, the arguments it surfaces are real debates that show up across the developer community in Brazil and beyond.
Why the dev bubble keeps attacking itself
The host's core claim is that the developer bubble does not need outside enemies because it produces its own. He walked through a chain of public spats: a consultant who argued that IT departments are the biggest enemy of companies, a founder who mocked another founder for playing mobile games, and comment sections where developers tore into each other's specialties.
One exchange stood out. A content creator posted a lighthearted complaint about addictive mobile games, and a founder of the payments startup AbacatePay replied that founders who waste time on games should feel embarrassed. The reply backfired: dozens of accounts responded by calling the founder's own market a dead end, proving the host's point that everyone in the bubble is one post away from being the target.
The pattern the show describes matches how public tech arguments spread on X, where a niche disagreement between two accounts becomes a referendum on an entire profession within hours. The host's own conclusion was半 half joke, half diagnosis: developers do not like each other, and they especially do not like the parts of the field that look less like coding.
The Power BI fight: is business intelligence actually IT?
The sharpest debate of the episode started from a TV clip in which a professional said he worked in IT, then described building systems with sensors and reports built in Power BI, Microsoft's business intelligence and data visualization tool. Chat and commenters piled on, with many developers insisting that Power BI work is spreadsheet work, not software development.
The host ran a live poll during the broadcast on August 26, 2026: of 396 votes, 65% said Power BI work is not IT, and the chat settled on calling those professionals 'performatic Excel users.' The vote is audience sentiment from a comedy stream, not research, but it captures a real hierarchy inside the field.
The roles discussed in the episode sit on a spectrum, and conflating them is where most of the fight starts:
| Role | What it involves | Common criticism heard on the show |
|---|---|---|
| Backend developer | Server logic, APIs, databases | Believes BI reports are spreadsheets |
| Frontend developer | Interfaces in React and Next.js | Mocked by backend devs as 'not real programming' |
| BI analyst | Reports and models in Power BI, SQL, DAX | Called Excel work by both sides |
| Infrastructure / support | Networks, access, hardware | Forgotten until something breaks |
A more useful reading, which some chat members offered, is that business intelligence is an umbrella term: a person who only builds visuals is closer to an analyst, while one who writes SQL, manages data pipelines, and touches APIs is doing engineering work. The title matters less than what the person actually builds.
How Yuri Dev hacked a hospital system live on stage
The most technical segment covered a live hacking challenge at Codecon, a large Brazilian tech conference, where creator Yuri Dev was given 30 minutes to break a simulated medical system in front of thousands of attendees. He reached the final flag only after the timer, then published a full walkthrough on his channel.
The attack chain, as narrated in the video the host reacted to, followed a path that security professionals will recognize immediately:
- He fingerprinted the backend, identifying the Express framework behind the patient portal.
- He exploited an unvalidated file download route using a path traversal payload, URL-encoding the slash as %2F to bypass filtering, and retrieved an exposed
.envfile from the server. - The
.envcontained credentials and an internal-only URL ending in a non-routable TLD, so he resolved it by adding a hosts entry with the server's IP. - He brute-forced a four-digit 2FA code using the Intruder tool in Burp Suite, PortSwigger's web security testing platform, finding the code 8232.
- Inside the admin panel, a URL-fetch feature became an LFI via SSRF: reading
/etc/hostsrevealed a Docker network, and scanning it exposed an Elasticsearch instance on port 9200 with user records, including the final flag.
The host's takeaway was about the market, not the exploit: vibe coding with AI tools is producing software with more vulnerabilities, and penetration testing is one of the few specialties growing because of it. That claim is the host's observation from his own ecosystem, and viewers should treat it as such, but it aligns with the demo: five separate flaws existed in a deliberately vulnerable target built for the challenge.
The Reddit story: why developers need audit logs
The longest segment covered a post on the show's own subreddit, r/bar DoChurume, in which a freelance developer described being called back by a clinic network nearly a year after his contract ended. The company faced a cumulative discrepancy of about R$10.4 million in its financial reports, and he had built the system involved. The figures and the story come from the post as read on the stream and are not independently verified.
The developer had insisted on audit logging when he built the financial closing system: every reopening of a closed month recorded the user, timestamp, previous and new values, and the person who approved the change. He had also kept an email in which the finance director formally requested and authorized the reopening feature, the exact feature later used to pull revenue between months to hit targets.
When the fraud surfaced, the audit trail let him reconstruct who changed what and when, and the saved email protected him personally. The host's advice to viewers was blunt: when a requirement feels dangerous, document your objection in writing, log everything, and never let a single person request and approve their own changes. Separation of duties, not clever code, is what protected this developer.
Absurd requests, second jobs, and the state of the market
The lighter segments fleshed out the episode's portrait of working life in the Brazilian dev bubble. Viewers flooded the chat with the strangest things people asked them to fix after learning they 'work with computers': rural phone antennas, electric gates, satellite dishes, blood pressure monitors during a medical emergency, and one request to roll back a car's odometer, which the host correctly flagged as a crime.
On the job market, superchat messages described people working two or even three simultaneous remote jobs, with one viewer reporting R$45,000 per month across three positions and another saying he would not repeat the experience because of the mental load. The host refused to judge the practice but said openly he lacks the temperament for three daily standups.
He also read a viewer message about being reallocated because budget for third-party contractors was shifted to AI spending, and used it to repeat his recurring sponsorship argument: developers who skip fundamentals and rely only on prompt-driven tools become replaceable. Educational offerings mentioned on the stream included the Full Cycle software engineering MBA and security platform Solyd, both sponsors of the show.
What this episode teaches developers
Beneath the jokes, the episode lands on three practical lessons. First, audit trails and written approvals are career insurance: the developer in the Reddit story survived a R$10.4 million fraud investigation because he logged changes and kept the director's email, while colleagues who said 'log demais' were gone.
Second, internal gatekeeping about what counts as real IT is noise. The Power BI poll was entertaining, but the useful distinction is what a person actually builds and maintains, not the label. The same logic applies to the frontend-versus-backend rivalry the host says has faded as everyone became full stack.
Third, as AI tools like Lovable, a prompt-to-app builder, and Supabase, a Postgres backend platform, lower the cost of shipping software, the shortage shifts toward people who can secure and audit what gets shipped. That is the host's commercial framing, since he sells an engineering MBA, but the live hack at Codecon shows the security gap concretely. Communities that argue about labels, from Vercel frontend debates to BI-vs-dev fights, are arguing about identity while the real risk sits in unaudited production systems. Anyone in education around this space, from Gustavo Dev Doido's Bootcamp do Dev Doido to the Crazystack Typescript community at Crazystack, is essentially packaging the same answer the episode keeps circling: learn the fundamentals before the tools.
FAQ
- Is Power BI work considered IT? The Mano Rage Show audience voted 65% no out of 396 votes, but the debate misses the point. Building visuals is analytics work; building SQL models, pipelines, and API integrations in a BI context is engineering work. The tool does not decide the category, the scope of the work does.
- What vulnerabilities did Yuri Dev exploit in the Codecon demo? He chained five flaws in a deliberately vulnerable target: an unvalidated file download with path traversal, an exposed .env file, a brute-forceable four-digit 2FA code, an SSRF-enabled URL fetch, and an open Elasticsearch instance leaking user records. It was a staged challenge, not a real hospital system.
- Is working multiple remote jobs at once sustainable? Messages on the episode describe earnings up to R$45,000 per month across three jobs, but also burnout from three daily standups. The host declined to judge the practice and said he personally could not handle it.
- Why did the developer in the Reddit story avoid blame for the R$10.4 million gap? Because he had logged every reopening of closed financial periods with user, timestamp, and values, and had kept the finance director's email authorizing the feature. The audit trail identified who moved the money and the email proved the developer only built what was requested.
- Was the episode itself reliable journalism? No. The host opens the show's description by calling it gossip and telling viewers to check sources, and several stories were read from Reddit posts or chat messages without verification. Treat the episode as commentary on community debates, not reporting.
Turn your own dev stories into an article
The Mano Rage Show works because its stories, the audit trail that saved a developer, the hack on stage, the Power BI war, carry lessons that disappear once the stream ends. If you have the same kind of knowledge trapped in your own videos, interviews, or live sessions, that insight deserves a written form people can search and cite.
You can turn that existing material into a structured article with Skala Blog: paste a YouTube URL, get a transcription, and generate an article you review before publishing.
The same video that fuels a two-hour rant can also become the reference post someone finds a year later.
Fork this article
Start a new branch from the same video, shaped your way. You keep the credit; the original keeps the attribution.
A fork in another language is filed as a translation of this article, so the two pages point at each other. You can unlink it later from the editor.
0/240
You are creating
- Format
- For
- Language
- Source
- Your angle
You will be asked to sign in before it is generated.
Buy credits