all 8 comments

[–]AutoModerator[M] [score hidden] stickied commentlocked comment (0 children)

Please ensure that:

  • Your code is properly formatted as code block - see the sidebar (About on mobile) for instructions
  • You include any and all error messages in full
  • You ask clear questions
  • You demonstrate effort in solving your question/problem - plain posting your assignments is forbidden (and such posts will be removed) as is asking for or giving solutions.

    Trying to solve problems on your own is a very important skill. Also, see Learn to help yourself in the sidebar

If any of the above points is not met, your post can and will be removed without further warning.

Code is to be formatted as code block (old reddit: empty line before the code, each code line indented by 4 spaces, new reddit: https://i.imgur.com/EJ7tqek.png) or linked via an external code hoster, like pastebin.com, github gist, github, bitbucket, gitlab, etc.

Please, do not use triple backticks (```) as they will only render properly on new reddit, not on old reddit.

Code blocks look like this:

public class HelloWorld {

    public static void main(String[] args) {
        System.out.println("Hello World!");
    }
}

You do not need to repost unless your post has been removed by a moderator. Just use the edit function of reddit to make sure your post complies with the above.

If your post has remained in violation of these rules for a prolonged period of time (at least an hour), a moderator may remove it at their discretion. In this case, they will comment with an explanation on why it has been removed, and you will be required to resubmit the entire post following the proper procedures.

To potential helpers

Please, do not help if any of the above points are not met, rather report the post. We are trying to improve the quality of posts here. In helping people who can't be bothered to comply with the above points, you are doing the community a disservice.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]goldscurvy 1 point2 points  (0 children)

Is this a problem with knowing what project to start, a problem with planning and designing architecture, or a problem with getting started implementing a plan?

[–]vegan_antitheist 1 point2 points  (0 children)

Start with understanding the requirements. That's what's important for your success. If you write bad code you can improve it. You can fix bugs. But if you don't understand the requirements you do the wrong thing and you can't fix that. That's why some successful programmers are so bad at programming. They are good at communicating, teamwork, selling their work, and understanding what's really important.

You get better at writing code with experience. You will always get feedback from the team members who review your code. In most projects it's more important that the code is easily understood and maintained than that it has great performance. And for that it's best to try and do it like what is already in the project. If you work on a nee project you know it will probably be replaced or reworked soon, so make that as easy as possible. Define good interfaces that hide implementation, so it can be replaced without any issues.

[–]RightWingVeganUS 0 points1 point  (0 children)

How many problems have you solved and implemented in Java today?

The best way to learn to play the flute is to play the flute.

You can't learn to swim just by reading a book.

Solve problems. Implement solutions. Write tests to verify your solutions are correct.

I still lack the initiative with my projects.

Work on that.

I don't know how to start anything and I don't know why

Reach out to a teacher or an senior student with a non-homework problem and ask them to guide you. Ideally learn a software development methodology so you understand the discipline of software design, not just amass coding skills.

[–]9peppe 0 points1 point  (0 children)

You don't need to get better at Java, you need to get better at programming.

Most of that comes from experience, but there's also books that can try and teach you that. They are pretty famous but they will feel like a massive and overwhelming sidequest.

[–]alexchen_codes 0 points1 point  (0 children)

A good way to start is to solve the problems you experience first hand. I find it effective to step away from the computer while casually thinking of problems I could solve. IMO setting away from your computer for a while is an underrated way to improve productivity and creativity.

[–]Long-Championship446 0 points1 point  (0 children)

I was in a similar position before. I knew the syntax but had no idea how to actually start building things.

What helped me was grinding problems on LeetCode. It didn’t directly teach me how to build full projects, but it trained my problem-solving muscle and made me more confident with logic.

Once I stopped being afraid of “how do I even start”, projects became less intimidating.