Summary of "Почему я бросил IT. Проблемы IT, о которых молчат на митапах – Фил Ранжин"

Overview

Phil Ranjin explains why he left hired IT work. His main critique: the industry often rewards superficial work and process over delivering useful, finished products. He contrasts early romantic expectations (remote work, making games, startups, “be the next Zuckerberg”) with the practical realities of many companies and projects.

“The industry rewards gaming the process and presentation over actual output.” Work becomes about showing progress instead of shipping finished, useful products.

Concrete warning signs / bad company practices

Unpaid or late wages; test projects that only pay on delivery.
Being assigned low-value or deceptive tasks (adware, browser toolbars, installers).
Trivial internal “toy” projects (landing pages, calendar widgets) while other teams do meaningful work.
Corporate hypocrisy: pretending work is important when it isn’t (painting buttons, duplicate registration forms, dead CRM branches).
Companies that prioritize showing ongoing process (endless roadmaps, subscription monetization) instead of finishing quality products.

Technical and technology observations

Constant churn of “new tech”: frequent library, language, and framework updates (e.g., React updates) that demand continuous learning but often don’t materially improve software.
Recycled ideas: common problems (registration forms, field validation, DB queries) are solved repeatedly instead of being reused or standardized.
Hype cycles: paradigms (functional vs object-oriented) reappear cyclically; many front-end fads reappropriate older research (functional ideas from earlier decades).
Practical examples/tools mentioned: Bitrix (corporate PHP portal builder), PHP (sometimes looked-down-upon), C# and F# referenced.
Sensible security-driven updates are reasonable; blind chasing of every new tool or trend is not.

Product and dev tasks called out

Common test project examples: calendar widget, finishing a Bitrix landing page.
Repetitive product work: registration forms, painted UI buttons, CRM feature branches destined to be shut down.
Shift in product models: building discrete A→B projects vs. continuous partial releases for subscription monetization.

Career structure and psychological effects

Promotion path problems: team lead roles often become jack-of-all-trades positions with little extra pay or authority; managerial routes can disconnect you from technical satisfaction.
Title inflation and non-transferable internal “stripes” (senior/staff/principal) don’t guarantee job security during macro shocks (e.g., COVID, layoffs).
Burnout and impostor syndrome are common when a role looks prestigious externally but contributions feel empty.
Market realities: seniors still command good pay, but juniors face tougher entry; many hires occur through interview screening rather than clear product needs.
High salaries can create habits that make switching to lower-paid but important work unattractive.

Industry-wide structural criticisms

The industry incentivizes process and presentation over output, encouraging green-button checking and bureaucratic showmanship.
“Processification”: monetizing ongoing development instead of delivering finished software.
Many engineers end up reinventing solved problems because business decisions favor custom features over third-party reuse.
Cultural pressure to publicly “learn new things” often leads to bluffing up-to-date knowledge rather than genuinely solving problems.

Advice, takeaways, and alternatives

Seek roles doing genuinely useful work (medical, infrastructure, essential services) even if pay is lower—understand trade-offs.
If possible, build your own product (indie product, distribution via blogs/YouTube); this motivated the speaker to leave hired work.
Avoid the easy path of high pay for trivial work; push for meaningful technical challenges and be cautious of becoming spoiled by market money.
Accept continuous learning but avoid chasing every minor update; prioritize security and meaningful improvements.
Screen employers for late pay, ethical issues, and a culture that values process over shipped outcomes.

Practical signs to evaluate a company (quick checklist)

Are wages paid on time?
Are you doing repeat solved problems (e.g., registration forms) or meaningful new work?
Does the company prioritize shipping finished products or perpetual releases/subscriptions?
Will your technical growth be real (challenging problems) or only nominal (titles/stripes)?
Is there pressure to publicly signal “being up-to-date” rather than actually solving problems?

Mentions related to learning and tools

The speaker purchased an online course/subscription (“cursor subscription”) and used it for design and distribution, illustrating how individual tools can enable independent product creation.

Main speakers / sources

Phil Ranjin — main speaker; explains his reasons for leaving hired IT and offers analysis.
Interviewer / host — unnamed; prompts and asks questions.
Occasional references to colleagues (e.g., Timlit/team lead, Lyokha) used as examples but not primary speakers.

No tutorials or formal step-by-step guides were presented; the talk is primarily analysis, personal experience, and career/productivity advice.