Skullspace Hardware Programming Challenge - Revision history

Takaji at 16:32, 4 October 2017

2017-10-04T16:32:08Z

Markjenkinsparit: clarified project joining

2012-03-24T05:59:33Z

clarified project joining

Markjenkinsparit: new level, invite to join, re-order

2012-03-24T03:57:31Z

new level, invite to join, re-order

Markjenkinsparit: hands on imperitive

2012-03-24T03:50:32Z

hands on imperitive

Markjenkinsparit at 03:08, 24 March 2012

2012-03-24T03:08:26Z

Markjenkinsparit: spelling, and re-wording

2012-03-24T01:30:39Z

spelling, and re-wording

Markjenkinsparit: spacing

2012-03-18T02:06:26Z

spacing

Markjenkinsparit at 18:27, 17 March 2012

2012-03-17T18:27:08Z

Markjenkinsparit at 18:20, 17 March 2012

2012-03-17T18:20:18Z

Markjenkinsparit at 18:18, 17 March 2012

2012-03-17T18:18:09Z

← Older revision		Revision as of 16:32, 4 October 2017
Line 1:		Line 1:
		+	[[Category:Events]]
		+	{{Archived}}
		+
	The Skullspace Hardware Programming Challenge is inspired by the puzzle solving spirit of the [http://www.skullspace.net/2011/01-level/secretchallenge.php Skullspace Challenge] -- but the major difference is that you have to show up at Skullspace, and write and run a program to operate weird and/or interesting hardware in order to solve each level. Specifically, there will always be a "secret message" that the participant must be access through an input/output device. You present the secret message to the challenge masters to show them that you've solved the level and they verify that indeed you did. (The level-master can be an automated web page eventually...)		The Skullspace Hardware Programming Challenge is inspired by the puzzle solving spirit of the [http://www.skullspace.net/2011/01-level/secretchallenge.php Skullspace Challenge] -- but the major difference is that you have to show up at Skullspace, and write and run a program to operate weird and/or interesting hardware in order to solve each level. Specifically, there will always be a "secret message" that the participant must be access through an input/output device. You present the secret message to the challenge masters to show them that you've solved the level and they verify that indeed you did. (The level-master can be an automated web page eventually...)

@@ Line 34: / Line 34: @@
 == Levels that are under development  ==
-Feel free to propose your own level and/or write yourself in as a fellow level master on any of these.
+Feel free to propose your own level and/or write yourself in as a fellow level master to join the development effort on any of these.
 *[[Back in my day, we punched tape instead of each other]]
 *[[Home cassette taping is killing the software industry]]

@@ Line 34: / Line 34: @@
 == Levels that are under development  ==
 *[[Back in my day, we punched tape instead of each other]]
 *[[Home cassette taping is killing the software industry]]
 *[[IDE can not copy that floppy]]
-*[[Peekaboo]]
+*[[Pawn to CLIÉ4]]

@@ Line 1: / Line 1: @@
 The Skullspace Hardware Programming Challenge is inspired by the puzzle solving spirit of the [http://www.skullspace.net/2011/01-level/secretchallenge.php Skullspace Challenge] -- but the major difference is that you have to show up at Skullspace, and write and run a program to operate weird and/or interesting hardware in order to solve each level. Specifically, there will always be a "secret message" that the participant must be access through an input/output device. You present the secret message to the challenge masters to show them that you've solved the level and they verify that indeed you did. (The level-master can be an automated web page eventually...)
 In some cases, the secret message will be obtainable with just read I/O, at other times correct write I/O will be required to unlock or solicit a response from an attached system which then responds with the "secret message". And in some cases, even after your code has obtained the secret message, the problem setup will force you to use a specific kind of output device in order to get it out of the system and into a form you can present.
 == Old hardware  ==

@@ Line 19: / Line 19: @@
 For the most part, any underlying hardware or software work behind each level can be openly published without actually giving away the level solution or secret message. The creation of new levels will an open project open to all Skullspace members.
-This never ending challenge can also serve as a permanent education fixture at the space -- an amusing entry point into hardware programming for new members and/or "right of passage". The open hardware and software design behind the levels will further serve as interesting works of study.
+This never ending challenge can also serve as a permanent education fixture at the space -- an amusing entry point into hardware programming for new members, perhaps even a rite of passage.. The open hardware and software design behind the levels will further serve as interesting works of study.
-== Levels that are ready and available for members to solve  ==
+==Order, Difficulty, and Recognition==
 None, currently. [[Proposed projects#Skullspace Hardware_Programming Challenge|Applying for project funding]] to accelerate the under development levels (below)

@@ Line 11: / Line 11: @@
 Like the [http://www.skullspace.net/2011/01-level/secretchallenge.php Skullspace Challenge] there will be an element of secrecy to create some excitement, "Rule 1, don't talk about hardware challenge". Each level will have solution code developed by the level masters to ensure the hardware actually works and the levels are do-able. But, this "official" solution code will not be published and neither will the secret messages.
-One difference -- instead of leaving clues that approrpriate clue/guess followup, each level will come with complete links that provide development software (such as cross-compilers), documentation on how to use them, and documentation on the IO devices involved. Where possible, quality, generic, docs that are already published out there on the web on this hardware and software will be used over custom docs specific to the level. So, the path to each secret message won't require guessing, but careful reading and writing of compliant code.
+One difference -- instead of leaving clues that require appropriate clue/guess follow-up, each level will come with complete links that provide development software (such as cross-compilers), documentation on how to use them, and documentation on the IO devices involved. Where possible, quality, generic, docs that are already published out there on the web on this hardware and software will be used over custom docs specific to the level. So, the path to each secret message won't require guessing, but careful reading and writing of compliant code.
 But, this difference doesn't make the challenge easy -- it can take a lot of time and patience to get hardware code right, even when its documented. The requirement of having to program tangible platforms external platforms will in some cases make things more slow and frustrating compared to a purely emulated environment.
@@ Line 17: / Line 17: @@
 Anyone complaining about the levels can be told to RTFM -- and as such the "official" secrecy of the solutions (that is, Skullspace operated sites) can be kept in place -- there isn't the same compelling reason to release them that there is with a clue based challenge where people naturally just miss some clues and end up begging for published solutions.
-For the most part, any underlying hardware or software work behind each level possible can be openly published without actually giving away the level solution or secret message. The creation of new levels will an open project for Skullspace members.
+For the most part, any underlying hardware or software work behind each level can be openly published without actually giving away the level solution or secret message. The creation of new levels will an open project open to all Skullspace members.
-In addition, with actual solutions not made officially available, the challenge can serve as a permenant education fixture at the space. The challenge can serve as an amusing entry point into hardware programming for new members. The open hardware and software design will further serve as interesting works of study.
+This never ending challenge can also serve as a permanent education fixture at the space -- an amusing entry point into hardware programming for new members and/or "right of passage". The open hardware and software design behind the levels will further serve as interesting works of study.
 == Levels that are ready and available for members to solve  ==
@@ Line 27: / Line 27: @@
 *[[Back in my day, we punched tape instead of each other]]
 *[[Home cassette taping is killing the software industry]]
-*[[AMIGA say "IDE floppy is for PC fools]]
+*[[IDE can not copy that floppy]]
 *[[Peekaboo]]

@@ Line 30: / Line 30: @@
 == Levels that are ready and available for members to solve  ==
-None, currently. Applying for project funding to accelerate the under development levels (below)
+None, currently. [[Skullspace Hardware Programming Challenge|Applying for project funding]] to accelerate the under development levels (below)
 == Levels that are under development  ==