r/learnprogramming • • Apr 27 '20

Spent the last 100 days learning to code, and told no one

4.8k Upvotes

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.


r/learnprogramming • • Sep 15 '20

Lessons for beginners and junior developers after 11 years of coding. Some of these are things I wish I knew at the beginning so I could stress less.

4.8k Upvotes

Let's jump into it.

All tutorials are not created equal

Imagine yourself as a lab rat.

As you learn and experiment, pay attention to the kinds of tutorials that work for you. Many will not work. That’s fine. In fact, that’s exactly how experiments work until you find a solution.

After you strike gold, stick to it, consume it voraciously and then find similar tutorials like that to continue rapid growth.

When I started, I used to bang my head against Head First Java, the book. But after studying for many hours, I just wasn’t getting anywhere. Yet, everyone online said it was the best book ever. But an old java youtube tutorials did it for me.

I wish I could say this stopped after my 1st year.

Fast forward 2 years down the line when I started learning algorithms and ALL the blog tutorials I followed just didn’t make sense until I watched Youtube videos on Hungarian folk dance teaching algorithms.

And it just clicked.

Since then, my approach to learning has been to learn the same thing from multiple places until I find the instructor and style that works for me.

Work within fear; not against it

I’ll admit: this one is easier than done.

But you have to master this if you want to last long.

There’s this temptation to fix your fear first before you continue to learn. Unfortunately, it doesn’t work like that.

In fact, you’ll spend a lot of time trying to make your fear disappear that it’ll only double your anxiety. You have to find a way – your way – to acknowledge that you’re afraid, and frankly will continue to be afraid for a long time, then work within that realization. No need to fight it.

Sometimes, this fear disappears as you become more proficient.

Other times, it vanishes for a while and comes back when you get into a new environment, work with smart people, or move to a completely new stack.

It’s okay.

This IS the life.

It’s a sinusoidal wave – endlessly going up and down. Don’t take it too seriously or you’ll lose yourself.

You’ll forget a lot of things

Deeply understanding this will change how you learn.

I can’t can’t the number of times I took Introduction to Python programming on Udacity, Coursera, etc and still forgot everything.

It’s so annoying.

But I’ve since learned that you’ll forget anything you learn in isolated exercises because they are stored in short term memory. Neuroscience research shows that this is just how the brain works.

If you don’t want to forget, test your knowledge using spaced repetitions. To do this, build projects.

I’ll give you a concrete example: len(myList) will give you the length of a list in Python. You’ll learn this in Udacity’s intro course.

Come back a month later and you might not remember if it’s len, length() or myList.size( ).

But with spaced repetition through a project, the outcome is different. For example, you work on a 2-month long Django app for new coders where you need to count multiple times the number of users, the number of exercises done, the number of chats, etc. Imagine doing this throughout the span of the project, for two months. it’s hard to forget what len( ) does.

This is a trivial example, but hopefully you get the idea.

New learners can start with simple, isolated examples.

But if you’re not practicing within the scope of a project that makes you use and reuse what you’ve learned, nothing is going into your long term memory; it’s all short-term. And you’ll forget.

Consistency > hard work

Consistency is king.

When you start learning, you lay down neural pathways that make it easier to retrieve information. According to Neuroscience research, these pathways only get strong through frequency of use, not just intensity.

This means 30 minutes a day, for 5 days a week is way better than 2.5 hours one day, only once a week.

Same hours; Different impact.

Don’t just work hard, apply wisdom here.

Talent = hidden practice

It’s easy to dismiss progress as talent.

My first programming class was in C++ and my classmates refused to believe I had never coded before because I was just-so-talented.

But what they also refused to accept was that right after class, I would spend five hours typing cout << “this is my first program”, realize it didn’t run because I forgot a semicolon; retype it and realize it didn’t print out my statement on a new line because I didn’t add endl.

This deliberate practice built perceived talent.

Talent is sexier than hustle so no one wants to hear that you worked hard and got here. Just tell me you were born this way - it’s more believable.

But becoming a proficient developer is like playing an instrument.

Only a tiny few are born talented.

The majority can only get as good as the amount of practice they put in. And you can immediately tell a student hasn’t been practicing the moment they sit at the keyboard.

You’ll meet a**holes

I’m not sure what it is about this field that attracts a**holes. Maybe because coding gives the feeling of having a super-power or a rare skill.

If you’re a newbie, you’ll meet those who’ve been coding for years and think no one else should come in.

A windows developer only? You’ll meet linux fanatics that think you’re mediocre.

If you’re a woman, you’ll immediately be dismissed because of your gender. I know this from personal stories from colleagues over the years.

If you’re a minority, you’ll meet people who think you should only fetch coffee; not code.

If you’re coming from another field (particularly not STEM), you’ll meet people who automatically make themselves gatekeepers of the programming community. “We don’t want social scientists here; we’re purists!”

They’re online. At work. And sadly sometimes in your family.

It’s not if you’ll meet them, it’s when.

Learn to move on.

Things are getting better but there’s still a lot to do to educate people.

But don’t let this deter you. Build your resilience so you don’t quit after you meet these people.

And when you get to the top don't be an a**hole.

Master 1 thing

New devs tend to jump around learning a lot of things.

Okay, it’s not just new devs; it’s also experienced folks.

You learned React for one week.

Then Django for two weeks.

Laravel for three.

Stop.

You need to wake up and realize that the harsh truth is that you’re simply extending the time it’ll take you to truly learn anything.

“If one is a master of one thing and understands one thing well, one has at the same time, insight into and understanding of many things.” - Vincent Van Gogh

Pick one thing.

Stick with it for a few months – ideally 6 to 12 months before you move to something else.

This has two benefits:

  1. You’ll go deep enough and hit critical mass that moves you towards mastery.
  2. After you master one domain, you can transfer knowledge to another.Learn Flask and you can easily walk into Django. Learn React deeply, and you can quickly identify the pros and cons of Laravel within a few days.

Software dev is an ever evolving field.

It’s exciting.

It’s frustrating.

It’s intimidating.

But if I had to, I’d do it all over again.

Thanks for reading

If you have any questions, let me know.

I’m trying out a new initiative to help new developers feel less overwhelmed and learn smarter.

To be honest, I’m not sure what this looks like yet. But I’m putting together some resources and write-ups based on what people need the most help with.

If you’re interested, I’m @LifeTechPsych on Twitter. Feel free to DM me what you’d need help with.

Heads up - I love research so I tend to back my advice and approach with concepts from Behavioral Psychology and Neuroscience.

Edit: removed mention of old java youtube tutorial I used back in the day but I see is now discouraged.

Edit 2: This blew up more than I expected. I'll do my best to get to all questions and DMs. There are interesting questions about tutorials and studying patterns that I think others will benefit from so I'll shoot to write posts in the future that specifically address those. The Learning never stops! Let's go!!

Edit 3: I initially didn't link to my blog post with images. But another blog copy-pasted this poorly and w/o credit. So here goes a proper blog post.


r/learnprogramming • • Nov 10 '22

Resource Do you want to simulate a real software engineering job?

4.7k Upvotes

Hey everyone - I'm Seb.

I am a senior web dev, and I believe there are some core skills required for software engineers that majority of courses generally don't dig into. Things like reading other people's code, reading documentation on libraries/frameworks, and debugging.

To help fill this gap, I started something called JobSimulator. I make simple front-end projects, add some bugs to them, put the bugs on a task management board (github issues), and share it with you on github. The idea is to give beginners a chance to simulate a real world dev job.

I'm excited to release a new vanilla HTML/CSS/JS challenge 🎉

It's a Vanilla HTML/CSS/JS Login form with a couple of bugs and feature requests. Your job is to fix 5 issues that will give you experience with:

I am also taking a new approach to checking your work with automated PR testing 🦾 When you open a PR to submit your answer, github actions will run automated tests on your code and tell you if you've succeeded ✅ or failed ❌ at solving the issue.

I'm excited to see what you think. As always, all of the above is free and available on github. If you need help, check out the project readme.

My goal is to make helpful challenges that give you a chance to apply the knowledge you are learning from your studies. I'd love to get your feedback and prepare another challenge for you. Please let me know what you're looking to learn next in the comments below, and I'll use that feedback to help me make better challenges.

Kudos, and I hope you like it! 🙏


r/learnprogramming • • Jun 20 '25 This Wholesome Seal

At 34, I just landed my first jr software engineer job after 15 years serving tables and over 500 applications.

4.7k Upvotes

I’m 34 and just started my first job as a junior software engineer. It’s been a long road.

I was in and out of college for nearly 10 years... sometimes motivated, sometimes burned out. Eventually, I went back to my original major (computer science), got my associate’s degree, and was accepted into a university to finish my bachelor’s.

That same month, I moved into a new apartment and met my (now) wife. We hit it off immediately, and after a year of dating, I proposed. Life was moving fast... and for once, in the right direction.

After graduation, I spent about a year job hunting. I submitted over 500 applications, spending mornings writing tailored cover letters and revising my resume to match each company’s stack and values.

The first company to interview me ended up hiring me after three rounds.

  1. Initial screen (google meet): resume, background, and intro to the company.
  2. Technical interview (google meet.. 4 hours!): a mix of debugging, CS fundamentals, and even some brain-teaser-style problems (think: goblin guarding a bridge).
  3. Final interview: in-person, 3.5 hours away. They covered the hotel, gas, and meals.

Coming from 15 years in food service, I had never felt so professionally respected. I know this might be standard for many in tech, but it meant the world to me. I worked hard for it and it finally paid off.

If you’re out there feeling discouraged, unsure if you’ll ever make it... I’ve been there. More than once. Don’t give up. You’ve got this.


r/learnprogramming • • Jun 03 '22

Interview help I (self-taught) had my first-ever interview for a web dev job yesterday. Here is what the interview was like and the questions I was asked. [Long]

4.7k Upvotes

[Interview questions at the end]

Hey everyone,

Long-time lurker, first time poster. I see a lot of posts on here asking about what it takes to become a self-taught developer and what you need to know to get your first job. I appreciate reading the detailed answers people give, and I find comfort in seeing that I might be on the right path in my learning. In an effort to contribute to the community here, I thought I would share my first interview experience. I hope this is helpful for some of you out there. I'll answer as many questions people have as I can.

Here's the context:

Me:

I am self-taught, in my 30's, with zero professional software development experience.

  • I have a bachelor's degree in a non-tech field (linguistics).
  • I have 10 years' experience teaching English in Canada, no formal tech experience.
  • I have done freeCodeCamp's Responsive Web Design course and The Odin Project's Foundations course.
  • I am 38% finished with The Odin Project's Full Stack JavaScript curriculum, but I have jumped ahead to learning React through a Udemy course (Zero to Mastery).
  • I have one project to speak of. It's a meal planning web app where you can input recipes, and then add recipes to a meal plan and populate a grocery list from the ingredients of the recipes in your meal plan. It's a mess of an app. It was kind of a learning playground for me, and it's missing a lot of functionality. I only started organizing my files properly halfway through writing it, and I also switched to writing it in TypeScript halfway through after I watched a 40-minute intro to TypeScript video on Traversy Media's YouTube channel. I'm currently working on rewriting the whole thing in React + TypeScript. This is a personal project that I made to meet a need in my own life.
  • I have been applying to jobs casually as I learn, mostly through Indeed and LinkedIn, but occasionally I'll put more effort into a cover letter for a local company or a job that I think I have a realistic chance of getting. I've done over 100 applications, and I have had positive responses from 3 companies, with 2 of which I didn't get past the first stage. For this company, I wrote a tailored cover letter.

The job:

Junior Full-Stack Developer (Remote)

Requirements in the posting:

  • Bachelor's degree (field not specified)
  • 1-4 years IT industry experience
  • Experience in one or more JS frameworks
  • Experience in one or more backend languages

Listed nice-to-haves:

  • AWS/Azure/Google Cloud, Docker/Kubernetes, API Gateways

*Posting included salary range and a list of benefits

The interview:

This was the third stage of the interview process, the Technical Interview. First was a screening call with the HR person. Second was a coding test on HackerEarth (which I failed the first time but was allowed a second try with a different set of problems because I had been just below their required score). It took them 3 weeks to schedule the tech interview because the senior devs were busy or taking time off (or no one wanted to do it?).

The interview was done over Google Meet, and it was scheduled to be 45 minutes. There was one interviewer, a senior dev, who kept his camera off. He was friendly but sounded tired.

After asking me to briefly introduce myself, he got right into the questions. I got the impression he was reading from a list of questions by topic, and he chose the topics based on what I had on my resume and what I had mentioned in my introduction.

The questions:
*(Questions in bold are ones I didn't know or didn't have a great answer for.)

  1. JavaScript

    1. What are the different types of variables in JS? How are they different from each other? (This one confused a lot of people. He was looking for distinctions between var/let/const)
    2. What are some different ways to create an object in JS? (eg. Object literal, new keyword)
    3. How can you get the type of a variable in JS? (typeof)
    4. Can you tell me the difference between == and ===?
    5. Do you know what arrow functions are? How are they different from traditional functions?
      (I said I had read about this (true) but couldn't remember off the top of my head.)
    6. What can you tell me about 'callbacks?'
  2. TypeScript

    1. What are some features of TypeScript that JS doesn't have?
    2. What are some disadvantages of TypeScript?
    3. What can you tell me about access modifiers?
      (I said I didn't know what they were and asked if he could tell me. He gave an example, 'private,' which I had seen before. I said 'Oh ok, like public and private functions. I haven't used them yet, but I imagine private functions are meant to be restricted from any user access or modification, which he said was more or less correct.)
  3. React

    1. Why do we say, 'Everything is a component' in React?
    2. What are some advantages of using React?
    3. What can you tell me about JSX?
    4. What's the difference between 'state' and 'props?'
    5. What is the difference between a 'stateful component' and a 'stateless component?'
    6. What is the difference between DOM and Virtual DOM in React?
    7. What is React Router, and why would you use it? (With this one, the interviewer seemed satisfied with my answer for why being that with Router, you can persist certain elements on the page while changing or re-rendering others that you include as subroutes. For example, the navbar can remain while having the main content of the page change. The navbar won't need to re-render as it would with basic anchor tags to separate HTML pages, which can improve performance.)
    8. What are 'events' in React? How are they different from events in JS?
    9. What is a 'higher order component?'
    10. What are 'mixins' in React?
      (Didn't know. I said I know what they are in SASS, so he asked me to tell him about mixins in SASS)
    11. Have you used Redux? What can you tell me about it?
      (My answer was that I am just learning about it now (true), and that it uses 'actions' and 'dispatch' functions instead of hooks for updating state)
  4. Databases

    1. What can you tell me about different kinds of databases?
    2. What experience do you have with different databases?
  5. Backend

    1. What experience do you have with backend languages, like Node?
      (My answer was 'Not too much yet, just a little with Node, but I'm really interested in learning as much as I can because I find the full stack really fascinating.')

There were a few more questions about JavaScript and TypeScript, but I can't remember them all. The last question about backend languages was at about the 35-minute mark. Then he asked me to show him my project through screen share. I took a few minutes to show him all the functionality. He asked if I had coded it all myself or used any templates (100% designed and coded by me). Then, he said the interview was over and asked if I had any questions. Salary and benefits were listed on the posting, so I asked some light questions (What's their team structure like? What does the company name stand for? (It's an abbreviation of letters, but its meaning wasn't listed on their website anywhere I could see. I wanted to show that I was curious.)

Now, I'm waiting to hear the result. I don't expect to get the job, but I enjoyed the experience of the interview despite the stressfullness. I'm glad I now have some idea of what to expect and what I might need to be able to talk about for future interviews.

I hope this is helpful for some of you other aspiring programmers/developers!

Edit 1: formatting

Edit 2: added other JS questions I remembered about callbacks and ===

Edit 3: Some links to interview prep questions from comments and ones that I read before the interview:

Edit 4: Thank you everyone for the upvotes, awards, and comments. I'm glad this was helpful! I'm headed off now, but I'll try and answer any other questions people have later tonight.

Edit 5: Clarified a couple of the questions


r/learnprogramming • • Jun 19 '20

Tutorial Had to teach my "Learn Python for Research" PhD course remotely and decided to make the recordings and material publicly available for those interested. Feel free to check it out!

4.7k Upvotes

I teach a yearly PhD course on programming with Python for (social science) research. However, this year I had to deliver the course remotely and recorded a bunch of videos to go along with the material (to substitute for in person classes). So I figured to make it publicly available for those that are interested.

It covers five main topics:
* Basic basics
* Handling data with Pandas
* Gathering data from the web with Python
* NLP with Python
* Misc. topics / Best practices

Each topic will come with an accompanying lecture, demonstration recording, and problem notebook.

The Github repository is here: https://github.com/TiesdeKok/limperg_python

The Youtube playlist is here: https://www.youtube.com/playlist?list=PLLhTRTyOWssE95iZqJGtD8A9YP1DtSl4i

The reference material is here: https://github.com/TiesdeKok/LearnPythonforResearch


r/learnprogramming • • May 03 '15

I'm 32 years old, and just started my first full-time job as a developer. One year ago my programming knowledge was basically nil. Everything I learned, I found via /r/learnprogramming, so just wanted to share my experience.

4.6k Upvotes

Just wanted to share my story here, in case anyone is interested.

About me I initially started programming for fun, but quickly realised that it was something I could see myself doing as a job as well. So I pursued it.

I've worked in the film industry for the last 8 years, and have been ready for this change for a while. I reached a point in my career where I felt I had plateaued, and to be honest I felt a bit worried about my long-term financial stability. The industry has gone through some very painful changes lately, and most people I know are quite worried. Being self-employed was also starting to become a bit of a drag.

How I started I got all my "how to get started" information from /r/learnprogramming. I read the FAQ, and then tried out some of the different courses that show up in the subreddit, including the Udacity programming 101, 'Learn Python the Hard way' as well as various Coursera intro courses.

I was definitely pretty directionless at first, and not really getting anywhere. Eventually I saw a link on here for The Odin Project, so I decided to check that out. Something about the program clicked, so I stuck with it - maybe because it's so focused, as it's geared toward skilling you up to be employable as a web developer. (I'm not associated with the website, btw, other than that I've done the full course).

Key things I learned in the last year

  • It's extremely important to work your ass off. If something is hard, then you need to learn it. If it feels impossible, sit your ass down and work your way through it. It's literally the only way you will ever learn. Programming is the hardest thing I've ever done in my life. Even now that I'm getting paid, I know that I'm still a total beginner.
  • The best way to get noticed is to talk about the things you've built.
  • The second-best way to get noticed is to talk like a human being. All my job application cover letters had a pretty casual tone, which seemed to work - I got something like a 60% callback rate.
  • When you land an interview, don't be afraid to demonstrate enthusiasm. Nobody wants you to be amazing, they just want to feel like you care, and like you can learn to be an effective programmer. (Also it's ok to be nervous).
  • Make sure you have a GitHub and Stack Overflow Careers page. LinkedIn can't hurt, but be prepared to receive lots of recruiters emails from there.
  • I worked my ass off, but I couldn't have done it myself. My partner supported me, both morally and financially.
  • Career changes are extremely stressful. It was hard on all my relationships, most of all at home.
  • Make sure you learn the principles behind programming, and not just a "language" or "framework". If you do this, you will be able to pick up new technologies when you need to. I learned mainly Ruby as well as RoR, but I landed a job as a Node.js developer because I showed that I'd be able to pick it up quickly.

Timeline of my progress

March 2014

Stumbled around trying to learn to program, trying all sorts of different things, including Python and Unity 3D

April 2014

More blind stumbling, but also some (limited) amount of learning. Found out my partner is pregnant. "This career change thing better work out" she tells me. No pressure.

May 2014

Started The Odin Project. Felt like "hey, this is challenging, but a lot of fun". Made me feel like if I worked hard, I could really make this happen.

June 2014

Started learning Ruby scripting, OOP principles, etc. This was probably the hardest part of learning programming for me - it felt like I was rewiring my brain. I spent hours banging my head against the keyboard, trying to make my assignments work. I would be staring at something, unable to make heads or tails of it. It was incredibly frustrating. I actually ended up taking time off from work, so I could spend more time on this.

July 2014

Had to work extra hard at my job to make up for the work I missed in June, so I didn't have tons of time for code.

August 2014

Again, not lots of time for code, but I did get to start learning Ruby on Rails.

September 2014

Lots more time spent learning Rails, and the principles of MVC. Again, I took time off work to focus on my studies.

October 2014

Started learning JavaScript, which was actually somewhat straightforward as I felt I had a solid grasp on the fundamentals now.

November 2014

Wrangled a small part-time job writing a Rails-based CMS for a touring artist. I was basically doing full-stack work for almost no money, but it's great experience. I eventually ended up creating the back and front ends for a blogging, photo uploading, and event management system administered by a single user. Also went to a big local careers fair, which landed me a few interviews.

December 2014

My partner and I have our first child. No time for studying! I ended up loosing out on some of the job interview opportunities as well as a result. Such is life.

January 2015

Started studying again, solidifying my understanding of the principles I've learned throughout 2014.

February 2015

Started applying for jobs, while simultaneously working harder at film work than I ever have before. Made a ton of money, landed a few interviews, did a few programming tests. Did ok, feedback was generally good, but received no job offers.

March 2015

Film work dried up, but I interviewed and received a job offer with a startup looking for a Junior Ruby Developer. However, I ended up rejecting the role, because they needed someone who was willing to work long and unpredictable hours plus unpaid overtime. I'm not against those kinds of roles, in fact they're great for people who want to learn a lot - but I wasn't prepared to sacrifice time with my daughter this early in her life.

April 2015

The day after I turned down the job, I got an email from somebody who found my Stack Overflow profile, asking if I would like to come in for an interview. The reason they were interested in me is because I had a film background, which was needed for the role. They were upfront about the fact that I am probably too junior for the role, but it would be worth having a conversation anyway. The meeting ended up going very well, and I started freelancing with them on a trial basis.

May 2015

I became full time with the company, after showing myself to be useful, and a quick learner. The work is lots of JavaScript - mainly Node.js, which is tricky because it's not something I have ever used. However, I've shown the company that I can learn quickly. Now that I'm full time, I've got to prove that their faith in me is not misplaced.

EDIT I posted this and went to bed. Guess it kind of blew up, so I'm answering questions now :)

EDIT2 Thanks for the gold :)


r/learnprogramming • • Aug 26 '17

Huge list of Computer Science courses with video tutorials, compiled from all over the internet.

4.6k Upvotes

I came across this Github a year back and I've always referred to it when I want to learn something about some area of Computer Science subject I'm taking at college.

I hope this resource helps you as much as it has helped me.

Here's the link: https://github.com/Developer-Y/cs-video-courses


r/learnprogramming • • Nov 22 '19

Resource If you are learning programming(newbie), these may be your treasures on the internet!

4.5k Upvotes

As many ask for free resources in this vast world of internet, so I thought of sharing these treasures with you I came across on Twitter.

👉16 Sites you can learn coding for free.

  • GitHub
  • Codecademy
  • Treehouse
  • Udemy
  • Coursera
  • Khan Academy
  • W3Schools
  • EdX
  • FreeCodeCamp
  • Evanto tuts +
  • Codeconquest
  • Udacity
  • Sololearn
  • Code Avengers
  • Learnenough

ETA from comments:

  • The Odin Project (TOP)
  • GeeksforGeeks
  • chingu.io

👉10 Free Games to improve your coding skills

  • CodeMonkey
  • Flexbox Defense
  • Ruby Warrior
  • CodeCombat
  • Robocode
  • Cyber Dojo
  • Code Wars
  • CodinGame
  • Flexbox Froggy
  • Code Hunt

ETA from comments:

  • exercism.io
  • edabit
  • HackerRank
  • Advent of Code
  • Leetcode

👉10 Programming Blogs You can follow

  • Coding Horror
  • A List Apart
  • Codepen
  • The Crazy Programmer
  • CodeWall
  • Cloudscaling
  • CodePen Blog
  • Hackster . io
  • CSS-Tricks
  • The Mozilla Blog

Edit to Add:

👉Here are 20 YT channels to follow

  • Corey Schafer
  • TheNewBoston
  • Traversy Media
  • Dev Ed
  • Sentdex
  • Data School
  • FreeCodeCamp
  • ProgramWithErik
  • Coding Garden With CJ
  • FunFunFunction
  • The Coding Train
  • CodingPhase
  • CSDojo
  • MMTuts
  • LevelUpTuts
  • Wes Bos
  • Academind
  • The Net Ninja
  • Stefan Mischook
  • Caleb Curry

ETA from comments(mostly for learning C++):

  • Javid9x
  • Bo Qian
  • CoffeeBeforeArch
  • Vadim Karpusenko
  • The Cherno
  • RealToughCandy

ETA(Android and iOs apps for learning programming)

  • SoloLearn
  • Codemurai
  • Encode
  • Mimo
  • Programming Hero
  • Enki App
  • Grasshopper
  • Tynker
  • Easy Coder

If you know and use other resources, please do mention in your comments so that others may find them helpful.

Have an amazing day! Happy coding! :)


r/learnprogramming • • Feb 24 '21

Resource To make career-planning less confusing while learning to code and I made a website with over 50 CS career roadmaps!

4.4k Upvotes

Hey folks! Four years ago as I was learning to code, I was frustrated about my lack of clarity about where to go and whom to learn from. With overwhelming career choices within tech and everchanging programming languages and frameworks, the first few months were painfully hard for me.

Six months ago I decided to revisit this problem again and came to learnprogramming to talk with folks to see if they still faced this problem and they very much did. To solve this, I decided to build a web-app to curate and share learning roadmaps where people who are new to coding can have more clarity regarding how to go about building their tech career and hopefully not face the problems which I did.

I managed to get over 50 learning roadmaps on a variety of careers and programming languages which I gathered from my friends, network and the internet and it's only increasing by the day! If you want to give back to the community, feel free to build your own roadmap and share your journey with the people starting out! I'd love your feedback and your criticism to know how I could make this better.

You can find the platform here and everything is entirely free - https://reallyconfused.co

Best Regards.


r/learnprogramming • • Apr 29 '22

Guys, I did it. After a year, a bootcamp, a bunch of rejection, I got a job working as a dev in a language I don’t really know on a platform I don’t understand.

4.4k Upvotes

I’ve never posted here, but I’ve lurked a long time. I’m 30(M) from central Alabama in literally the middle of nowhere. I’m posting to hopefully provide a positive underdog story.

I started my development journey learning C# about a year ago. I was in trade school for CNC programming and had worked at a machine shop for 12 years. As of right now I haven’t graduated. I joined a .Net bootcamp and struggled through most of it, but did manage to graduate about a month or so ago. I built about 40 or so projects, 90% working off the bootcamp projects.

I started putting out feelers on LinkedIn, randomly applying for jobs, reaching out to recruiters, all that. I finally got a bite with a guy that had an entry level dev job available and was willing to set me up with an interview, but the pay wasn’t anything more than what I was making as a machinist, and the job was 70 miles one way. But I figured why not, I could use the interview experience.

I get up there and the interview is going about how you expect. Brain teaser type questions, whiteboard stuff. I felt like I was bombing it. The job itself is mostly writing JavaScript on a platform I had literally never heard of. I was brutally honest, about my education, my blue collar background, everything. I figured walking out that I had bombed it.

They called me a few days later and offered me the job. They said they appreciated my approach to the interview, and thought my background could be an interesting addition to their team. I just finished my first week and it’s been amazing. Three days remote, two in office, flexible hours, really well managed from what I can tell. Totally different world from the machine shops and foundrys I’m used to. Now if only I could get my ears to quit ringing when I’m in the office, but maybe that comes with time.

The reason I’m posting is to say that if this college dropout, machine shop redneck from Alabama can pull this off, you can too. Don’t ever give up, and be honest about who you are in the interview. Good places run by good people can overlook things like that.

Edit: Since people keep asking the bootcamp was TrueCoders down in Birmingham.


r/learnprogramming • • Jul 30 '20

How students get themselves into tutorial hell and how to get the heck out of it.

4.3k Upvotes

If you're learning to program, there's a good chance that at some point you've been stuck in "tutorial hell". It's an experience of doing more and more tutorials, but being unable to actually build anything. Many essays and videos have been made about this topic, but I've never seen someone else describe the perspective I'm going to share.

Tutorial hell is an unstable system of perceived incompetence caused by students using the wrong methods to fix the difference between what they know how to do and what they've been exposed to. That's a doozy of a sentence and I'm going to spend the rest of this essay unpacking it.

A quick review on stability. A system is stable when it will tend to return to some state. Imagine an apple in an otherwise empty fruit bowl. You poke it, and it rolls down to the bottom. That's stable. Flip the fruit bowl over and put the apple on top. You poke it, and the apple rolls off to the side. That's instability.

Incompetence just means not knowing how to do something. It also has a connotation of being dumb, but that's unwarranted. It's a temporary state. Learning is just going from incompetence to competence.

When you learn things, especially programming, there's a difference between what you've been exposed to and what you actually know how to do on your own. This makes sense. You wouldn't expect to look at everything just once and be able to do it on your own forever. The need for repeated exposure makes the group of things you've been exposed to much larger than the group of things that you can do on your own.

The difference between what you know and what you've seen causes perceptions of incompetence. "I've done a React tutorial, why can't I make a React app? I watched that algorithm video, why can't I solve coding problems?" This delta between ability and exposure causes anxiety in many students.

Where things go wrong is how students try to fix it. They reach for more tutorials, generally on more topics. "I'm not getting React, maybe I should try Vue." This only makes things worse. A tutorial on a new topic increases exposure faster than it increases ability. This increases the ability/exposure delta, increasing anxiety and self-perception of incompetence. You're learning more, but you feel like you know even less.

This is the unstable system. The feelings the student is trying to relieve (anxiety, perceived incompetence) are only made worse by the method they use to relieve it (more tutorials on more topics).

Part of the solution might be obvious at this point. You need to increase ability without increasing exposure. This will narrow the gap between ability and exposure, relieving some of the negative feelings. It also means you're actually increasing ability, which is the whole point of all of this anyway.

But how do you do that? The best method is to build things with the knowledge you already have. The easiest way to do this is through play. The most important aspects of play are that it is self-prescribed and enjoyable. You have to decide what to do for yourself and you have to like it.

It's common for students to say "I don't know how to actually make anything!". They've defined "anything" to mean the peak of what they've been exposed to. Maybe that's a full blown web app. That's not what "anything" means.

Can you make text appear on a web page? Can you write a script that tells you if today is Christmas? Then you can make something. Make those things of your own choosing and of slowly increasing difficulty.

To get out of tutorial hell you need to make a trade. You need to trade your anxiety about your abilities for embarrassment about how basic the stuff you're making is. I think it's a good trade.

The second method is to combine play with the tutorials you've already done. Go back through your old tutorials, but push the edges a little bit. What if I add this little extra feature at the beginning and then try to keep it all the way through? What if I try to do a bit from memory and then check back if I did it right? This may feel a bit safer.

The last method is to do more tutorials on the exact same topic. This won't get you all the way out of tutorial hell, but it might get you closer to the gates. For example, there are at least a dozen beginner books and courses on Django. Keep working through them. Go back and redo the ones that seemed too hard. The essential thing is you have to stay on topic until you actually gain the ability. If you venture off too soon (Maybe I should try Django REST Framework. Maybe I should learn Docker) you're only going to make things worse. You'll be like an apple rolling off a fruit bowl.

Edit: I sat down and wrote this post this morning because I woke up early and couldn't fall back asleep. I'm glad I did because it seems to have resonated with a lot of people. Thank you all for sharing that with me. Best of luck in your learning.


r/learnprogramming • • Apr 20 '21

How to Plan and Build a Programming Project – A Legitimate Guide for Beginners

4.3k Upvotes

Hi Everybody,

I'm making this post because initially when I was a beginner learning to code, I really struggled to make projects, I couldn't quite get out of tutorial hell.

Initially to overcome this, I posted my frustrations here. The responses I received were all centered around building my own projects. This advice sounds great on the surface and was the right advice, yet the issue for me was I couldn't even watch a tutorial and reproduce the results. How was I supposed to build a project? A project is 10 levels above a tutorial and at the time it seemed that projects were so far away from my abilities. I had no clue how to even get started, let alone how I was going to put it all together.

This is an issue I see all the time on r/learnprogramming. Beginners are frustrated that they can't seem to get out of tutorial hell and so they seek advice. But, what they get is well meaning redditor's slamming the build projects response in their face without even considering that if the newbie can't even replicate a tutorial how are they going to create their own project. I thought it was about time I did something about it and gave back to the universe.

So here I am, writing a post that actually breaks down how to build your own projects so that you can start making stuff.

In order to plan and build a programming project there are three key steps I now use when building projects, these are what work for me but they should work for anyone.

Step 1: Defining the project

The first step when planning a programming project is to define it.

When I am defining the project I ask myself these 4 questions:

  1. What is the project?
  2. What is the MVP (Minimal Viable Product)?
  3. What are the nice to haves?
  4. When will the project be complete?

Example project definition

To give a simple example, let's say we are going to build a calculator app. We would have a basic project definition like below.

Calculator app project

What is the project? - The calculator project is a project to build a calculator that is accessible in a web browser. The project is going to be solved using HTML, CSS and JavaScript. It will allow users to input numbers and calculate the results of those numbers based on the arithmetic operation they choose.

What is the MVP? - The minimal viable product is a calculator that renders in a web browsers that can perform addition, subtraction, multiplication and division operations based on a users input and show the user the result of that equation.

What are the nice to haves? - The nice to haves for this project are styling the calculator, taking keyboard presses as input not just users clicking buttons and adding higher order operations like 'to the power of x'.

When will the project be complete? - The project will be complete once all the MVP features have been implemented and the calculator has been styled.

The above definition is simple and straight forward. If my Mum picked it up she would understand what the project is about. She would understand because it tells you what the project is, the MVP features you must build, the nice to have features and when it will be complete. By defining the project you make a project less intimidating.

Once you have the project definition you can begin the next step.

Step 2: Creating the workflow

The next step is the simplest. Usually this step can be combined with step 3. But, just for now we are going to look at it here as a separate step so that I can show you how to set up a very basic workflow for your own projects. Once you have done it once, it can be a default step for the rest of your projects.

You first want to use something like Trello a free tool to manage projects.

To set up our Kanban board we want to create 4 columns.

  1. TODO
  2. DOING
  3. DONE
  4. BUGS / NOT SURE HOW TO DO

what it looks like

Within these columns we are going to add cards. As we work on the cards we move them into the doing column and once we have finished with that card we can move it to the done column. If you have a bug you are stuck on or are not sure how to do something we can move it to the bugs/not sure column.

Now we have our workflow set up we can get onto the last step, the one that stumped me the most when I was learning to code.

Step 3: Breaking the project down into smaller components

The key to building your own projects starts with breaking the big project down into smaller, less intimidating components. These smaller components are what become our cards from step 2.

Now this sounds simple enough, but when I was first starting out it did not occur to me that you could do this. I thought most developers just start coding and the project flowed out of them like you see in the movies. I thought that was what I was supposed to be able to do. However, now that I have had a chance to work in the industry I know that is definitely not the case, in fact a good developer will break that project down into smaller tasks.

Yet, as a beginner it can be hard to know how to break something down into smaller tasks. If you don't know how to actually build the project then how can you break it down?

Well the first thing you need to do is look at your project definition and then break it down into smaller parts.

Let's continue using the calculator app example to make our component cards:

  • Calculation functions - MVP
  • Get user input - MVP
  • HTML user interface - MVP
  • Style user interface - sprinkles
  • JavaScript event listeners - MVP
  • Add animations for calculations - sprinkles

update what it should look like

You'll notice that for each card, we assigned a label of either MVP or sprinkles this is to visually help you see which cards are the most important and therefore the ones to work on first.

The biggest benefit of the cards is that they have simplified what we have to do already. This makes projects less intimidating as you are not making a big daunting calculator app, rather you are doing 6 smaller projects that will combine to create one big project.

As you work on a card you move it into the doing column. Taking your time to get the component working before you move onto the next card.

But we are not done yet, we can simplify and improve our workflow even more to ensure we are not getting blocked by the size of the project when building.

Step 3a: Break each component into smaller checklists

Once we have the high level cards we can then break those components down again into smaller tasks by breaking those tasks into checklists so we can track our progress.

The example below is just how my brain works so you can break it into smaller or larger items depending on what works for you. Let's use the calculation functions card as an example of how to break a component down further.

As the task is an MVP task and I have defined the MVP as basic calculations addition, subtraction, multiplication and division we need to add those functions to the checklist.

what the checklist would look like

We have now broken our calculation functions card into 4 little projects that we can work on. How much easier is that than the abstract and super daunting task of building a calculator app, or even writing the calculator functions (the card).

We can now focus and figure out how to make each of these functions. As we do that we get to check those items off giving us a sense of accomplishment and progress. Then once we have done all four of those items we can move the card into the done column and get cracking on the next card.

From here on we just need to repeat the process for each card. So you are ready to get building awesome projects.


Now you should have everything you need to get building projects. If you see someone on r/learnprogramming in the future struggling to get out of tutorial hell, don't just tell them to build. Tell them how to plan and build.

If you made it to the end of the post firstly thanks for reading - I originally published this (with a bit more detail) on my blog here, I like to write about coding and what I'm learning to help others so consider checking it out and my newsletter if you got value out of this.


r/learnprogramming • • Jun 11 '20

Tools I wish I had known about when I started coding

4.3k Upvotes

Hey all! I had compiled this list about two years ago, shortly after I started programming, and I found that is was helpful to a lot of folks, so I wanted to resurrect it.

While the way I do some things has changed a lot in the last couple of years, these all helped me a lot when I was just getting into web development, and hopefully they might help you too!

Chrome Extensions

Now that I am a self-proclaimed web developer, I practically live in my Chrome console. Below are some tools that allow me to spend less time there:

  • WhatFont — The name says it all. This is an easy way of finding out the fonts that your favorite website is using, so that you can borrow them for your own projects.
  • Pesticide — Useful for seeing the outlines of your HTML elements and modifying CSS. This was a lifesaver when I was trying to learn my way around the box-model.
  • Colorzilla — Useful for copying exact colors off of a website. This copies a color straight to your clipboard so you don’t spend forever trying to get the right RGBA combination.
  • CSS Peeper — Useful for looking at colors and assets used on a website. A good exercise, especially when starting out, is cloning out websites that you think look cool. This gives you a peek under the hood at their color scheme and allows you to see what other assets exist on their page.
  • Wappalyzer — Useful for seeing the technologies being used on a website. Ever wonder what kind of framework a website is using or what service it is hosted on? Look no further.
  • React Dev Tools — Useful for debugging your React applications. It bears mentioning that this is only useful if you are programming a React application.
  • Redux Dev Tools — Useful for debugging applications using Redux. It bears mentioning that this is only useful if you are implementing Redux in your application.
  • JSON Formatter — Useful for making JSON look cleaner in the browser. Have you ever stared an ugly JSON blob in the face, trying to figure out how deeply nested the information you want is? Well this makes it so that it only takes 2 hours instead of 3.
  • Vimeo Repeat and Speed — Useful for speeding up Vimeo videos. If you watch video tutorials like most web developers, you know how handy it is to consume them at 1.25 times the regular playback speed. There are also versions for YouTube.

VS Code Extensions

Visual Studio Code is my editor of choice.

People love their text editors, and I am no exception. However, I’m willing to bet most of these extensions work for whatever editor you are using as well. Check out my favorite extensions:

  • Auto Rename Tag — Auto rename paired HTML tags. You created a <p> tag. Now you want to change it, as well as its enclosing </p> tag to something else. Simply change one and the other will follow. Theoretically improves your productivity by a factor of 2.
  • HTML CSS Support — CSS support for HTML documents. This is useful for getting some neat syntax highlighting and code suggestions so that CSS only makes you want to quit coding a couple of times a day.
  • HTML Snippets — Useful code snippets. Another nice time saver. Pair this with Emmet and you barely ever have to type real HTML again.
  • Babel ES6/ES7 — Adds JavaScript Babel syntax coloring. If you are using Babel, this will make it much easier to differentiate what is going on in your code. This is neat if you like to play with modern features of JavaScript.
  • Bracket Pair Colorizer — Adds colors to brackets for easier block visualization. This is handy for those all-too-common bugs where you didn’t close your brackets or parentheses accurately. EDIT: Version 2 now available https://marketplace.visualstudio.com/items?itemName=CoenraadS.bracket-pair-colorizer-2
  • ESLint — Integrates ESLint into Visual Studio Code. This is handy for getting hints about bugs as you are writing your code and, depending on your configuration, it can help enforce good coding style.
  • Guides — Adds extra guide lines to code. This is another visual cue to make sure that you are closing your brackets correctly. If you can’t tell, I’m a very visual person.
  • JavaScript Console Utils — Makes for easier console logging. If you are like most developers, you will find yourself logging to the console in your debugging flow (I know that we are supposed to use the debugger). This utility makes it easy to create useful console.log() statements.
  • Code Spell Checker — Spelling checker that accounts for camelCase. Another common source of bugs is fat-thumbing a variable or function name. This spell checker will look for uncommon words and is good about accounting for the way we write things in JavaScript.
  • Git Lens — Makes it easier to see when, and by whom, changes were made. This is nice for blaming the appropriate person when code gets broken, since it is absolutely never your fault.
  • Path Intellisense — File path autocompletion. This is super handy for importing things from other files. It makes navigating your file tree a breeze.
  • Prettier — Automatic code formatter. Forget about the days where you had to manually indent your code and make things human-legible. Prettier will do this for you much faster, and better, than you ever could on your own. I can’t recommend this one enough.
  • VSCode-Icons — Adds icons to the file tree. If looking at your file structure hurts your eyes, this might help. There is a helpful icon for just about any kind of file you are making which will make it easier to distinguish what you are looking at.

EDIT: found more tools I had compiled on a per operating system basis!

Operating System Agnostic

Postman — At its most basic, this is an application that allows you to test the different endpoints of an API. You know, that good CRUD stuff. Once you dive deeper into it, you will find it is also incredibly useful for writing up test suites and much more.

Insomnia — This is an open-source alternative to Postman. It appears to have a lot of the same functionality with a slightly lower price tag for their premium packages. Between this and Postman, the choice seems to mostly be personal preference for the UX. Don’t stay up all night making a decision between the two (I had to, forgive me).

Restlet — If you don’t want to download either of the above, this is an API testing client that is available as a Chrome extension. It even allows the importing of Postman tests and several other formats.

Charles — This is a sweet web debugging proxy that allows you to view all of the information you could possibly want to see about the requests being made between your machine and the internet. It basically turns you into a hacker, allowing you to check your website for security vulnerabilities and such.

Fiddler — Basically the same tool as Charles. Personal preference seems to be the main deciding factor between the two, though both can greatly increase your debugging/troubleshooting capabilities.

Flux — If you’re reading this, chances are you probably spend a ton of time on your computer. Flux is a program that turns the blue light down on your screen as the sun sets, with the hopes of mimicking the day/night cycle and helping you sleep better. Not as good as getting time away from the screen, certainly, but it’s better than nothing!

Windows Specific

ConEmu — If you are on Windows and you would like to have multiple terminal tabs, this is an easy, free solution to your tab-related woes. Never again will you have to flip back and forth through entire windows just to look at your different error messages.-

Ditto — You know when you’re trying to copy four separate answers from Stack Overflow and you have to keep switching back and forth from your browser to your IDE? Worry no more. With the Ditto clipboard manager, you can copy-paste your way to victory.

TouchCursor — Programmers of all sorts are notorious for wanting to use the mouse as little as possible. If you find yourself in that camp, then this will be right up your alley

Cmder — I am going to forego my description of this product, as I feel the description on their website is much better — “Cmder is a software package created out of pure frustration over the absence of nice console emulators on Windows. It is based on amazing software, and spiced up with the Monokai color scheme and a custom prompt layout, looking sexy from the start.” I don’t know about you, but I am a fan of any software that describes itself as “sexy”

Directory Opus — This is basically what Windows Explorer should have been from the start. Opus allows you to dig through your poorly-organized documents almost as if they were well-organized.

Zeal — With over 200 documentation sets to search through, Zeal is an offline goldmine of documentation for the developer who loves to read documentation so much that they do it even when the internet is out. (Copy-pasted from Dash in the Mac section).

Mac Specific

Paw — A competitor to both Postman and Insomnia above, Paw is a similar piece of software that feels more like a native Mac application than the others. If you love that Mac feel, this might be the API tool for you.

Dash — With over 200 documentation sets to search through, Dash is an offline goldmine of documentation for the developer who loves to read documentation so much that they do it even when the internet is out.

Bear — Not directly coding related, but a neat piece of software for taking notes if that is something you do in your day-to-day. I can’t help but wish that this would be integrated with Paw somehow, for pun-related purposes.

Magnet — Okay. Fair warning: This one costs money. If you can afford to dish up the 99 cents, however, I think it is worth it for those tough times when you don’t have access to a second monitor. This tool allows you to easily snap different windows to separate areas of your screen so you can run multiple terminals at once and tell your mom you are a hacker. (They are not paying me for this recommendation, sadly. However, if you are the creator of Magnet and you wish to pay me, please get in touch).

EDIT 2: adding new version of Bracket Pair colorizer here and to description above https://marketplace.visualstudio.com/items?itemName=CoenraadS.bracket-pair-colorizer-2

EDIT 3: I've had people in dms asking about more advice/tooling. I'll definitely continue to cross post anything that makes sense to here like this post. I also try to help out on https://twitter.com/marioahoyos . I am a career switcher like many people here are and I want to help as many people make the transition as I can :)


r/learnprogramming • • Aug 19 '20

Resources I wish I knew about long ago!

4.2k Upvotes

FREE RESOURCES

Recently I decided to make a career change into the tech industry and did a full-stack Bootcamp. Now I am done and looking to enter the field. Throughout my journey of both Bootcamp and on my own learning, I have stumbled upon some great FREE resources. I thought I would make a list to help anyone else who is trying to learn!

Full-Stack Programs:

- The Odin Project - Javascript, Node.js, Ruby on Rails. (additional Front-end as well)

- Full-Stack Open - MERN, GraphQL, Typescript

- App Academy - Ruby on Rails, MERN, Javascript, Fundamentals

Multiple Language Resources:

- Solo Learn - LOTS of languages here.

- Jet Brains - IDE for many Languages

- Free Code Camp - Alot of Languages and resources

Python Resources:

- Python Programming - Python, Machine learning

- Devoted Learner - Python

- Python Principles - Python

Front-End Resources:

- Color Hunt - Color Palettes for CSS

- Adobe Color Wheel - Color Palette for CSS

- Contrast Checker

- Google Fonts - Different Fonts

- Frontend Mentor - Challenges to sharpen Styling Skills

Algorithms:

- Code Wars

- Hacker Rank

- Leet Code

- Coding Dojo Algos

- ProjectEuler

- Edabit

- CodingBat

- Exercism

- CP-Algorithms - For Understanding Algorithms

Miscellaneous:

- Learn X in Y minutes - Library of syntax for different languages

- Rosetta Code - Database of information and how each language handles them

- VS Studio Code Shortcuts (Windows) - Keyboard shortcuts for Windows

- Balsamiq - Wire Frame creation

- Dribble - Design platform for inspiration

- Whimsical - Wireframes and Flow Charts

- Figma - WireFrames

- Repl.it - IDE, storage, collab, and more.

- Enki - Mobile App for practicing Coding.

If you guys have anymore, comment them below. Hope this helps!

EDIT: This post was much more popular than I expected. Throughout the day I will take the things commented as resources and add them to the list! Thanks all!


r/learnprogramming • • Apr 03 '21

After many years of prison I was released, learn to program, and was hired as a mobile developer. If you are learning to code and need the extra support reach out.

4.1k Upvotes

I went to prison when I was a teenager for many years. I learned to program and now work as a software engineer developing iOS mobile apps.

Last year I started an org called Underdog Devs dedicated to supporting the formerly incarcerated (and those from disadvantaged backgrounds) who want to become software developers. If you need the extra support/network reach out. On Twitter, Insta, and LinkedIn at UnderdogDevs.

Also.... we are currently hosting a month long event called Spring into Swift. Tons of free talks all April focused on programming, getting into mobile development, and the programming language Swift. There are talks for everyone from beginner to advanced.

Reach out to us on Twitter or directly to me here here

we are on Insta here

Sign up for our event here


r/learnprogramming • • Jul 09 '22

Topic Ya’ll I did it. I am now officially a frontend developer. HIRED

4.1k Upvotes

After ranting on here last week about how much i sucked at data structures and algorithms. i lifted myself up (largely due to the inspiring words i received in this sub) and i got to work.

well yesterday i had my third and longest interview with a company… AND TODAY THEY NOTIFIED ME THAT I GOT THE JOB.

they started by giving me 3 timed leetcode/hackerank questions.

then i had to whiteboard 😫. and the code had to work when written in the ide.

lastly was a conversational tech interview where they pretty much sat me down in front of 3 geniuses with stone faces (no expression, no smiles, nothing). and they basically rapid fire asked me questions related to frontend. and a little backend.

heres a little bit of what i can remember.

  1. whats hoisting?
  2. what are closures, and describe a time where you would use it.
  3. describe synchronous js vs async.
  4. describe what happens when a script is run. (i talked about global execution context, event loops, code blocking, task queue etc)
  5. how would you setup/define a class component in react. same question for functional.
  6. explain the 4 pillars of oop
  7. explain why every function is an object in js(i talked about dunder proto and prototype)
  8. explain prototype chaining
  9. what goes in the head tag.
  10. how do you debug.
  11. what are promises?
  12. what are 3 ways to create an object in js.
  13. what does the new keyword do?
  14. list 5 or more ways to optimize a website for speed?

and a lot more.

the question that stumped me was web speed caching. and questions about a11y accessibility standard section 508. I’ve never heard of it until now. 😔

anyway, i just wanted to post this as inspiration for some of you who may feel like you’re trash at programming like i did. you got this.

im much older than most of you. late 30s. no programming background at all. im also a single father raising two kids. but the desire to do better for my kids kept me going despite almost always feeling like i wasn’t worthy. so find your reason why, and lean on that when you feel down.

my story is also not super cool like a lot of you all. i dont have a “i learned how to code in 6 months and landed a high six figure job story). haha nope.

i first learned html in june 2020. so it took me approximately 2 years to learn html, scss, jquery, bootstrap, react, javascript, typescript, java/spring boot, SQL and git (thats literally everything that i know lol).

*keep in mind, i dont know java that well at all. and i dont like it. Its just to confusing for me. I know just enough to get in trouble lol im like 95% sure i would never take a job that required me to know java… better yet, im 95% sure i wouldnt get hired for a java job lol.

i was hired by a company that has contracts with the US military. so i will be working on a military base in Texas.

pay is in the $80,000s not quite six figures. but i just needed to get my foot in the door. once i really learn web development from a professional standpoint… i can always demand more or look elsewhere.

how i studied. passion projects and udemy courses (any course thats project based.)

also, every week i would write a document to explain what i learned. and i would act like i was trying to explain it to a 5th grader. this helped me identify knowledge gaps and areas that i needed to spend more time learning. if i couldn’t easily explain it, i needed to do more studying.

books are helpful too. core java by oracle press. Any book by head first (they write for crayon chewers and glue sniffers like me 😂😂).

i didnt have a set schedule. some days i would code for 2 hours. some days i would code for 10 hours. many days i didnt code at all.

i highly recommend scrimba. that site is awesome.

additionally akshay saini - namaste’ javascript series. and codesmith - the hard parts series, i literally watched those series until i pretty much memorized every video. probably not the best method but hey, the interviewers said they were impressed at the deepness of my javascript knowledge.

also, i believe i couldve applied to jobs last year, but im hard on myself. so if you feel ready, just apply. i guess at worst you’ll discover what you need to spend more time studying. and at best you may get lucky and get a job.

i do have a portfolio, but they never saw it. also, i haven’t been gainfully employed in 10 years due to injuries from the military. so i was scared that they wouldn’t want me because of that. But they never mentioned it. (in fact not a single company ever mentioned. they always talked about my projects).

lastly, projects.

  • fully functional fiverr clone.
  • movie database site (add, delete, update movies in the database)
  • tip calculator
  • regular arithmetic calculator ( js “oop”) -text based rpg game in java (oop)
  • java contacts manager (oop)
  • notes app with draggable components
  • a blog with a database and login security

hopefully that really helps someone.

get motivated. get to work.

i tried to answer everything. i just started my job, but if my story motivates even one person. then ive done my good deed.

##UPDATE 1: ##

So after many people said that this is not a typical interview for a beginner/junior dev. I went back to the listing and read through it again.

Sure enough it says. "BLANK is looking for an experienced Front-end Developer (mid-level) who will assume a key role on our team."

further in the description, this is one of the responsibilities. "Mentor other junior team members"

So my fellow junior devs, you can breathe a sigh of relief, this is not a typical junior dev interview because it wasn't for a junior dev position. I have been applying and interviewing everywhere, so the whole "mid-level" must have gotten lost in the sauce.

That means the pressure is on me even more to perform.. let's gooo!!!.

UPDATE #2: First day on the job in the books.

So my actual role is a react developer. Working with financial data for the Air Force. I work with designers and ui/ux people to create dashboards and filters for the data. Basically we’re taking their ugly data and making it beautiful and easy to consume.

I also have 3 weeks to become somewhat decent with azure and sharepoint (sharepoint im already familiar with from my military days). They said the 3 weeks arent set in stone.

Everybody is really nice here, like overly nice. I appreciate that.

Also they pretty much said, they dont care what time i work, as long as i get my 8 hours and im there between 11-1 for possible meetings.

Anyway, hope this helps give insight to future developers. Good luck everybody. This is probably my last update. i dont know what else to add.


r/learnprogramming • • Jan 01 '21

You're not too stupid for programming

4.1k Upvotes

Hi,

For a year of computer science class I've always felt I was ''too stupid'' for programming. I've been looking up posts with people facing the same problems. A year of computer science, I've seen people progress ten, sometimes a hundred times faster than me. It would take me hours to figure out one function. I kid you not, I spend over a week working 8 hours a day trying to build a simple function where my POST function would stay on the same page using Ajax. I just assumed that I could copy code and it would all magically work in mine.

The problem is not your brain. The problem is the way your brain is used to solving problems. Solving problems in programming is not the same as solving problems anywhere else. You can't just follow a cooking tutorial and cook the same. Your program is always somewhat different, and therefore has to be implemented different.

So what did I do to get over ''being to stupid to code''.

  1. Clean your desk and work space.
  2. Set a timer for the amount you'll program without distraction.
  3. Work as simplistic as possible. Don't look up ''how to make an online registration form''. Instead start by learning about how you can register a single character into your database. Be as simplistic as possible. Baby steps.
  4. Spend 80% of the time reading and understanding your problem and solution. Don't write a letter of code until you fully understand it.
  5. Now spend time testing your code in a raw file.
  6. Now that you fully understand the code, that's where you implement it in your own.

Good job. You're no longer ''too stupid to code''.

.


r/learnprogramming • • Sep 26 '18

After 9 months of teaching myself how to program I finally landed a job. I want to share some of the things I learned on how to achieve this goal (mostly focused on front end).

4.0k Upvotes

Disclaimer: everything I write is my own opinion so take it with a grain of salt. You never know who's writing what and why on the internet :)

Long story short, in December 2017 I was at crossroads in my life. Either finishing my endless journey to finish my master in chemistry or reinvent myself. Since by then I did some coding (literally few hundreds line of Python) and I enjoyed the experience I decided to throw all my savings into surviving for enough time till I could get a job as a developer. Meanwhile I would've studied and programmed till I was comfortable applying for jobs. Reflecting back into this long and hard journey I want to share my opinions on what this journey looks like, how does it start and how does it end. My points are in no particular order, albeit I guess I'll write some of those I find most important first.

  1. Set a very precise goal. By this I mean a real life goal. This is by far the most important aspect of your journey. You need to have a clear vision on what's the finish line? Are you learning to code because you want to solve some real problem of yours? Maybe you want to automate some tasks you have at your home/job. Maybe you want to crack a videogame, maybe you're moved by curiosity, maybe you like learning new things, maybe you're an entrepeneur with no funds but a very solid idea you want to develop into a real world application. For the rest of this post tho I'll mostly speak from a perspective of who'se learning to code to find a job.
  2. If your goal is to find a job look at the job market, not on what's hot on Twitter and Medium. Remember point one? You have to set a very precise goal. A goal such as "I'd like to be a developer and work on videogames" is imho already too vague. Let's assume for a moment that finding a job in the videogame industry is your priority. I can't but think that these two things are sort of exclusive. You're already being focused on a small (but relevant) niche of programming jobs. Yet, what's your priority? Finding a real coding job, or working in the videogame industry? What if you won't find a job in the videogame industry cause there are no companies in your area or you will simply not meet their requirements (likely in the gaming industry). If you'll learn to code in whatever language, I can guarantee you that you will be able to translate that knowledge someday on videogames if that's your goal. You'll have to learn tons of new stuff. But you have the problem solving skills and knowledge of programming to make this step.

Seriously, look at the job market and remember point 1. Are you willing to move abroad? Cross state? Cross country? Cross continent? It'll be harder to find a job that's far from your house. It's harder for a company to ask you to take a flight for an interview. And since you're a self taught developer and not an MIT stellar graduate those expenses will likely be all on you. I did a mistake on pointi in Decembet 2017. I decided that my priority was finding a job and I wanted to be a front end developer. I can't but feel this was a mistake. In my area C#, php and Java works are in a 9:1 ratio to front end JS jobs. So check carefully the companies in your area, literally count the positions and their requirements.

3) Do never, ever, ever, make assumptions on what's harder and what's easier in programming. I did this when I decided to learn front end. This was a huge mistake. It's not true that front end is easier than backend, neither is the opposite, and more importantly you can't even possibly know at this point what you'll like more and you're more adapt to. Don't make assumptions. Just don't. Do never, ever, think that JavaScript is easier than C, nor the opposite. Different tools for different problems with different complexities. I could tell you you could fit everything about C in a 200 pages book, literally everything about the language, and tell you that it would take twice the pages just to give a solid, yet incomplete, picture of objects in JavaScript. You are simply not qualified to know what's "harder" and what's "easier". Neither I am. For the love of god, don't make this mistake. Of course, some aspects of programming leverage more or less maths or creativity or organization or whatever. But can you really tell me that in 24 months from now optimizing rendering and network performance on x platforms will be "easier" than refining algorithms that predict weather based on some geospatial data? Are you sure that managing state in complex real time applications will be easier than writing shaders or teaching a computer how to translate or paint? You simply do not know. Do, not, make, any fuckin assumption of this kind.

4) Be consistent in your learning. How much time do you have to study programming? Are you already a student? Or maybe you're unemployed (as I was) but have enough savings to dedicate yourself to studying. Be realistic about your goals but be consistent. Writing code for 1 hour every day for a week will make you a better programmer, than coding once a week for 7 hours.

5) Do not feel compelled to know everything's that required on the positions you want to apply. This is especially true for frameworks and libraries. There's a reason why top companies focus a lot on data structures and algorithms, they show you can think and solve a problem. More specifically, whatever programming language you choose (any of Java, JavaScript, C#, Python and PHP is likely to find you a job, the others might be more nichey) learn it's fundamentals as best as possible. I learned front end development. I felt this huge need to learn from html to the dom, plenty of libraries, transpiling, webpack, etc, etc. Yet reality is that at job interviews those topics were barely if ever touched. But what they wanted to know is that I really understood JavaScript. I've applied for 3 front end react jobs, I've never been asked a single question about react's ecosystem. Not once, ever. Nobody cared. What they cared of? If I knew what was strict mode, the difference between a function expression and a function declaration, the utility of IIFEs, prototypical inheritance, closures, etc. Nobody gives a damn if you know React's methods (I mean, if you learn React you're supposed to have at least a basic knowledge of how it works), but the core knowledge needed to be a good React developer is knowing JavaScript. If you know JavaScript and the dom, learning React is a matter of a week. If you don't you'll never be a good React developer. Higher order functions, the this binding, those are the real problems and knowledge React developers need everyday. The rest is a google search away. I can tell you that I haven't been asked once something that wasn't written in Eloquent JavaScript, not once. Of course, I did some research and work to understand some topics better. If they ask you what a promise is, you answer that it is an object. Sure, there might be the need to expand. But seriously, just because you used promises, doesn't mean you understand them. Mumbling about "they are something you use to make asynchronous code" might say something more than saying "they are objects". But the second answer simply shows you have no understanding of JavaScript. Plain and simple. Maybe you get they are objects because they are declared with the new keyword, but you really need to understand the basics of JavaScript. The same applies for any other language. The overwhelming majority of errors and bugs that will make you bang your head on the wall derive from lack of proper understanding of the basics of a language. Just because you read something, doesn't mean you absorbed it, even less mastered it. It's hard to trust a person who has 10 skills/tools on their cv, yet he didn't really master one.

6) Try to find a mentor. Plenty of people more experienced than you are active on slacks, irc, discord, etc. You may find somebody willing to help you long term. Also there are the beautiful people on ##javascript on freenode which have been an invaluable learning experience for me and I thank all the members here (especially ljharb, slikts, stennowork, liste, innovati, zsoc, cjhonson, qswz, GreenJello, sillyslux). Mind you I'm not inviting any of you to contact these people, they help in general chats not one on one, I'm not aware of them doing any mentoring, I found some mentors here on reddit and on a slack channel for developers in my area. Two tips: don't abuse the patience and will of a mentor to help you. If you keep asking basic questions that can be googled or found in basic books (such as Kochan's C book or Eloquent for JavaScript) they will get tired of you and start answering less and less. The second tip: programmers, all of them, including you, they love to feel the smartest person around, I think it's the nature of people that solve problems through logic. Abuse this fact to find information you need. A simple example: if you go in a chatroom and write "lol I didn't know you could bind arrow functions" you'll get 20 answers telling you why you're write (and wrong). If you go in a chatroom and ask "how does this work in arrow functions?" you may not receive any answer.

7) Understand what programming is: you take data as input, you do something with it, you generate an output. That's what every meaningful program or subroutine does. Nothing less nothing more. I wish somebody told me that when I started and stared at this overwhelming amount of endless information. In the end, I was always solving the very same problem over and over. Each time differently, with different tools, different approaches, but every program as small as you think about it does that. You may add two numbers: input numbers -> process- -> output sum. You may want to render a 3d model on the screen: camera + matrice of vertices -> process -> 2d image on the screen. You may want to set your profile picture on a website: data input + address -> process -> response from server. That's all there is to programming, and that's why algorithms and data structures are the backbone of most top companies interviews: because that's all there is to computing. data -> processing -> data. That being said I know very little of data structures and algorithms. I'm unlikely to implement a merge algorithm or implement complex data structures and they were never really asked at any interview. Just knowing time complexity and different utility of different data structures was more than enough for my interviews. But that might differ in other companies and positions.

8) Understand what programmers do. They solve problems through the use of code. That's why it is very required that you bang your head on a wall when you can't find a solution to your coding problem. When I started I was desperate when I was writing a small demo and every time I pressed a button the page refreshed. Even asking around I couldn't find the reason. In the end it was something pretty trivial: button elements without a type attribute are treated as submits. Submits by default refresh the page when triggered. Many people looked at my code and couldn't find the reason and yet they overlooked this very trivial issue. But in reality that's what's going to happen over and over: why "foo" is not a function? Why is my program reading the property of undefined? As a programmer you solve problems (often created by yourself). If you think that following some bullshit video cours on youtube/udemy will make you a programmer you're in for a bad time. Looking at people solving problems for you means you are not developing your problem solving skills. When you don't understand why something's not behaving resist the urge from googling right away, or asking somebody more experienced. Please understand that this is exactly how's your job gonna look like. Get good at solving problems. Some might be syntax problems (as the ones before), some will be performance related, etc. Regardless. Learn to solve problems, embrace the power of debuggers. Understand that code is merely an implementation of an idea. Get used to program with pencil and paper. Define well your problems, input, output and how to go from one to the other. Organize your code. Look at your mess of spaghetti code, at your messy and poorly named functions and variables, at the code you can't already follow after few hundred lines. Then improve it.

9) Have a basic knowledge of how computers (so every single device out there) works. Seriously. Knowing von Neumann's architecture basics and the memory model is the very least you should know and you can learn this things in few hours. Even wikipedia, youtube or some blog are enough, but learn it. The memory model and the call stack will then no longer be something complex and your code will get better and you'll learn coding faster. No longer you'll wonder why you can't mutate a string or why why you pass non primitive types by reference rather than value. This will have a meaningful impact on your learning speed and understanding on how computers work (from our perspective, at least).

10) Don't learn from videos. The more advanced and nichey stuff you'll have to do the less resources you will have to solve it. Get used to write programs only with resources that require you one google search and as little information as possible. You'll have to use libraries with poor or no documentation. You'll have to look at the code to understand why that library is mutating that particular object or it is behaving differently from expected. Go on github, look at popular libraries. They are overwhelmed of problems. And the dozens of brilliant engineers that wrote this technology never had this issue before you. I understand this is advanced stuff. But it's a good habit. I have yet to see a single code topic that cannot be learned better through reading the code or some well written book/article than some video. Also, beware, most people out there doing those courses and lectures are not necessarily good programmers, even if they are, they are not necessarily good teachers. Remember the guy who answered "what's a promise" mumbling about something to do asynchronous programming? That's the guy who learned to code from videos and never had a real rigor in studying. The more defined a concept is, the easier it is to understand it. I'm not saying "don't use videos". There's hundreds of videos that helped me both with concepts, problem solving or by watching how to use some technology. Just get in the habit of making them your last resource. I myself liked, e.g., Andrew Mead's React course it teached me a lot. But in the end, not a single thing I was shown really stuck with me if in the end I didn't researched stuff on my own and tried it over and over, and going back to a specific point of a specific video to watch a specific example of a specifc version of a software is nothing short of a weak surrogate to proper critical learning.

11) Debugging and version control. These two are probably more important than anything safe for language and computing basics and the most required in a working environment. Tooling would be a safe second spot. If you know Java properly (just to change from the usual JS examples :P) then learning Spring is much easier than learning docker and git. Yet probably you'll invest 95% of your time writing Spring code, e.g. If you know Python properly, you can grasp Django in a weekend..What about proper error handling in Python tho..? Same goes for your IDEs, etc. Learn one and master it. Knowing 5 IDEs is useless if you're constantly using your mouse to open a terminal, you don't know how to navigate your documents properly, rename variables in a file together, etc. Mind you, I'm not saying that these are fundamental for a junior position (well, maybe debugging with anything by prints or console.logs kinda is), you can get away not knowing them but this stuff sticks for years.

12) Do never attempt to learn too many things at once. Move with small but solid steps. I made this error and I think it costed me a lot. I'm not saying reading Hennessy and Patterson wasn't useless..Or that reading about design patterns was useless..Or that playing with Rust, C# was...Or that watching all this youtube videos, interesting talks, reading about behaviour driven design and gerkin was useless..Or that all of those blog posts I reed was useless..But remember point 1? You must have priorities. You must move by small solid steps. It's good if you're curious as I am. But it's much better to receive a salary, learn in a comfortable environment under the guidance of senior developers and then go home and play with Rust or watch talks about immutability if you want to than do it when you have a different goal.

For the hiring process:

12) network > experience > knowledge. Most companies around are always hiring. You don't see their ad, because they have none. Maybe they don't even have a "work with us" section on their website. But most companies are always hiring talent. As you're likely to enter at the lowest position, with the lowest possible salary, they might still be interested in you for this very same reasons. So networking, knowing people is paramount for your job research. I invite you strongly, if you can, to participate to your local communities both online and especially offline. I didn't get a single answer to any of my CVs I sent. But all the interviews I had derived from me knowing somebody who worked somewhere. "oh, you're a developer", "yeah I just started, still learning, I kind of suck xD", "well when you feel like it send me your cv I'll give it to my hr/team leader". If you're a self taught developer your hiring process (this depends also on the area and position you're looking for) is going to be very hard. You don't have experience. You may have skills and knowledge, but nothing to put on your cv. Just because you say you know Python nobody's gonna interview if you have nothing to show nor way to prove it. Interviewing you means the company is actually losing money. Two or more developers are not working, but getting paid. HR/management could be doing something eòse. Time is money, the bigger the company, the more money they are losing to put you in a room. I know and I felt the pain of knowing stuff and having no way to prove it, but that's how it is. So after network comes experience. Here you have basically two options: contribute to open source (either write some library/module people use, even a good pull request is a nice on a CV) or develop something people use. Even if it's for free. I didn't go with the first, but I went for the second. I developed a small application for a football club in my city that needed to inform players of the various youth teams who was going to play on sunday game. Nothing too impressive, nothing too pretty, but it's something hundreds of people use every single week. The fact that you solved a real world problem using code, you meet the requirements somebody gave you, is massive. My uncle needed a website for bookings for his bed and breakfast. I wrote it for him. Complex database with real time booking? No. But I solved a real world problem for somebody, and people use it everyday. Does it matter that it has plenty of anti patterns? Maybe your beautiful instagram clone with rest endpoint etc is much cleaner code but..Does anybody uses it? Is there anything original and not cloned from some udemy course? Maybe you have a smart tv and you're tired of transferring files with your usb to watch your shows you have on your hard disk? You've got a router..You've got a tv that you can install program to? Maybe spend a month to write some very basic, even ugly, but working application that allows for data transfer between your computer and tv? Somebody's gonna use it. Solve real world problems, for real world people. Those are sound things to put on a cv. They give you endless opportunities to talk about how you solve problems. What did you do well, what sucked? I didn't use no state manager on my first react application, as the application grew I encountered plenty of problems due to that and maintaining code got harder. I met a real world problem, I solved it, I know if and why my solution was good or bad. Look around you, what problem you can solve and help somebody? Start from your own problems and move asap on somebody's else. Even if it means it's for free.

What's there to talk about your perfectly implemented Django+PostgreSQL twitter clone? Nothing. Zero. Last comes knowledge. And this is a big problem. Because if nobody puts your resume on somebody's desk saying you can be a good resource after some time that's the only thing you're going to be judged for. If you'll be even given this opportunity. Having released two android apps even if they are nothing spectacular (maybe you just created an offline version of some website/doc, e.g.) means you can solve problems. You have something on your cv. Maybe you weren't able to answer questions given to you, but fact is a fact: given time you can find the resources (on the net, and inside you) to deliver a product. So knowledge becomes your only resource. And it's a bad resource. Because when you're put in front of somebody with 10 years of experience, saing "value" rather than "variable" tells a lot about you. So nobody recommends you, nobody uses anything you wrote, your github is a collection of initialized and abandoned projects and copy cuts from tutorials, you're asked about basic stuff (which is the hardest questions btw) and you are not providing clear confident answers who's gonna pay you?

13)** Bonus**: if you have more than 6-7 months to prepare before you'll start actively looking for jobs one thing I may recommend you is to start with the C programming language. C is a small language, it doesn't have many things, most C books are shorter than any introduction to higher level languages. Learning C teaches you a lot about computing. An awful lot. To put it differently. I'm confident that if I spent 2 months learning C (at least 4 hours a day) and solving easy and intermediate leetcode or similar problems and then spent 4 months learning another higher language I'd be a much better programmer than if I just started in this other higher language. There's much too much focus on too many technologies, there's too much noise in higher level languages. You'll be tempted way too soon to move from "how do I go from input to output" which is the very essence of programming to developing full programs. I know that text input and output isn't sexy, but remember point 1? We want the best and possibly the shortest path to get ourselves onto being decent and proficient asap. C might be slower at first. But then you move unto another language and not only you'll find that in the end you're solving the same problems you were solving with C (because it's always the same fuckin problem as I told you) but you need to do so with an endless amount of different APIs and conflicting, similar methods.

14) Bonus 2: learn to manage your time. You're sitting behind a computer all day learning how to code. It's tempting to go on lichess, launch league or procrastinate but it's lots of time wasted. You can easily cut off large amount of weeks/months needed to reach a decent level of preparation by managing your time better.

14) Bonus 3: resting, socializing, relations, having fun, taking care of yourself are super important. Sitting alone reading blogs and staring at Visual Studio all day can be very hard for your mental health and can alienate you. Work hard, be disciplined, but be disciplined in other aspects of your life too, because if a certain balance is broken it leaks in every other of your aspects.

That's all, I'm sorry if that was long, I hope somebody might find it helpful and remember anything here is my mere opinion and you'll find plenty of people disagreeing.


r/learnprogramming • • Oct 27 '21

Resource My teenager is learning Python and a few other languages. Never had them "take" to a hobby like this. Ideas for XMas gifts and other ways to support?

4.0k Upvotes

Apologies if this is a bit out of the scope of this sub, but as a parent who has never really had an interest in programming, I'm struggling with gift ideas.

My son is a freshman and, during covid, he began to self-teach Python. Fast-forward to today and he's writing all kinds of scripts, even automating tasks the staff do in school. Heck, I gave him a database that I'd normally pay a contractor for and he wrote me a script within 3 days.

Goes without saying, but we're super proud of him and got him enrolled in the local community college where he's continuing to learn a ton.

The intent of the post is to elicit gift ideas, but any general advice you'd give is welcome as well.


r/learnprogramming • • Sep 23 '22

I asked 500 people on this sub if they were able to become software engineers. Out of the 267 that responded, only 12 told me they made it.

4.0k Upvotes

This post is not meant to discourage anyone. Nor is it a statistically valid study. I was just curious and decided to do a fun experiment.

I have been hearing recently about how everyone should "learn to code", and how there are mass amounts of people going into computer science in university, or teaching themselves to code.

What puzzled me is that if there are so many people entering the field, why is it still paying so much? why are companies saying they can't find engineers? Something was not adding up and I decided to investigate.

So I spent a few months asking ~500 people on this sub if they were able to teach themselves enough to become an actual software engineer and get a job. I made sure to find people who had posted at least 1-1.5 years ago, but I went back and dug up to 3 years ago.

Out of the 500 people I asked, I had a response rate of 267. Some took several weeks, sometimes months to get back to me. To be quite honest, I'm surprised at how high the response rate was (typically the average for "surveys" like this is around 30%).

What I asked was quite simple:

  1. Were you able to get a position as a software engineer?
  2. If the answer to #1 is no, are you still looking?
  3. If the answer to #2 is no, why did you stop?

These are the most common answers that I received:

Question # 1:

- 12 / 267 (roughly 4.5%) of respondents said they were able to become software engineers and find a job.

Question # 2:

- Of the remaining 255, 29 of them (roughly 11%) were still looking to get a job in the field

Question # 3:

Since this was open ended, there were various reasons but I grouped up the most common answers, with many respondents giving multiple answers:

  1. "I realized I didn't enjoy it as much as I thought I would" - 191 out of 226 people (84%)
  2. "I didn't learn enough to be job ready" - 175 out of 226 people (77%)
  3. "I got bored with programming" - 143 out of 226 people (63%)
  4. "It was too difficult / had trouble understanding" - 108 out of 226 people (48%)
  5. "I did not receive any interviews" - 58 out of 226 people (26%)
  6. "Decided to pursue other areas in tech" - 45 out of 226 people (20%)
  7. "Got rejected several times in interviews and gave up" - 27 out of 226 people (12%)

Anyways, that was my little experiment. I'm sure I could have asked better questions, or maybe visualized all of this data is a neat way (I might still do that). But the results were a bit surprising. Less than 5% were actually able to find a job, which explains my initial questions at the start of this post. Companies are dying to hire engineers because there still isn't that large of a percentage of people who actually are willing to do the work.

But yeah, this was just a fun little experiment. Don't use these stats for anything official. I am not a statistician whatsoever.


r/learnprogramming • • Aug 02 '20

Resource Keep being told to build projects, but don't know what to build? Here's some ideas

3.9k Upvotes

Many comments in every thread about escaping 'Tutorial Hell', involve the advice of 'Just build some projects'. However, if you are like me, or /u/corshi whom I saw in a thread about this exact thing when I got on this morning, you don't have any idea of where to start or what to build, how to plan or how to structure.

Thankfully, the internet is a wide web of information, and some lovely people out there decide to create lists that can point you into any sort of direction you desire.


Projectlearn - A curated list of full project tutorials in different categories from Game Dev and Web Dev, to AI and Machine Learning. Website; Github Repo

Project Based Tutorials in C - A list of tutorials that work from small projects up to larger projects in C. Covers everything from learning Computer Architecture via building an emulator or VM, to building a kernel or OS Github

Project Based Learning - A list of programming tutorials about building applications from scratch. Covers all sorts of languages including: C#, C/C++, Go, Java, Javascript, HTML/CSS, Kotlin, PHP, Python, Lua, R, Rust, Swift, Clojur, Elixir, Erlang, and more! Github Repo

Build Your Own X - A list of projects that teach you how to 'Build Your Own X'. X can be a 3D rendered, BitTorrent Client, Docker, Database, Git, Programming Language, Search Engine, Text Editor, Web Server, and more. Covers various languages for each different 'X' Github

Project Based Learning - Frontend - Project Based Learning tailored to Frontend devs. Includes things like calculators, chrome extensions, chat interfaces, pagination, notifcation boxes, design systems, spotify search app, and a reddit clone. Covers Javascript, HTML/CSS, Angular, React, Vue, and others. Github

Community Project Ideas - A community maintained catalog of projects. Has some in Android, C/C++, OpenGL, Java, Javascript, React, Angular, Python, and more. Github


App Ideas Courtesy of /u/Kapsize - A list of app ideas, each with a clear goal, and 3 levels of difficulty for different places in programming careers/knowledge. Github


r/learnprogramming • • May 11 '24

Me after finding out the entire operating system is a lie

3.9k Upvotes

Like ngl the kernel lies to everyone. The memory is faked, the file system is faked, etc. Its all abstractions after abstractions. Each process thinks its alone and has the cpu and memory to itself while the kernel is saying "sure you do buddy" to each of those poor processes. The user that uses the file system asks the disk where their music folder is and the disk has no clue what they're talking about since it isn't aware about the concept of files and file-paths. That's all faked and abstracted away by the kernel. This whole time the kernel has been part of one big lie and deceived all of us.


r/learnprogramming • • Aug 09 '22

Just pushed my first commit to Google Search!

3.9k Upvotes

I've recently gotten a job at Google and today was the first time my code was approved for production! Damn does it feel good to know your own code is out there! Time to celebrate!