Do you know of any Open-Source Job-Board, Applicant Tracking System in Laravel?

do you have a better idea on how to get started?

@dipherent Yes. You can…

Thanks for your USELESS comment

Never mind. Not going to waste my time with sass like that.

@dipherent Hi. So, had a couple of days to reflect on this and, likewise, there was no offence intended on my behalf either, but was clearly interpreted as such, so I apologise and would be happy to draw a line under it and start again if you are?

What I meant by my comment was, if you just find an open source project that does what you want then yes, you’ll have the code in front of you that does what you want that you can copy from, but what you don’t get (or learn) with already-built solutions is the why. You don’t get the decisions that have gone into writing the code or solving things the way that it has been written and solved. You’re only seeing the end result and not how that end result was achieved.

The best way to tackle things is to just look at the problem and break it down into bitesized pieces. Don‘t look at something as a whole, because you’ll just overwhelm yourself. But if you start carving a problem up into small chunks, and then tackle each chunk where you’re focused on that chunk only, you’ll find you’ll keep a good cadence in terms of developing, and by just focusing on one particular chunk at a time, you’re thinking about that one thing and not overwhelming yourself trying to keep the whole of the project in your head at any one time.

So, I’d tackle your project in the way you’ve described:

I am looking forward to building a Job Board

That would be what I‘d focus on first. Create a Laravel application, and then create a job posting model and controller that lists jobs, and the details of a job when clicking on one. Once you have this in place, you can then move on to…

a simple application process (or Applicant tracking system)

You have an application showing jobs. Now create a model to represent a job application. It can be a simple as a model with two foreign keys: one pointing to the user who is applying, and another pointing to the job they are applying for. You can then build on this model, maybe adding a state for where an applicant is in the process (applied, reviewing, interviewing, offered/declined role, etc).

Hopefully that helps you on your way. Again, sorry my original reply came off as combative and condescending. It wasn’t intended to be.

@Snapey thanks for your comment bro; and for your help over the years. I am grateful for whatever I learned from you; but honestly this was the first time I see someone reply to a question like that. I was really looking for help and not for such attitude.

I come to this place because everyone has been nice and helpful;

I knew this post was ruined the second I read his comment. Of course no one will waste their time in a rude post like this.

Anyway, thanks for your response.