
Original screenshot by Kai
Have you ever wondered what phone number you should get? Have you ever wondered what your phone number might spell? … Well, I had to dive into this since I’ve been thinking lately of ditching my current Telecommunication Service Provider for another one – seeing that another TSP charges less and provides longer validity.
Now, when people here in Kuwait decide to get a new phone number, the majority goes for what they call “golden lines”: phone numbers that contain as few different digits as possible and as structured as possible (e.g. xxxyxxxy). The only problem with those numbers is that they are extremely expensive – some reached above 1000KWD! But honestly, even if they were not as expensive, let’s say as cheap as the regular phone numbers, I wouldn’t be that interested.
However, what interests me is phone numbers that actually spell words; phonewords; vanity numbers (e.g. xyz-NUT). This is uncommon in here, in fact, I’ve yet to meet someone that spells his phone number! Objectively, I dislike this fact, but subjectively, I love it; it means we, those who seek phonewords, have a greater chance to get what we want! … That’s why I had to know what numbers some great names would correspond to on dialpads.
At first, I grabbed my phone and manually translated the words I had in mind. All one has to do is looking up the corresponding number of a letter on a dialpad. GNU:468; linux:54689; debian:332426; ubuntu:828688; python:798466. However, upon finishing that, a bunch of other names came to my mind. I couldn’t take it, so much unnecessary effort has been put. I decided to write a script.
If you wish to continue reading the post, click this link!
Posted in Diary, Programming, Python
Tags: Arabic, dialpad, English, filter, keypad, permutations, phoneword, possibilities, python, script, translate, unicode, utf-8, vanity number, wordlist
Writing Code in a Professional Manner
•February 5, 2015 • Leave a CommentINTRODUCTORY PROGRAMMING CLASS DISCUSSION BOARD ARTICLE
“Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live. Code for readability.” – John F. Woods
In order to have your code respected and appreciated, it need not only to be efficiently programmed and well constructed but also well written and well formatted! Yes, not having bugs is essential and of primary importance; however, what good would it be if it can only be poorly understood, barely maintained, or hardly developed?! A professional programmer always keep the code clean, formatted, and well commented.
… Though one may question these factors as how their style is made or picked. Well, there are conventions and defined styles for almost everything: variable and function naming, indentation, and even commenting. When programmers worked on large projects, they’ve noticed that abiding a convention or a standardized style always ease up the development process and understandability of code written by different coders.
Continue reading ‘Writing Code in a Professional Manner’
Posted in C, Class discussion board articles, Programming, Ranting
Tags: C, camelback, camelcase, casing, commenting, documentation, indentation style, programming style