Friday, April 26, 2019

How I am learning Machine Learning





I have wanted to learn ML for a while but finally started learning hard core when I saw a former co-worker predict the price of Bitcoin. I decided to make a goal for myself, predict whether or not the stock ticker VIX was going to go up the following day.

My Dad has been day trading and intra trading stocks for many years, but I have never had any interest in stocks as I didn't understand them. This past year that changed I started learning everything I could about trend trading stocks in October of 2018. In December I took $2,000 and put it into my UStocktrade account https://www.ustocktrade.com/  ( I have no affiliation ) and haven't looked back.

Though I've had trading setbacks (losing 16% in my first month ), I have regained all of my losses and am up over 9% for my total account. I have tried several different approaches and strategies for trading stocks. Currently I like trading the VIX ( fear in the market ) and SVXY ( the inverse of the VIX ). Basically you play the stocks like a yo-yo, one goes up the other goes down.

Long story short I have been reading charts, news, and guessing as to when I think the VIX will spike ( bad news in the world, Fed announcements, etc ). This has worked well enough, but I wanted to find a way to give myself an advantage.

This gave me the perfect side project and motivation to learn ML for real. Having something I am passionate about would only help me to push through any ML challenges I would face. I did a lot of research online and finally signed up for Elite Data Science's paid course here:
https://academy.elitedatascience.com/ ( NOTE: I have no affiliation, and make no money from suggesting them ).

The course was simply amazing and I highly recommend it to anyone who wants to learn ML in the shortest amount of time possible!  As part of the course you build several ML models and learn solid ML concepts. The final part of the course is your capstone project. I decided to make my current VIX prediction problem as my final capstone project.

I am not done with the VIX ML model but am more than halfway done. I demoed what I had made to a local AI/Deep Learning group yesterday and was encouraged by all of the positive feedback ( I am my own worst critic ). I have set a goal to have the VIX ML model done by the end of May. I'll let you know how it goes in June :-)

This is what is so fun and amazing about learning to code! When you know the basics of coding, the sky is literally the limit, you can be a developer, a QA, Test Automation Engineer, or become a Machine Learning Engineer.  I have fallen in love with Python even more than I was with Ruby, and also love using Anaconda with Jupyter notebooks.

Keep learning, never give up, press through any and all challenges, learning to code is worth all of the effort!


Wednesday, May 30, 2018

Why you should learn RPA or What I would do if I was learning to code today

NOTE: I’ve been informed by my lawyer that when talking about sensitive subjects like the following I need a disclaimer, here goes:


Everything you are about to read is merely hypothetical, and shouldn’t be taken as fact.


6 years ago I was desperate to get a job to provide for my wife and 2 little kids. My strategy was to figure out the hottest web development language and learn it.

My thinking was if the new hot framework had only been around a few years and didn’t have many people with much experience, they might give me a shot despite my lack of credentials.

Turns out my logic was solid and I learned Ruby on Rails and landed a junior dev job. Now though Javascript has eaten up the world, it’s what everyone is learning.

Richard Branson says: “Never do a business that you don’t love.” 

I don’t enjoy JavaScript it changes so fast and a new JS framework is created every 5 minutes.

What to do???

I saw the market shifting in early 2014, I tried learning JavaScript and found it frustrating for many reasons and just not fun.

After the front end team got laid off from my first job, I had 8 final interviews each time they said they loved me but my JavaScript skills were too weak.  They suggested I apply for their QA job.

With my severance running out I decided if I was offered a QA job again I would hop on it.  My 9th final interview the same thing happened, this time I answered that I would absolutely LOVE to try a QA role! ðŸ˜œ

Long story short, I ended up liking the QA role as it was really a Test Automation role. It was the first time I learned about Selenium and how cool Automation was!




Where am I going with this?

Learn to code yes, but don’t limit yourself to only being a developer. Most people who reach out to me want to be cool and have hip stickers on their Mac while drinking coffee.

The truth is learning to code and being a professional developer are worlds apart. They are as different as your grandma’s computer skills are to yours.

Yes, THAT different!

My common sense and strategic thinking is strong and I’ve found the next big thing, and I think you should check it out as another possible alternative to being a full-blown developer.

I have learned the basics of pen testing ( ethical hacking ), started learning data science but didn’t fall in love with them.

I loved outsmarting websites and scraping data and automating ways to win free things online. I always used Selenium or a headless version like phantomJS ( Poltergeist ) to be faster.

I would use some of my hacking skills to change the user agents and try to automate stuff that I probably technically shouldn’t have ðŸ˜¬ - that was the hacker in me, I thought it was fun.

Enter LinkedIn, they have one of THE hardest sites to automate, they change elements and totally disorients Selenium, Selenium acts like it's drunk and had no idea what is going on.

I spent a week in my free time trying all different types of tricks and ways to automate LinkedIn. Nothing worked. I stalked people on Quora who used to work at LinkedIn and read posts and learned some of the things they do to try and prevent automation and web scraping. I came back to my script and tried for 2 more days, no luck.

I love automation, I love web scraping and have done it at many companies for them professionally, but this defeat really discouraged me. I focused on my side businesses and left it alone for a month. 

I looked into OCR and tools like Kantu and Sikuli. I got them to kind of work but they weren’t fun to use and felt brittle.

Fast forward 1 month.

Through luck and chance, I heard about RPA ( Robotic Process Automation ). I started Googling and started learning one of the top RPA tools who shall be nameless. Long story short I didn’t think tihe tool was very modern it felt old and clunky.

The ability to automate virtually anything was cool though! A friend told me to try out UiPath as he thought it was WAY better than the other RPA tool I had been using.

Oh, my gosh guys... BOOM! UiPath is AMAZING! It can automate literally anything without even breaking a sweat! I won’t say exactly WHAT I’ve automated, but where Selenium would fall over and get crushed, UiPath breezes through!

I use it for so many things that used to be hard and take a lot of skill to automate, now it’s actually easy.

I’m not paid to say any of this.

Guess what?

RPA is a hot new technology that I think will literally change the world. The barrier to entry is set really low and you don’t have to be a full-blown developer to use it.  You just need to know the basics of coding!

Oh, and its income potential is on par or better than a developer. I absolutely love UiPath and am moving towards doing it full time.  I suggest you check it, even if only to help automate tricky workflows.

People email me and want to know what I would do if I was starting today.  Well, now you know.  I never do what everyone else is doing or thinks is cool.

Learn RPA, it already has some AI being integrated into it. I recommend UiPath, but any tool is better than none.

Always be learning something new, never slow down always be hustling, and turn off Netflix ðŸ˜œðŸ‘ŠðŸ’¥

Thursday, January 25, 2018

9 things I have learned with using only Windows for a year

I took a position as a QA / Test Automation Consultant at a Windows shop for the express reason of giving Windows a shot. Up until then I had always worked on Macs and absolutely love them. I took the job because I wanted to better my skill set, be strong on both Mac and Windows. Forcing myself to only use Windows products seemed like a good way to do that.


I like Mac better than Windows. However, I have come to appreciate somethings about Windows that are better than Mac. Overall I am so glad I put myself out there and used Windows straight for a year.  I still have a Mac at home and prefer it.



9 things I've learned

1. Windows has better file searching.  Mac's Finder sucks everyone knows that, yes you can add Alfred ( which I do to make it better ).

2. Windows has these 2 apps that are simply amazing.
"Search Everything" - you can find files at lightning fast speeds it is unbelievable, I wish Mac had this.
"GrepWin" - You can find text in a file at astonishing speeds. Yes, you can use the command line Grep with Mac. ( Which I do, but this is far better in my opinion )

3. There are more apps for Windows, simply because Windows is more prevalent. I can find an app I like on Windows and then I can't find it for Mac.

4. Windows has greatly improved from when I used them in 2008 - 2010.  Back then they were "dog slow" and constantly broke or had the "blue screen of death". I remember I had an 18-month stretch having to buy 3 Windows machines because they broke for various reasons.

5. Windows have touch screens. I don't use it that much but it is nice to have the option.

6. Windows has become more "Mac like". The icons are slicker and I can set it up to look more like a Mac by docking the apps that I want to use.

7. Windows are cheaper. I always knew that but with Apple not being on it's "A Game" the past 2 years, it's nice to know you can easily pick up a new Windows machine for pretty cheap.

8. Windows is getting better year over year. I don't see that with Mac right now. Also, Windows came out with Visual Studio Code which is simply amazing!  So amazing in fact that I stopped using Sublime Text editor which I swore I never would.

9. C#. I learned C# this past year and it has some pretty amazing automation frameworks better than Ruby ( my favorite language ). I think overall Windows has closed the gap between Mac.



Why I still love my Mac better

1. Mac "just works". Mac's solutions are usually easier to set up than Windows.  If you download an app on Windows it will be easier to use on Mac.

2. Mac has Unix shell! Windows command line is a joke, in fact, when I use Windows I install the Unix command line so I can use it instead.

3. Mac is more developer friendly. You can easily create and change PATHS. Also, I can very easily create Aliases in Mac. For Windows, you have to sell your soul to the devil to figure it out.

4. I like open source. I feel open source software is far easier to use with Mac. I love that Mac comes with Ruby pre-installed on it.

5. Macs are faster and generally don't simply crash on you. Windows is far more buggy and almost every day I have to use "Task Manager" to kill an app that is acting buggy.

6. I like how nice Macs are. They are sexy with their slick Aluminum bodies. Windows machines feel like they are made out of melted Legos. :-)

7. Macs are typically newer. What I mean is when you work at a company on the engineering team you are assigned a computer. If you work on a Mac team you typically get a brand new Mac. When you work with a Windows team you will usually get an old "brick" sized laptop that is super slow
and cries a lot. :-)

All in all, I can't do too much bashing, pun intended. I am super grateful I took the plunge and learned Windows. In a perfect world, I would have one of each. I think the moral of this story is always keep an open mind, try new things out and be willing to change your opinion when you are wrong.

Also whenever you do hard things you will see growth in your life. For me, it's a better appreciation for Windows.

Whatever machine you have, you can learn to code! Start where you are with what you have, there is no reason not to learn to code and every reason to learn, You can do this!

Monday, September 4, 2017

It is so easy to get hired in tech!

Hey Guys,
    Al is working his butt off and doing well, but he struggled initially with the 21 hours per week time commitment.  The most common thing I see with people learning to code, trying to land their first tech job is not studying 3 hours per day.

Everyone wants to get hired.  Everyone hates making retail money, but very few people are willing to turn off Netflix for 2 - 4 months, buckle down and do the work.  Al is going to get hired, he is committed, where will you be in 4 months?

The world is changing, the way to break into the tech scene is changing.  Netflix and T.V. will always be there to distract you. What's the number one that thing that if you did it would change your life?  You should go do that!

Guys, follow me on Instagram, I am going to be using it more and Twitter less.  @joshuakemp85

You don't have to be a computer scientist to get hired or be the smartest person.  You just have to be willing to not quit, never give up, and do your best.  I love coaching people and watching them double their incomes and change their lives.

Don't give up, work hard, and turn off Netflix :-)

Friday, June 23, 2017

Test Automation is the fastest way to get hired!

Another person hired as a Test Automation Engineer!  Seriously forget the things you hear about your first coding job should be as a junior developer.  Getting hired as a Test Automation Engineer is way easier and still allows you to write code :-)

I only personally coach 1 person at a time these days.  Please welcome Jae Shin to the tech field as a Test Automation Engineer.

Getting hired is simply, learn how to code, learn how to market yourself, and share that enthusiasm and passion during the interview.  Most people can get hired in 4 months once they set their mind to achieving the goal of getting hired.  Now is the perfect time to break into tech, there is more opportunity than ever in the tech scene.  Seriously go to any job board and search for "QA" or "Test Automation" and see all the jobs that are available.


Here is Jae's review from his coaching experience, by the way he got hired in 1 month:


"I can't thank Josh enough for coaching me through the steps in locking in my first tech job. Josh's guidance can only be surpassed by his sheer enthusiasm for watching people succeed. Not only did he walk me through what skills I needed, but also continuously challenged me to become a greater coder with his assignments. The skills I learned, in addition to the encouragements I received, gave me the confidence during my interview and landed me my first tech job."


- Jae Shin, 
Test Automation Engineer,
Accenture

Be encouraged, charge forward, never listen to the naysayers!  You can learn and you can get hired, and it doesn't have to take years!

Always keep learning :-)

Thursday, May 25, 2017

How to be an instant hero at work!

Let's face it when you work at a tech company, there is never enough good documentation to know how certain processes work.  Another issue is that you never have enough time to document the new workflow, or how a back end web service works.

Previously I have used a text editor and simply wrote my own very crude documentation, as I learned a new web application or back-end system.   I tried excel for a while, didn't really like it.   I also tried using Mac's built-in Notes app.  I even tried a mind mapping tool called Freemind, nothing worked well, looked good, or was easy to use.

That has all changed!  I finally stumbled upon  XMind the open source mind mapping tool.  I am here to tell you that even the free version of XMind is simply amazing!  I feel bad for myself these past 3.5 years of keeping track of notes and writing documentation without using XMind.  I personally have the paid version of XMind because it is that good.  I literally use it every single day at work for taking notes, documenting a new workflow or process, and when I am working on a user story.

I make test plans, test scenarios, and test idea sessions all with XMind.  I absolutely love the "brainstorming" feature for test scenario creation!  The app is super easy to use straight off of the shelf and super intuitive, it just makes sense.  I have over 30 XMind mind maps for work, I can't share those with you as they are strictly work mind maps.  However, I plan on making more mind maps for personal projects so that I can share them!


How does using XMind make you an instant work hero?

Whenever I work on something that is poorly documented, a team member or manager will ask:  "Did you document the new process that worked for you?   Can you put it up on a Confluence page?"
Normally that is a lot of extra work and extra formatting to make sure that my documentation all looks correct.  Also for Confluence ( and a lot of other intranet sites ) they only have an import feature for Word Docs.

This is what is so amazing about XMind, it will let you export your mind map to TONS of different formats and they all look amazing.  With 2 clicks I literally have a perfectly looking Word Doc that I can instantly upload to Confluence in 10 seconds.  Virtually everything that I touch at work is being improved, people have been thanking me for "taking the time" to document or clean up a process.

I don't tell them that thanks to XMind's built-in export tool it doesn't take me any extra time.  Xmind literally has 20 different formats that you can use.  It doesn't matter if you need the document in an Excel format, CSV, Word, or whatever.  XMind does it all!

I don't recommend things that I don't believe in as you all know.  I literally use this tool every day for at least 1 - 2 hours.  I highly recommend you try it out and see how much easier your life gets. Being a documentation "rock star" at work never hurts either.  Let's face it most people hate writing documentation, with XMind it's super easy!

Check out XMind

Keep on learning how to code peeps, you can do this!

Friday, March 24, 2017

I've been coding for 4 years... here's what I've learned

I am a Test Automation consultant, I write and read code most days.  Over the past 4 years I've done many different things with code:

I've written basic Rails applications - this is how I got hired at my first job as a junior developer
I wrote web scraper scripts and used Jenkins to automate them  - At my second job - this is where I really started to get better at coding, I learned the basics of automating things.
I worked as a mid level software engineer in testing using Javascript exclusively for 6 months - I really started focusing on test automation, learned the importance of writing cleaner code.  I also realized I didn't want to become a Javascript developer.
I helped create an API web service test automation framework in Ruby - I paired with a senior Ruby developer for 6 months straight creating the framework.  The code reviews and pairing took my coding skills to a higher level.

I don't know everything but I've learned a few things along the way that I would like to share with you:


Code reviews - be mean to the code, nice to the coder - alot of people still don't know this or use it.
I had a boss who would flip me off every morning and thought it was funny, after day 210 it starts to get very annoying.  I have had about 4 developers who really knew how to do a great job at code reviews.  Code doesn't have feelings, people do.  When you are a junior level developer you are going to be getting tons of comments on your code reviews, this is a good thing as you will get better.  Developers are notorious for lacking empathy, alot of code reviews suck because of it.  My advice is to remember the humiliation and frustration when you have a *%$* reviewing your code, and to not do that to someone else when you start doing code reviews.  Also try to not take anything the developer says personally ( even if they make it personal ).


Make it run, make it right, make it fast.
I used to want to make something or write a script and I would try to plot out the perfect path to make the code awesome before ever writing a single line of code.  Instead, think about what you want to make long enough for you to be able to write a "first draft" that works, albeit it's ugly.  Get your code working and then start making it pretty and start looking at how to really improve it.  Lastly you should look at ways to improve performance before pushing your code up for review.  For me this was a very freeing concept to start writing code and not just trying to have everything perfect in my head from the start.  I think as you gain more experience you will be able to write awesome code right off the bat, I have seen very senior developers do this.  I don't think most entry level tech people will be able to for several years.


The courses you take online are not really what you do in real life.
Courses are not geared to helping you land a job in the shortest amount of time, for the most part they want you to keep paying a monthly subscription fee.  The real world trenches look very little like the clean beautiful courses you took online, which is why I recommend getting your first job as quick as possible, getting your wet and figuring out what it actually means to be a professional in the field.  This may sound backwards, but I see far too many people who are waiting to get "good enough" coding in their parents basement's for 3+ years.  There are many jobs out their with less qualified people filling them, I think the key is your passion and willingness to learn.  If you have those you will grow your skills organically as needed, when "pain points" arise you will learn enough to get through them.  Someone with 1 year of real world experience is far more hirable and productive than a 3 year "basement coder".


Algorithms are hardly used in the real world.
I have almost never used an algorithm in my professional job, I have only ever needed to know algorithms for interviewing purposes and other mind games.  Real world coding is much more about these topics:
Knowing OOP
Writing methods that only do one thing
Creating separate classes to keep the code cleaner
Writing method names as verbs
Naming variable that make sense - tip: name it what the method is returning back, also make sure to name it singular or plural depending on what is being returned.
Reading code - this is the hardest thing that is almost never taught.  It's hard to read other people's code, but that is 80% of your job.  A good IDE helps.
Refactoring
Debugging - senior devs are amazing at this

NOTE:  This has been my experience with web development and test automation, I think the more senior level a developer becomes that changes some.


Refactor organically - slowly as you go.
The last senior developer that I wrote the API automation framework with taught me this.  Become aware of pain points in your code.  When you are writing your code and start getting annoyed or frustrated with it, ask yourself why and how can you remove that pain point?

Simple example:  Whenever you find yourself writing the same line fo code more than once - make a method.  When you have to change your code and it takes forever or is confusing, figure out how you can make it easier.  Don't be afraid to make another class to clean something up or break methods down further.


No one is truly TDD - bet yes, have tests - unit tests are amazing.
I hate writing unit tests and really don't like the whole TDD thing ( yes I know it is important ).  I also realize that one reason Rubyists are so caught up with TDD is because Ruby is an interpreted language, and doesn't show compile errors.  I have not worked with a single developer in real life ( not at conferences ) who actually wrote tests first.  What I did see in real life was developers who wrote tests and checked their unit test coverage before pushing their code up for review.

From the QA side of things, whenever I found a bug, a good developer would instantly write a unit test ( where applicable ) to cover that "missed test".  I will say from the QA / Test Automation side of things their is nothing better than seeing a ton of unit tests.  Why?  Unit tests are super fast and give a high level of confidence that the web app has been tested.  Also unit tests are awesome to run every time you pull down a new feature branch from a developer. Nothing beats unit tests  for regression testing.

Lastly unit tests will make QAs happier everywhere :-)  So the moral of the story is yes, please write unit tests, whether or not you write them first, make sure you have some written.


In a nutshell how to write better code - think of others.
You could spend your entire life on just this subject alone, but since you have a real job and must write code now what do you do?

Writing cleaner / better code really comes down to one thing:

Thinking of others.

Someone is going to have to change your code in the future, how hard or easy is it going to be?

Keeping that thought in your mind while you are writing code will help you the most.  When you are faced with the decision to write some code that will be easy to implement but hard to maintain, don't do it.  You can write code as a first "rough draft" but you should never push the code up for review knowing it will be hard to maintain.  Always take the approach that will be easier to maintain in the long run, even if it's harder for you to implement now.


Being okay with abstraction and not understanding how everything works
I used to freak out when I would be faced with a new code base or product if I didn't understand exactly how everything worked.  The truth is sometimes you are given an object and you need to take it for what it is an object and figure out what you can do with it.  Being comfortable with not understanding something is hard, I have gotten better with getting thrown into a new project or team and "rolling with the punches" until I figure out the lay of the land.


As a junior developer you need a really nice senior developer to take you under their wing.
You don't know what you don't know.  I am a very driven person and always try to improve my skills, whether it be writing code, testing, pen testing, or data science ( my latest passion ).  Finding a mentor will make you get better at a rate impossible on your own.  I have worked with lots of crappy developers and testers, don't be one of those.  You absolutely need a mentor, I can't tell you exactly how to get one, but you should always be on the lookout.  Always be the best student and do the work required to grow.  With my new endeavor ( Data Science ) I have several people who I can reach out to and ask questions whenever needed.  Find someone who will be that for you.  Pairing with the last senior developer for 6 months straight helped me grow more than I thought possible and gave me the confidence to learn my first compiled language C#.

All in all learning how to code is one of the most useful skills you can learn on the planet.  You don't ever have to be a full blown developer, but learn how to write loops, variables, how to navigate / read code, make methods and classes.  You will know how to code enough to get your feet wet in the tech field :-)  You can do this peeps!





























Saturday, March 18, 2017

Becoming a Data Scientist - Part 2

Wow, thanks for the out pouring of advice and help.  A special thank you to Ryan Herr who is a Data Scientist!  Follow him on Twitter at @rrherr, I really appreciate the help!!!  Whenever you are moving into a new field, one of the fastest ways to achieve your goal is to find a mentor.  I know several people from work and online who are currently Data Scientists or have been in the past.  Find people online who can be a mentor to you or who you can follow.  Here are some basic things I am doing and recommend so far:

Listen to podcasts on the way to work:
http://www.becomingadatascientist.com/category/podcast/  

My commute is 25 minutes each way so I should be able to get through all or most of these podcasts in a month without too much effort.

DataQuest:
https://www.dataquest.io/

I have started Data Quest and highly recommend it, it's like an online Data Science boot camp.  One thing I would like to note.  I used to be supportive of coding bootcamps back in 2012 - 2014, I am no longer supportive of coding bootcamps.  The reason being there is a glut of  "junior developers" on the market because of all the coding bootcamps who constantly "churn" them out.  In any new field which is in constant change, there is a huge opportunity for people who are less qualified to break into the field.  This is what it was like from 2012 - 2014 with coding bootcamps, if  you went to a bootcamp you could easily land a job afterwards.  That is not the case anymore, there are literally hundreds of people all applying for the same junior dev job. Most with virtually all have the same story: "I attended a coding bootcamp".  This is not a good way to stand out from the crowd anymore, in fact it almost makes you "unremarkable".

The reason I am doing DataQuest is that the data science field is still very new, and there are no clear paths on how to get hired as a Data Scientist.  Basically in my mind the data science field feels very much like trying to get a junior dev job back in 2011 - 2012.  It's hard because there is no clear path, but it's also very freeing because no one can tell who is truly "qualified" or not.  This is why I am trying DataQuest, I feel like they have a pretty good path ( so far ) that gently introduces you to data science topics.  I think 5 years from now there will be 100 data science bootcamps and everyone will be telling you to attend!

I have always thought and have done the following:

"Don't do what everyone else is doing.  If everyone is doing something then do the opposite"

Also I look at trends and which jobs are getting outsourced or are easier to outsource.  I also know that the reason brain surgeons make so much money is because they are hard to replace.  Not many people can do what a brain surgeon does, brain surgery is a real skill.  The tech field is the same way, the more people who have a certain skill the lower the income, and the easier to outsource the job.  I also believe in doing something that I am passionate about and enjoy doing, it's not only about which job makes the most money.  You need to enjoy what you are doing, this is the reason I am not interested in becoming a Javascript developer, I simply do not enjoy using Javascript.  I was a mid level software engineer in testing for 6 months and realized it wasn't for me.

The whole key it to learn the basics of programming, once you do there are so many different opportunities for jobs out there!  Spend at least an hour every day learning something new in the tech field, for me it is data science.  Get moving peeps, you can do this!!! :-)



Wednesday, March 15, 2017

Watch me become a Data Scientist!

You may or may not remember me, I am that guy who used to do this for 8 years:




My "secret technique" was shoeing large angry horses all day, putting my kids to sleep, then spending time with my wife, and finally from 10pm - 1am ( or till I fell asleep on the couch ) learning how to code.  I did this for 9 months, 2 days straight without missing a day.  I am a very driven person and believe in pushing myself to new levels, I also get bored very easily and love to learn new things.  One of my favorite sayings is: "You can sleep when you're dead" :-)

I had thousands of people follow me on my journey of learning to code and eventually landing a junior developer role.  After getting hired I was inundated with hundreds of emails asking how a "dumb Blacksmith / Farrier" learned how to code, so I wrote a book.  After a few years in the tech field I started coaching people how to land jobs. I soon realized that coaching was way too time intensive, and I could never keep up with all the coaching requests.  I also realized that the reason people weren't getting hired had very little to do with their technically ability, and way more to do with their ability to network and market themselves.  So I created an online course teaching people how to get hired super fast.


Why am I telling you this???   Bragging? 




No.




I am embarking on another equally exciting and challenging journey, and I have decided to let anyone who would like to follow along with me on this journey.  In August 2013 I thought I wanted to be a senior Rails developer in 5 years, that is no longer my goal.  I am currently a Test Automation and QA consultant for a very well known company who shall be nameless.  My journey has been successful, but my journey is not over.  I thought I wanted to be a "Ethical Hacker" so I got a mentor, and learned as much as I could for 4 months.  I decided that wasn't the path for me.  This time around I thought I would let you watch me struggle and learn a new field, one that is not very well charted at this point in the tech industry.  I am going to become a Data Scientist.

I don't know all the answers about how I am going to make this happen, but I do know that success for me will be landing a Data Science job.  I was going to wait for a while until I knew a lot more about the field. Instead I decided to let you in on the "ground floor".  I have been doing my homework, studying the industry for the past month in the evenings after work, and have come up with a basic plan.  I will tell you more about my plan as time goes along.  One of the biggest issues that people face is not starting with the end in mind.  I have a very clear target: Data Scientist position.  Having "analyis paralysis" is another common problem, too many options so they don't pick any.  Others find themselves with too many choices and resources!!! So they keep bouncing around and switching material constantly.
 
If something is not working for you, then by all means stop using it and try something else.  If however you are constantly chasing the new shiny thing, then you will never accomplish your goal of landing a job.  Make no mistake, I do not live in my parents basement, I live in the real world with real world bills.  The best way to see if you are "good enough", is to go out and try to land a job in your chosen field.  Becoming a professional in the industry is tough, being a "Monday morning quarterback" is not hard.  Waiting until you are perfect is a waste of time, and something that will never happen in the tech industry as it changes too quickly.  I say jump in the game, get your feet wet, that is the best way to learn and push yourself to new levels.

If you would have told me that I would be a highly paid consultant 3 years 8 months ago I would have laughed at you.  I have worked at 4 companies in 4 years, I have seen some awful situations. I have experienced good management and horrible management.  I have seen first hand the problems of "technical debt", I don't need to read about it or take a test, I have lived it. I have had to learn entire new frameworks of code and start contributing to them in a matter of weeks.  The only thing that is constant about tech is that it will always change, and that in order to stay ahead you will have to always be learning!  No hand holding here, this is the big leagues, you will have to figure it out fast or get laid off ( true story ).

So here I am again, ready to crawl and fight for every shred of knowledge about Data Science. It's scary too when you say things like this in public.  People send you mean emails, call you stupid just because you set big goals.  I don't care, when people tell me I can't do something it just gives me more fuel to my fire!  This blog has always been about helping people, and making it easier for others to navigate the crazy tech field.  I won't blog everyday, but I will share with you anything and everything I find out along the way.  I hope you will follow along and watch me acheive my goal!!!

You can do this, never let anyone say that you can't! 


Tuesday, January 17, 2017

Why you should buy me lunch :-)

I received an email today from a guy in Winston Salem N.C.  who is learning how to code.

So what?

I loved his outside the box thinking!  He asked me if he could buy me lunch and "pick my brain".  Mind you he will have to drive 100 miles EACH WAY!!!  I've had this happen before, I had someone drive over 150 miles to buy me coffee at Starbucks :-)

Why do I tell you this...to brag?  no.

Coding bootcamps are churning out fresh new coders everyday, thousands and thousands of new coders every year.  Coding bootcamps are the solution to getting a job...except they're not.  Bootcamps are having a harder and harder time getting they're students hired, I receive many emails that tell a similar sad story.

Attend bootcamp >> land job >> 3 months later laid off

There are only so many junior level jobs on the market at any one time.  There is a glut of bootcamp grads these days.  Also the entry level skills required to land an entry level dev job are becoming harder thanks to Javascript usage growing everywhere.

I have some good news, there will always be jobs for people who know where to look, and who think outside the box.  What do I mean by this?

College was a great way to get a high paying job back in the 70's - 90's 
Bootcamps were an amazing way to get a junior dev job 2013 - early 2015

There is a new way to break into the tech field that I have touched on before, but the point is - there will always be jobs for people who don't follow what everyone else is doing.  If you wait until everyone is doing something you are too late.

The best way to predict your future is to create it! When I was shoeing horses for a living I used that to my advantage to stand out from the crowd with my unique story.  I needed help with coding but couldn't afford to go to a coding bootcamp, I met David Bock ( a very senior Rail developer ) for coffee, I had to drive 1 hour and 30 minutes to meet him.

Meeting with David helped me learn about the tech industry, and helped me meet people I didn't know. That relationship eventually helped me land my first tech job as a junior developer.  I am constantly emailed and asked by people to give them personalized private coaching for free.  Most of these people have not paid $10 for my book or course, they simply want my help for free with absolutely ZERO effort on there part.

That's what 90% of people ask who email me. 

Guess what I say when someone offers to drive 100 miles and buy me lunch???  YES!  I love helping people, I just can't personally help every single person do to the number of emails I receive.

I have 2 final thoughts:

Be different, think outside the box - don't do what everyone else is doing.
Buy me lunch :-)  Think about it $10 - $15 to hang out and get my personalized advice for 45 - 50 minutes is a deal.  It's the cheapest coaching program ever, if you ever are in the Raleigh area, feel free to reach out to me and I'll do my best to help you!

 

Sunday, December 11, 2016

How to automate everything - part 3

The world is changing faster than ever!  When I started learning how to code things were changing fast... now it's changing at warp speed!  Things I have told you as a fact in the past, I am now seeing changing.  You have to stay up to date or else get swept down the tech stream.  I always keep my eye on emerging technologies, but the most important source I keep my finger on is tech job apps.

When they change, I change.  If your goal is to stay employed you need to stay fresh with your tech skills.  In my opinion there has never been a better time to get into QA than right now, this article backs me up as well:

https://www.jibe.com/ddr/the-top-5-skills-and-occupations-in-demand-right-now/


I found this article very interesting for anyone wanting to get into QA:

https://www.qualitestgroup.com/blog/future-of-software-testing/the-qa-job-market-is-a-killer-would-you-stand-a-chance/

One thing that is awesome about the QA field is that it is changing over to to automation at a rapid rate!  What does that mean to you?  If you are just out of a coding bootcamp and find the junior dev field crowed by a lot of other coding bootcamp students, than think about the QA field.

Test automation is at least 50% writing code, 50% manual testing.  One of the best ways to learn more about testing and automation is to start listening to "test talks", I listen to them on the way to work everyday:

test talks podcast

What if you are a manual tester who can't write a single line of code ( many of QAs are in this boat )?I suggest you start writing automation, - doesn't matter what you automate,it  doesn't matter how crappy the code, just start writing!  Push all of your code up to Github so you can start building a little portfolio for potential employers to see.

As an example do what I did, while watching some Netflix in the evening with my wife, I wrote a basic script to automate the process of earning points youlikehits.com site.  I don't need the script, don't really care about the script.  The point is to practice writing code and slowly improving your automation skills over time.  Check out my script...laugh... cry, write better code than I did and send me a pull request :-)

you_like_hits_auto_points_collector

I am learning to write my scripts more organically as of late.  I start writing the basics of what I want to the script to do, I start refactoring as the script starts to annoy me and starts getting painful to work with.

Instead of sitting and staring at a blank text editor and trying to write perfect code from the start, simply start writing and pay close attention to the "pay points".  NOTE: this is not good advice if you are a full blown developer.  I am speaking about people who are new to writing code.  When I follow my own advice I find myself feeling more free to actually just start and enjoy the process of writing code.

Isn't that the whole point?  I mean if you hate writing code and stress out every second you are working, why do it?  Let me know what you think of my script :-)  Next up,  I might try and write a script to automate a job on Fiverr!  Give me some ideas, tell me something that is painful for you.
joshuakemp85@gmail.com

Monday, November 7, 2016

How to automate everything - part 2

Want to be more productive at your job?  You don't have to learn how to code just yet to increase your productivity.  Remember we want to automate anything that we have to do 3 times, we don't necessarily have to write the code to do it.  If you use the internet in your day job and a web browser then listen up, I'm going to show you 2 tools / plugins that I use everyday.



Auto Text Expander - Chrome Addon.



I use Auto Text Expander when I am writing test cases in Jira.  Some people keep track of old test cases and try to reuse them.  I find it easier to make common "snippets" and reuse them.  For example I like to be able to type: "red" and have Auto Text Expander instantly auto type: "{color:red} {color}".  This is a small example but there are many more examples that I use at work that are project specific.  The whole key to getting started with automation is learning to become more aware of things that you repeatedly do everyday.  If you are constantly typing the same long phrase, make a shortcut and have auto text expander do it for you!



Autofill - Chrome Addon.


If you have to create dummy accounts or fill out the same forms everyday, do yourself a favor and download Autofill.  I use Autofill to fill in my Test Executions in Jira among other things.


You may not think the above are actually automation, but they are.  Anything you do 3 times in a day you should try to automate.  Which leads me to my last tip:

Never sign emails again!

I hope you are already doing this, but if you aren't using your emails auto signature you need to now!  Don't just read this post, download the addons and START using them :-)

Monday, October 17, 2016

3 reasons why you're not hired.

You want to know why you aren't hired?  It's really simple actually, three things.  See if any one of these is your personal kryptonite.


Not studying 21 hours per week:

It doesn't matter if you are self studying, going through Free Code Camp, or an online boot camp.  If you are not on your computer every night for at least 3 hours, you will never have the technical skills required to land an entry level tech job.  This is the most common mistake I see with people who are trying to break into the tech scene.  Sitting on Twitter or coding chats for 3 hours, sharing "great resources" is not studying.  It's okay to do occasionally, but if that becomes your pattern, you won't get hired anytime soon.


Don't have good people skills:
Only 50% of getting hired for an entry level tech position is technical ability.  The other 50% is people skills and knowing how to market yourself.  The best birthday gift I ever receiveed was a used worn out copy of "How to Win Friends and Influence People" by Dale Carnegie.  My Aunt gave me the book and 1 stick of Wrigleys chewing gum for my 14th birthday.  I guess I was a rude bad breathed teenager :-)  That book changed my life, I always get compliments about my ability to connect with people.  How can you nail interviews if you can't connect with people or you come across as rude?  What's the sweetest sound to any person?  hint: it's in the book ( and no I don't get any kickbacks )


Don't know how to sell yourself:
I learned this skill from listening to an interview of Robert Kiyosaki.  He talked about how he wasn't a great writer, but he was a best selling author!  He made it very clear that he wasn't going to ever challenge the great works of fiction.  He talked about how important it is to understand selling, if you ever want to make serious money.  I am always shocked by how many technical people are way under payed.  I have worked with senior level architects for test automation that were just terrible, yet highly paid.  On the flip side I know many talented and skilled developers who make far below what they are worth.  If you don't learn to sell yourself and abilities, you won't be able to nail interviews or even get interviews in the first place.


There are obviously other things that are important to know, but the above 3 are the most common issues that I see.  It's not rocket science or magic to land a tech job.  People all over the U.S. landed tech jobs today, you can join the ranks by following the above list!  Don't give up, you can do this!

Monday, October 10, 2016

Why Free Code Camp is only for the elite 1%



Everyone loves Free Code Camp, why shouldn't they?  Quincy Larson basically devotes his life to keeping Free Code Camp up and running and constantly growing, for that he should be very proud.

However if you are currently going through Free Code Camp's curriculum, hoping to one day land a job.  You should stop as soon as possible.

Why?

Free Code Camp is a great free resource for people, but it is lousy at getting people jobs.  The entire Internet has too many free resources!  The fact is that if your goal is to land a junior dev job by taking Free Code Camp's curriculum, you have about a 1% chance of doing so.

If you look up Quincy Larson's profile on Quora he says over 300,000 learn to code and build projects for non profits.  According to their home page Free Code Camp has gotten 2,000 people developer jobs.  Let's do some basic math here:

That's a dismal 0.67% of people who start Free Code Camp actually get a paid dev job!

I also clicked on the link on Free Code Camp to read the camper's stories, maybe I am wrong, but many of those stories aren't actually hired as devs or even in a real "techy" job.  Click on the Linkedin profile and you will see things like "freelance developer".  The point is maybe these aren't the 2,000 they are referring too, but still if only 1% of people get hired that is really low!

Again I think it is a great collection of free resources, but I don't think it is a great way to go about getting a dev job.  Think about it, do you think you are the 1%???  Now of course if you want to devote the next 2 years of your life to the program instead of going to college, that's cool.

Quincy has a really good answer on Quora about this idea actually that I like:
Quincy's Answer

Literally your chances of getting hired with free code camp are slim to none. If you want to do Free Code Camp to get badges, and look cool, that's fine.  If however you have legit bills to pay or people you have to provide for financially then you are mainly wasting your time.  If you want to have a tech job actually making money, a company paying you in the shortest amount of time than you need a clear plan to make that happen.

Quincy is being honest with what he does, it clearly admits No one has ever finished Free Code Camp, as of January 2016

According to this answer by Quincy Larson on Quora:
How many people have finished Free Code Camp so far?

I just think that the average person who signs up for Free Code Camp really believes that if they do the course work they will land a job.  The truth is your chances are slim to none with Free Code Camp, you need to learn how to market yourself, not just write code.  Remember this:

"Only 50% of landing an entry level tech job is coding ability, the other 50% is people skills and knowing how to market yourself!"

Don't just do coding tutorials and think someone will see your cool computer stickers one day at Starbucks and offer you a job.  Figure out a way to be different, don't do what millions of other people are unsuccessfully doing.  You can learn to code and you can get hired, but you need to set yourself apart from the rest of the crowd by being remarkable and unique!







Monday, October 3, 2016

How to automate everything series starting

The world is changing faster than ever, you need to be different than everyone else just to stay ahead.  I've said it before, you should learn to code but don't become a developer, at least not at first.  The fastest way into the tech field is through a QA position.

Even if you don't want to be a QA or Dev, you should learn more about coding, it can only help you.  I believe one of the best fits for people who want to write code is to get a test automation job.  What better way to practice automating stuff than in your own life?

I am starting a series called: "How to automate everything!"  Even if you have no interest in being a QA or Dev, you know that learning more about coding will only help you.  This isn't going to be scary, we'll take it in small bite sized pieces.  Pick one thing at work that you do multiple times a day and try to automate it.

If you do something 3 times, you should try to see if there is a way to automate it.  

I know that may seem ridiculous to some, but what I do at work is to keep a list of anything that I do 3 times or more a day.  I have a huge list to automate, I may not even get to them all, but what you will notice is that when you start keeping track of things you repeatedly do everyday, you will want to try and automate them.

All of the things I will use or show you will be are free, I want to help anyone from day one who wants to automate something.  The reason I am going to be showing you how to automate everything is so you can follow along and find a task of your own to automate!

If you want to dabble with code I personally find sooo much more motivation and passion if it is a real problem that I am trying to solve.  If you can make your job a little bit easier by automating one tiny aspect of it, why not?  In the process you will learn some things about coding and how code works, as well as some free tools to check out.

I will tell you a real life story of something that I automated to help my brother make more money.  My brother is a salesman at a well known store that mainly sells T.V.s.  The T.V.s aren't cheap, and he was constantly having this issue:

A person would come in, like a T.V. and tell my brother the following:

"If that T.V. drops in price by $100 in the next month call me, I'll buy it!  Here's my email and phone number."

What happened was my brother would write down phone numbers on pieces of paper, than after time he started adding them to an excel spreadsheet.  Spreadsheets of the SKU numbers of the T.V.s and a list of people interested in them.

I wrote a very simple script that checks if the price in the spreadsheet has changed ( it gets updated weekly from the company ).  If the price had changed my script would then grab the SKU number of the T.V., and search the list of people who wanted a call if the price dropped.  If the SKU number matched, it would send my brother an email with the person's name and tell him to email them about the price drop.  This is a simple example, that actually can make more money.

If you automate something drop me an email and I can tell others about it or share a link to your blog.  If you are super lazy or way over your head with not understanding code or how to automate something but need it automated, maybe you can hire me to do it for you :-)  Feel free to shoot me an email.

Follow along as I show useful ways to automate things, I will be using the easiest language to learn and use, Ruby.  I don't care about showing you the coolest ways to automate things, I will show you how to get stuff done using simple scripts and tools!

Thursday, September 22, 2016

Bash Aliases - Why you should use them and how to make them.




I will be giving a free 30 minute Google hangout session showing people why to use bash aliases, how to make them, and some more uses for aliases that you may not have thought about.

The first 7 people to email me and who can make the Google hangout time ( I will email it to you ), will be invited to the hangout session.  Bash aliases are super useful and not hard to use, once you see how powerful they are you'll be making some of your own!

I will be showing you some of my alias so you can follow along with me, you should have a Linux or Mac.  I want everyone to participate that attends, I want you to walk away with a new skill and not just have watched me type :-)

My email is:
joshuakemp85@gmail.com




Monday, September 19, 2016

Ruby Poltergeist gem the best way to scrape data

Over the years I have used several different gems to scrape data.  My 2 favorites being:
Nokogiri and Mechanize.  Both are very similar, but recently I had a challenge that neither Nokogiri or Mechanize could handle.





Here's the situation:

I needed to make a HTTP POST, passing basic auth to a login form, then go to another URL and scrape some data.  All of this can be done using the Mechanize gem.  The problem is after making the POST the site used AUTH0 for authentication, which was implemented using Javascript.  The Javascript redirects to another URL looking for the successful login code from AUTH0.

THE PROBLEM???

Mechanize and Nokogiri don't handle Javascript.  The good news is Poltergeist can easily handle Javascript, no sweat!  After using Poltergeist one time to solve this challenge, it has become my "go to" gem for anything and everything!

Poltergeist uses PhantomJS to run as a headless browser, I can still use the awesome Ruby gem Crack gem to parse any JSON or XML.  I can't show you the exact example I was working on as I am not allowed, but I can show you something similar.

There is as an old web based game called Hyperiums II I honestly don't play the game, but my friend does :-)  This isn't a post about how to cheat the game ( although you could ),  I want you to fall in love with this gem!  Once you use it, it will become the gem you grab if you need to scrape data or have a simple task that you want to automate.  Poltergeist is my secret weapon when doing any web scraping!

Here is a sample Poltergeist script of logging into Hyperiums II and navigating to build factories.  You can modify this code to do most any small task or test that you need!

Hyperiums II script


Saturday, September 10, 2016

Mr. Kemp you have been Terminated

Mr. Kemp we have decided to terminate your position, effective immediately.  Sign these documents please, I will need your badge and computer, best of luck for your future.



There is something inside of every provider that freaks out when being let go.  As I said goodbye to my former co-workers and got into the elevator, tears started to well up in my eyes. I got home in record time, there is no traffic at 11am.

It didn't matter to me that the company had laid off 11 other people the past week because they hadn't landed any new contracts. The reason didn't matter at all.

What matters was figuring out how I was going to get my next job AND FAST!!! I had no clue this was coming. I was told I was doing a great job and wasn't even looking for other jobs.

I will spare you all the depressing details and stress I went through. What came out of the experience was 9 days after being laid off I accepted a job offer for a mid level position paying $11K more!

I went on to coach other people for the next 12 months. I helped get people hired in record time all over the U.S. 

You don't have to cry like me, you don't have to stay awake at night with heartburn and stress unable to sleep hoping to land a job.

You don't have to read the 2,000+ emails I've sent to coaching clients listening, understanding their story and situation.

I poured my heart and soul into this course. I made the course I wish I could have had when I was let go. I would have slept better. I wouldn't have felt like I aged a year in those 9 days.

If you need a tech job in the shortest amount of time possible, this is the course for you, this isn't a learn how to code course, this is a : "LET'S GET A JOB COURSE".


I hope to see you in class!

Tweet one of the course links below and like the ‘course’ Facebook page and I will personally send you a free copy of my book: “No Degree, No Problem”! The course officially launches Monday September 12 but the first few lectures are up now if you want to get a jump start! 



People will go to bootcamps and take coding tutorials BUT when they are REALLY ready to land a job this is it here: http://bit.ly/2czEzCv ( Tweet this )

Need a tech job fast? Check out @joshuakemp01 's new course. A proven method and fastest way ever developed http://bit.ly/2czEzCv ( Tweet this )

Anything worth having takes hustling and an effective roadmap. Land a dev job now: http://bit.ly/2czEzCv                          ( Tweet this ) 

Sunday, August 28, 2016

The Fastest Way to Land a Tech Job

Where have I been for the past 2 months???  Working, hustling!!!  I keep trying to stop coaching but I have a serious waiting list, and people keep emailing me!!! It was getting hard to keep up with. I still have a passion to help others land a tech job, get out of their current career and help those who have dropped out of coding bootcamps.

I decided to take everything I have learned from coaching people on how to get a: Junior Dev, Test Automation, or QA job from all around the country and condense it down into a course. I've taken what I've learned from walking people through the process of landing their first tech job. On average I would send 200 - 300 emails to each person over the course of the coaching! Instead of you having to read all those emails and try to figure out what worked, I have done it for you. In a simple at your own pace course and at a more affordable price too!

The Fastest Way to Land a Tech Job course officially launches September 12th, but I am allowing people to sign up for a pre release launch and have access to the first 4 lectures ahead of time! You can find more info about what's in the course and watch the promo video at the link above.


Saturday, June 4, 2016

How to become a hacker: Part 1

I know it's been a long time since blogging, I have been finishing up with coaching clients, working, and studying in the evenings.  I have decided to show you what I have been learning and how you can do the same if you want.

The biggest advantage I have with becoming a hacker has been having a friend ( who is a hacker ) agree to mentor me.  My end goal is to get hired as a Ethical Hacker / Pen Tester, I am not simply learning to learn.  I want to learn how to hack and be good enough to actually go out and get hired as a hacker.  I am not learning to impress anyone or look cool, the mission is:

Get good enough to land a job as a hacker.

One of the first questions my mentor asked me ( who is on a Red Team currently ) was what type of security testing / hacking do you want to get into?  He compared me wanting to become a hacker as the same as someone saying:

"I want to get into Computer Science."

That is too vague, computer science is not specific enough, you could become a programmer, you could become a test automation engineer, you could do Big Data, the possibilities are endless.  The same is true with becoming a hacker, that is too vague, you need to get clear on what you will be security testing / hacking.

I decided on web application security pen testing since I like working with web apps and am most familiar with them.  My hacking training is specifically geared toward learning web application pen testing techniques.

So the first rule to becoming a hacker is:

Get clear on what type of security testing / hacking you want to do, don't try to learn everything.

On that note, I am learning some of the lingo used by real world hackers, and have found that they actually do not like the term 'Ethical Hacker', they call themselves 'pen testers', or penetration testers' but almost never Ethical Hackers.

The next issue is where and what to start learning?

There are so many resources and places to learn you can absolutely waste your entire life trying different courses and tutorials.  Everything I am writing about is my own personal journey to becoming a web application pen tester, with that said here is the first resource that you need:

http://www.cs.fsu.edu/~redwood/OffensiveComputerSecurity/lectures.html


Start on lesson 16and go through lesson 19.  The other lessons are good, but I am told are over my head for now.  The hardest part of this training is the homework, reading 80 - 100 pages after each lesson takes a long time and even longer to really understand what you are reading.  The book you will need is:

Web Application Hackers Handbook.

The to learning pen testing is not simply watching a video and reading a book, pen testing is all about hands on.  You absolutely must do what the book recommends as exercises or else you will only get the theory but not the actual how to.

How to actually do the exercises?

You need a web application that you are actually allowed to pen test without going to jail or being illegal.  The solution is:

https://github.com/WebGoat/WebGoat

Web goat is the best way to actually try out all the techniques you have read about.  Watch the lesson, read the homework go through some challenges using web goats insecure web application.  This is how I am learning and will be for sometime. 


Tools:

The first thing you need to do is to only use a Virtual Box or VM for all of your testing in case something goes wrong, you can simply delete it.  I did this wrong before, trust me you need a VM.

Install Virtual Box

Install Kail:
https://www.offensive-security.com/kali-linux-vmware-virtualbox-image-download/

On Kali install:

Firefox
Burp suite ( latest version )

There are more things you need to know, you will need to know how to set up a browser proxy to talk to Burp Suite so that you can test the web app.  If there is interest I will write some more posts on more specifics ( as they can be tricky when you are new to it ) if I receive enough emails.

The last thing I will say is that learning how to code was tough, getting an actual junior dev job was even harder, but none of this will be even close to how hard it will be to land an actually job as a pen tester at a company.  Companies want you to basically be able to hack an international bank and not get caught with very little supervision.  I am nowhere even remotely close to that level of skill but know I will get there eventually.  Follow along on this journey if you want me to show you the way!

Never give up, you can do it!