People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.
Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.
The simplest way to add an alias for a specific git command is to use a standard bash alias.
# .bashrc
This post also appears on lisper.in.
Reader macros are perhaps not as famous as ordinary macros. While macros are a great way to create your own DSL, reader macros provide even greater flexibility by allowing you to create entirely new syntax on top of Lisp.
Paul Graham explains them very well in [On Lisp][] (Chapter 17, Read-Macros):
The three big moments in a Lisp expression's life are read-time, compile-time, and runtime. Functions are in control at runtime. Macros give us a chance to perform transformations on programs at compile-time. ...read-macros... do their work at read-time.
| Taken from: https://hackerlists.com/hacking-sites/ | |
| 22 Hacking Sites, CTFs and Wargames To Practice Your Hacking Skills | |
| InfoSec skills are in such high demand right now. As the world continues to turn everything into an app and connect even the most basic devices to the internet, the demand is only going to grow, so it’s no surprise everyone wants to learn hacking these days. | |
| However, almost every day I come across a forum post where someone is asking where they should begin to learn hacking or how to practice hacking. I’ve compiled this list of some of the best hacking sites to hopefully be a valuable resource for those wondering how they can build and practice their hacking skill set. I hope you find this list helpful, and if you know of any other quality hacking sites, please let me know in the comments, so I can add them to the list. | |
| 1. CTF365 https://ctf365.com/ |
| ### Basic ### | |
| # The directory to store the downloaded file. | |
| dir=${HOME}/Downloads | |
| # Downloads the URIs listed in FILE. | |
| input-file=${HOME}/.aria2/aria2.session | |
| # Save error/unfinished downloads to FILE on exit. | |
| save-session=${HOME}/.aria2/aria2.session | |
| # Save error/unfinished downloads to a file specified by --save-session option every SEC seconds. If 0 is given, file will be saved only when aria2 exits. Default: 0 | |
| save-session-interval=60 | |
| # Set the maximum number of parallel downloads for every queue item. See also the --split option. Default: 5 |
| Basic | |
| ===== | |
| [Shift]+[Mod]+[Enter] - launch terminal. | |
| [Mod]+[b] - show/hide bar. | |
| [Mod]+[p] - dmenu for running programs like the x-www-browser. | |
| [Mod]+[Enter] - push acive window from stack to master, or pulls last used window from stack onto master. | |
| [Mod] + [j / k] - focus on next/previous window in current tag. |