Live From Code Noob Central

It's been a while!

Sun, 22 Jul 2012 23:29:37 +0200

Well I was really busy actually - finding a job, moving countries, dealing with movers, insurance claims, doctors, flat hunting and all that on top of a really challenging new job (no worries, I am surviving!).

So here I am, finally tackling something new! Blame the bookshop Foyles, where I found this Visual C# programming book by Jonathan S. Harbour and immediately started playing with WindowsForms. It took me a while, as the book clearly forgets to tell you how to actually open new projects (good thing author has a forum!!)

Anyway, the first project is familiarizing yourself with drawing shapes and bitmaps with GDI+. The structure of the code is fairly easy once you’ve understood it, even if you have never looked at C# before.

The code is divided in easily identified categories.

At the top you have your global statements, where you create your main objects.

This is followed by the Form1_Load section, which allows you to define the settings of your Form. In this case, the author uses the PictureBox control to blend with the Form1 frame and define the canvas. It is in the section as well that the settings for the Bitmap surface and the graphics device, as well as the random generator.

Think of the Bitmap as a polaroid taken after each change. It is independent from the PictureBox and can be saved. The graphics device is defined as the tool that will impact on the bitmap surface.

After the Form1_Load, it is time to work on the graphics device function, which gets its own section. This first project proposes to draw lines in random colours and widths. The colour of the line is defined by randomly assigning values to each segment the ARGB scale. A Pen object is used to gather the coordinates defining the beginning and end of the line.

A Timer object is also used in this particular instance. It defines the interval at which a new line is drawn. This object is also part of the Form1_Load section.

And finally, the code closes with a “free memory” object. This object basically throws away the data stored regarding the graphics device, the surface and the timer and is good practice when running code that uses a lot of memory.

I’m not pasting the whole code here but I thought the section on creating the graphics device was the most interesting:

Meet Arnold

Tue, 17 Apr 2012 11:26:54 +0200

You’re going to ask… who’s Arnold?

Well, to tame beasts and others, I give them pet names. There is a spider on my kitchen wall who currently answers to the sweet name of Bert. The dead pixel on my old laptop is called Matt. Giving it a name, helped me accept that obnoxious red dot in the middle of my screen (I lie, it’s in a corner)

So, for you not to feel stalked in your every move… meet Arnold. My personal spybot. Tracking you, stalking you… it KNOWS you and what you are doing here….

…

Ok, I’m mentally challenged today and I have delusions of grandeur. All this to say, I’ve hooked my blog up with Google analytics. More statistics, more numbers! Turns out the person who wrote the html of this particular theme was even kind enough to include a Google Analytics meta. No pasting scripts, just had to paste my ID. thank you tumblr!

So keep visiting me… Arnold would really truly miss you otherwise. (yes, in my head, Arnold looks like r2d2… what’s wrong with that?)

Decking the cards part 1

Tue, 17 Apr 2012 11:00:00 +0200

Coffee breaks are generally good but this one was particularly productive as I talked some more about my little blackjack game with a couple colleagues and I think we have pretty much sorted a way to limit the randomization to one deck of cards.

I have to work on this but I thought I’d lay down the theory before playing around with the technical side. So theorically, we want all cards to belong to one deck (52 cards). The goal is therefore to create the deck using nested arrays. Each card should get a unique value between 0 and 51 and the function deal() will therefore only need to use one Math.random on 52 values instead of two on suits and numbers respectively.

Adding a third property to each card will permit to know if the card has already been distributed or not and a simple recursion should run deal() until the card selected by the Math.random has not been distributed before. Or while loop, haven’t decided yet. I also have to create a method that changes the distributed property when the card is pulled by the deal() function.

I haven’t decided yet on what to do when the deck runs out. I should probably check what happens in an actual blackjack game before doing so.

Thanks for the input, colleagues!

photography credit: http://www.ath1337.net

Stroll through the Games industry

Sat, 14 Apr 2012 14:53:50 +0200

Let’s deviate from our programming babble to take a little stroll through the Games industry. Why? Well, because I take an interest in it and this is my blog, deal with it. Why? Actively seeking jobs, it seems games industry recruiters are quite interested in my profile. Don’t ask me why, it must be classified information.

At any rate, I’ve been applying to a few positions in the Games industry and I’ve observed various side-effects: my mother freaked out (but she does that whenever I apply to something that looks “not serious”), my brother started talking to me (let’s not go crazy, only when he really cannot play Starcraft because he’s shoving food in his mouth) and people have started asking me for my opinion when they can’t pick which video game to play (how am I supposed to pick between Oblivion and Left 4 Dead, I do not really know. I just give random answers). But the most interesting was one of my friends saying “Really… Isn’t it a bit nerdy to work in the video games industry?”

Well ok, I can understand that the perks I got in the fashion industry were much more interesting to her. Which woman in their right mind doesn’t know how to take advantage of half price designer shoes and handbags? But funnily enough, the processes behind creativity is what interested me in fashion and it is also what interests me in video games.

Sure I like playing. It’s fun to be actively involved in the adventure rather than just watch it. But really what I find fascinating is the design, the creativity. How lines of codes build these worlds, how complex algorithms engineer the game and how your characters actions influence the scenario. I want to dig deep behind the wonderful graphics and dissect everything, understand all the processes, the behaviour of the game, the behaviour of the people who play the game.

That does sound a bit nerdy, doesn’t it? I can live with that. I can be a nerd with designer handbags (or not, I’m trying to sell them) who spends hours dissecting processes or building little JavaScript text-based games.

This time of job hunting is hardly a walk in the park. Every rejection stings. But I think I have learnt a lot. About myself, about my interests and about various industries. I wanted to write a little bit about this one because working on my little Blackjack game made me think about the incredible work done by game studios.

And just to conclude: if you do not know what to get me for my birthday, feel free to look up that great tetris lamp! (source: tomsguide.fr)

The Blackjack deal

Fri, 13 Apr 2012 23:18:00 +0200

Tonight, I am proud to post that I have successfully finished my JavaScript Blackjack game challenge on codeacademy.com! Of course there’s always room for improvement but give me a break, I have a NEARLY fully functionning blackjack game, which now only requires pulling cards from a deck to avoid generating the same card twice.

One challenge a day though! My challenge for today was to make the actual game more “readable”.

The original code does not include creating suit names, or clearly identifying face cards, which makes it difficult to read when your output resembles: “you have card 7 of suit 2 and card 1 of suit 4 and dealer has card 4 of suit 1 and card 13 of suit 1”.

Not exactly user friendly.

Codeacademy proposes to include the information mentionned above using switch statements. I have decided to take another route and used arrays. I created two new methods in my Card constructor, one to get the suit name and one to get the card number or face.

When the card is randomly generated using the deal function here below, thevariables s and n are only numbers. Suit goes from 0 to 3 (four suits) and card number goes from 0 to 13 (fourteen cards).

The two methods getNumberLab and getSuitLab are then called when printing the hand, transforming the numeric variables, which correspond to positions in the suitName and numName arrays into actual cards and suits.

Easy right?

You can find my complete code here: http://pastebin.com/fLmp0THi - all credit to codeacademy.

Image Credit: by zari 906 So you remember inception and the...

Sun, 08 Apr 2012 15:57:22 +0200

Image Credit: by zari 906

So you remember inception and the dream within the dream within the dream and ooooh Leonardo di Caprio. Got distracted, sorry.

Well in programming (and math), there’s the nightmare within the nightmare within the nightmare. Also known as… recursion. Just typing the word makes me shudder although let me tell you, I am doing my best to tame this beast.

So if I got this well…. Recursion = calling a function inside itself until the certain conditions (base case) are met. There’s also a termination condition, in case your input is really off its rocker. It’s supposed to keep your program from going all Nyan cat on you, in infinity and beyond.

Anyway, recursion… It’s my first real programming pet-peeve, if you don’t count OOP, which I just forget. The information just slides out of my ear and drowns into a puddle before I can do anything about it.

Stop ranting, it’s time to go beat up recursion. Oh yes.

Introduction to Madness

Sun, 08 Apr 2012 11:56:40 +0200

Welcome to my new blog… Where you will be able to follow my adventures in the terrifying, dark-side-cookie, globally crazy world of programming. That’s right people, contrary to all normal people who suddenly wake up with the urge to write a blog about cooking (I love those blogs, by the way), I woke up with the urge to share my nerdy experience with you.

So you’re going to ask, who in their right mind suddenly decides to take up programming at the sweet and old age of 27. Well, first of, this project has been growing in my little brain for quite some time. To be perfectly honest, I bought my first geeky book a few years ago. It was HTML. The will died after 5 weeks.

In 2011, I made a new investment… book introducing two programming languages, to build a game. I thought, there’s a winner! Two languages, and a real project! Oh boy. After an afternoon of trying to understand how they were trying to make me use cmd, I gave up.

My life changed very beginning of 2012, when someone introduced me to the magic of codeyear.com - interactive, little modules, new materials every week. Quite proudly, I can now say I’ve been studying JavaScript with them for 3 months.

That’s right, three whole months! Quite a feat for someone with the attention span of a teaspoon and let me tell you, it’s not rosy everyday.

In conclusion, why this blog? Well, in time, I hope to show you that programming, and the dark side of the IT industry (there is no light side but let’s lull ourselves in a false sense of security for a while) are not that scary. Maybe… ^_^