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

Life using the Linux operating system exclusively for the last few years

Above: my Linux desktop layout. Back in 2017, I switched my operating system entirely to Linux. In case anyone is wondering, here is what I experienced over the last few years. Others I interact with have no idea I'm on Linux. For example, if someone emails me an MS Word document that I need to complete, I simply open it with LibreOffice (an open-source word processing program that is pre-installed on most Linux systems), edit the document as needed - which is very easy since the same sorts of functionalities are available in LibreOffice - and then I can save it in MS Word format and email it back. Likewise, if I'm on a Zoom call, everything works just the way it does on PC and Mac. Zoom makes their application available for Linux too, I downloaded it and let it self-install, and it works exactly the same way as it does on other operating systems. I can point-and-click my way to whatever I need to do on Linux; no special knowledge required. If you want to dig deeper into script...
Read more

Correct usage of unwind-protect and with-open-file in Lisp

Learning to use unwind-protect in Lisp typically crops up very early on when you're first learning the language. In fact, anything to do with I/O is going to be something you'll need to know early on. Yet unfortunately, I find that unwind-protect is not explained sufficiently well for a beginner to understand not just how to use it correctly, but why and when . Grappling with this myself, I found that hands-down the best explanation came from this YouTube video from Baggers: Luckily, in the case of file handlers, LISP already assumes you'll want to open a file with unwind-protect, so it provides the with-open-file macro for this exact purpose. It closes the file handler for you with a built-in unwind-protect. This is an advantage over manually opening and closing your file handlers, because if your program opens the file but never gets to the part with the close command (for example due to a run-time error in between those stages), the built-in unwind-protect make...
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.