From now, November 22th, 2024 to the next 100 days, i commit to consistently code without skipping any day. i will be focusing on freecodecamp course, the odin project, euler projects, Full Stack Open, or learning Laravel. i will keep track of my progress each day through this journal.
in general, i want to be a full stack web developer using MERN stack or Laravel and get ready for wed dev jobs!
- Fluent in PHP (using Laravel Framework)
- become a front-end professional
- fluent in Javascript (using Node JS - MERN Stack)
বাংলা - català - 中文 - deutsch - español – français – italiano – 日本語 - 한국어 – nederlands – norsk – polski - português do Brasil - русский – українська - ελληνικά - srpski
If you want to help by providing a translation of content/rules in the language you know, submit a pull request (or DM me on Twitter @ka11away), adding a sub-folder in the 'intl' folder with the files of the translation there.
- Check out the Official Site for the #100DaysOfCode movement. Connect with others on the platform of your choice from this list: www.100DaysOfCode.com/connect Also, here is a invite link to the 100DaysOfCode Slack channel
- Read Join the #100DaysOfCode
- Fork this repo and commit to the Log or to the Alternative, rapid R1 Log (R1 stands for Round 1) daily. Example.
- Code minimum an hour every day for the next 100 days.
- Encourage at least two other people in the challenge on Twitter every day! Pay it forward!
- Change the date in Rules to the day you've started the challenge.
- Delete the examples in the log, or comment them out, and start filling it with your own content.
- Tweet your progress every day using the #100DaysOfCode hashtag.
- Follow Alex, creator of #100DaysOfCode & 100DaysOfCode Twitter Bot that retweets the tweets that contain the #100DaysOfCode hashtag. It's a great way to keep yourself motivated and to participate in the community. Thanks @amanhimself for creating it!
- Important: (see No.4 above for a specific rule on this) Encourage others who are doing the same challenge on Twitter or elsewhere - by giving them props when they are posting updates on their progress, supporting them when things get difficult. Thus we will grow a community that is helpful and effective, which will lead to a higher success rate for each person involved. It's also more likely that you will stick to your own commitment, given that you will get acquainted with a couple people (or more) right away.
- If you find a great, helpful resource that others would benefit from, either submit a Pull Request to add it to the repo, or just tweet at me (see info below)