Raja W.

Hello! This is a portfolio of most projects I have ever made.¹ Really! Because I have a large array of projects to organize, I have created a system to title and curate projects that makes it easy as possible to find and group similar projects.

Let me preface by saying that most projects are in a completely unusable or unfinished state. Most that are unfinished will continue to be and forever be unfinished.

Featured projects

ID string

Each project is assigned an id string, which have several sections that make them easy to search up. For example, this website would be catalogued under the id A150P0000A00. The current version of the id string is revision A. For revision A, Each project is assigned a 12 character identifying string.

x xxx x xx xx A xx
- --- - -- -- - --
|  |  |  |  | |  └-> object #
|  |  |  |  | └-> id string revision 
|  |  |  |  └-> 5. object series
|  |  |  └-> 4. frameworks used
|  |  └-> 3. exigence
|  └-> 2. disciplines
└-> 1. purpose

The object # can be thought of as the number of attempts I have tried a project. It’s how many of a specific project I have tried to create. It’s not in order of creation date – it’s probably in order of catalogue date. You would be surprised how high this number can get.

The following tables are subject to change.

1. Purpose

Purpose is really simple – what use does this project have?

2. Disciplines

Each digit in this three digit number represents a different discipline that was required to make this project. It’s basically a list of disciplines required for a project. No more disciplines is represented with a 0. For example, a project that just used programming would start with R100.

3. Exigence

Exigence is a deeper purpose to the project. Why did I make it?

4. Frameworks, 5. Series

Because these tables will be huge, I have dedicated another page to tabulating Frameworks and Series. This can be found here.