#Devember: The Month of Code
Published by Alex 5 years, 3 months ago (2018-11-26T21:08:36+00:00) | Discuss this article

First off, what is Devemeber? Devember is a programming challenge you take up. It is an excuse for programming, for learning to code and for sharing it. We at Cemetech want to encourage you guys to partake in this; we encourage you to not do a calculator project but instead do a web, computer, mobile, or hardware project. This is not a contest but you will be rewarded with new knowledge and personal satisfaction. :P

If you wish to partake in this Devember challenge, create a new topic in "Your Projects" with the words #Devember: {$MY_PROJECT_NAME} and include the following info in the message body along with the repo you plan to use for your project.

From here on out I'm going to basically plagiarize the Devember website.

      I, *insert username*, will participate to the next Devember. My Devember will be *insert objective*. I promise I will program for my Devember for at least an hour, every day of the next December. I will also write a daily public devlog and will make the produced code publicly available on the internet. No matter what, I will keep my promise.

      *here describe your Devember*


    What is an Objective?
    • learning programming
    • learning Ruby
    • programming a game
    • programming this game: 'Clowns Inc.'
    • programming a tool to manage wifi
    • programming a library to record videos
    • Anything else you can think of


    In the final section describe more in the detail what your Devember will be. What guide, or book, will you be following. What language, libraries, tools will you be using. What are your plans. You can have the same Devember together with other people! If so write their names in this section.

    Everyone is encouraged to join Devember. From newbies to pro developers. Everyone can learn. Learning is life. Sharing boosts learning. When, in the contract, you agree to keep a devlog, is because of two reasons. In the first instance it gives you a daily motivation to keep faith to the contract, but it also makes you share your experience with everyone else. This means you will get both the feedback from others and their own experiences. And all this is mutual. This is humanities superpower: community learning. It is together that our societies evolved through history. Now, Devember is coming. Will you join the others? Will you join the learning? Will you join the fun? Will you join Devember?

    Put your contract somewhere public. It can be your blog, your Facebook, your Tumblr, your Devember devlog, etc.

    When you write about Devember, please use the hashtag #Devember.


We at Cemetech believe that it's a pretty difficult promise. Heck, rewrite that promise a bit so you feel better about keeping it. Maybe instead of everyday, change it to be "I will code 5 hours every week." We won't shun you for breaking the promise so take that promise as seriously as you'd like but at least keep us updated weekly with how (un)helpful your tutorials and resources have been, what new resources you have utilized, what additions and changes you've made, any challenges you are facing or hurdles you foresee, and anything else. Naturally, Devember asks that all projects be open source so please include a GitHub, GitLab, or other repo link in the topic.

If you're reading someone else's Devember topic please help them out! If they're struggling, point them to some resources, explore their code, etc etc. Offer alternatives and explain why you suggest the change. No one is going to learn when you drop a change with no explanation or suggest new resources without a reason why you think it'll help.

Below I'll write a sample Devember topic (not one I actually plan to follow through with at this current point in time, sorry!):


    I, Alex, will participate to the next Devember. My Devember will be learning to develop my own MagicMirror module. I promise I will program for my Devember for at least an hour, every day of the next December. I will also write a daily public devlog and will make the produced code publicly available on the internet. No matter what, I will keep my promise.

    Most map and traffic modules for the MagicMirror software uses Google Maps, which charges for their API usage. I plan to use OpenStreetMaps to source the data. I plan to support multiple pins as such to mark someones Home, place of Work, and other POI's. I will be using MagicMirrors Module Template to help with with this as well as various tutorials online to help me navigate OpenStreetMaps API.

    You can checkout my source at: GitHub.com/qczar/projectname


Permalink

Advertisement