code2flow is an experimental script which sweeps through your project source code, looking for function definitions, then does another sweep, looking for where those functions are called. It connects the dots and presents you with a flowchart estimating the functional structure of your program. It is especially useful for untangling spaghetti code and getting new developers up to speed. code2flow is experimental and meant to provide a rough overview of the structure of simple projects. Source code which is just a little esoteric will break this. Even with normal code, there are many known limitations and many outright bugs.
wger Workout Manager is a Web application that can manage your workouts, group them into schedules (A>B>C), and print them as PDFs. It helps you keep a log of the weights lifted in the different exercises as well as your own body weight and can also create and manage your diet plans.
MetaPath is a tool for the analysis of metabolic pathways and associated visualization of experimental data. Built on the MetaCyc database, it provides an interactive map in which multiple pathways can be simultaneously visualized. Multiple annotations from the MetaCyc database are available, including synonyms, associated reactions and pathways, and database unification links. Metabolomics change data can be imported via simple CSV formats for visualization on targeted pathways. Pathways can be mined and removed algorithmically to identify key regulated pathways within a given dataset, providing a simper route to metabolic functions.
SQLet allows you to directly execute SQL on multiple text files, right from the Linux commandline. In one single command, you can read in text files (with or without header lines) and perform arbitrary select statements, including joins over several files. SQLet can thus replace awk or grep in some instances.
Flawless traps exceptions and then uses git blame to send an email to the developer who wrote the buggy code. Even if a particular line of code causes thousands of exceptions, only one email will be sent. It uses git-blame to figure out which developer is responsible for a particular exception, and will only email that developer. If you set report_only_after_minimum_date, then Flawless will only report exceptions caused by code modified after report_only_after_minimum_date. You can mark certain files/functions as library code, and when an exception originates in those files/functions, the caller will be blamed for the error instead of the library code.