Greywacke, signing in.

Fist things first - the name - why "GreyWacke"?

Well, this is actually a nod to myself in the alternate reality in which I chose a path of science, rather than video games development. Greywacke happens to be the name of a particular type of rock of which the name stuck in my mind. I've since adopted it as an internet pseudonym because, well, Geology Rocks! (no, I'm not sorry).

Both Science (in various forms) and Video have been interests of mine for as long as I can recall, though for many years I seldom considered the latter as a serious career path, and consoled myself with modding and map-making in my spare time.

That was until I spotted a Video Game Design course at a different college whilst studying that I decided to realise the potential of building a career from what was before simply a passion I entertained in my pass time.

And so, I took steps towards making this dream a reality (with the additional byproduct of me employing this awful cliche to express my position).

It has to be said that an interest in science is likely a better supplement to a career in video game development than the other way around, so it would seem like a win-win scenario!

I say this, because many a time possessing an interest in another field of study has provided inspiration for a game mechanic, or informed a the design of a piece of art or architecture in an environment.

On the subject and nature of the intended future content of this blog - this is to be my online repository of information - a place in which I can store development process, thoughts and [hopefully] useful information on various subjects; usually related to video games and/or the development process.

This archive can then be accessed whenever necessary in order to demonstrate to others, or to remind myself of how a particular endeavor was undertaken or the thought process behind it. I know many a time I've had to dig into the documentation of an old project to suss how I achieved a certain effect.

I've always got a project on the go in my spare time, so this is the place I intend to talk about such projects in some form of development logs. With any luck, these will be both insightful to myself as I analyse my own work, but also to any potential readers who seek to gain some useful insight into my process.

There is potential value in storing such information for future use, but I suspect that there is also value in extracting thoughts and giving them a "physical" presence in the world. That's not to say that the neurological machinations behind such thoughts are not physical, but rather that there are benefits of making said thoughts manifest.

I suspect that in my ramblings that I am likely to traverse many tangents similar to the one above, but as this is in fact a personal blog - I perceive relatively little harm in dong so.

That said, I would like future posts to be useful to anyone travelling the same trail as myself. I don't consider myself a blogger as such (and likely never will), but I am interested in contributing some of my work to the wider community as a whole.

This is in part a form of repayment for the many times a forum or blog post has rescued me from many a potential headache by providing useful programming and software tips and advice.

Consequently, I'm happy to allow material owned by me posted on this site to be used in projects the projects , provided I haven't stated otherwise , of course (a spot in your credits would be appreciated, however). Naturally, if work posted by me does not belong to me, then you ought to seek the original owner's permission, but the majority of my work should be fair game for pilfering.

Here's hoping I can provide something worth stealing, eh?