Hey Reddit, this is my first post ever. Seems like a cool community so I thought I'd share my story.

I started coding January 17, 2020, I’m now 101 days in.

An interesting side note: In the past 100 days, I have told no one what I was doing. My friends, family, girlfriend. No one knows that I'm learning to code. So you’re actually the first.

Learning To Code

I wanted to document, both quantitatively and qualitatively, what it’s like to learn coding. For anyone completely new to this, I hope it helps. To any vets, your feedback is incredibly valuable.

To begin, I started from actual zero. I didn’t know what a <div> was, a function, loop, the difference between front-end and back-end, and honestly I think I had never used a curly brace in my entire life.

I began reading blogs, detailing people’s personal journeys with coding. The most influential, for me, outlined how she became a developer in 1 year, making several original web apps along the way. She estimated her time spent learning to code (having documented every day she actually spent learning) around 300 hours.

When I actually committed to this Project, I oscillated between “how fast I can learn this”, and “how effectively I can learn this”, the latter was without a consideration of time (and not to be confused with how efficiently can I learn this). I created a plan, knowing well that things would change as I moved forward. In the time since starting I've more or less kept to the original concept while tweaking details along the way.

Base Level Plan

I determined with focused practice, 3 hours a day, every day for 100 days, I would reach the 300 goal in, more or less, three months. Getting to the bloggers (who I based much of this project around) proficiency. I reached that today. I still have quite a bit of work to do.

Second I determined FOCUS was probably the single most important variable. It seems that many people “work” or “study” for much longer hours (I believe much of which is hyperbole), and see diminishing progress.

An analogy that I like to use is, if you give a bodybuilder and a novice the same weight to work out with, will they achieve the same results (or more specifically will they achieve equal muscular stimulation?) The answer is obviously no. Rest time between sets, movement quality, heart-rate, range of motion, time spent in eccentric vs concentric are all variables in the gym. All to say that, how you use the tool (time, in this case) is equally, if not more, important than the tool itself. Reducing all of “learning to code” down to “time spent” simply wasn't a helpful metric alone.

So what did this mean?

• Study Sessions would be no longer than 1 hour. After which I would take between 5-15 minute break before starting the next session.

• All notifications would be turned off every device I owned. None of the tools I would use would even have the ability to distract me.

• Using a focus app (Forest for IOS) I would set a timer before I started a Session, and then leave my phone in the other room. This allowed me to track actually time “in-focus”

• No other tabs would be opened. If I had a question, I would simply jot it down, and move on. (This became painful later on when trying to diagnose errors, but led to more time trying to reason through and solve problems in my own code. i.e. a super important skill)

Focus Stopped

• If I saw that my hour was up, regardless of where I was in my lecture or in my code, I would stop.

• My focus broke. I would count this as any time my mind wandered in any way.

  • If I started thinking about problems at work.

  • What I was going to have for lunch.

  • If I was working in a coffee shop and started eavesdropping on someone else's conversation

  • If I started fiddling with things on my desk, or daydreaming of any kind.

  • If my focus extended beyond the 60 minutes (which happened on the rare occasion I truly lost track of time. Usually deep in a project) that time would count. Thus leading to the possibility of 90/60 minutes of focus or a 150% focus for that session.

  • Side Note: I used a screen time restriction on all social media to 8 minutes a day, across all devices. I can’t attribute this to better focus (since I didn’t also conduct this independently while having a limit of, say, 2 hours) but I think it definitely helped, at least my mental health.

The Three Phases

I split my learning into three distinct Phases.

Each Phase is 50 days long. Split into five, 10 days Sections.

• Phase 1- Learn

  • The learning Phase was all about figuring out “The right questions” to ask.

  • There was so much (and still is so much) about this world that I don’t know or understand. Learning the fundamental concepts was the first goal.

  • With that understanding I could begin to create a mental map of the road ahead, and more importantly find better tools to help me along my way.

  • There were some hiccups here, with direction.

  • For example, I started with CSS, then HTML, then moved to JS, then React. Realized I didn’t know enough JS to learn React so went back to JS. Learned some Node and Express, then back to React.

• Phase 2- Practice (Where I am now)

  • The goal of this Phase is to create as much as possible.

  • To make things, either through code alongs, prompted projects, and even personal projects and experiments.

  • One of the best tools for this was learning a new method, and then the next day (leaving a little time to forget) test myself by trying to build a small, invariably ugly little application using it.

  • Many of my apps are beyond hideous. Inelegant code, little to no styling, but every once and a while I’ll write something and just look at it thinking “Wow, that’s actually pretty badass”

• Phase 3- Build

  • This is all about building big, fully functional apps.

  • Working only projects that take weeks or even months to fully see realized. This is about trying to simulate, as close as possible what it’s like to actually be a developer.

Tracking

When I started, I didn’t even know what would be important to track. So things have grown, quite a bit, since day one. I spend about 3-5 minutes updating my spreadsheets before and after my hour-long Sessions. As well as 15 minutes at night writing a summary of everything I learned that day.

Here’s a link to Phase 1 and 2 Tracking as of today! There are accompanying Google Docs with notes, and summaries of what I learned everyday.

Phase 1 Notes

https://docs.google.com/spreadsheets/d/1eMZ9JO5CA_kuagzTasagde46jVcUmJkipsnG9dKTWD0/edit?usp=sharing

Phase 1 Focus Tracking

https://docs.google.com/spreadsheets/d/1Rh78qLXiL_MfllhI1OwbKKvvn0JXfH4avYP7TbACmcM/edit?usp=sharing

Phase 2 Comprehensive

https://docs.google.com/spreadsheets/d/1gN73DpRbQrBIPO4CAmNPcWBsE-9A8prEZWtOeY0-rUs/edit?usp=sharing

Tools

Before listing out the Tools I use, I really want to warn you if you're thinking about starting on this journey. It’s not about the specifics of the tools. It really isn’t, and it's hard not to get caught up in that. It’s about the application of the knowledge, thats where the real learning happens.

When you JUST start out, find an instructor online that you like, and make sure the course is up to date. Those two will get you 80% of the way there. Keep moving forward, momentum is your friend.

As you’ll see below, I like Colt Steele, his style is great BUT at this point I’ve realized I need to see other people write code. So in addition to learning new material during a course, I’ll search on YouTube for the same specific topic that he's teaching, and watch how other people implement that technology. There are so many ways to do the same thing. Now..... tools!

Tools

• Codecademy

  • I used the editors on here to complete HTML, CSS, JS and React.

  • This and FreeCodeCamp are where you start.

• FreeCodeCamp

  • What’s nice about them is the blogs that are featured on their site.

  • I also signed up for their newsletter which features some interesting articles and quick reads to expose you to more of this world.

• YouTube

  • Avoid at all costs, honestly.

  • Now obviously you’ll need to go here, but youtube is kinda like the slimy underbelly of learning to code. You go in for something that you need, but (quite literally by design) you’ll be enticed to stay, go off on tangents, and start thinking to yourself “Hmm I wonder what extensions he’s using on VS Code” or “Wow, I do need to know the top 7 tricks that ex-Facebooks used to get an interview”

  • Get it, get out. Other than that, there are a few good Youtubers, who have udemy courses. Which leads me to...

• The Web Developer BootCamp (Colt Steele Udemy)

  • Great, great, great introduction to full stack web development.

  • Slightly outdated. In all honesty I cut it short when it came to the backend because almost everything they were discussing and tools they were doing needed to be modified in some way.

  • At the time I wasn’t great at reading documentation, so I ended up spending more time trying to make code compatible, than actually progressing through the course.

• Modern JavaScript BootCamp(Colt Steele, Steven Gridder Udemy)

  • This was a doozy, directly after The Web Developer BootCamp. It rehashed alot of the same topics, but with new examples and updated JavaScript syntax which is nice.

• The Modern React BootCamp (Colt Steele, Udemy)

  • I’m still working on this now. So far, I would give it (and plan to) 5 stars.

In addition I just bought

• The MERN fullstack guide (Maximilian S., Udemy)

• CSS- The complete guide 2020 (Maximilian S., Udemy)

Beyond this, in my notes I list specific documentation I read on a daily basis, blogs, and specific YouTube videos.

Goals For Phase 3

Next as you can see I’ll be working on both deepening my understanding of backend development, as well as design and CSS. Kind of seem at odds right?

Goals

• Post more on Reddit, and get more involved in the community (timing is pretty awful, I know).

• Create projects and seek feedback from other developers.

• Have actual conversations with developers and in an attempt to uncover my blindspots, and to help tweak my trajectory.

• Publish on Github.

• Build something aesthetically pleasing (lol).

I hope this was helpful if you’re just starting out on your journey. If you have any questions for me, please feel free to reach out. I’d love to talk to someone about this, considering I haven’t in the past 100 days.

Hey fellow/future coder, I am the creator of a newly established YouTube channel by the name of Code Talks. When I started coding there wasn't any good programming courses that you didn't have to register for. I want to bridge that gap. On my channel I teach computer science, and computer engineering concepts such as Java, Python, Arduino, Processing, and more! This channel is for anyone who wants to learn about some cool concepts, and projects. I upload mostly on weekends sometimes on Tuesdays. My mission is to allow anyone to get into coding easily, I’m sure a lot of you experienced programmers found breaking the ice between yourself and coding very hard, I want to remove that ice from any new programmers! Please visit my channel at:

https://www.youtube.com/channel/UChVyhDWb0z8giBTf51tK_PQ

Please take the time to watch some of my videos and like and subscribe. When you view a series from my channel, videos are longer at the start and as we progress we get shorter videos as more knowledge is gained throughout the series. Thanks.

Hey! I just graduated college as an electrical engineer and have a solid foundation of python and c++. However I feel stuck. In college I was given skeleton code to implement the functions I created. I can write functions to do things but idk how to build those functions into a full program on my own.

Now I don’t have a professor sending me skeleton code and I don’t really know where to go. Could anyone direct me to some Sample problems or topics to study? I’m looking to know what it is I don’t know. Kinda like a next step in my self taught curriculum.

Also should I continue with c++ and python or should I start on a new language? I’m not sure what trends there are in the industry in regards to language usage.

For anyone that's been having trouble with this assignment (It's really taken a shit all over my day) here is a working code for the program. I really don't like the way the assignment was worded

"Write a function called

isEven

that returns a boolean of whether or not a value is even or odd. The

isEven

function should not print anything out or return a number. It should only take in a number and return a boolean."

Basically the way this one works is by creating the function "isEven" as a means of figuring out your boolean, and then instead of creating a "isEvenNumber" function you just want to go ahead and slap it into your start function as a variable.

You want your "if(num==SENTINEL)" to come first in your "if/else" statement so that it actually registers -otherwise your SENTINEL will just register as even and the program won't break it will just count it as another number.

I know this program is painfully simple to anyone that knows anything about coding but I hope this helps all of you Computer Science Principals kids that might be confused as to why you're getting "True/False" returned instead of "Even/Odd".

var SENTINEL = 0;

function isEven(num) {

if(num%2==0) {

return true;

}else{

return false;

}

}

function start() {

while(true) {

var num=readInt("Enter a number: ");

var isEvenNumber=isEven(num);

if(num==SENTINEL) {

println("Done!");

break;

}else if(isEvenNumber==true) {

println("Even");

}else if(isEvenNumber==false) {

println("Odd");

}

}

}

Just wanted to say thank you for the recommendation and comments to continue with the course! It is awesome!

I am a software engineer with 8 years of experience in the industry, I would like to take some time and teach a group of 5 random people on the internet on how to code. Number 5 is arbitrary, not too big of a group and not too small of a group, but has to be defined. I would give you four hours weekly at least of classes and it would take a few months (depends on how long does it need to be).

When we form a group we'll define the best path to take in terms of technologies and programming languages, you need to have a good internet connection to be able to share screens in time of our classes.

Here's registration form if you wish to apply: https://sulejmansarajlija.typeform.com/to/e11Uz9Je

Hey. I found r/learntocode around 1 year ago, looking some change in my life. Checked the top posts at that time, found upskillcourses and project odin(from comments). Today i signed a cotract as ruby/ruby on rails developer.

Just wanted to say, THANK YOU!

Hi! I’m a full stack web and JavaScript developer with experience in HTML, css, JavaScript, python, java, dart, and much more. If anyone wants to learn basic programming I’d be happy to walk you through writing your first python game. Just pm me. :)

When I started learning to code, I had no idea what I was getting myself into. As I was reading blogs, watching videos on this topic, I noticed two main things. The first one was: ‘Everyone can learn to code because coding is easy’ and ‘People getting stuck because things did not make sense to them’.

Well, now, as I’ve been coding for a few years professionally and mentoring people how to code for a living, I realized the 3 biggest mistakes I made while learning to code.

1. Shiny object syndrome (S.O.S.)

Shiny object syndrome is when you jump from tutorial to tutorial, from course to course, roadmap to roadmap, thinking that finally, you will get the best solution for your problems, this is the only thing you have to do to learn to code and get a job.

As you go through the course, you will reach a stage where things will get difficult and you will think this course it’s dumb, or you are too dumb and instead of pushing through the discomfort you decide to buy another course or find a better alternative. And you go again through the basics, waste one more month, just to find out that when it gets hard you want to quit again in favor of the next shiny new thing that is on discount on a course platform.

This comes from the idea that what you are doing right now it’s not good enough or you feel like it’s too hard and there should be an alternative that’s easier. Because learning to code it’s easy, which is not. If it would be easy you would not get paid over $100,000 per year.

Instead, if you have the shiny object syndrome, you should just stick to your course or your roadmap for at least 60 days. The best way of sticking to something its accountability, found someone to hold you accountable and you will be golden.

The grass is not greener on the other side, the grass is greener wherever you water it.

2. Not doing

Not doing means exactly what you think, it means you spend hours watching tutorials, maybe not even typing along, thinking that somehow you will learn how to code. Instead, you know a lot of things that make no sense to you. The moment you close the tutorial, you forget everything you learned, you hate the boring syntax because you don’t understand what it does.

Congratulations, you got 100 points in the javascript quiz, but you can’t even put some text on the page without checking 10 tutorials.

Instead what I would do, is try to make a small project, and break everything down into small steps and google word by word all the steps and try to put them together. It might take you 2 weeks to learn to toggle and HTML class, but you will be thankful for those 2 weeks in one year from now. Learning is based on the compound effect. In the beginning, you might not see any progress, but at some point, things will click for you and your knowledge will explode. You will write code with your eyes closed ;).

3. Not having a roadmap and a war map

War map? A war map means planning 3-6 months ahead, knowing what you will be doing every week, every day.

Do some market research, find out what the jobs in the niche you want to work from your area require. Put all the skills on a piece of paper, and google all of those skills, you will start noticing some of those skills coming up and up again. Don’t be lazy with this. Don’t waste your time. That’s your gold, learn those things.

I help aspiring frontend developers in their 30's and 40's to get their first React job, and so I’ve been asked many times how to start learning to code.

What are you currently struggling with?

So long story short I'm 30 years old male... Since I was a kid computers and technology were always my passion I loved fixing them installing different software and stuff like that. Over decade ago started a college majoring in computer engineering, but due to financial hardships and other things I quit after 2 years. Now inside me I feel like that need to learn something new and was thinking about learning to code. I've seen a lot of courses online but not sure where to start and what is really good... Should I start with Java or Python first? What online free courses would you recommend. Im planning to spend at least 30min to an hour every day to learn & how long it usually takes to become proficient at them being self taught? I really appreciate any other tips and advices.

See full post with images: https://loopinput.com/the-heros-journey-of-coding/

Almost universally learning to code is hard. It is hard and it is frustrating. Resources to go from 0 to 1 as a beginner are easy to find but figuring out the path from 0 to mastery are not.

The modern coding environment only complicates this as more and more options, tools, frameworks, and potential paths are invented. These options are designed to make coding more manageable, but for a beginner can be overwhelming.

My goal here is to lay out a clear, structured path from 0 to mastery I call “The Hero’s Journey of Coding.” The Hero’s Journey is hard. The Hero’s Journey will be frustrating and will feel hopeless at times. But the Hero’s Journey works.

I heavily based the strategy on research from Cal Newport (computer science professor at Georgetown University) and Barbara Oakley (professor of engineering at Oakland University), as well as on a large body of research into learning, and more specifically, learning technical subjects.

Learning to code is a non-linear process and forcing a strictly linear structure on it will slow your learning process. It is analogous to learning a language.

Two hypothetical people start studying Mandarin at the same time with no prior knowledge of the language. One begins a course that promises mastery of the language by the end of the course. The other takes the same course… but supplements it with reading books in Mandarin, watching shows in Mandarin on Netflix, speaking to Mandarin-speaking people in his or her area every day, listening to the news in Mandarin, listening to podcasts in Mandarin, memorizing Mandarin grammar structures and vocabulary words, switching to the Chinese servers in the online games they play, asking about aspects of the language that confuse them in Mandarin language forums etc.

Because the second person is varying their types, contexts, and methods of learning, they will learn Mandarin surprisingly faster than the first person while preventing burnout by altering the kind of cognitive load they place on their brain.

Additionally, since the gains are cumulative, the second person will exponentially approach mastery faster. This approach is backed by research. If you want to look into it further, Harvard has an excellent compilation of research into the topic here: https://bsc.harvard.edu/study-tips-guides

Differing your types and content of learning also promotes neurogenesis (production of new neurons in the brain). Here is a study on the fact: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3445739/. The other thing proven to increase neurogenesis, by the way, is exercise (specifically aerobic exercise). The same study linked covers that topic as well if you are interested.

In this guide, I’ve put together the findings of this research into an actionable sequence I call “The Hero’s Journey of Coding.”

Some parts of this guide, particularly towards the end, will upset people and may be construed as overwhelming or discouraging towards beginners.

I’ve purposely constructed this guide to be the antithesis of the other guides I’ve read (and I’ve read hundreds) which have been too vague, too introductory, and too afraid to get into the nitty-gritty of how the actual process usually looks.

What I lay is not the only way to learn, but it is a research-backed, experientially backed, and effective way to learn. Here I offer the gory details of the whole process, so I hope you are ready.

The Call to Adventure: A Guided Introduction

The first step in the hero’s journey is a guided introduction. Before a hero can pursue his core quest, he must learn the ropes. This most often comes in the form of a course, often a video course.

You are going to want to find a long-form introductory course (minimum should be 40 hours). You can start by going to Udemy and sorting by duration (https://www.udemy.com/topic/javascript/?duration=extraLong&sort=popularity). Other popular alternatives are the Odin Project (https://www.theodinproject.com/) or Code Academy (https://www.codecademy.com/).

Two instructors I personally like are (https://www.udemy.com/user/maximilian-schwarzmuller/) and (https://www.udemy.com/user/coltsteele/). But make no mistake, this course is just going to give you the shallowest feel for what you are about to pursue.

You will begin to get the breadth of what you need to learn. You will start to know the tools, frameworks, terminologies, and places to look for knowledge.

Don’t worry too much about the language or frameworks that you start with as long as they fit your end goals and are popular. Coding languages are not like spoken languages; once you know one in-depth, you can pick up others fairly quickly. So the language you start with will not doom you down the line if it falls out of popularity. Also, as you become more knowledgeable, you can make a switch if necessary.

Don’t fall prey to language and framework “paralysis by analysis” and instead do a week’s worth of research and then dive in and commit at this stage to the course, language, and framework you have chosen. Finish the entire thing from start to finish.

Other alternatives to a video course are classes or boot camps if that is more your style. If you went to school for something like computer science or have the equivalent experience already, you can skip this step entirely.

Think of the guided introduction as defeating the low-level beasts you need to get from level 1 to level 10. Make no mistake, some of these “low-level beasts” will be formidable.

In fact, the low-level beasts are often a more significant obstacle than the higher level beasts that will come along later because your skills will scale up faster than your enemies.

You are going to need a little help. It’s time to consult the oracle.

Supernatural Aid: Consult the Oracle

Who is the oracle? The oracle is known by the mystical name “Google.” You can ask the oracle anything, but you need to ask it the right way.

As you ask the oracle more questions, you will get better and better at divining answers from her mystical responses, which may often lack context and appear unusual. Often answers will appear in coding forums like Stack Overflow (https://stackoverflow.com/).

Sometimes you will find out your question has already been asked and the answer is already available. At other times, you will find out that you must ask the question yourself.

As you go further along, you will never stop Googling but the answers to your questions will more rarely appear as they get more technically complex and more specific.

The Vision Quest: Your Core Quest:

You cannot keep dispatching low-level beasties forever. You need to pursue your core quest. Your core quest is a project which you continually build on and improve as you learn more.

The core quest should start as soon as the guided introduction is finished. You need to learn how all the concepts tie together and work in the real world. The less like a simulation and the more like your end goal the core quest is, the better.

The core quest will start out humble but will develop into a save the world scenario. The core quest is what you never lose focus on and is the most crucial part of the journey. All the other parts of the journey are to supplement the core quest.

The core quest is from where the glory and victory in the Hero’s Journey comes from.

Descent Into the Underworld: Do Battle

As you pursue your core quest, you must do battle with great foes to improve your skills. These foes come in the form of coding challenges from sites like leetcode (https://leetcode.com/), codewars (https://www.codewars.com/), or hackerrank (https://www.hackerrank.com/).

Coding challenges are a different kind of coding than your core quest or guided introduction. You want to pursue different types of knowledge paths so you don’t burn out doing the same kind of learning. Remember, research indicates that diversifying your learning strategy exponentially improves your path to mastery.

Start with the most manageable problems and eventually try to work your way up to the hardest ones. Try to make it a goal to do every single problem in the site in your chosen language if possible.

The Master of Two Worlds: Learn from the Masters

As you slay great enemies, you will feel the need to go more in-depth in specific subcategories of battle. This is where you consult the masters.

The masters have created great tomes for you to pore through. Using Javascript as an example, start with the thinner tomes (https://eloquentjavascript.net/) and work your way up to the great towering tomes (https://www.amazon.com/gp/product/B07FK9VBD7/?ie=UTF8&%2AVersion%2A=1&%2Aentries%2A=0).

This does not come after your core quest or doing battle but is interspersed between. As you pursue your core quest and do great battles with enemies, you will need to take breaks to regenerate and refresh yourself. That is when you read these great tomes.

Ascension, Apotheosis, and Atonement: Arcane Knowledge

The tomes will give you great knowledge but you will find yourself thirsting for the more arcane and specific knowledge. This is the last part of the coder’s journey.

The arcane knowledge is the documentation itself. This is the raw, unfiltered, incantations. You will learn sick and unnatural abilities from these arcane sources. Start out by reading the documentation as a reference point beginning with the core quest but the spells and incantations are brief and specific, and so, should eventually be memorized.

The documentation itself is usually brief enough to be fully digested overtime. I suggest turning the entire documentation for the tools, frameworks, and languages you use into online flashcards using something like quizlets (https://quizlet.com) and gradually memorizing them.

So, for example, if you are a web developer using MongoDB, Express.js, and Node.js that would include the entire mdn docs (https://developer.mozilla.org/en-US/), MongoDB docs (https://docs.mongodb.com/), Express docs (https://expressjs.com/en/api.html), and Node.js docs (https://nodejs.org/en/docs/). It would also include any tools you use like Bootstrap (https://getbootstrap.com/docs/4.3/layout/overview/) or Mongoose (https://mongoosejs.com/docs/api.html). If you use it and it has docs, include it.

This may seem overwhelming, but you would be doing this over a long, long period of time and piece by piece. Evidence that this strategy is effective: https://bsc.harvard.edu/files/smarter_studying_8-10-16.pdf

Having the documentation memorized is a sick and powerful ability. This is the most grueling, controversial, and formidable-sounding part of the hero’s journey, which is why I saved for last.

This comes after you have slain your great foes and have completed most of the journey and are searching for that last, last edge to push you over the top into glory.

Go forth, hero, and find your glory.

I am currently developing a web application and I am looking for individuals who are interested in testing the application and providing feedback on their understanding and any areas that require clarification. You can access the application on my website https://jeanphilippebelley.com/ and join the Discord channel for any queries or concerns.

As a benefit, you will have access to a programmer who can provide assistance in your learning journey.

I am so excited to introduce you to Median Bootcamp, which will eventually be a completely self-paced Coding Bootcamp, all online.

Median Bootcamp

I currently have a full course on HTML and a guide on Python Web-scraping Basics. The CSS course is coming soon.

HTML Full Course

Python Web-scraping Basics

My goal is to have an entire Bootcamp curriculum including projects, project review, career guidance, and certificates. I am so excited to kick this off and I hope you'll check it out.

Edit: After receiving feedback I making a website for it too. I will update this post when it’s ready

Hi all! I'm a computer science student who is streaming coding on Twitch. I work on my projects on stream so you can see the entire development process. I'm currently building an electron and react app for habit tracking and I'd love to see more beginner programmers on my stream.

I know what it's like to feel overwhelmed and lost and I'd like to help my fellow coders as much as possible. I really enjoy being able to answer questions and research new topics with everyone and my stream is very welcoming and we joke around a lot :) I'm hoping this can help you on your journey! All the best x https://www.twitch.tv/bashbunni

With this guide, you will learn how to build a GitHub Portfolio and how to make live websites to show off your code. You will also learn all about version control and working with repositories and branches.

Git and GitHub Tutorial

As I said in the title, I've also got long-form article courses on HTML and CSS with interactive coding examples. I hope they will help someone out.

HTML Full Course

CSS Full Course

Happy Coding Everyone!

P.S.

(I'm working on a MASSIVE Article for a JavaScript Full Course and then there will be a Python one so stay tuned)

Am I too old and face the real reality of ageism??

I will turn 51 next month. I’ve worked construction, factories, shipping/logistics, automotive industry, R&D lab technician and presently as an Automation/maintenance technician in the aerospace industry. I would consider myself somewhat tech savvy. I’ve just started learning to write code. It’s going well and find it very interesting. I consider myself a “life long learner” with a variety of hobbies(precision shooting, amateur radio, musician). How does the industry view older people entering the field?

The format is mob programming, where we all as a group work together to solve a problem--there is one person typing and everyone else is discussing ideas. DM me if you are interested.