100 Days of Code Challenge Day 19

Photo of Light Bulb


I approached  my Tipcal app today and got it working. My light bulb moment finally came! Things were clearer and I figured out what I needed to research. I’m marking today off as a WIN!

There are a few other things I want to add to the app:

  • Add bootstrap or make responsive on mobile
  • Media Query to remove slider div on mobile
  • Create favicon
  • Add comments to code
  • Create my own 404 page

A clearer head prevailed.


Contributing to Open Source

Today, in the CodeNewbie twitter chat, we talked about contributing to open source There were so many great questions posed.  The answers were even more revealing about what we thing about when we hear the words open source.


For me, it’s fear of the unknown, imposter syndrome and being in over my head. I found out, I wasn’t alone. Many of us new coder have to deal with what we think we know verses what we have to offer.  What I discovered was that I do have something to offer and there are projects for me out there, I just need to know where to look. A great thing happened, call it serendipity,  @CodeForPhilly was on the chat and commented on one of my answers.



I’ve wanted to join A Code for Philly MeetUp for sometime, but they are always on Tuesday evening. That’s when I teach a class at a local gym, so I haven’t had the opportunity to go. It’s been on my list to find out about some of the great things they’re doing right here in my back yard and tonight drove it home. I signed up for the Code for Philly site and I can’t wait to see where I can make a contribution to projects that affect my city.

Docker MeetUp

All in all, a very productive evening. I also went to a MeetUp in Wilmington, DE with Docker Wilmington. Learned a bit about Docker, had a great meal, networked, and came home with some super swag! Today was WIN-WIN-WIN! This tech girl is TIRED! Until tomorrow…



2 thoughts on “100 Days of Code Challenge Day 19

  1. Hi, saw this linked from CodeNewbie’s twitter and was curious 🙂

    FWIW, open source has numerous facets. One is contribution, which is a little alarming at first, I was definitely scared I’d get made fun of or have done something embarrassing on my first contribution. But the part that makes it viable is that it’s source code you can access and use.

    This second case is rather interesting, because the opposite of “open source” is “proprietary”, where you don’t have access to the code you’re using. Typically proprietary software is given to you as “binary code”, instructions that your computer can execute but that are meaningless and illegible to humans. I think in Java they would call it “bytecode” which is subtly different, but it still has this “meant for machines” aspect. For example, Internet Explorer is proprietary, but Firefox and Google Chrome are open source. This means that you have the ability to go fix a bug that’s *bugging* you 😛 You can add new features to those tools (they’re big projects, and it would probably not be worth the effort to maintain your modified version, but the option is available). With open source you can go read the code whenever the documentation isn’t helpful (eventually you might get to a point where you start with the code and fall back to the docs!). If a tool is doing something that seems like magic, you can go figure out how! If the maintainer of proprietary code stops caring about it, you’re out of luck, that software will never be updated again >.< With open source code, communities spawn around abandoned packages that they care about, they'll take it and make it their own and the progression continues. This is why things like Ruby, Rails, and Node.js have so little risk: even if they were abandoned, their source is open and many billion dollar companies depend on it, so they would step in, and pay their devs to maintain it.

    A great way to learn is to clone (download) the source code for something you're using and look through the first several days of commits (a commit is like hitting the "save" button in a word processor), they'll often contain the big ideas that the code still uses, and they'll be much less formidable because there's much less code and abstraction. You can see who worked on it, when the work was done, if you find something confusing you can read the commit that introduced it as people try to leave explanatory messages when they commit.

    So yeah, the idea of contributing to open source is alarming at first, but it will be a proud day when you hit that milestone. And in the meantime, there's tremendous didactic value in having access to the source code and it gives you a much richer set of ways you can interact with the code. Cheers, and congrats on 19 days ^_^

    Liked by 1 person

    • Thanks for the insightful comments. I’m looking forward to digging into some software & seeing how it ticks! I appreciate you reaching out & sharing your expertise. This is why I enjoy being a part of the CodeNewbie community.


Comments are closed.