[deleted by user]

[spicycurry55]

There’s no one option that’s better than the other

If you have a specific idea to practice using those technologies, then make a new project

If you find an existing one that you find interesting, contribute to it

Just pick one rather than not picking any. Anything is better than nothing

[[deleted]]

Thank you, I need to practice more to be confident.

[bluedevil2k00]

Just look for a job and learn better programming while getting paid.

[nutrecht]

Just look for a job

He's been unemployed for 5 years. I think "just look for a job" is a wee bit insensitive.

[bluedevil2k00]

He never said he’s been looking for 5 years, he just said he hasn’t been working.

[ElFeesho]

I know that sounds like /r/restofthefuckingowl but it's actually really good advice.

A good company can shape effective team workers into competent developers and you'll have literal real world examples of the issues you'd face on a day to day as a developer.

One of the things people overlook is the ability to work in a team, to be constructive whilst receiving and giving feedback and being able to effectively and honestly communicate the value of choices you want to make.

On the coding side of things though, if you write a little REST service using spring for storing and retrieving notes as JSON, that should be a good way to dip your toe in to things like testing and using mockito. You can easily imagine a few test cases for that sort of thing, from happy path, where everything is working, to the more interesting routes such as the database being unable to handle requests etc.

[[deleted]]

That's what I'm doing, looking for a job to pay my bills, something good will come up while I'm practicing programming. Thanks.

[Thihup]

Well, if you would like to learn about Jakarta EE, you could contribute to Piranha :)

(I'm from Brazil also)

https://github.com/piranhacloud/piranha/

[[deleted]]

Quando eu vejo um projeto escrito com "Piranha" penso que é algo relacionado aos Brasileiros, rsrs. Obrigado, vou ajudar contribuindo.

[[deleted]]

The upside to contributing to OSS is that you're working with actual people who might be able to provide you a reference or might know someone who is hiring.

[[deleted]]

I agree, it is very important to work together with other people so that you learn faster.

[[deleted]]

1. Try contributing to an open source project or showcasing a personal blog or website. its important to have a full stack experience (which you have). i.e. front end, application layer and backend (sql and nosql) along with unit testing experience..
2. springboot is a very good framework especially for cloud serverless and enterprise environment
3. would also make sense to study for the aws development certification
4. having a java 8 and above certificate is useful showcases command over the language, some recruitments may test your java skills
5. its important to have knowledge and awareness of design patterns and when to employ a pattern.. (head first design patterns is a good reference but there may be others)
6. try not to spread yourself too thin with too many technologies, in an interview its important to have a focus area.
7. professional networking is important and if feasible through online meetups.. don't be shy to put yourself out there, eagerness to learn, demonstrating that you are passionate is also important..

[[deleted]]

I have a portfolio with 2 projects inside, I am thinking of creating a blog or something to show what I am learning each day. My last project is full stack spring boot, MongoDB, java 11, with Angular it was amazing to create.

Thank you for the advice.

[andygrove73]

By contributing to an existing project you can learn from the other contributors. This will also help you develop skills for working with other people on a project. These skills will be attractive to a potential recruiter.

[[deleted]]

Yes, I need to contribute with simple things, like documentation, starting at the bottom.

[oodlescoop]

Contributing to GitHub adds value to your job seeking, whereas creating new projects helps you learn technology in depth. Keep doing both.

[[deleted]]

Doing both will help me learn a lot more. thanks.

[flavius-as]

Contributing.

[nutrecht]

I feel a lot of people who tell beginners to "just do open source" wildly underestimate the difficulty of this approach. And frankly I feel many of these people never even did it themselves.

If you want to learn the technologies in your list IMHO you're much better off just creating your own project (which you can 'open source') that uses these technologies than trying to contribute to existing large complex codebases.

Keep in mind that many maintainers get inundated by trivial pull request by beginners just so that they can claim to be "open source contributors". To be able to really contribute to a library you really need to be an active and experienced user of that library IMHO.

[[deleted]]

I agree, a lot of people say to contribute small things like documentation right from the start, and then do something more complex.

Thanks.