Sunday, 30. August 2009, 20:25:55
development

I just got done removing all spam trackbacks from my blog. Obviously, SPAM isn't what I meant this blog to be used for. While thinking about this, it reminded me of how things used to be done in some cases.
Let's create an imaginary scenario. Suppose we have a very fast machine with all the hardware and resources one would need except for ONE thing. It would only have a CRT monitor. You can use an LCD if it supports the right connection, but that's not the point. The scenario I'm setting up has one more oddity. Your video card can only display ONE color. You can select from 16 million colors, but it only has ONE register where you can set the color that will be sent out to the monitor.
Some people would have a problem with this. For others, it wouldn't phase them one bit.
Suppose our CRT runs at 60hz with 60 frames per second, we can change the screen color each frame. With a normal machine, we can change the screen 60 times a second no problem. So that much stays the same. But having a single color isn't very interesting. If we can change screen colors once per frame, what's stopping us from changing it more often? Nothing.
Read more...
Saturday, 8. August 2009, 23:15:46
development
If you like rockets, computers and the space program, you'll want to see this. Talks about creating the computer that went into the Apollo program. 72K of hand weaved memory if you can believe that. Found it on
reddit.
http://www.youtube.com/view_play_list?p=7F223B0B5228CB54I'm reading that it's from a 6 part show called Moon Machines aired on Discovery.
Friday, 31. July 2009, 16:07:16
development
I've been thinking about this game concept for a very long time. I'm not sure it's viable, but I still think it would be a cool concept. It's a game for programmers. Not only would it be for programmers, but it would be a mechanism for learning how to program. If you need a particular feature to get to the next level, you'd probably be inclined to remember it. After a while, you could learn how to unlock doors, break into safes, bring up maps of the facility to find weapons or more gear, etc. You'd only learn one or two things at any given time and have to use it several times before moving on to the next technique.
I was thinking about a game somewhat like Neuromancer. But where you actually go into the details of the devices. Where your cyberdeck (or whatever machine you use) has its own opcodes. You could make this really simple, but perhaps be for more advanced levels. You could have simple compilers available for each deck. Servers would likewise have their own set of opcodes and you could write viruses or whatnot to break into systems.
Read more...
Saturday, 18. July 2009, 00:32:53
development
I was thinking about my undo problem again and although I had a solution mostly worked out, perhaps there is an easier way. I wanted to enable the sharing of data amongst multiple users. So you could work on a part of the project while someone else works on something else. Also, I wanted to be able to make changes in someone else's workspace. I thought I had to build a custom back-end platform to enable all of this. Then again, perhaps not. Would there be any drawback in using a wiki to store projects? The data itself would mostly just be junk if you were to view it through a web page, but comments, copyright, inputs, outputs, component name, usage, author, history of changes, etc. would all be there.
I think I'm going to go this route. You can load up a local copy and the IDE will mark another page stating that you're working on it. Of course, the IDE would check this list first and inform you that it's being worked on, giving you the chance to visually connect to the active worksheet on someone else's machine if they allow it. In essence, I would use certain pages as a tracker to monitor who is working on what as well as a way to connect to each other P2P style in order to be notified of changes, especially for chat and concurrent updates on the same worksheet.
Read more...
Wednesday, 1. July 2009, 23:22:05
development
I was busy with other projects and really wanted to quench my thirst for programming due to withdrawal symptoms. I needed something quick, but fun. So Mandelbrot it was. I think the last time I programmed a Mandelbrot set was way back in my University days when computers available there went from 8088 to Pentiums and video cards went from CGA to SVGA. The very first Mandelbrot set I did at University was in CGA with a monochrome monitor in a computer lab for first year students. (edit: I should add that I wrote this in Modula-2, awful language that it is.) These machines were ancient. I also wrote a program to compute Julia sets. Most people had no clue that these machine could do graphics at all. The reaction from others in the computer room was quite entertaining because normally, the ambiance in there is somewhat like the movie Das Boot. Tons of people in a large, but confined space. So when someone did something to change the monotony of working on assignments, it was often very motivating since people wanted to know how it worked. Oh yeah, back then, it was direct access to the video card. No fancy API's.
Read more...
Monday, 29. June 2009, 19:03:57
development
Handwaving, Lawyer Speak and avoidance are three of my favourite techniques that I see used by people who don't understand a particular topic (mostly when I go on other sites, but occasionally here as well). Perhaps I should qualify that. It's not people that don't understand the topic, but rather people who do not want to understand. Most often, these people simply repeat what they've been taught, what they've seen or what they've read. In a conversation, you don't need these people to be present. They can simply give the reference and be gone.
Handwaving is when you state something that you think is obvious, but never think of producing any explanation. Begging the question is a form of this, but handwaving doesn't even try to set up an argument. It's only the first part of begging the question.
Lawyer Speak takes the top spot for deceitful tactics. It's really effective against someone who has never encountered it before. And even then, if you haven't recognized it, you will continue to be fooled by it. The technique involves argument X, but then you state argument X again but about topic Y. Topic Y seems like it's related to X on the surface. But it is in fact completely irrelevant to the situation. Ad hominem attacks are a form of this, but Lawyer Speak is never direct. In fact, the subtlety of it is what makes Lawyer Speak so effective.
An example of Lawyer Speak is someone trying to convince you language A is just as good as language B since they are equivalent. Sounds good on the surface, but equivalence has nothing to do with what language is better.
Read more...
Thursday, 18. June 2009, 23:50:46
development
While this article deals with the Halting Problem, there is a critical property of programming and computing that has been overlooked called compositionality. Composability is a well known concept. In programming, it involves the rules for combining different things together such as functions, objects, modules, etc. But compositionality deals with the relationship between data items and the meaning of the overall program. If we're dealing with the behaviour of programs, specifically if they halt or not, then we're talking about compositionality. Compositionality has very specific rules and guidelines that you can follow to determine the behaviour of programs. More than that, you can often tell if a program is valid (all required computations have the necessary inputs). Many programs can be executed, but it doesn't mean they are valid. Most people think that all composable programs are automatically valid. This is not so. Compositionality has a few things to say about this topic. Those details are the purpose of this article.
Read more...
Sunday, 7. June 2009, 21:25:34
development
PART IIIHiding the KingIn Part I, we mentioned how we built the first grid with SHDRLU. I'm sure some astute readers are wondering what the other six characters would give. So let's try it.
ETAOINNow, we need another 2 letters. DH seems like good candidates as they stick out in D
YAH
R and are found in the second group.
Read more...
Sunday, 7. June 2009, 21:11:59
development
PART IIThe Americans are Flying HighIf we started with Russians, you can bet the Americans will not be upstaged.
In the last part, we mentioned the importance of the X's and O's. We're not done yet.
Let's take the ciphertext of all the X's found in K2. We even take the ones from the words E
XACT, SI
X and the missing X just before LAYERTWO. We also take the ciphertext of the misspelled U since it covered up an O.
ARSTATOSRead more...
Sunday, 7. June 2009, 21:07:13
development
Kryptos sculpture at CIA.
My partial solution to Kryptos.
Before I begin, I need to mention that I don't have the final solution and am no longer interested in obtaining it. Perhaps I'm wrong. I hope I am and I'll need some humility going forward. But if what I present here is in any way true, then I want no part of the final solution. I may still look at it from time to time. I know where the next part is and know some of the details for deciphering it. But my interest just isn't there anymore. You'll see why as we move along. The beginning is very interesting. There is even a clue at the end that I found quite intriguing, even fun. But it only confirmed my worst fears. I once had a comment that I was climbing mountains. I think that comment should be redirected at Sanborn if the following XI part series is true. It's crMzy what's here. You will see exactly WHY, or should I say C exJctYL Y it's never been cracked, and why I leave this here for others to C. Annoying, isn't it? But like I said, the first parts are quite entertaining.
Read more...
Showing posts 11 -
20 of 375.