New to programming? Not sure how to start learning? See [FAQ - Getting started][faq-start].
Have a question? Our [FAQ][faq] covers many common questions; check that first. Also try searching old posts, either [via google][google] or via reddit's search.
Your question isn't answered in the FAQ? Please read the following:
If your question is about code, make sure it's specific and provides all information up-front. Here's a checklist of what to include:
A [concise but descriptive title][debugging-title].
A [good description][debugging-description] of the problem.
A [minimal, easily runnable][debugging-posting], and [well-formatted][debugging-formatting] program that demonstrates your problem.
The output you expected and what you got instead. If you got an error, include the full error message.
Do your best to solve your problem before posting. The quality of the answers will be proportional to the amount of effort you put into your post. Note that title-only posts are automatically removed.
Also see [our full posting guidelines][debugging] and the [subreddit rules][rules]. After you post a question, DO NOT delete it!
What have you been working on recently? Feel free to share updates on projects you're working on, brag about any major milestones you've hit, grouse about a challenge you've ran into recently... Any sort of "progress report" is fair game!
A few requests:
If possible, include a link to your source code when sharing a project update. That way, others can learn from your work!
If you've shared something, try commenting on at least one other update -- ask a question, give feedback, compliment something cool... We encourage discussion!
If you don't consider yourself to be a beginner, include about how many years of experience you have.
This thread will remained stickied over the weekend. Link to past threads here.
Here is the original post: https://www.reddit.com/r/learnprogramming/comments/9t9kyr/ive_completed_freecodecamp_and_received_all_the/e8upqvc/?context=3
So Yes! I've found a job since then. I've been working as a Software Developer for an year now. After that last post, I started applying and soon found a good job. They took me as a MERN stack web developer initially, But I worked on different technologies and learned a lot. We mostly develop Enterprise solutions (Data warehousing products, ETL Tools, Management Systems, etc.) using C# .Net Framework and whichever set of front-end libraries we like. I've since then, learned about software architectures, design patterns, rational databases and most importantly working in a team.
I've learned a lot more on job than I'd have if I would have waited to learn some more before applying. So my advice is to stick to a course (whether it's a course on udemy/coursera/edx, Odin project, freeCodeCamp or a good book), learn enough of what it has to offer (but not more - as you might fall into the tutorials hell where you just keep learning more and more but never apply it and end up forgetting the previous stuff you learned).
Finally I'd like to say that I did not have the best of portfolio or best of anything for that matter. And as I look back now, Consistency was the most important thing in my path to self-learning. So be consistent, take small steps, understand that it is okay If some things don't make sense at first, don't burn yourself, don't compare your progress to others, ask a lot of questions, and most importantly, find other things that you are passionate about and use your new programming skills to enhance them in some way.
I wish you Good Luck in your journey.
So, I'm in collage studying Computer Science. I always loved programming soon as I learned about it. The problem is that I don't think I'm good enough at it, and I'm afraid that even if I put a lot of effort on it, I still not good enough. For example, I'm learning C and had a test about loops, strings, functions, etc (the basics). I studied a lot for it, made all kind of programs and exercises related to it, and had a bad grade even tho people were saying that this test was pretty easy (and now I see it really was).
The point is that I'm not thinking about giving up because of a bad grade. I'm thinking on giving up because I know that I studied a lot more than everyone but that still not good. I'm not good at it as I thought I was. if I'm having such a hard time in the easy part, I can't imagine how it will be going forward.
I'm just getting it off my chest. Idk what's going to happend and I'm afraid of it. That's it.
Hello,
I am preparing university notes in which I make the concepts concerning programming simple, so I would like to discuss them with you so that I can have different opinions.
Regarding the answer to the question, based on the book "Thinking in Java", I arrived at the division of the principles into 5 phases:
Everything is an object. Think of an object as a fancy variable; it stores data, but you can “make requests” to that object, asking it to perform operations on itself. In theory, you can take any conceptual component in the problem you’re trying to solve (dogs, buildings, services, etc.) and represent it as an object in your program.
A program is a bunch of objects telling each other what to do by sending messages. To make a request of an object, you “send a message” to that object. More concretely, you can think of a message as a request to call a method that belongs to a particular object.
Each object has its own memory made up of other objects. Put another way, you create a new kind of object by making a package containing existing objects. Thus, you can build complexity into a program while hiding it behind the simplicity of objects.
Every object has a type. Using the parlance, each object is an instance of a class, in which “class” is synonymous with “type.” The most important distinguishing characteristic of a class is “What messages can you send to it?”
All objects of a particular type can receive the same messages. This is actually a loaded statement, as you will see later. Because an object of type “circle” is also an object of type “shape,” a circle is guaranteed to accept shape messages. This means you can write code that talks to shapes and automatically handle anything that fits the description of a shape. This substitutability is one of the powerful concepts in OOP.
However, I can't make it even easier. You have tips, even twisting the points or making them more synthetic. Also, could you recommend books that talk about Java in a really easy way?
Hi everyone, I'm a 24 year old commerce student living with my parents. No job. Broke. With no knowledge about programming. I want to become a software engineer. I'm determined, dedicated and fully going to devote my life on becoming a successful software engineer. I need your guidance. Anyone a single soul willing to help me with any information, I'll take it.
What is the best DS & A course? Also, is there any textbooks you can recommend? It can be paid or free. I appreciate the input.
I've started my first soft.eng job recently and the vast majority of the tools such as Airflow and Ansible are great to use and learn, but I don't know where to start looking for these sorts of technologies.
Where should I start looking to find useful dev-ops related tools? I'd like to boost my understanding further of how to orchestrate a dev-ops oriented stack.
Community Details
1.2m
Members
3.7k
Online
Sep 24, 2009
Cake Day
Welcome to LearnProgramming!
r/learnprogramming Rules
Asking debugging questions
When posting a question about code, you must include the following:
- A concise but descriptive title.
- A good description of the problem.
- A minimal, easily runnable, and well-formatted program that illustrates your problem.
- The output you expected, and what you got instead. If you got an error, include the full error message.
See debugging question guidelines for more info.
Asking conceptual questions
Many conceptual questions have already been asked and answered. Read our FAQ page and search old posts before asking your question. If your question is similar to one in the FAQ, explain how it's different.
See conceptual questions guidelines for more info.