Posted onApril 24, 2017
CommentsLeave a comment
I just started to learn how to boost my productivity skill making some tasks faster and faster not by quality reduction, but by routine reduction.
It’s thought that I don’t know any text editor as a usual developer should know. I’ve got a choice between emacs, Sublime Text and vim. I can’t describe why, but I tried vim. May be because of enhanced command choice and full keyboard use.
At the middle of 2010`s cloud infrastructure became necessity for software infrastructure. There is a huge trend to move a hardware maintenance from local datacenters to the cloud.
Many people think that the problem of application performance, security and networking lies in supported services. Like Nginx is proxying too slow or remote DBMS cannot see my network. Frequently the problem in OS. Default values of system settings can restrict our environment to make the service jobs quick and simple. The best way to change your system configuration – change the system variables.
In first steps young DBA can greedily soak up all kinds of database knowledges: as RDBMS as NoSQL. We’re realising things like how table index works, how to optimize memory caching, write triggers and procedurs etc.. But we still can forget a simple command to create user or show tables list. Also we can get stuck when switching from MySQL to PostgreSQL or whatever else, cause command syntax is different.
File ~/.bashrc is a simple configuration of Linux user where user can describe all shell instructions necessary for each session. It’s a frequent practice to leave useful command at this file, but aliases and functions looks much more suitable for this configuration file.
iptables is Linux firewall standard. You can easily open and close network connections through it. Actually it’s pretty easy, but sometimes we can’t remember any flags and commands to create firewall rules. Here is a cheatsheet table constituted by all necessary iptables rules for novices. I’ll try to update it once in a while.
If you totally get to the bottom of Linux shell – you’ll agree that it’s a powerful environment. Understanding of things like text manipulators, system utilities etc. makes a great deal in operations performance. But sometimes we have a desire to simplify command line toolkit. Days go by and we’re starting to notice that some mechanisms could be better. Command history search is complicated. “du” scrolling doesn’t show up a descriptive filesystem usage statistics. And sometimes instead of command line we’re picking GUI programs. Despite of we know this way as less productive.
Linux terminal includes myriad of opportunities by default. But sometimes we can’t figure out how to execute any operation easier. From scratch we tried to parse enourmous logs by eyes or use graphical instruments when it’s not necessary. Another problem – we’re forgetting how to type any helpful command we need. Thus there is one way to scroll Google and read the same forum branch we did before. So, it would be better to have a petty prompt with command syntax we really need. It’s useful as on the tab of your document application as well as pinned to the wall in your room.