1、Ubuntu 中的几个有趣的命令
1.1、sl 命令
(1)首先安装sl
sudo apt install sl
(2)然后直接输入sl,就会出现一辆动态的火车头
1.2、cmatrix 命令
(1)安装cmatrix
sudo apt install cmatrix
(2) 输入cmatrix,会出现流星雨
(3)还可以加上-C 参数,后面加上颜色,可以把流星雨的颜色改变
cmatrix -C blue
cmatrix -C black
cmatrix -C red
1.3、oneko 命令
(1) 安装oneko
sudo apt install oneko
(2) 直接在Ubuntu中输入oneko命令,不要在远程工具(Xshell,Putty,SecureCRT等输入),会出现一只动态的猫。
2、Python之禅
In [1]: import this
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
翻译:
优美胜于丑陋(python 以编写优美的代码为目标)
明了胜于晦涩(优美的代码应该是明了的,命名规范,风格相似)
简洁胜于复杂(优美的代码应当是简洁的,不要有复杂的内部实现)
复杂胜于凌乱(如果复杂不可避免。那代码间也不能有难懂的关系,要保持接口简洁)
扁平胜于嵌套(优美的代码应当是扁平的,不能有太多的嵌套)
间隔胜于紧凑(优美的代码有适当的间隔,不要奢望一行代码解决问题)
可读性很重要(优美的代码可读的)
即便假借5特例的实用性之名,也不可违背这些规则(这些规则 至高无上)
不要包容所有错误,除非你确定需要这样做(精确地捕获异常,不写 except:pass 风格的代码)
当存在多种可能,不要尝试去猜测
而是尽量找一种,最好是唯一一种明显的解决方案(如果不确定,就用穷举法)
虽然这也不容易,因为你不是python之父(这里的dutch是指guido)
做也许好过不做,但不假思索就动手还不如不做(动手之前要细思量)
如果你无法向人描述你的方案,那肯定不是一个好方案;反之亦然(方案评测标准)
欢迎大佬们扫下面二维码关注我个人微信公众号(Java大数据架构师成长之路)