NeuDev

MySQL

2010-06-26T03:34:00.000-07:00

I am currently revisiting MySQL. I am fascinated by databases and DB design. I have learned so much already and I hope to possibly use this some day when developing an A.I. engine.

2010-06-26T03:21:00.001-07:00

Update:
A return to the project "Kite". I have decided to do this in Python. I have considered Java and Ruby but neither provided the tools or results of Python/PyGame/TKInter. The results of this will determine future game design and builds.

My Authentication Code Collection

2008-05-24T20:12:00.000-07:00

Revealed, my authentication code collection. Collecting these small (and annoyingly appropriate security images) is akin to an Easter egg or scavenger hunt-- save that you never know when one will pop-up for your use. Just when you have forgotten about auth-codes when registering for your 5th GMail account, for example, another distorted and bizarrely rendered image presents itself, the key to your online user creation. It is always exciting to find a new auth-code to add to my collection.

The included image (above) is a small portion from my collection. Each is unique in appearance, repeats not being acceptable for this collection.

Automated Tasks via...

2008-05-24T14:34:00.000-07:00

RUBY. Automated Tasks via Ruby, a new terrain that is being explored.

The QA team I am a member of has taken upon itself (ourselves) to dev scripted tools using Ruby in order to automate repetitive tasks; these tasks (such as User account creation, site login, etc) are impediments to streamlined testing during every testing cycle.

So far, we have been writing small scripts (very small scripts). These scripts are promising and exciting. To run a Ruby script from a desktop environment and then sit back and watch it move through the tedious steps for you-- well, it's magical.

Thank-you Ruby (and John and Chiky).

Boston Dynamics "Big Dog"

2008-04-01T15:47:00.000-07:00

An amazing DARPA-funded robotics project. Watch and be amazed how far AI and movement has evolved...

TaskStream - My Job is Great

2008-03-15T14:53:00.000-07:00

"Pleasure in the job puts perfection in the work."

KITE

2008-03-12T08:41:00.000-07:00

Kite is a game, or rather, a "toy". Flash-based, this game is set in a field during a storm, the object originally being to control a kite amidst scrolling clouds, each cloud struck equaling a point-range earned.

I am now considering redesigning this game to be a puzzle, dynamic in its approach. I have not yet determined what the logic of this puzzle might be.

Although "Kite" has not been built/coded yet, the overall design seems promising.

*The screenshot above is a mock-up simulation and does depict actual game play.

AI - Sterling

2008-02-23T09:54:00.000-08:00

I started new work on the artificial intelligence dev project. After many years and piles of scattered notebooks full of fragments of code, theory, and test plans I've began the process of compiling all of this work into one master book, pulling together all of my previous designs and actually adding new material.

Algorithms are my main focus at the moment, in this case a primary algo-- one algo to rule the rest. This algo is a holy grail and is code-named "Sterling"; It is young, undeveloped, but the goal is becoming defined slowly along with the mathematical structure(s) needed for processing. Sterling will be a component of the main engine but will also serve a greater role as a top-level control.

I am also working on an algo called "Harlequin": I will not go into the depths of Harlequin at this time as it is a unique algorithm construct that I am very protective of. It will be used for the analysis of memory\arrays, process optimization, and DB control.

Under The Volcano

2008-02-23T09:42:00.000-08:00

I went to a post-launch get-together with the company the other evening at a Manhattan bar named "Under the Volcano". I had a nice time. I sat with one of the QA team, Chiky, and with a programmer, Jesse. We talked the whole time mostly about programming, languages, needed QA tools, etc. Everyone sat in small groups over drinks just chatting, relaxed. This was fun and a different aspect of the workplace; This allowed for a sense of celebration for the hard work that was done (for the project) and it also allowed for everyone to get to know one-another a bit better outside of the office.

Testing Over-- Party Begins

2008-02-15T18:19:00.000-08:00

Well, according to the title bar, the new version testing is over for the build and a party began to celebrate this at a bar in Manhattan, tonight. The party didn't start for me, though. I went home to see Monica, instead.

The QA team\testers, programmers, all support staff, and myself were invited to an Irish pub-like bar near the office for a drink. And, I didn't go. Doesn't surprise me; I like each person I work with and sort of wanted to go but there is some (un)natural resistance within that prevents my joining-in in situations like this. I'm not exactly sure why. But, the testing is done and that's what is important.

Blog 1.2

2008-02-14T17:14:00.000-08:00

It has been a long time since I've posted-- almost a year. That's hard to believe in some ways. I will not commit to daily updates at this time as, for now, this will suffice. I've done freelance web dev, contractual web dev + graphic design, and various interviews and "tryouts" (a bizarro-world take on an extended interview of sorts) over the last year; I put much serious time into all of this and I thought it meant a lot. It means a lot as to 'experience' but now, not much more. Perspectives change.

The change as of late is with a new job: I was hired by 'TaskStream' in Manhattan as a software tester. Sweet. TaskStream develops high-end educational and assessment software for schools, the military, and other organizations. This began as a contractual job for end-cycle testing ( late February, 2008 release) That was cool but in some ways depressing; I soon came to really like this place, the work, and all the people that where there. I tested, reported bugs, and have learned so much doing it, the whole time knowing it would end soon. But it didn't.

I was recently called into the boardroom one afternoon by the QA Manager and the Lead Web Developer. I thought: "What's this about??" I soon found out. I was offered a full-time job as a web developer && a graphic designer! Very sweet. The testing cycle ends in a few days and I will begin new web dev projects with my new boss. This is all very exciting and somewhat hard to believe.

Brief Return:

2007-05-31T17:04:00.000-07:00

It has been some time since my last log-in and post; I have been experiencing some non-programming related turmoil and have not been incredibly active as of late.

I have recently began an online, OOP-Java class which is very interesting and a great refresher for OOP programming skills. I am also looking for new\additional coding work in NYC which is both exciting and intimidating.

No independent projects scheduled at this time.

The Wonders of Collision Detection!

2007-03-14T21:39:00.000-07:00

Tonight I finally endeavored to understand and implement "collision detection" for a video game (Flash) : it is quite easy after doing it, actually, based on the X -Y axes and purely mathematical, of course. The mystified magic of collision detection has been finally demystified for me (although, I have only worked on a basic system-- there is finer detail to be sure) I also worked on physics for the same game tonight; this may stand as even more important than collision detection if not its equal. Once again, simple mathematics made use of to create what amounts to an illusion.

It is quite exciting to attempt something and with a bit of work conclude a small project with a feeling of solid understanding.

~Magic Fountains~ (Flash)

2007-03-14T21:32:00.000-07:00

Macromedia Flash ... New Job

2007-03-06T11:50:00.000-08:00

My new job is not involved with Macromedia Flash, or, at this point, even programming (I am about to begin writing ad-copy for a search-engine optimization company located in Boulder, Colorado) This is quite exciting and a dream position come true.

FLASH : I am studying Macromedia Flash (and ActionScript coding); this is very interesting, fun, and seems to be full of massive potential as a programmer\designer\artist. I have worked on a few tutorials with some interesting results.

Well, Well

2007-02-24T21:16:00.000-08:00

A new Job?! Yes. I have been hired at a new firm. I have not began yet and am not exactly sure of my direct assignment(s) but it sounds juicy. Much more on this to come.

New Build:

2007-02-18T21:43:00.000-08:00

AMGINE

NEWS: [Build Complete]

2007-02-12T18:02:00.000-08:00

The final build and testing is complete for "Sith Realms" now entitled "Cantina ~ Monte".

Rebuild?

2007-02-09T15:35:00.000-08:00

A rebuild? Well, sort of. I ruminated over the "Sith Realms" game for some time now and some of the contained algos. I will say I made some fine headway but it occurred to me upon waking one morning that I could still improve upon the build and this would most likely require demolition of areas of the code and a thorough rebuild (in specific areas).

This I have done, stripping areas bare of run-on code lines, extracting the useful functions and denying those which only exist for their own sake, for perpetrating the ideal of functions used "when functions can be used".

I am still working on this and it has been very fun, simple, and quite easy. This brings some well-earned joy after weeks of digging through my caves of lost code.

The Lone Developer

2007-01-30T14:28:00.000-08:00

A great Wiki article aimed at the single, one-person game developer-- tips, hints, and suggestions: Lone Developer

Return

2007-01-24T09:58:00.000-08:00

I began work once again on the game yesterday. At first I resisted deeply considering what I was doing but I continued on and, after a time, I found that I was making a good deal of progress. I primarily worked on button controls and some logic concerning the computer-player's A.I. I came to a point where I decided to save and exit the compiler, stopping at a reasonable point. I felt it would be better to rest on that night's laurels than press on, become tired (it was late), and end up with a coded train-wreck that I would have to untangle today.

This afternoon I need to look at and fix some of the variables that are throwing obvious errors (returning zero as a value) I believe I may be done with the principle build by the end of the weekend and can then schedule final testing.

Rest_Read_Rest_ [code?]

2007-01-21T19:51:00.000-08:00

I have taken a short break from work; I have been resting and reading: Plato\ Socrates, OOP, OpenGL, Basic4GL, The Bible (Psalms). Yes, resting in the form of naps-- I never take naps. For the last few months between work and personal projects I have been keeping odd and almost bizarre hours, or should I say (?) no particular hours. Hmm, my body noticed and for the last almost 2-weeks has been inducing day-naps and end-nights where I am asleep before Midnight. Odd, but I believe it is necessary for health and there is no stopping the body when it needs to reset itself properly.

I plan to finish off the "Sith Realms 21" game this week for the most part minus final testing (unit testing and benchmark testing last week brought me to a nice point allowing me to take this break). I am hoping tomorrow brings the urge and resolution for completion of this project. Hoping.

The Glory of a Proper Algo

2007-01-15T07:23:00.000-08:00

I cannot claim to directly know of the absolute algorithm intimately, but I do know it exists. After much work and struggle in programming as of late, I reach what I think to be the peak of a mathematical discovery, learning how it works from within, and how the results spill forth upon me as simply perfect-- then I fall down the slopes into the valley only to be forced to view the peaks once again wondering aloud if I shall ever reach the top.

It requires a forward push. It requires a faith in numbers, a spirit that reminds one of the truths when an algo produces negative results :"It is not I, fool-- my form is gracious. It is you who does not understand the depths of my language nor how to speak of my ways." So true.

But, I try to push forward, day after day, and I see the sun skirt the glacial faces as the winds break free upon the Northern realms above. I must prepare better for my ascent.

The Importance of Unit Testing

2007-01-10T11:37:00.000-08:00

The importance of unit testing during a program dev is beginning to ring true! Not that I really ever doubted it, I just never truly considered it. I have always "unit tested" (as we all do while producing code-- compiling, editing source, etc) but I have never until last night made it a priority. I'll admit, it is probably too late to officially begin this method for "Sith Realms 21" as this particular program is almost complete, but this very foray into proper unit testing, that is, writing actual logic tests and documenting their results helped me to solve (it seems at this point at least) some serious logic errors that prevented the clearing of an important milestone towards completion. I have adopted this technique and plan to use it from this point forward.

Testing: by Evelyn Mitchell

2007-01-09T03:58:00.000-08:00

The 17th century German philosopher and poet Novalis said, "Most marriages are divorces." Had he been a software developer, he might have said, "Most programming is maintenance." Still, with careful testing from the outset, the maintenance of existing programs can be made much easier, but only if the effort of writing and running tests is justified.

Unit testing is the process of testing code as you write it. You can also use unit testing during regression testing, in which you determine if a program is working the way it did before you modified it. Unit testing is also known as "white box" or "glass box testing," as opposed to "black box testing."

Black box testing is, roughly speaking, testing done by someone who does not have access to the program's code. In black box testing the program is viewed (you might have guessed) as a black box that takes inputs and produces outputs, but doesn't reveal its internal structure. By contrast, unit testing exercises your full knowledge of the code by testing the interfaces to other code components and to user space, as well as the implementation.

Unit testing fully tests every interesting function a program performs. You can test for unusual data, or for combinations of values that should always or must never occur. You can even use it for coverage testing, to make sure that you've exercised every path through a program.

You can write the unit tests once you understand what you want a module to do, even before you've actually written the module. Kent Beck (author of Test Infected: Programmers Love Writing Tests -- see Resources) recommends writing the tests before you write the code because they can help to clarify your understanding of what the module is supposed to do independent of how it will do it, thereby separating design testing from implementation testing. If you can't write a test for a module before you write the module, that may suggest that you do not understand the design, or that the design has an error. If you can catch a design error at this stage, you've just saved yourself some coding time.

A unit testing framework, such as PythonUnit, makes it easy to test your code after every change, no matter how trivial. I work with multiple windows open -- one for the code I'm editing, one for the testing -- and I pop back and forth as I make changes.

This makes finding errors simpler because you know that the change you just made caused your test to fail. Frequent testing can eliminate those multi-hour debugging sessions where your code gets filled with print statements while you try to find that good line gone bad.

Writing all those test cases may seem like a lot of work, but I find it to be a very effective way of learning how a new piece of code functions (or doesn't function the way I thought it did). The time I spend writing tests is time I would have spent guessing about how something works, to no good end.

The simple fact is that the earlier you find a bug and fix it, the cheaper the fix is.

Twisted Variables and Flying Roaches: The Mighty Dogfight

2007-01-08T04:31:00.000-08:00

The program I am currently working on, "Sith Realms 21", is nearing completion; at this point I am doing a lot of testing, not the proper testing one reserves for a release but a real-time testing (unit testing) that is forced. "Forced" in this case is not a burden but is not welcomed with heart-warming grace, either. I, the ever-impatient programmer\artist wants it done, complete-- a folder in my virtual portfolio to show a potential, future employee. I must always remind myself of the real purpose of this work: through mistakes and errors you will learn (hopefully), and through having to fix a misconceived design you may be developing a vaccine against future, disastrous designs. Just try to learn calmly as you stare at the compiler, and do not give up the fight of error eradication.

It is not unlike a WWI dogfight sometimes: You know that the enemy stalks the horizon. You hear the hum of his engines and the whirl of propellers. Your instinct tells you that if you come in contact with your opponent it will be a nasty fight, but you fly on. You now see their canvas wings as you draw closer-- they are not quite the enemy you feared. But, they let loose with a barrage of lead volleys that almost gaze your leather helmet and punches holes in your planes skin. You tilt and roll racing towards the Earth not in pursuit of a fiery death but only as a defensive move to regain your arial footing and produce a new, aggressive stance. Your co-pilot screams for you to blaze a trail to the heart of your enemy even if it means both your deaths. Victory is possibly only a moment away. Your tear loose with an attack of machine gun fire that strikes the enemy pilot in his hands and his head. That plane now falls free and bleeding smoke, a torn kite now fuming with sure defeat; the dead, enemy craft thrashes the ground not unlike a shattered spear and explodes in a glorious gulp. Your co-pilot yells "Aces High!" and you prepare to return to base. You have just won this round and you can rest perhaps for a moment. Your team will seek and search to recover the destroyed enemy plane to study the wreckage for secrets and technological advancement-- all you do is fall into your bunk and retire with victory for a few hours in dreams of blasts and breath-stealing bail-outs. You will awake in a sweat for another take.

Such is the days of a programmer at times. Although I am making use of lofty, dated imagery and metaphor to describe my struggles with code at times, it is how I feel it at the moment and I pray for victory and yearn to return to base, perhaps to gun another day for all the twisted variables, redundant code bunkers, and the notorious bugs who fly in bomber-formation in search of birthing a firsescape in our eyes. Aces High!

More On the Star Wars Card Game...

2007-01-04T05:47:00.000-08:00

I worked for hours tonight searching for bizarre bug anomalies-- zero appearing as a mathematical result over and over-- this made no sense and I had never before seen this in this program; I took notes on paper of the outcomes and their possible area(s) of origin. I looked for patterns (this is important) and deduced a target to shoot for. I knew it was buried somewhere least suspected as is often the case. After listening to Iron Maiden for hours and immersing my head in code I found the suspect area and it did not turn out to be what I first thought, a mathematical error. It was multiple typos involving lists elements replicated throughout the code due to unfinished, non-updated cut-and-paste. I clone a block to save time and end up spending five hours fixing it. I should have known. Now I do.

Promo: Complete

2007-01-02T16:33:00.000-08:00

The Team KAIZEN promo is complete. It came out quite lovely, really. I am not completely satisfied with it as is the case with any of my work-- I know it can always be better.

There were some issues with PyInstaller-- I will have to look into and investigate this further in the future before I need to make another Python executable.

The promo is ready to ship and I will send it to my boss within the week.

PyInstaller (building a Python executable)

2006-12-28T13:30:00.000-08:00

The promo for my company is almost finished and ready to ship; the next concern was how to ship it to my boss. I knew I would have to produce an executable of the program in order to provide a neat and professional alternative to running it directly from the Python interpreter (IDLE). I attempted to use Py2EXE but instantly ran into technical trouble with this. I turned to a another suggested approach, PyInstaller (pyinstaller 1.3); with help and coaching via DaniWeb, I was able to produce a tidy executable of an acceptable size. I am very pleased with the results. The following tutorial link provides all the information necessary to produce a Python executable.

Promo App

2006-12-25T19:04:00.002-08:00

Included are screenshots of a Python\ Tkinter program that I developed for the company where I currently work; it will be boarding a jet with the President of the company and traveling to Tokyo, Japan where he will be giving a promotional demonstration to one of the world's major video game producers.

Ruby Resource

2006-12-22T10:46:00.002-08:00

"Take a true object-oriented language, such as Smalltalk. Drop the unfamiliar syntax and move to more conventional, file-based source code. Now add in a good measure of the flexibility and convenience of languages such as Python and Perl. You end up with Ruby."

The Pragmatic Programmer's Guide to Ruby is a nice resource to examine and make use of if you are just starting out with Ruby or you wish to fine tune some of your Ruby skills.

My Logic -vs- "Logic"

2006-12-21T22:43:00.000-08:00

The ideals of logic span the globe and hold true in various forums; mathematics, computer science, debate. Yet, as much as many of us value this and think we embody this ideal, higher "logic" is oftern replaced with our own versions: hurried, sketchy, half-truth logic, the kind that leads to server-crashes and endless bug-hunt, extermination missions that can last for weeks on end all over a glitch in our thinking or perhaps a lapse of reason. Why exactly this is could fill whole volumes of analysis but it comes down to a few basics at the least:

How well did I plan?
How well did I double-check these plans?
In programming, how well did I double-check my coding\ typing?
How well and often did I test my code by establisting valid testbeds?

This above list could go on-and-on up to a reasonable level; this level could go up unto the level you require. If implemented as an afterthought I imagine the level depends upon how damaged one's code is.

Often, the answer to each of these points are answered in the negative, unfortunately, with only myself to blame. I remember many of these points when I am already deeply sunk into a mire of "if's" and variable camouflage; these points rain down like neon bolts damning my syntax and ruining my progress at times.

This is coming from valid experience as of an hour ago and dating back for years. How many more projects do I have to begin with the best of logical-intentions and end up with a floundering, skittish half-app? I fear at least a few more unless this writing will supplant my bad habits and preface future projects with a committment to proper logical design and planning before a compiler is ever fired-up for composition.

Maurice W. Discovers Debugging

2006-12-20T22:47:00.000-08:00

As soon as we started programming, we found to our surprise that it wasn't as easy to get programs right as we had thought. Debugging had to be discovered. I can remember the exact instant when I realized that a large part of my life from then on was going to be spent in finding mistakes in my own programs. -- Maurice Wilkes discovers debugging, 1949

The Python Style Guide:

2006-12-11T12:19:00.000-08:00

Your code needs style! Python provides a way. (from the creator of Python, Guido van Rossum)

http://www.python.org/doc/essays/styleguide.html

~ Literate Programming ~

2006-12-11T12:13:00.001-08:00

Donald Knuth has spent many years developing the concept of literate programming. He is best known for the page layout application TEX and the typeface design system METAFONT. The codes for these have been published as full-length books. Why would anyone want to read a book full of code? Perhaps the answer lies in how it is presented. Knuth explains his philosophy succinctly in the preface to Literate Programming:

Programming is best regarded as the process of creating works of literature, which are meant to be read.

Literature of the program genre is performable by machines, but that is not its main purpose. The computer programs that are truly beautiful, useful, and profitable must be readable by people.

In order to accomplish this goal, Knuth wrote the simple scripting language WEB which acts on an input file in two ways. When "weaving the web," the input file produces documentation; when "tangling the web," program code is produced. Since WEB is responsible for structuring the code as the compiler wishes to see it, the programmer can write down the routines in the order which seems most fitting. Indeed, Knuth argues against the traditional hierarchical arrangement of routines in much the same way as proponents of hypertext argue against strictly linear narratives. He believes that a "stream of consciousness" order is both easier to write and read.

The parallels with hypertext go further:
I chose the name WEB partly because it was one of the few three-letter words of English that hadn't already been applied to computers. But as time went on, I've become extremely pleased with the name, because I think that a complex piece of software is, indeed, best regarded as a web that has been delicately pieced together from simple materials. We understand a complicated system by understanding its simple parts, and by understanding the simple relations between the parts and their immediate neighbours.

Logic Soars

2006-12-02T00:50:00.000-08:00

I have made some nice advances tonight with the Python, gaming project: It was really just by following the rationale of pure logic that any progress was made. Even as a programmer, it is easy to forget at times that the basis of logic is the only way to achieve a robust program-- must remember this always and not panic when errors are thrown.

GUI Rough:

2006-11-29T12:01:00.000-08:00

An early edition of a current, Python GUI-build

entitled "Sith Realms 21"

break;

2006-11-20T16:30:00.000-08:00

I am taking a brief break on the coding project(s)-- nothing to report. I have been reading a C++ PDF which goes into some nice detail of some often overlooked areas of this particular language. I plan to reinitiate coding this week.

Compilers: What They Might Do

2006-11-06T11:35:00.000-08:00

C-3PO, in the Star Wars movie The Empire Strikes Back, makes the statement: "Sir, I am fluent in six million forms of communication. This signal is not used by the Alliance. It could be an Imperial code." At times I think my compiler only communicates in "Imperial code".

I love my compiler, a Microsoft Visual C++ 2005 Express, but our relationship is tumultuous. Of course, it is not the compiler's fault but my own; I am sloppy at times or I fail to notice the small syntax flecks that will surely evolve into downhill snowballs-- but will not my compiler become enlightened enough to go the extra step and explain these errors to me in simpler terms? Seemingly not. My compiler, ever the vanguard against deviant coding, springs forth with its verdict-- error, error, error! It is sometimes disheartening that my trusted machine can not speak to me in a language that I understand.

I enter C++, it replies with a shout in Symglish (symbolized English); the scattered English nouns and verbs amongst the hexadecimal blurbs and references to what is happening in\ on the stack can instantiate a cognitive overflow in my forehead. Its difficult enough sometimes to fix the error when discovered and pointed out, never-the-less wade through an error output that looks as if it were downloaded from the mothership.

But I learn-- The compiler does now have to. Its education is left up to the programmers and designers that created this monster in the first place. I love my compiler, but sometimes I wish C-3PO was here by my side so he could interpret the error messages with me.

nasal demons

2006-11-03T18:25:00.000-08:00

nasal demons: n.

Recognized shorthand on the Usenet group comp.std.c for any unexpected behaviour of a C compiler upon encountering an undefined construct. During a discussion on that group in early 1992, a regular remarked "When the compiler encounters [a given undefined construct] it is legal for it to make demons fly out of your nose" (the implication is that the compiler may choose any arbitrarily bizarre way to interpret the code without violating the ANSI C standard). Someone else followed up with a reference to "nasal demons", which then quickly became established.

More Code -- Less Drama !

2006-10-16T18:28:00.000-07:00

In any industry (job, assignment, gig) one will always face the inevitable... co-worker conflict. This is no revelation to anyone, and perhaps many have seen it more than I, but one thing is for sure: it is counter-productive and ridiculous.

I would rather take this time to log great (or even lowly) advances in my programming or the study thereof and, even though I still am very active in coding and research day-by-day (night-by-night) I am distracted by a terrible reminder of our human foibles-- mine, his, ours, yours.

Sparing myself and you the gory details, I have been dealing with a fellow team member who is, let's say, more than aggressive and arrogant and by default, less than tactful. I take it in stride and really laugh about it although it is not exactly funny; upon kindly confronting this person as to why his attitude was so hostile towards me he responded in the affirmative that "Yes" he was feeling hostile as he is "getting sick of hearing other team members backing me as the next possible Lead (programmer)" and that he thinks "the rest of the team thinks I am a better coder than I really am."

I have been detecting ultra-negativity from this guy for weeks now as well as blatant rudeness and a nasty demeanor. Coupled with his arrogant e-mails and cruel replies to company issues addressed by me, I decided (upon the recommendation of my girlfriend) to speak to my supervisor and owner of the company. Essentially, my boss agreed with me and dealt with this employee in question appropriately.

There are lessons in all this, surely, at least in reference to how to deal with others and be civil, forgiving and patient, but again I just extend my hands to the Heavens and say... "Why do things have to be this way?"

Forgive me, it is not technical

2006-10-05T01:51:00.000-07:00

Languages: There are so many, and so many are just not right-- but does that matter? These and all coding languages amount to elitist, competitive shells easily brought down to a command-line yelling in binary. The aim is the same, the results the same, but the tongue speaking the output different. Python, C++, Lisp? I could care less-- please just tell me which one is deeper, faster, and the easiest to use for the job? Oh, and which one is the prettiest to look out for hours on end?

I build a castle of stone and realize too late that I used the worst rock available and when it rains it seeps, and these walls let in ghastly amounts of cold air. What do I do? Tear it down and start over using the right stone and perhaps preserve some of the adornments, gargoyles, and ramming stones (elements of the old code if it will mesh smartly) and reuse what I can. If not, drop the worthless slabs into the bay and mine somewhere else. Know when to cut losses and run into the arms of a better quarry.

We all have a library of biases towards or against particular languages, apps, hardware, etc-- it has always been that way, but please do not swear that my choice is incorrect just because less books exist on the subject or not enough servers yet serve their masters in this doctrine. That is just Draconian.

A Transformation

2006-10-05T01:13:00.000-07:00

The game dev project moved along at the same rate, new ideas acquired and displaced through various methods of programming. But, sometimes the little achievements are not enough when a boat-load of small strokes amount to a handful of weightless results. I hit a point two-days ago with the GUI where I just had to take a break and regroup.

I met a new language and, simply put, have fallen in love. I will not declare my vows openly here, but it is a fine language (it seems) and full of possibilities and hopes. I believe I shall be able to rebuild the game in this language eventually as it seems to have similar graphic(s) capabilities. I am not abndoning Python, no, just altering my strategy a bit for the time being. I will not name the new language here, but the python logo to the left ( ->) may just indicate the new direction.

Warts and All

2006-09-25T14:18:00.000-07:00

The Jargon File's definition of the term "wart" is:

"A small, crocky feature that sticks out of an otherwise clean design. Something conspicuous for localized ugliness, especially a special-case exception to a general rule."

Object-Oriented

2006-09-24T19:30:00.000-07:00

Object-Oriented design and programming stands at times as confusing and\ or theoretical at best. Even greatly-experienced coders find themselves muttering "What the *$%& ?" occasionally, lost in a self-created world of classes, objects, and callbacks. The below paragraphs were taken from a programming forum and briefly explain a simple manner in which to view some of these areas of contention:

Originally Posted by Poisos (unedited)

Think of classes as your BLUEPRINTS for later manufactured objects! In your class definition you describe how you would build i.e. a car ... but since then there is no real car, right(only the pice of paper with your blueprint on it)? So you have to build a car according to this BP. This is done by making an instance of it.In Python: myCar = blueprint_of_a_car()

Now the little "data elves" in your computer actually build a car named "myCar". Now you would be able to drive that car or accellerate it and so an (ever drove a blueprint !?). This brings us to inheritance and polymorphism. If you would like to build a new car with special tires, seats or a different motor you wouldn't design a whole new car, now would you? Instead you would just change your motor or your tires and leave the rest as it is.

This is done by creating a new class (or blueprint) which inherits all the attributes and methods from your original car class (copy all information of your original blueprint to another) and then overrides the information i. e. of the type of motor what should be in the car (erase the data of your motor on
your copied blueprint and specify another one).

The Unexpected

2006-09-23T17:20:00.000-07:00

Today I thought I would have a lazy Saturday of fooling around with more graphics work with Photoshop, perhaps. I actually ended up working on a RNG and test statements to check loading elements of the game, and considered error-checking code for future use. I wrote psuedo-code outlining logic areas for the RNG and loading elements. By doing this, I possibly answered some questions posed in development so far such as how to load randomly-called images (RNG) into prepositioned widgets upon the screen.

Progress

2006-09-23T00:25:00.000-07:00

Made some decent progress today in the Python project: much research led to some simple yet important steps which has taken the GUI from rough to less rough, which at this point is acceptable and quite exciting. Most of the work today consisted of graphical work for the GUI, images edited and built in Photoshop. This topped off a week of chipping away
here and there-- and more to come.

A GUI Direction

2006-09-20T22:07:00.000-07:00

My initial challenge of the Python GUI interface has been solved! Thanks to help from a group of DaniWeb (** see link bar) coders, I have been able to create the initial background and 1st-layer image inlay. The code is working and will serve as a fine template for what I need to continue with. Thank-you DaniWeb!

Py for Today

2006-09-20T16:46:00.000-07:00

Python is a vast language. This is not generally portrayed as such even in many coding communities, but none-the-less, this language is deep. Some consider it almost too "simple" to be of much use, but the more I dig the more I find.

In regards to this current project, a game using a GUI interface, the logic of the game itself is not of any concern yet, but the understanding and control of the visual representation of the game is a whole other story. It is challenging in a fun way, actually, and there is much to play with. "Much" being many modules from different sources that do similar and at times very different things in the handling of graphics to the screen. "What are you trying to do?" asks Python: view images, animation, file manipulation, enhancement... Python and its libraries will be able to do it for you. The key is taking the time to research and experiment with these modules in order to find exactly what you are seeking.

I have been trying alot of things today in Python (while I listen to hours of Iron Maiden) in order to get the system to respond to code, hence, rendering to the screen my visual image for this 2D game. I have had some very interesting results which excites me, but... I have not figured it out yet. I cannot wait to begin writing the logic code and working on the NPC A.I..

Neu News

2006-09-20T04:07:00.000-07:00

Two new projects (one major, one minor) have begun:

I have been hired as a programmer with a video game company located in the Western United States; development has just started and no code has yet been written. The company is still obtaining the engine for this project and we do not yet know the language and specs of the project. The game will be made for the Nintendo Wii and should be released within two-years.

I have also started a small project written in Python. This is simply meant as an extended exercise in OOP, honing skills and syntax in order to be even more prepared when the professional job officially begins and the code starts being compiled.

2006-09-20T00:20:00.000-07:00

-NueDev is a technical log of current programming projects focusing on the languages of C++ and Python-