meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 11 months |
| seen | May 17 at 20:56 | |
| stats | profile views | 5 |
|
May 31 |
awarded | Yearling |
|
Mar 24 |
awarded | Critic |
|
Mar 21 |
awarded | Citizen Patrol |
|
Mar 16 |
revised |
Implementing a “tech tree” Move explanation to top |
|
Mar 16 |
revised |
Implementing a “tech tree” Remove building example code |
|
Mar 16 |
revised |
Implementing a “tech tree” Fix variable name |
|
Mar 16 |
comment |
Implementing a “tech tree” I edited in another (somewhat nicer) implementation. There is still lots more you can do with enums, like implement abstract functions for each instance. |
|
Mar 16 |
revised |
Implementing a “tech tree” Added 2nd implementation |
|
Mar 16 |
awarded | Editor |
|
Mar 16 |
revised |
Implementing a “tech tree” added 229 characters in body |
|
Mar 16 |
awarded | Supporter |
|
Mar 16 |
answered | Implementing a “tech tree” |
|
Mar 13 |
awarded | Nice Answer |
|
Mar 7 |
awarded | Teacher |
|
Mar 7 |
answered | Which approach is better: Frequent small updates, or occasional large ones? |
