I am delighted to announce that I have just passed the AWS Certified Developer โ Associate exam...so happy to add some color to my existing AWS badge ๐ Thank you The Brilliant Club for all the support.
https://t.co/iDHbYGMCLn
@LifeLongThinker Thank you so much ๐.. I recently started working as a junior developer. Next is โฆ I am trying to learn and understand about the existing environment / tech / codebase and become a dependable team member ๐ sorry for replying late๐ค
Day100 of #100DaysOfCode
โ Codewars
โ TypeScript tutorial continued
โ Started working on a coding challenge
โ Links in the portfolio are sorted. (Extra spaces are still glaring at me but that's a problem for the next day)
Day 93-98 of #100DaysOfCode
Keeping up with social media is really not my forte anyway...
93- Implemented Foursquare API and Geolocation API on my app. They are working exactly as I wanted, although it took time to get around the Foursquare at first.
96 - Started a course on Pluralsight to add to my learning of TypeScript
97- Continued TypeScript course on Pluralsight. Changed styling of my portfolio, and now the mobile version is much better.
In relation to SemVer, fix type commits should be translated to PATCH releases. feat type commits ( when you add feature/features) should be translated to MINOR releases. Commits with BREAKING CHANGE in the commits, regardless of type, should be translated to MAJOR releases.
Day 91 of #100DaysOfCode I've been reading about the following topics:
Semantic Versioning and Conventional Commits
In SemVer (Semantic Versioning) version number format is MAJOR.MINOR.PATCH