Blog of Sara Jakša

Why Writing Add-ons is in Some Way Simpler

I have recently tried to figure out, how to make a non-obtrusive popup in one of the add-on that I have been writing. I was in luck, as something like that had already been implemented in the program itself.

All I needed to do what figure our when does it appear, find the function that is at work in the same and check what function or group of functions does it call. It ended up being a single function:

    tooltip(string)

When I actually checked, what would I needed to do, if it was not implemented, it look quite a lot more complicated. There was 28 lines of code with mixture of qt signals, timer, changing global variables and even some html and qt element properties to make it look more pretty. Not that complicated as a whole, but compared to a single line, it is.

I believe that similar thing most likely happens when using frameworks or libraries. I don‘t even want to think about what would I do, if I needed to program myself all the statistical element, that came prepackaged in R. Or if I actually needed to program all the website handling that frameworks like sinatra or fat-free framework take care of it themselves.

Even something like choosing a random number would be a pain in the ass without the already implemented solutions like:

    random.randint(a, b)

All of these things make it more possible for the people without a extensive practice or formal education, like me, to still play around and enjoy the working of a code. On the other side, it this making us less willing to actually go into the code and master it? And how many programmers do we need that are the top masters, and how many would simply benefit from being able to string something together?