Mac

For many students in mathematics, physical sciences, engineering, economics, and other fields with a heavy numeric component, MATLAB is their first introduction to programming or scientific computing in general. It can be a good tool for learning, although (in my experience) many of the things that students and researchers use MATLAB for are not particularly demanding calculations; rather they could easily be conducted with any number of basic scripting tools, with or without statistical or math-oriented packages. However, it does have a near ubiquity in many academic settings, bringing with it a large community of users familiar with the language, plugins, and capabilities in general...

There's much more to managing a project with git beyond just committing code and working with branches. GitHub-Driven Development is a process that will help you organize and manage the progression of a project on GitHub, although much of this could be applied to other systems, such as GitLab, as well. This concept isn't only for developers; it can be used for project managers or anyone involved in the development of a project—it could even be applied to non-code projects...

The Docear academic literature suite blends Freeplane and JabRef to make a comprehensive academic paper-writing application, with support for mind-mapping, citations, notes, and many other features. Writing a major scholarly paper can be a daunting undertaking. Turning a collection of scholarly research into a coherent paper requires a great deal of organizing and planning. To simplify that task, there are many tools available to assist a researcher with keeping track of their bibliographic citations, and there are also plenty of tools to help a user organize their thoughts...

During my career I have spent a lot of time packaging other people's code, writing my own, and working on large software frameworks. I have seen projects that still haven't released a stable version, never quite hitting 1.0, while others made 1.0 releases within months of beginning development, and then quickly moving on to 2.0, 3.0, etc. There is quite a variance in these release cycles, and this coupled with maintaining large projects can make things difficult. I will go through some of the decisions we have faced in projects I have worked on and the pressures on the project. On the one extreme, users would like to have a stable API that never changes, with dependencies that don't specify a minimum version so that they can choose whatever version works best...