I spend most of my computing life in the Shell (command line, terminal or whatever you want to call it on your platform of choice). This can be a bit challenging, though, when I need to work with large groups of other people, especially in big enterprise companies that \u2014 well \u2014 use anything but the Shell.\nThe problems that crop up are made worse when other people within your company use a different platform than you. I tend to use Linux. If I\u2019m doing a lot of my daily work from a Linux terminal and the bulk of my co-workers use Windows 10 (entirely from the GUI side), things can get \u2026 problematic.\n\nLuckily, over the past few years, I\u2019ve figured out how to deal with these problems. I\u2019ve found ways to make using a Linux (or other Unix-like systems) Shell much more doable within a non-Unix, corporate environment. These tools\/tips apply equally well for SysAdmins working on a company\u2019s servers as they do for developers or marketing people.\nCommand line tools for working with non-Linux users\nLet\u2019s start by focusing on the two areas that seem to be the hardest to solve for many people in big companies: document compatibility and enterprise instant messaging.\nDocument compatibility between Linux and non-Linux systems\u00a0\nOne of the biggest issues that crops up is that of simple word processing document compatibility.\nLet\u2019s say your company has standardized on Microsoft Office. This makes you sad. But do not lose hope! There are ways to make this (mostly) work \u2014 even from the Shell.\nTwo tools are critical in my arsenal: Pandoc and Wordgrinder.\nWordgrinder is a simple, straight-to-the-point word processor. It may not be as full-featured as LibreOffice (or, really, any major GUI word-processing application), but it\u2019s fast. It\u2019s stable. And it supports just enough features (and file formats) to get the job done. In fact, I write the majority of my articles and books entirely in Wordgrinder.\nBut there\u2019s a problem (you knew there had to be).\nWordgrinder doesn\u2019t support .doc (or .docx) files. That means it can\u2019t read most files that your Windows- and MS Office-using co-workers send you.\nThat\u2019s where Pandoc comes in. It\u2019s a simple document converter that takes a wide range of files as input (MS Word, LibreOffice, HTML, markdown, etc.) and converts them to something else. The number of formats supported here is absolutely phenomenal \u2014 PDF, ePub, various slideshow formats. It really makes converting documents between formats a breeze.\nThat\u2019s not to say I don\u2019t occasionally encounter formatting or feature issues. Converting a Word document that has a lot of custom formatting, some scripting, and an embedded chart? Yeah, a lot of that will be lost in the process.\nBut in practical terms, the combination of Pandoc (for converting files) and Wordgrinder (for document editing) has proven quite capable and powerful.\u00a0\nCorporate instant messaging between Linux and non-Linux systems\u00a0\nEvery company likes to standardize on an instant messaging system \u2014 something for all employees to use to keep in real-time contact.\nFrom the command line, this can get tricky. What if your company uses Google Hangouts? Or how about Novell GroupWise Messenger? Neither have officially supported, terminal-based clients.\u00a0\nThank goodness, then, for Finch & Hangups.\nFinch is sort of the terminal version of Pidgin (the open-source, multi-protocol messenger client). It supports a wide variety of protocols, including Novell GroupWise, (the soon to be dead) AOL Instant Messenger, and a bunch of others.\u00a0\nAnd Hangups is an open implementation of a Google Hangouts client \u2014 complete with message history and a nice tabbed interface.\u00a0\nNeither of these solutions will provide you with voice or video chat capabilities, but for text-based messaging, they work delightfully well. They aren\u2019t perfect (the user interface of Finch takes some getting used to), but they\u2019re definitely good enough to keep in touch with your co-workers.\u00a0\nWill these solutions allow you to spend your entire work day within the comforts of a text-only Shell? Probably not. Personally, I find that (with these tools, and others) I can comfortably spend roughly 80 percent of my day in a text-only interface.\u00a0\nWhich feels pretty darn great.