cs-topics VS semver

But a software developer is not a software engineer, and I'll have to work on the side to make up for the holes in the developer cursus. I turned to reddit to look for recommandations, and I'm quite enthusiast with the TeachYourselfCS learning track - which I started along the Java lessons.

HtDP [0], CS50x [1], and whatever strikes your interest from teachyourselfcs [2], in that order.

Also highly recommend the book for nand2Tetris after CS50.

[0] https://htdp.org/2023-8-14/Book/index.html

[1] https://www.edx.org/learn/computer-science/harvard-universit...

[2] https://teachyourselfcs.com/

This is a really good fundamentals resource: https://teachyourselfcs.com/ They list books and videos.

Study computer science, either through college or via teachyourselfcs.com.

In the current market it's better to just put some resources together and learn from platforms like OSSU or Odin Project or FreeCodeCamp to really dip your toes in. The bootcamp era was a byproduct of interest rates at the time and shoveling in as many bodies as they could into the field. You can literally build a curicullum yourself for 6 months and see how you like it while working retail or whatever else. Or for the more technical side: teachyourselfcs.com gives you some ideas if you wanna start actual cs concepts.

https://teachyourselfcs.com/ also has a bunch of great resources for CS fundamentals.

Knowledge in a programming language is not complete without a full CS education. I recently found out this site: https://teachyourselfcs.com/

what's your opinion on teachyourselfcs.com for the fundamentals?

Using Conventional Commits ⭐ as a standard for your commit messages, makes Semantic Versioning 🔖 as easy as can be, with tools like Conventional Changelog 📄 Standard Version 🔖 and Semantic Release 📦🚀

Semantic Versioning: for every update (major, minor, or patch) made, increment the version number according to semantic versioning.

npm automates the process of installing, updating, and managing dependencies, which helps to avoid "dependency hell." It supports semantic versioning (semver) that automatically handles patch and minor updates without breaking the existing code, thus maintaining stability across projects. npm also provides the capability to run scripts and commands defined in package.json, which can automate common tasks such as testing, building, and deployment.

We are pleased to introduce Semantic Versioning and release channels to Snyk CLI from v.1.1291.0 onwards. In this blog post, we will share why we are introducing these changes, what problems these changes solve for our customers, and how our customers can opt-in according to their needs.

Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org

I believe neovim follows semantic versioning. https://semver.org/