Explore >> Select a destination
|
You are here 
|
locklessinc.com | ||
| | | | |
blog.sanctum.geek.nz
|
|
| | | | | [AI summary] The provided text is a collection of various technical topics and articles, including: 1) A guide on using command-line tools for development, covering debugging, profiling, and performance analysis with tools like GDB, Valgrind, and others. 2) An in-depth look at version control systems, from early systems like RCS and CVS to modern ones like Git and Mercurial. 3) A discussion on shell scripting, including Bash, custom commands, and automation. 4) A series of articles on Vim, covering configuration, diffing, and debugging within the editor. 5) Miscellaneous topics such as terminal usage, shell configuration, and system administration practices. The content is written in a technical style, suitable for developers and system administrators workin... | |
| | | | |
initialcommit.com
|
|
| | | | | Makefiles are used to build and compile programs. We explain how Git's original Makefile works line by line to help clarify how programs like Git are developed. | |
| | | | |
mesonbuild.com
|
|
| | | | | [AI summary] The Meson Build System's Wrap dependency system automates the process of embedding third-party libraries and dependencies into a project, simplifying multiplatform development by allowing automatic downloading and integration of required components. | |
| | | | |
claritydev.net
|
|
| | | Lately, I have been asked increasingly often for some tips on how to become a self-taught developer, so I thought I'd write a post about it, reflecting on my experience and pointing out the things I'd do differently. In this article, I'll try to give general advice on how to improve for those considering or maybe already on the way to becoming self-taught software developers. It should be noted that the focus of the post is on front-end development since that's what I did; however, a majority of the advice can be applied to becoming a software engineer, irrespective of focus. | ||
