pouët.net

Your clock is wrong, it's 16:28 here.

welp, did the interview, took 2hrs.... they said i'm qualified, and sent me home with the book... i think this means i probably got it! :)

fame and fortune here i come!!!

GOOD! :))) wtg xteraco

reading between the lines of the email you got its obvious that the guy sent it to you wants _you_ for the position. otherwise he wouldnt give you all those shitloads of hints on how to pass the 2nd level :)

Congratulations if you got the job, how exciting!! I really hope you can find suitable programs to steal for your new (probably ficticious, but who cares) job, I guess that if they ask you to write anything by rbraz that he posted on a public forum then yo'll be able to meet the deadline eh? :-P

Welcome to the world of paid programming, where the ability to jump into an existing project full of someone else's crappy non-modular code and fix it up so that it doesn't suck is a very useful skill indeed (and one you're going to use a lot, probably).

Thanks for all the advice everyone, its nice to have the extra encouragement ... I wont know if I got it for sure untill tommorow, they said they would call ... I'll keep you guys posted though.

For those who were following this post... I got the call, and I start working as a professional web coder on July 9th! Thanks again for all the advice :)

Good luck! And hey, you didn't end up coding games!

Thanks! Hehe, no game coding.. Pretty excited though, I'm going to be working with C# and ASP.NET.

Congratulations. Welcome to hell.

man they've given you the bad language for web coding, you could do so many dirty things with PHP instead :D

.NET kids make me laugh

nice oxymoron :)

All my personal projects are done in PHP, unfortunately I have no choice in language.

smash: i'm not a coder with your experience but seriously, procedural code follows exactly assembler language whereas object is not a concept known by standard machines, so that you have to add all the management of the objects over the top. Though this CPU and RAM overhead is prolly peanuts compared to the capacities of nowadays' machines.

if you try to trace some oo code through a debugger/disassembler, it's not that readable compared to some C code. That's why a particular decompiler is better for oo code.

and all the better because oo implementation is usually managed through virtual machines which slow down the run time, as you said.

at the end and in the facts, oo apps are way slower. But as coding time is precious/pricey and cpu/ram supercheap, oo is clearly the winner choice for pro teamwork projects.

to be accurate, i was thinking of Delphi as a *non managed* oo code : delphi uses complex objects for its interface, so if you trace a delphi code through a common debugger/disassembler like ollydbg you are quickly lost among the extra code added by the delphi compiler, while a scener has made a nice tool called DeDe (Delphi Decompiler) in order to reconstitute the delphi interface and classes :)

Pouet uses .net!! har har, get it, pouet.net!

Ok, sorry... Its been a long day, I had to.

zest: seriously, where are you reading this stuff from? :)
in c++ a class with no virtual methods directly compares to some c functions and a struct. you could get more or less exactly the same assembler out of it.
but in the c++ version you have wealth of nice language features that go with it, and more things you can tell the compiler to help it along. there are some you know have a little bit of extra overhead like virtual calls, and you know when and where you should avoid using them where it'll make a difference.

if you're talking about object management and ram overhead maybe you're talking about interpreted oop languages like java, which are probably better compared to interpreted procedural languages like basic. :)

if you're a coder who sits there saying "im not going to use c++ cos its oop and it'll be slow, so i'll use c, but thats compiled so it'll be slow, so i'll write it in assembler.." you're probably the kind of coder who didnt know what they were doing in the first place, and would be better off just reading up on what the stuff in their language actually does and getting to know what the compiler does with your code. :)

( i cant believe im arguing about this. time to move on. fasttracker rules! megadrive is better than snes! )

About OOP, a nice read. At least an eye opener for those who have had a very basic education about it.

http://okmij.org/ftp/Computation/Subtyping/

smash: i haven't mentionned C++ because it's indeed quite readable in a disassembler, i was rather thinking of Delphi, and interpreted and/or managed languages like Eiffel, Java, C# (.NET), etc...

anyway my main complaint was that advanced oop languages make you clearly write everything (good for teamwork and bug protection) but a loose and lazy language like PHP is like a fresh breeze :P

zest: so you didnt consider comparing to c/assembler any oop langauges which actually fully compile their code? great comparison there! :) yes, it's reasonable to suggest that interpreted or JIT languages might not be as efficient as compiled ones, you're absolutely right. :)