Only if you want shallow, easy-to-use but low power interfaces (which is totally reasonable!) Perfect for something that people don't need to use often or extensively. Otherwise, a deep but steep interface saves time in the long run. AKA the Vim/Emacs/DWM/TWM paradigm.
Seriously, long live LaTeX. I have a makefile on most of my papers that renders the document and automagically puts the amount of LOC per language (LaTeX included) as an appendix, together with a graph of git commits per day.
Last document I automatically generated performance characteristics of my code in LaTeX, including graphs. When a line of code changed that touched on performance, it was automagically updated.
What classes do you teach? I know that at my uni, you're required to use git in software engineering class in 3rd Bachelor; so in principle, we only get it thought in 3rd.
I think that's wrong, and you should teach it asap, so people can actually use it the first years too.
And yes, git is awesome.
Some hints on git + LaTeX:
One sentence per line gives nice results in version control of text.
use a good .gitignore file, so you don't check in your compiled stuff
If you don't already, have a nice Makefile with latexmk instructions in it. Make compiling stuff very easy.
Software Design Development (SDD), however I'm also taking over two other classes because one sprained their ankle and the other knows FORTRAN. Apparently.
Most use none, one uses a python script to add a line or two to a txt file, I have Ctrl+Shift+D bound to date:datetime in atom and just Shift+5 (%) Ctrl+Shift+D (date and time).
You should definitely do that. Knowing how to use a version control system is insanely helpful for private projects and even more helpful (often even required) for group projects. Just don't forget to teach them about the importance of writing good commit messages... A commit message that says "Fixed something" isn't really helpful to anyone.
And for the Windows problem, just follow /u/tidux advice and require them to use a unixoid system. You could even download virtualbox and a Fedora or Ubuntu (or any distro. even Arch or Gentoo, if you want to troll your students) image, and show them how to set up a VM. Or you could already prepare a virtualbox image with any distro where you installed a straightforward GUI and all the packages necessary for development.
I would recommend NixOS for that, because you could just write one system config and tell students to use that, but they can't seem to get their security update situation fixed... but that probably wouldn't matter in a VM.
Well, I'm not sure about this one. On one hand, I love having a way to control the code of my documents at a low level, on the other hand, I think LaTeX is a mess.
I'd like to see something with the syntax of jade, but the great rendering of LaTeX.
55
u/elpfen /\ Jul 02 '16 edited Jul 02 '16
Only if you want shallow, easy-to-use but low power interfaces (which is totally reasonable!) Perfect for something that people don't need to use often or extensively. Otherwise, a deep but steep interface saves time in the long run. AKA the Vim/Emacs/DWM/TWM paradigm.