Showing posts with label challenge. Show all posts
Showing posts with label challenge. Show all posts
here we have me hiding my tripod remote in one hand

In the past few months, I have attended a Hack-a-thon and a Design Challenge (which was basically a Hack-a-thon but for designers). A hack-a-thon starts off with the hosts giving topics - i.e. Healthcare, Women in STEM etc. The next step are for coders/developers/designers to form a team and decide which topic they will be creating a project for. And then they're off coding a project all night until it's time to submit.

So, the reason I'm starting off with a brief intro into my own coding life is because for both of those Hack-a-thons I wasn't the most confident- I hadn't attended a hackathon before. And on top of that, for the past few months I've been applying for Front-End Developer positions (speedy translation: I design/code websites!) and I've always gotten one of these responses: We went with someone who had more experience; after examining your experience we've decided to not move forward at this time; your background was not a fit at this time.

I actually got two rejections on Monday which was when my latest video on my YouTube channel was supposed to be up. It didn't go up. It's all becoming a cycle of I need to have prior experience in order to get experience. I started tracking the amount of applications I sent in an excel sheet, and since I've been doing that that brings a total of 18 rejections. Last week I started to wonder if maybe there isn't any room in this field for me. And that although I love this field (honestly coding is so much fun) maybe it isn't for me with the amount of rejections that I keep getting.

_____
So I actually got a little bit curious:

 How many recent college graduates are unemployed?
According to Forbes, 1 out of every 40 college graduates are unemployed.
_____


When I went to the Hack-a-thon, I went alone and there were a few other solo coders and that's how I ended up on a team. Two members of the group were recent graduates (one being me) and the other two were still in school for their Bachelor's in Computer Science. The other recent graduate decided that the easiest way to complete a project was to use one of her own projects she created, make minor edits, and pass it onto the judges as if we all coded it. I wasn't on board with that idea. The point of a Hack-a-thon is to test your brain and skills to work in a tight time constraint not use something that's already been created.

To make a long story short the other recent graduate left the group and the remaining three of us decided to actually design and code a project from scratch. Of the group, I had the most experience with coding while the others were still relatively new to it. Our project we created ended up passing the first round, and secured a place in the Top 4 for the Healthcare category. 

We didn't have a lot of experience - it was all our first hackathon- but we didn't let that stop us from creating a project. We were surprised that we passed the first round  (there were a lot of awesome projects) and although we didn't get the first place prize we were all able to realize the benefit of doing our own project rather than passing one skilled person's project as our project.

We tested ourselves. We learned a lot. We lost a lot of sleep. 

here we have my code disrespecting me and me trying to figure out why it's not working

For the Design Challenge I attended, I sat down next to someone and started talking to them. It was their first hack-a-thon and they were nervous that they'd do badly. That's when I found myself giving the advice that I now remind myself through my rejections: Your lack of experience does not mean a lack of skill.

If you're also in the same boat as me, there is a lot that can be running through your head with rejections and thinking that it means you lack skill. You don't. You know so much more than you give yourself credit for.  When I looked at what I've created, the coding projects I literally assigned myself because I wanted to improve and learn, I realized that for each project I've grown as a developer even if I didn't realize it at the time.

For every door that closes there's another one that opens. I'm not sure where that open door is but every closed one leads me closer to it.

I recently started thinking about my Front-End Developer life in the same perspective as I view my running. In both running and Front End Development the learning never stops. I'm constantly learning new exercises to have a stronger core to run faster, and with Front-End Development I'm constantly learning faster ways to do certain things.

From this maze of unemployment I've realized that my happiness doesn't and shouldn't stem from me having a job. Although having a job in my field would be great, it is also important to note that happiness comes from within you not from something outside of you.

If you're also in the same maze of unemployment: The right opportunity is out there for you even if inner you tries to convince you it isn't. Don't give up on yourself, keep! applying!







Towards the end of June, I saw that Amber from Barefoot Blonde was doing a gallon of water a day challenge. This had me thinking - how much water do I actually drink in a day?

Well, sometimes I find myself forgetting to drink water and if I do drink water it's only a small cup every few hours. When I go running, I don't really drink water like a mid-break-type-of-thing. This is because:

A. I don't feel like carrying a water bottle in my hand.

B. Taking a string backpack to put only a water bottle in - having it bounce on my back the whole time - doesn't really spell out a nice comfortable run.

Solution?

Drink water before and after a run (though, I do have to admit, sometimes mid-way through my run I do get thirsty and want water to hydrate).

I have seen the I AM RUN BOX backpack and it's made specifically with athletes in mind - doesn't bounce while running- however I think it's a bit too big to just put a single water bottle inside. 

Technically speaking if I exercise a lot, shouldn't that mean I drink more water? Well, that's how it's supposed to be.

You're losing a lot of sweat = you start to get dehydrated = your body is begging you to drink water. 

The only days where I find myself drinking a lot of water is during strength training - those days are intense and if I don't have water I might as well not workout at all.

According to WEB MD it says that a person should be drinking eight 8-ounce glasses of water. (Would you believe me if I told you when I first read that, I thought it said to drink 8 ounces of water then had to re-read it.) If you exercise you should be drinking more water to keep yourself even more hydrated because you're sweating so much. You have to drink water to make up for the water your body is losing via sweat.
_____
WEB MD IS COMING THROUGH WITH THE INFORMATION TODAY:

On the second page it details a schedule go when to drink water before/during/hours leading up to a workout.

If you decide not to read it that's cool too; here's a quote from it:
"I tell all of our young athletes this: you can improve your performance simply by drinking enough water."

_____

So I decided why not set myself a challenge to drink at least one water bottle a day for July because really I need to start drinking more water, 3 cups a day isn't enough.

According to WEB MD I should be drinking 64 ounces of water. A water bottle is 16.9 ounces. OK THAT IS VERY FAR OFF HOWEVER IT'S BETTER TO START SMALL AND THEN MOVE UP TO 64 OUNCES.

Currently - as of the 4th of July - I've been drinking at least 1 bottle a day & occasionally drink 2 bottles if I'm doing HIIT workouts.

Anyone else forget to drink a lot of water?

Drink water = you won't feel dehydrated & you'll feel more energized

If you drink water bottles regularly, that's awesome keep doing that, your body is thanking you for drinking water! If you don't drink water, and tend to drink sugary drinks, maybe think of joining this challenge with me?