dittonedo

Seems lovable

I think for a person to understand programming better they must learn as many programming languages as they can. Each and every language has something to show in terms of (software programming technologies).

Perl taught me to use and appreciate regular expressions.

C it taught me how to be cautious when working with pointers, how to use external libraries. It also taught me an art of not-wasting memory, by passing by references that values. This made me to love variable mutability better.

Lisp (Common Lisp) taught me the power of creating functions at runtime. The power of (lexical scopes although I was also shocked recently to some other dialects that use dynamical scopes) and Emacs lisp which allows a programmer to switch to their preferred ones.

Python and Java, object orientation. With Python teaching me rapid prototyping. They also taught me about exceptions.

Lua taught me an amazing world of generators (coroutines). That made me to appreciate Python iterators. I was surpised that on many of the languages I mentioned above a could actually yield a closure. I love the ideas of pcall.

There are also languages like vimscript, javascript and many others I tried them to be taught some software programming "technologies". These technologies exist in often many languages, whats crucial is to understand those technologies and you will be at a level to nearly " grok" anything you want in programming.

Merely learning one language, makes you prone to blurb paradox!

I just wonder why can't hackers write homoiconic (if thats the word), languages that get array tokens and provide results like so. I often wonder what if sqlite was also designed to have its statements like ('select '* 'from 'table), it would also had been better for third part libraries, to implement their orms.

Since all of this (byte coding) (AST) is done by almost many programming languages I ever explored (Python,Ruby, lua, ...). It would have been awesome, if they were easily parse-able I guess.

Most of the ORM implementations are very error prone to those design decisions. (Especially SQL databases).

I had been addicted to Github's "green" dots. I hate being an addict, hence I programmed this program. It shows some colouring on days with "git commits" for any specified git repo.

You can change the year ranges, at the bottom of the calendar.py file. Seems better than Github's "Green" dots for me.

Fork it and improve it if you interested.