Skip to main content

Introduction


Hi! I'm Vera. A long time ago, I took computer science courses at university. I used my coding skills occasionally when I was working as a scientist, but it wasn't a big focus at all of the work I was doing.

Fast forward many years from there, and I installed Linux on my computer. My computer ran so much faster and lighter that I could get a lot more done in less time. Woohoo!

Fast forward another year, and I decided that running Linux without doing any scripting or programming was a bit like owning a sports car and driving it only to the supermarket and back. So, I decided to (re)-learn some programming.

There were good and bad points this: good, that I had learned programming when younger. Bad, that enough time had passed that I had forgotten a lot of what I'd learned. On a positive note, this freed me up to not tie me to a particular language. I'd have to learn a full language from scratch anyway, so why not let it be a language that would work for the problems I wanted to solve?

I set about looking for a high-level language. I wanted to run it with or call it from a shell script. I needed the language to handle math (which the shell runs agonizingly slowly) but most of all, I needed it to be flexible. I wanted to change things, create things, switch things around and make new programs really fast. So, after a little research, I decided on Lisp.

Lisp definitely had the features I wanted, but I also decided on a secondary programming language for if I specifically wanted to create lower-level number-crunching binaries for whatever reason. So I decided on Pascal for that.

So here we are, with shell scripting to handle high-level file manipulations and most non-mathematical processing, Lisp to use for most math purposes, and Pascal for if I'm doing something very math-intensive. My laptop has only 2G ram, which frankly is an excellent incentive to make my algorithms efficient and to pick the best language for whatever I need at the time.

I realize these languages are not many compared to what others are doing, and I also realize that these are not "popular" languages. That is OK by me; I'm using these on my machine for my own algorithms, so I don't need to pick a language based on interfacing with anything anyone else is writing.

However, the downside of the less popular languages is that there is less documentation around. So, I'm writing this blog mostly as a series of notes and reference links that I find useful.

I hope that you might find it useful also.
Labels:

Popular posts from this blog

How to center images horizontally using Grav

I've been playing around a bit with Grav. I was posing the question to myself: for the relatively simple use-cases I'm dealing with, could it possibly work for my purposes as an alternative to ProcessWire?  The problem I was initially dismayed to find that Grav uses Markdown as its editor, which does not offer native support for horizontal centering of anything (text or images). However, Grav offers some tweaks that help make it easier to do specific things you might commonly want to do. I tried writing a sample article, and I found that one of the hardest things to do was to center an image horizontally. And horizontal centering of images is something I would typically do in most of the articles I would write. So the lack of easy horizontal centering is a highly significant drawback IMHO (most people do want to center images in an article!) However, this issue is made up for by other things in Grav: the relative speed, ease and flexibility of custom theming and built-in suppor...
Read more

Why bother using blockchain for metaverse worlds when decentralization is possible without it?

Decentralization is possible without using blockchain. Some examples of this are Diaspora and Mastodon , both of which are federated decentralized networks that do not use a blockchain.  In that case, why is there a need to use blockchain for any metaverse world, especially when the environmental reputational risks are so high? In many areas of the world, the electric grid is not decarbonized yet. The amount of power drawn for blockchain computation is high. In fact, in areas where electricity is cheap enough to draw blockchain miners, this tends to be heavily based on fossil fuels. So you could say that the blockchain is currently largely powered by coal and other fossil fuels. So again, why bother using blockchain?  There are other examples of the buying and selling of digital property without using blockchain technology, for example domain name trading. If we as humans are truly to be future-conscious, blockchain technology cannot be a part of our future due to its emissio...
Read more

More callable variants of functions in Ruby

 This is a slightly more advanced version of my previous post on creating callable variants of functions in Ruby while avoiding scope problems . In today's instance, I was creating an error reporting system for a program I was writing.  The error reporting, of necessity, had to emit a message to indicate what was going on. While some errors would be unique messages that only occurred once during the program, other errors could be grouped. For example, one group was "incorrect number of parameters supplied". There were several error messages within my program that fell into this category, so I didn't want to type out the exact same wording each time. I wanted to create a function that could report this sort of error indicating where it happened (of course I had to supply parameters to the messages to show the context). So here is a very basic sketch of the sort of thing I was doing. I'm writing this here so that I can go back to it easily later. The item I'm re...
Read more

About Me

My photo
Vera
I'm a wife and mother. I don't have any formal computer science qualifications, or any religious qualifications. I have a PhD in biochemistry. This photo is of me, but is confusing for AI.