5 ms·
How about a competition where: Round 1) You write some core algorithm Round 2) You write a library that uses algorithm Round 3) You write a tool that use
by icefox 17y ago
How about a competition where:
Round 1) You write some core algorithm
Round 2) You write a library that uses algorithm
Round 3) You write a tool that uses the library
Round 4) You write a different tool that uses the library, but have 1/2 the time
The end tools would be tested with a million edge cases.
Round 5) Someone else on your team that has not seen the code yet gets 2 hours to fix as many edge cases as they can.
Testing design and maintainability
- icefox 17y agoThe more I ponder it the more I am curious just how this would turn out. Would it be like usability tests were in round 5 the team is screaming at the team member behind the sound proof glass while he fumbles around? Would each group end up with their own version of "The Little Manual of API Design" tweaked for their language/tools? Would writing tool #2 actually be harder than #1?
- nopassrecover 17y agoHeh I thought this was sarcasm/satire (especially given the million edge cases) but it's not a terrible idea as you say.
- cbr 17y agoOr simpler: you solve problem X, making you code as clean, documented, and extensible as you can. Then a team member has to extend it to solve X', where X' is designed to show up bugs in the solution for X (turkish language insteadof english, etc).