αbout me

Innate fathomless curiousity made me a voracious reader and avid knowledge gatherer as I can remember myself. Initially it was just a knowledge thirst and fun aquiring them, a bit later I commenced a conscious approach to learning and found an urge necessity for meta-learning: skill that allows to study any subject much effective.

After acquisition of these skill, when I've learnt how to learn, naturally loomed the next challenge:

What should I know to be healthy, wealthy and wise?

Soon it became clear to me I should know everything for that and it is just impossible due to infinite amount of knowledge. So I need to find a trade off, a some hack which allows me to be happy enough to live and prosper. And I choose to study Computer Science that by definition ought to amplify my ability to sift, put it in order and consume information. And, as an inevitable catalyser, model thinking was a right tool in the hands. Furthermore these skills will liverage my capability to acquire the knowledge much faster.

Further, pondering in this direction pointed me out Python as the main tool to cope with a plethora of Data, Emacs as the powerful enough tool to cope with Python, Bash, computer and me in the same time. A mammoth task was to find a clue to myself, elaborate the right system in learning, all that left required only time and patience.

Several years I've spent studying these mighty tools, from time to time practicing in applied areas, making pauses for contemplation, and now I'm proud that I've forge another person from myself, and seems it is very time to help other.

βrief overview

Python deliberately sliced and diced in Emacs - this dish is for gourmets and connoisseurs only. More than 30 years experience in applied programming, more than 10 years of acquaintance with Python allow to define me on the expert level, and seems like I literally am a programming adept!

γist

Linux

I've installed my first Linux distro (it was RHEL4 from CD which I've serendiptiously bought on the flea market) in 2007. And it was acute and palpable sensation from obtaining a freedom from proprietary OS. Later were Ubuntu and Debian in the different shapes, CentOS, AltLinux, Gentoo, DamnSmallLinux, Fedora, PuppyLinux and even i386 Porteus as a portable version of my favorite OS on a 512M USB-stick.

Naturally it was easy to me to switch on the cloud infrastructure provided by Amazon Web Services. I've commenced to utilize EC2. And it was 2011.

Now I use Chrome OS on my HP ChromeBook with Debian BullsEye out from the box.

Emacs

My first aquaintance was in 2011 and in that moment, due to the lack of experience, it repelled me by its weirdness and complexity. Later, than I've got enough adventures with other IDEs, the obvious thought strikes me:

All these commercial IDEs are use the mouse as a main tool to handle the code. And the mouse has only two keys on it. On another hand, Emacs uses a keyboard with at least 104 keys on it.

The advantage is obvious: if you are a touch typist (and I was since 2008) it should be much convenient to use a keyboard to manage your routine tasks around software development. It has a lot of keys on it, and your fingers are able to remember these keys to use them fluently.

Python

Initially I met Python code snippet around 2010 and the first impression was utterly astounding and overly enchanting:

It was like you've finally met a well-known, but occasionally forgotten by you, version of algorithmic language with additional faculty to understand you on the fly.

All in Python was familiar to me, and multiplied by 100 by unnamed magician who are unfathomably brainy. Yes, the lists is a perfect idea, and innate methods to handle them are just a deft and obvious approach to liverage its power. It was a pure rapture there, and now, more than 10 years later, it becomes clear - it barely is an incessant rapture.

All that I only dreamt on to have in my hands as a flexible and powerful tool to rule machines, - all this it has already inside.

Δesired role

  • A synergy among the team is not just only a sum of knowledge, our goal is to obtain its product literally:

    \(\displaystyle\sum_{n=1}^{team}\sum_{k=1}^{skill}\to\prod_{n=1}^{team}\sum_{k=1}^{skill}\)

  • In other words the desired aim should be a knowledge multiplication: sustainable state of continuous intellectual advancements for each collaborator in particular;
  • I see myself in the team of professionals with mostly contiguous skills;
  • Right now for professional growth I'm crucially need in knowledge exchange: who knows something fascinating and would share it with me, please?
  • I would be a team catalyst, accelerator and propeller. Who next will fall in love with Emacs and Python simultaneously?

εmacs

The rule of thumb is: the tough task split requires a handy and mighty tool in your hand. Mighty tool demandss a lot of time and patience to become handy.

All tasks are tough enough to be cracked by mighty tool in several deft gestures; most of the people haven't time to learn any potent tool and spent all theirs lives tinkering around the shallow tasks in attempts to resolve them by what they have in theirs disposal - a set of rude but simple tools with limited functionality but with low entry threshold.

μotto

Synergy → the interaction or cooperation of two or more organizations, substances, or other agents to produce a combined effect greater than the sum of their separate effects:

\(\displaystyle\sum_{n=1}^{team}\sum_{k=1}^{skill}\Rightarrow\prod_{n=1}^{team}\sum_{k=1}^{skill}\)

Σkills overview

Λife long learner

with Double Loop Learning approach in my disposal at least 25 years.

εmacs

dressed with ELPA/MELPA packages galore

∏ython gently preliminarily cooked in Emacs:

  • Built-in functions test suite
  • Cookbook in a TDD dissection
  • OOP design patterns scrutiny


blog comments powered by Disqus

Published

13 October 2016

Categories

Emacs Python Literate Programming

Tags