*sam* Posted Aug 13, 2007, 6:22 pm	Just something small: you can now issue ladder challenges from the lobby. Click on the name of someone who isn't in a live event and you'll see extra options. You're automatically registered for the ladder if necessary.
*Zothen* Posted Aug 13, 2007, 6:51 pm	Yeah, nice feature! thx Sam! What happens when one or both players are not signed into a ladder when issueing a challenge?
*sam* Posted Aug 13, 2007, 7:02 pm	Quote: What happens when one or both players are not signed into a ladder when issueing a challenge? Quote: You're automatically registered for the ladder if necessary.
Jag Cancer Posted Aug 14, 2007, 1:12 am	Lol. Nice hacking Sam I do that all the time - suggest something cool and quick to the client, they say yes, I do it, they're happy. Then someone points something out I hadn't considered... Such is a coder's lot.
*JD_Basher* jd.basher@charter.net Posted Aug 14, 2007, 1:37 am	Quote: Lol. Nice hacking Sam I would beg to differ on Sams' behalf...... Hacking implies covert access to memory or entry to files usually not meant to be available. "Developer"  is a better description of what Sam does. Hence, the game we all play!
Clifton Posted Aug 14, 2007, 2:22 am	great addition! I gotta admit...I'm kinda surprised at how often new stuff gets added. I love it! Keeps my attention piqued. Keep up the good work!
Jim Posted Aug 14, 2007, 8:51 am	Quote: Hacker, as it relates to computers, has several common meanings. Hacker is often used by the mass media to refer to a person who engages in computer cracking and is also often by those in computing fields to refer to a person who is a computer enthusiast. http://en.wikipedia.org/wiki/Hacker
Jag Cancer Posted Aug 14, 2007, 1:06 pm	However, the term 'hacking' was used as a programming term before it was adopted to describe 'illegal entry to computer systems'. Hacking in a traditional sense is making particularly talented/lucky/clever changes to or adding code without full planning or according to a spec. In commercial projects code is created according to the design spec and managed. In smaller projects it tends to be hacked together. ie no proper planning or design - just writing as you go. While this is generally quicker and requires more knowledge of the system it tends to result in more unreadable code and a lack of cohesive structure. Thus I described what Sam did as hacking. If it was planned and designed then the eventuality would have been catered for as it would have been designed, written and tested :P Hacking is ideal for prototyping as a prototype app doesn't need full functionality as often it is purely for use as a 'proof of concept'. If ya gonna quote wikipedia try: http://en.wikipedia.org/wiki/Hacker_definition_controversy BTW, it was not meant in a negative way at all. Most of the stuff I do is hacked together due to lack of proper design brief by clients.