Skip to content

Keeping it real (The Representation Of Real Numbers)


What is a real number

1,2,3,4,5,6,7,8,9,10 etc


What isn’t a real number



So then what’s floating point representation ?

The way we store these numbers in a computer system (Using 2 different pieces 0f data)

What’s the mantissa and exponent?

Those 2 pieces of data I just mentioned

Be More Specific ?

The Mantissa is the base

The expononent is basically the power of.




Only 10 people in the world understand Binary


Binary is the essence to how your computer works. It is essentially just two numbers 1 and 0. 1 represents an active state and 0 represents a non-active state. Now that probably confused you so I'll reword it like so:

Binary represents voltage, for example say that the computer screen your staring at now decided to eletrocute you for no apparent reason then this would be represented as 1. Now if it didn't eletrocute you and you weren't flaling about like a drunk family member attempting to dance then this would be a 0. 

Now because binary is only two numbers it's a bit hard to use this to represent an actual number so we use bits. Bits are pretty much the standard for what number we're trying to represent using binary, so for example if I wanted show you how 3 looks in binary I'd show it to you in 3 bits like so:


Now your really scratching your head but in all honesty it's not as hard as you think. Recall how you learned to count up to the hundreds and thousands in primary school. That old hundredth's tenth's and units stuff. That's basically the key to working out binary. Binary is the same as that system except instead of counting doing 1 x 10 = thenths 1 x 100 = hundredths it uses x2. [ This is because there are only 2 states of binary where as our number system has 10 states because we have 10 fingers. Your computer technically only has 2].

So when we do the x2 system, it goes a little like this:

1024  <----- This number should be familar, and now you know more about file storage too.

Get it ?
We're just doubling the number to add the next bit on. That 011 thing must be making sense to you now it's esentially just

4 2 1   <---- Always In Right To Left Order 
0 1 1

We don't need the 4 because it's greater than 3 but we need the 2 and the 1 so we can add them together to make 3. 

I'll use another example incase i've confused you. I'll use a higher number aswell... like 36

32 16 8 4 2 1
1    0  0 1 0 0

32+4 = 36

That's all there really is to know about binary.

High level languages, Macros, Scripting, Procedures, Functions and Parameters

A High level language is basically a programming language which references the English language. For example binary is a collection of 1’s and 0’s so all the coding required for that is written as 101010100011100101010101 where as a language such as basic requires coding such as IF <65 then Pass. It’s a whole lot easier to understand a high level language than a whole big bunch of 1’s and 0’s

Scripting and Macros are basically the same thing. They’re each pre-defined functions that are binded to a singular keystroke for example CTRL +  C is copy, CTRL + V is paste. These can be user defined using built in editors in programs such as Filemaker Pro (Scriptmaker) and Microsoft Word (Macros)

A Procedure is basically a subroutine that creates an effect such as changing the direction the ghosts run in Pac-Man

A Function is a subroutine that edits a value for example eating the cherry in Pac-Man will change your score

A Parameter is a restriction that controls one entity for example

Inky, Blinky, Pinky and Clyde are all parameters in the sense that I could set a variable such as speed to Blinky but make Inky pass through walls.


A blog post about Documentation Evaluation and Maintenance, more specifically Documentation.

Alright the last 3 stages are labelled Documentation, Evaluation and Maintenance.  A short summary of each of these would be:

Documentation: The paperwork or any form of guide to help you use the program. This includes the user manual, technical guide etc.

Evaluation: Is the program fit for purpose, meaning does it do what it’s meant to do.

Maintenance:  Stuff can break over time, maintenance is there to try fix that.

EDIT: I did say Documentation would be done more specifically so here’s alot more info.

Usually a user and tech guide. User guide teaches you the program sometimes printed on paper but usually found by slamming the F1 key in a fit of rage while the program is open. This type of help brought on by the frantic push of F1 is called “Online Help although why it’s called online help and not just help is beyond me considering you don’t even need to be on the internet to bring it up.

The technical guide aka a horror story for the elderly and technophobes. Basically it’s all the fancy stuff your computer needs to be able to do to run the program aswell as some stuff noone really cares about such as version numbers and credits to the people who were paid minimum wage to create the program.

It’s not just limited to those 2 guides though there’s some others such as;

Quick Start Guide

Shortcut/Hotkey Guide

Video Tutorials

FAQ’s  (Frequently Asked Questions)
That’s all for now (Just noticed it’s a bit ironic that i’ve wrote somewhat of a manual about how to use manuals)


The Testing Phase


Testing is where roughly 40% of the dev teams money goes so yeah it's pretty damn important. Most companies save money though by fixing the obvious problems in the earlier stages of the software development cycle.

You might think that testing is quite an easy job but there's alot of common errors that plague it into being quite tiresome. Imagine if your job consisted of finding these issues constantly:

Incorrect interpretation of what the program was meant to do in the first place
Poor error handling
Bad time planning
Syntax Errors (Very Common even in the most basic of programs)
                                           ( ^ Pun Not Intended  )
Initilisation Errors
Errors in loop counters
Forgeting the variable names 

To find these errors we must enter test data into our program. Test data comes in 3 different forms these are
Normal             (Would be entering John Smith for name)
Extreme/Boundary   (Would be entering John FwufewijXmdnhwfbwefbwufbwufb To test character limit)
Exceptional        (Would be entering 43 23 to make sure numbers aren't allowed)

There are also different phases of testing these are

Procedure - Going through code one by one
Integration - Making sure all the little parts work together
System - Testing everything overall
Acceptance - The client makes sure everything is up to scratch
Alpha - A non-finished yet still workable version
Beta - A more polished alpha usually released to more people

Who tests the programs
Dev Team - Early Stages
Client - Late in the early stages
EDIT - The public can also test in the alpha/beta stages. You also cannot totally tell that I wrote this is Notepad first...

A Dance In (Analysis, Design and Implementation)

Analysis is pretty simple. The main role of an analyst is just to understand the client’s problem they can achieve this by interviewing the client and developing what is known as a “Software Specification”.

This software specification is basically a document containing the following 3 things:

. Clear statement of the problem ( A few sentences just won’t do)

A legal agreement ( Someone sues someone over something blah blah court blah blah loads of money)
^ You usually want to avoid this

You also have to do inputs, processes and outputs but they’re usually pretty straightforward.
For example a calculator would be like so:

Input – Numbers and an operation
Process- Do the sum (Duh)
Output – Display the answer (Bigger Duh)

Alright now you need a good design so that your programming doesn’t start going all over the place. It basically just makes everything so much easier as it breaks the program down into nice smaller chunks but it’s not that simple as you need to develop an algorithm which is a set of instructions for completing a task except in computing it’s usually some showoff nonsense like this:

(That’s not some weird nerd language, it’s just written on a window so it’s all backwards.)

now algorithms are the only way to break down a program you can use things such as structured diagrams and flow charts but everyone’s seen them before.

IMPLEMENTATION (The boring part)
it’s basically typing things that don’t quite make sense to you and rampaging to an Incredible Hulk extent when the computer moans your doing it wrong. Of course there are 3 different types of language you can use before it moans at you for doing anything wrong. These 3 are:

1. Procedural
2. Event-Driven
3. Declarative.

That’s all we learned about those 3.

Hello world!

Welcome to After you read this, you should delete and write your own post, with a new title above. Or hit Add New on the left (of the admin dashboard) to start a fresh post.

Here are some suggestions for your first post.

  1. You can find new ideas for what to blog about by reading the Daily Post.
  2. Add PressThis to your browser. It creates a new blog post for you about any interesting  page you read on the web.
  3. Make some changes to this page, and then hit preview on the right. You can always preview any post or edit it before you share it to the world.