The Principal Engineer's True IDE
Description
A three-panel comic strip meme in the 'Boardroom Suggestion' format. In the first panel, a manager at a conference table asks his team, 'What program do principal engineers code in?'. In the second panel, two employees offer standard answers: 'Visual Studio' and 'Vim'. A third, slouched and bored-looking employee chimes in with 'Jira'. The third panel shows the manager with an angry expression, followed by an external view of the office building as the third employee is thrown out of a window. The meme humorously and cynically points out a common reality in the tech industry: as software engineers advance to very senior roles like Principal Engineer, their day-to-day work often shifts from hands-on coding to architectural planning, mentorship, and project management, which means they spend a significant amount of time working in project management software like Jira rather than in a traditional code editor or IDE
Comments
15Comment deleted
A principal engineer's main function is to translate business ambiguity into Jira tickets with enough technical jargon that both sides feel understood but neither is accountable for the outcome
Career progression decoded: Junior picks a text editor, Senior picks a language, Principal picks which JIRA filter counts as “coding hours.”
The painful truth about principal engineers: they've transcended mere IDEs and text editors to achieve enlightenment through the sacred art of moving tickets across swimlanes while their muscle memory for actual coding slowly atrophies into phantom keyboard shortcuts
The tragic career arc of every principal engineer: You spend years mastering vim keybindings and IDE shortcuts, only to discover your primary development environment is now Jira's rich text editor, where Ctrl+C doesn't even work half the time. Your most complex 'code review' is now parsing whether 'blocked' means actually blocked or just 'I haven't started yet,' and your biggest architectural decision is choosing between 'High' and 'Highest' priority. The real kicker? You're still expected to be the technical authority, but your last meaningful commit was three sprints ago, and it was updating the README
Principal engineers don't code in Vim - they refactor Jira epics until the velocity chart looks optimized
At Principal level, your IDE is Jira, your language is JQL, and your CI/CD is a calendar invite
By the time you hit principal, the hot path isn’t your vimrc; it’s a JQL query - most diffs are rewritten as roadmaps and merged in steering committee
no matter how many features you have created. the main thing is how many tickets you moved to the status completed 😔 Comment deleted
I use Slack at least twice more than IDEA at work Comment deleted
another crypto ad ? Comment deleted
Removed that spam Comment deleted
This is not true at all, programmers at staff+ level don't even touch Jira with a stick Comment deleted
What do they do then? Just coding? Who is responsible for tracking their tasks? Comment deleted
Coding?? No, the only thing they code in is Google docs/sheets. Comment deleted
EMACS!!!!! <3 Comment deleted