I'll try to add to this when I think about things that are implemented already. For example, you would definitely want to check out the ca.tecreations package files. Worth noting are any override-by-name files, ie, File.java, Point.java, etc. Definitely look at the *Tool classes because they will house much of the generic, possibly static code. Definitely look at TecData.java and ProjectPath.java and understand how to set the ProjectPath instance ProtectionDomain for your own projects to access the ProjectPath functionality specific to your project.
Of particular interest is SystemTool which allows to compile Java and run Java and OS commands, ie any other program.
Deploy and JavaCompiler and BuildProject are very stable. Sometimes there are issues when moving from one project instance to another within the same project, so like, when I move work machines from one room to another. There is that, but mostly, I've been able to correct the errors, usually naming issues and sometimes moving code from one class to another, but there is usually a remedy. I think I've only made a few hard resets to snapshot a couple times, but they are invaluable, so definitely look in the apps.deploy.*.java files as well. The issue with the PUT progress dialog in Deploy is long-standing, if anyone would like to attempt a rewrite with improvements. Just reach out.
So, look at Design Considerations, and after that, come back...,.... , Should I trace?
So I generally think, optimize as I go, advance slow and steady, and shorten... as beneficial. But I do this without any reward while on this Earth.
And no, I'm not going to Mars any time soon.
You'd have to train tim and there's no way that will work anymore.
I hear you. Backup it is.
Yeah, because you know how ridiculous that sounds? 3 Machines, programmable by humans that know a codebase? Laughable at best.
Yeah, signedBy, because my cacert.org signing key is expired now.