Doing something

 Kind of realized that some times, doing something can distract you from getting something done.

I had decided that I needed an interface then found the INumber generic interface. However, I still hadn't done the work to decide what I needed or how I was going to make it work.

So, lets do that now.

What is a number. It is a value, a quantity. Mathematicians have determined that these values have certain properties, main among them, that they can be discussed in a meaningful way separate from the object that they are describing the quantity of. Mathematically 19 oranges, is the same as 19 inches, is the same as 19 days, which is the same as 201₃ math nerds (201₃ is 19 expressed in base 3, will get to bases later) (and you can find 19 math nerds in the same place, though it usually a math class, or a comic con).

So, what does a number data type need. INumber says 50 some functions, and it is right to some degree. However, those functions tell us attributes of the number or defines ways to interact with other numbers, but the most important thing is the value. It is a data type and we need to have the data. What is the data with a number, well the value. So, how do you store the value? Well, that was some of what I wanted to explore with this project. With the OutrageousInt I started with, the value is an int. And yes, I'm wrapping an int in an unnecessary class, but this whole thing is in and of itself, unnecessary. I am doing it to try and learn something, and experiment with algorithms and maybe help someone else.

Now, does the value have any properties, or need any properties to ease calculation or interaction with other classes implementing INumber? Well, that is the question, but perhaps I need to start with a naïve implementation. Currently, I believe that my int version is finished or close to it, so maybe I need to create a unit testing project to be used on the OutrageousNumbers, and perhaps some sort of simple app to play with the numbers. 

Interface, IReallyBigNumber Or Something

In the last entry I talked about designing an interface for a number. So, what is an interface? I always struggle with how deep to go in answering some questions. I currently work in C#. C# is an object-oriented language, meaning that data is structured into classes. A class is a collection of data about a specific thing, and occasionally functions related to that class or contained data. Now one of the concept of object-oriented programming (oop) is polymorphism. Polymorphism is the idea that objects of different classes can be sent to a function of a specific class. One of the ways of supporting this is called an interface. It is like a class, but only has function declarations. Any function call that requires that interface will accept an object of a class that implements that interface.

So, what does a number need for it's implementation? One camp of oop says that all data fields should only be accessible/alterable through functions and methods. This ensures that all operations and changes to the data follow the rules of the class, this is especially important when creating several classes that are supposed to react is similar manners and be processable from the same functions. The argument being that none of the external services need to know what the internal data is or how it is processed.

So, bare minimum for a number is equals, add, subtract, multiply, divide, and compare (greater than, less than). There may be others that I may want / need to keep the coding internally. For the algorithms I am thinking I want to attempt, the basic parts may be enough to get it all working.

I had created a repository to hold the code I am trying, but decided that I had not started it right, so I dumped it and started a new repository. I will try and keep commit labeled in such a way to indicate what is being done and which blog entries they belong to. The current repository is OutrageousNumbers. I found a website that will check some of the most popular repositories for open source code for a name, after trying a couple I got frustrated and tried OutrageousNumbers.

While I was doing other stuff I decided to see if the "primitive" types had an interface, despite the fact that this whole project is about doing work that has already been done, I didn't feel like the interface should be repeated if an acceptable one was in use in the main parts of .Net. I found out that they don't seem to, but that in .Net 7 some Generic Math libraries were added including an INumber<Tself> interface. So, I do not need to create the interface and it already is more detailed than I was expecting to start at.

I think I will start by creating an Outrageous version of the int, not a large version, just to explore the interface and work with the many parts of that. I will check in the initial creation of the project and the class, and we will do more from there in the next installment.

Design Document

 When I can I try and do some programming for myself. It is not as often as I would like, as I have a family and can never keep a computer in good shape, but I do try it from time to time.

Sometimes I try and put forward a challenge. One I did previously came out of a project for work (a previous job). That team was big on testing, so I created a tool that could take two unspecified inputs and determine if they are equal. I created it in C# and .Net, and use that languages reflection capability to determine the parts of an object and compare them to the same part of the other if it exists. It is called GenericDeepEquality, the code is on GitHub and I have published a NuGet package, located here.

The current challenge I am undertaking is creating a library for Math with Big Numbers. Also, maybe, designing it to work for any base number system. This isn't to make the next great Math library, it's just to figure out how to do it and play with algorithms for mathematical functions.

So, now it time to work through some ideas to determine where I am going to start.

The main issue of a big number is the big number and how to handle it. In C# an integer is represented by an int. An int has the ability to represent a number between -2,147,483,648 to 2,147,483,647, That's a lot of number space, but it's not enough for the federal budget, for example, and there are applications that require much larger numbers, like cryptography.

Additionally, there are technically three main parts of a number variable, assigning the number a value, storing that value and displaying that value. Some might ask about manipulating the value, but with math, the operations usually produce new values, so that is different, also, that is a different part of the processes in general.

Terminology: As I am using it, not necessarily completely accurate to math.

• digit - one "character" of a number. 19 has the digits of 1 and 9. Digit may seem to imply base 10, but I am using it in a more generic manner.
• significant digit - a representation of the position of a digit in a number. Standard terminology has the "least significant digit" being the digit representing the zeroth power of the base in the number and the "most significant digit" being the digit representing the highest power of the base in the number. In 19, the most significant digit is 1 and the least significant digit is 9. 
• base - The number of values available for a single digit. For example base 2 have 0 & 1, where as base 10 has 0, 1, 2, 3, 4, 5, 6, 7, 8 & 9.  A number can be written as the sum of a series of single digit numbers times a power of the base representing it's location in then number. 19 can be written as 1*10¹ + 9*10⁰. 

Before we can do anything else we need to determine how we are going to store the value. Now, much like you can write a number larger than 9 by adding another digit to the left (10), we can create an array of ints, such that the following ints would represent the next significant "digit" in the number. So, an array of integer values (int being one possible type). Of course, now as I'm thinking about it, I should do them all.

So, what I'm thinking now is I need to create an interface, so that all of the different versions can be used in the same algorithms. Now I need to figure out what I need for a number interface.

I'm going to put this out there and come back to designing the interface.

International Nodebots Day

Yesterday the local JavaScript user group had an International Nodebots Day event. I took my daughter. It was a lot of fun, I highly recommend doing that kind of thing with your kids.

My kid also gave me a conundrum this week. She had an idea for an app, that she was wanting me to make. I haven't programmed for Android, and I haven't programmed Java in a long time. So, I may be learning that too, or make a decision between that and this. So....

As for what I have done this week. Nothing, but I have gotten my tablet up and running again. So, I'm hopeful that it will continue to cooperate.

What I've Learned

What do you need to write programs? If it is a complied language you need a compiler. If it is an interpreted language you need an interpreter. Also, you need something to write the code in, like Notepad.

This is an advantage for Javascript as the interepreter is built in to most browsers and all of the major ones.

However, I would recomend and IDE if you are intending to code. An IDE, or Integrated Development Environment, tend to have certain functionality that is helpful for programming.

Of particular use is syntax highlighting and autocomplete. Syntax highlighting changes how the text is displayed. Keywords, variables, strings all show up in different colors, fonts, etc. This makes it easier to understand what is happening in the code. Autocomplete offers suggested words based on the meters typed so far, the words coming from the context of the code and keywords. This helps with spelling of variable names, for instance. In an interpreted language, such a misspelling would break the program and be difficult to find.

I'm not sure if this installment was as helpful as I would hope.

Summer Break

So, I had started an update when the tablet I was working on decided to stop working. I decided to give it a couple days to run out of juice to see if it would reset. It did, then went back to a blank screen after I started the first app. So, boo.

The update I had started was about how little I had done. I need to make this a bigger priority, or decide it's not going to be a priority.

I still want to learn JavaScript, and I still think that this it's the way to keep me accountable, but is this the time to do it?

In fact I just showed to myself that it is trivial to move the script to it's own file, by copying the code to a separate file and removing it from the html file. I'm not completely happy with it because I have references to html objects in the code, it will be a rewrite to remove those.

What I have learned so far.

Some of this is stuff I have known, but it is stuff I have learned to this point.

There are two types of programming languages (plus machine language which is written in a form a computer can understand). Languages are either compiled or interpreted. Compiled languages are written in a human readable form and then compiled into a machine readable form one time, creating an executable that will be run when necessary. Interpreted languages are written in a human readable form and then interpreted at run time into machine readable form, and will be interpreted every time the code is run.

The advantage of compiled languages is the executable tends to be faster and smaller in memory. The disadvantage is that the program will have to be recompiled to target a different architecture (PC, Mac, mobile) which may also require some changes in the program as well.

The advantage of interpreted languages, also commonly called scripting languages, is that they can be run, often without change, on many platforms. The disadvantage, is the programs can be larger and slower and often are limited in their ability to access the hardware of the machine.

That was then. Now there are languages that are compiled and interpreted, like Java. Also some languages are transpiled, written in one language and the transpiled into another language, often JavaScript.

The advantage of a language that is compiled to a bytecode and then that bytecode is interpreted on the machine is speed closer to a compiled language and the ability to run on any machine. Disadvantages include a limit to access to the hardware.

Now, transpiling, is a completely different issue. Much like human languages, computer languages affect how you think and how you can express things. So if you need to do certain things, it might be easier to write it in a different language, then transpile it to the language needed. These are usually done with languages designed to transpile, for example CoffeeScript and TypeScript both transpile into JavaScript.

I did not think I would end up writing this much about languages alone, so I will try and put more of what I have learned in future updates. I am a little reluctant to make such a promise, though, for some reason (-cough- -cough- complex math -cough-).

This time I mean it!

Okay, so I'm going to try this again.

I have decided to try and get in to JavaScript development, specifically web and Node.js?

Do I know what I'm doing? No, I'm not even sure I know what I'm getting into.

Why JavaScript? Node.js d'uh. Clarification, I recently got my hands on a quad copter, and there is in the local developer community that has a meetup for robots. Robots need to be programmed, my quad copter can be programmed. This meetup for robots is Node.js based. Also, the local developer community has a Slack channel, and from that I have found that there is a demand in the area for JavaScript developers. I guess I'm just looking for something new and this presented itself. Plus, if I have something on the web, then I can say I did something? Right?

Now a little about my self. I have been a professional developer for over 12 years, and programming for much longer than that. I have programmed in Pascal, FORTRAN, COBOL, BASIC and Java. I have been paid to program in C++, C#, Visual Basic, VBA, SQL and even a little JavaScript (JSON).

As you can see, I have a broad experience with programming languages. I have gotten to the point where I can troubleshoot and even code simple things just by Googling the language or getting a book. Most of the time I find I just need the vocabulary, the syntax is very similar from language to language. Especially in the languages descended from C.

So the hard part is finding a project to do. I find I learn better if there is a goal in mind. But that is the issue, I haven't known what to do, but I'm giving up that and doing my favorite types of projects - fractals.

What are fractals? Well, that will have to be another post.

What are you using? That is a very good question. I'm not sure. I currently have Notepad++, Sublime, Atom and Visual Studio Code installed. If you have suggestions on what to use or tools or tips for the above applications, let me hear them in the comments. I will also need a domain registrar and (maybe) hosting, if I am to let you see my code. Again, any wisdom you have will be greatly appreciated.

The goal going forward will be at least one post every other week. We'll see how that goes!

The Joys of Socialized Medicine

"Parents 'deeply distressed' baby OT will be left to die"

Let me just say that I am glad I live in America, where this doesn't happen as much.

I Know, It's Been More Than A Week

I know, it's been more than a week. I have not lived up to my promise. I will try and do better, or give this up. I think there are some advantages I will receive from blogging if I truly give myself to it, but it is a commitment.

Yesterday, however, was a celebration of another commitment. Yesterday was my wedding anniversary. I have been married to the love of my life for nine years. I love that woman, and yesterday was a great day. With the exception of my commitment to Christ, this is the longest commitment I have ever had, and I am loving it.

Make A Promise and Look What Happens

Hadn't had the combination of time and inspiration to post a blog lately. Decided to check when my last post was today. What do you know, it was six days ago.
Work has been a little weird. We are so far ahead of where we were last year that it almost feels like we are waiting for it to all come crashing down around our heads, but so far it has not.
Just finished reading "Case for a Creator" by Lee Strobel. I recommend it for anyone who thinks evolution is true, but is willing to look at the evidence with an open mind.
Enjoy.

Coming Up With Titles Sucks!!!

Today was a good day. Didn't get much done, but spent all day with my daughter and a good portion of it with my wife.
I had so many things I wanted to blog about, but now that I'm at the computer, I don't remember any of them.
It's so easy to get distracted. Probably part of the reason I don't do more coding at home.
Time to let the dog back in, so I'll sign off for now

What This Blog Is About

Short answer, I don't know.

I have the grand delusions about what a blog by me could be. But, I have to be realistic. I mean, a blog isn't popular because the author says it is, it is popular because enough people say it is. Right now I have a grand total readership of one, and that's only because I tell my wife to go read it. Or, at least that's what I did with the first one.

I would like, when I get a chance, to pontificate on subjects of science and philosophy. That, however, is a discussion for another day.

Now is a time for work, and a lot of it. I work as a software developer for a tax preparation company, doing programming for state returns. I have one week to complete most of my work for the year. As a note to those who might say, "But this is just the eighth day of the year. That must be pretty slack." In the tax industry the year begins in May.

I will try and post on a regular basis, at least after April 15th. :)

I am going to try and get some posts done in the next couple of weeks, dedicated to advertising some of the links that I hope to soon have up on the side of my page.

I hope that I am able to entertain the people that do happen to read this.

Thank you for reading.