the most powerful quality is the most human
enforce best practice
when, why you should enforce best practice..
essay: a case for active learning
an essay I wrote for a presentation I did in an institution
essay: stop manufacutring plastics
a little essay I wrote a while ago
design first program later
some guidelines for effective software development
english is not the easiest language
duplicate letters, words that are both verbs and nouns, overdependence on special-cases.
telegram bots as an editorial user interface
cool little idea I used in a recent project
never dream big
some thoughts about figurative dreams
documentation must available offline and in the command line
A common annoyance I experience when interacting with a new programming language is online-only documentation.
Most [programming] languages these days do not come with offline documentation by default, which really annoys me since it’s benefits are plenty and cons are virtually none.
Documentation should always be available offline and in command line form, online copies could exist. But the default must be offline, for the following reasons:
- It’s always available
- It’s easier to reach
- It’s fast
- Format your docs however you like
- Powerful filters via unix pipes
Take for example php, php has no offline documentation. AFAIK it does not have it as a command line utility or as a gui, which is really disappointing. You have to get a copy of their website offline and view it via your browser, which to be frank is too much effort.
free ssl with lego 🔒
how to get free ssl with lego