You can do the same thing with your own habits. Once it’s clear I’ll be doing it again and again, I know it’s worth the time to put a solution into code. When automating things in ops work, I watch what operations I do more than a couple of times, make notes on what I did, and put those on a list of likely script ideas. What else should you put in your beautifully customized new file? Let’s start with aliases. Run source ~/.bash_profile once you’ve saved your changes, so they’re live in your terminal (or just close your terminal window and open a new one). If you use a Mac, though, use ~/.bash_profile. This post gives a rundown on the purposes and tradeoffs of the two files. With a little observation of your terminal habits (and a little knowledge of Bash, the command language used in many terminals), you can put all kinds of things in here that will make your life easier. This file exists under several different names, depending on your OS and what you’re trying to accomplish, and it can hold a lot of things that can make your life easier: shorter aliases for common commands, your custom PATH, Bash functions to populate your prompt with environment information, history length, command line completion, default editors, and more.
We’ll start with possibly the most powerful one: meet ~/.bashrc and ~/.bash_profile. There are lots of ways to customize your command line prompt and terminal to make you more efficient at work. The good news is that developers can also learn a few tricks from the land of ops to make their days easier and their work better. Those same job posts often ask for automation skills, which is a positive way of asking for someone who’s professionally lazy in a way that results in efficiency. And all of it can help you work more efficiently and effectively.īash (a term used for both the Unix shell and the command language I’ll be using the second meaning in this post) is usually a skill mentioned only in job descriptions for site reliability engineers and other ops jobs. You can make it speak shorthand only known to your terminal and you. What you type into the command line can tell you about environment variables, hidden configs, and OS defaults you never knew about. An elaborate prompt can mean someone digs deeply into optimizing the tools she uses, while the information it contains can give you an idea of what kind of engineering she’s done.
0 kommentar(er)
