interpreter pattern parting shots wherever you are on your programming journeydecide right now that you will do the hard work needed to become better you do this by working on programming projects and doing programming challenges one such challenge by jeff bay can be found in thought works anthologypublished by the pragmatic programmers attempt non-trivial project (one that will require more than , lines of code to solveby following these rules only one level of indentation is allowed per methodthus no if statements in loops or nesting you're not allowed to use the keyword else all primitive types and strings must be wrapped in objects-specifically for the use they are put to collections are first classand as such require their own objects don' abbreviate names if names are too longyou are probably doing more than one thing in method or class--don' do that only one object operator allowed per lineso object method(is okbut object attribute method(is not keep your entities small (packages objectsclasses linesmethods lines no class may have more than two instance variables you are not allowed to use getterssettersor access properties directly exercises follow the same thought process we used when defining dsl for the restaurant to define dsl that you can implement in your own to-do list application this dsl should allow your program to pick up cues like "every wednesday and translate them to recurring tasks also add awareness of date and some other indicators of time relative to some other date or time