Level 75
Two things:
- When you apply, actually know how to code.
- Be the type person that is a problem solver
On point one, you either know or don't know. If you know how you are good to go.
2 likes
Jun 7, 2026
7
Level 1
How big of projects do I need to get a job?
If someone can take the time to look at this open source project https://github.com/invoiceninja and if someone can tell me do I have to create a few projects like these? I know they aren't system design and other technologies. But should I have a project like this or a little smaller to apply for a job? I was planning to create a project but if I create a basic CRM or maybe a but more than basic, and a few other projects. Will this be enough? But they do not have to like the invoiceninja. I was seeing a video on YouTube and saw two videos that were identical some what and in one of them it said "this is a oversimplified tutorial". So does a portfolio project doesn't need to be like Salesforce and not like invoiceninja? But also not to basic?
Level 1
So a MVP is like a ecommerce website or another type of web application with all the core features that type of web application has just with no system design, NFRs, UX, OWASP SAMM. Correct?
1 like
Level 20
I wouldn't hire you for one very simple reason (and it has nothing to do with your lack of understanding of what you actually need to do to become a developer from the development end of the wedge)... the sole reason is:
You simply don't listen/take on board anything that people that do know, advise you.
How many times across both of your accounts have extremely experienced engineers told you to ignore buzzwords, all these acronyms and everything else that some PoS AI is telling you? How many of those many times, have you once taken on board that invaluable information and put it into practice?
In fact, at this point, I can only assume that both of your accounts have not been set up to glean information from engineers here, but are nothing but pure troll accounts... for which this, you have apparently succeeded.
The only reason I have wasted digital ink in this reply is that I'm waiting for a CI pipeline to complete and I find your posts humorous.
Remember.. it's "in.... out... in.... out"... just in case you were also wanting to know how to breath.. or how it might be more relevant to you.. engage your respiratory system, expand your nasal cavities.. contract your diaphragm to increase space in the chest cavity. Allow the air to travel down your trachea into your lungs.. then begin to exhale and allow the CO2 to leave your body.
With this information.. you should now also be able to become a brain surgeon!
1 like
Level 50
Here are the skills I'd consider the minimum requirements for a full-stack junior position:
- Basic coding
- HTML
- CSS
- Basic understanding of databases
- Basic understanding of networking
- Basic understanding of security
- Some experience with a backend framework (Laravel, Django, Express, etc.)
- Some experience with a frontend framework (React, Vue, Svelte, etc.)
If you can't explain the request-response model or don't know the difference between an array, a map and a set, your GitHub is completely irrelevant.
2 likes
Level 80
@june92 Seriously, how many questions are you going to ask on this topic…?
You keep asking questions that if you do X, you will magically be a senior developer, or if you do Y, you will magically get a job. That’s not how the industry works.
1 like
Level 1
I got it now.
1 like
Level 63
Laravel is only a framework, a tool to develop. It's like a hammer. It's not because you have a hammer that you are a good carpenter. A carpenter has to know his job.
For the developers, it's exactly the same logic : it's not because you know Laravel that you are a good developer.
What is important is to acquire an approach. If you have the good approach, then coding is only manipulating lines of code.
And to acquire an approach, it's not just learning how to hammer nails, how to use Laravel or VueJS or Symfony or any language. Acquiring an approach needs that you have been confronted with problems and that you have experienced many solutions to solve this problem.
Furthermore, because development is so vast that you just can't know everything, you need to work with other people, not mandatory with your own team (you can for example work as a freelancer), but also sharing on social networks (like Laracasts).
So acquiring an approcha is possible only if you are curious with the stacks and over all if you listen what more experienced people advise you.
That's called experience.
1 like
Please or to participate in this conversation.