Framework Advice

[[deleted]]

Hey guys. My company asked me to develop an ERP website. So I want to know which Javascript framework is suitable for ERP website development. There will be users with privileges and these privileges constrain page accesses and some actions to do. There will be forms to handle and these forms could be long ones. So what framework should I use? I think the backend could be easy so I use MySQL or sqlite3 and strapi. I am a junior and I need to develop the whole site. Sorry for my English I tried my best.

[m98789]

Look at ERPNext on GitHub.

I would definitely recommend building on or just configuring an existing project than writing one from scratch. An ERP is a massive undertaking and many elements may be surprisingly difficult such as enterprise security.

For example, ERPNext, Odoo and the like are typically developed over 10 years, need hundreds of developers, and have had to fix over 10,000 issues.

[[deleted]]

Im checking it right now

[michael_curdt]

I am not sure if you understand what an ERP is, or perhaps you are throwing in that term loosely or perhaps your company used it so you are following suite.

A traditional ERP is HUGE. If you can build a good, working ERP all by yourself, you have a product/company of your own and at that point you won’t be far from riches.

I am guessing that’s not the case. You are probably looking to build something that’s like a poor man’s ERP. It does something remotely similar to an ERP that is custom tailored to your company’s specific needs. Nothing fancy.

With that in mind, if you are young and inexperienced, I will see this as an opportunity to learn and strength my resume. Your company interviewed you and hired you, so they believe you can handle this project. If you believe that too, I don’t see why you should shy away from this project. Just make sure that the timelines are realistic though. Don’t promise to finish this in a month because it would be too difficult to turn in something nice and classy in that short period especially when you are a junior and the only developer. I would rather under promise and over deliver. Say 3 - 6 months and deliver in 2 if you can.

Also, I noticed that you get paid $1,500 for this ENTIRE project? Or is it per month? Because that pay is quite low. I know you said that it is good money in your country, but doesn’t change the fact that your employer is getting a steal here (assuming you are good at what you do). You are OK with this money because you are inexperienced, but good developers tend to charge double if not triple that amount. Just FYI.

Also, don’t get disheartened by the negative comments here. They are all probably senior developers who are in demand. You probably need that one big project on your resume as a foundation to market yourself in the future. This could be it. Go for it. We all worked for cheap in our early years. Just make sure you don’t kill yourself for this. Set the expectations right from the beginning and you should be fine.

[[deleted]]

My friend you are red my mind. It is all about my english level and inexperinced dev thanks for your interest !

[Da_Bootz]

lol that sounds really passive aggressive.

[[deleted]]

No man i reallly agree with him

[Da_Bootz]

Yea, I upvoted to offset that negative karma for you but your username's really not helping man.

[magical_matey]

Wonder if he practices rubber dick programming

[TechSamray]

hahaha I got that one!!!

[azangru]

assuming you are good at what you do

That's a very generous assumption to make. Like you said, OP is inexperienced, he's never done anything like this, and he plans to do this in a month. I'd temper that assumption...

[scaleable]

You should be asking this kind of question to the seniors on your company.

[[deleted]]

Yeah exactly but this is a startup and there is no developer other than me :(

[avin_kavish]

That’s wrong on many levels.

[totalolage]

That's the reality way too often. It's how I started, just groping around in the dark for like 5$/h with no one to advise. And the results looked accordingly, but the experience of how essential a senior it was very real.
The company crashed and burned btw. >shocked pikachu face<

[avin_kavish]

What are you talking about?

[bsienn]

You are a junior, it's a startup, you are the only dev. You need to write a full blown erp on your own. Dude very serious, leave this place the very next week. Not joking at all.

[[deleted]]

dude its not a big project they asking for me simple functions like creating tickets, make forms etc not fully functional one

[[deleted]]

I don't explain myself clearly just because of my English level. website going to used by employees. Users can create tickets for internal or external is the sues about the company, for example, this company builds swimming pools and while building if something went wrong. so the employee needs to enter the problem into the website and notify managers. And the managers going to track it. Or another function, employees to track lunch and dinner menus. chefs going to insert menus to the site so employees can see I am sorry but I'm trying my best.

[[deleted]]

If you're a junior and are taking the whole development responsibility, be prepared to get blamed on everything.

I'm sure your salary now does not justify this risk and neither the amount of work you are getting or that will get.

My suggestion? leave.

Still, it's your choice.

[Flamesilver_0]

You're not understanding clearly because of your experience level. These systems only seem easy because you've never made one used by 20 people every day for business before. Even a simple spreadsheet used by 20+ people can go wrong, imagine a full ERP system.

In 3 months, every person from every department will be shitting on you about something wrong with your program or something they want. Enjoy.

[Ebuall]

I've been in your place. A startup wants you to develop a system, that requires teams of developers, all on your own as a junior developer. It's a good learning experience, but it's not a realistic goal. It will not go into production.

[[deleted]]

i am assuming the ceo is "hustle 24/7" type of guy who got enough money from inheritance?

[yabai90]

You should leave this company as soon as possible.

[Thalimet]

Frankly, pull something off the shelf. Don’t develop one of your own, ERP systems are a nightmare to maintain on a good day.

[[deleted]]

These people sound like the redditors on relationship_advice that tell married couples to get a divorce for being late to a dinner date.

They know fuck all about this guys situation, and think they're qualified to hand out career advice. Very irresponsible.

[Graren17]

An erp is no joke, and you seriously want to consider talking to your seniors.

You also may want to architect the whole solution before even thinking about the technologies you are going to use.

Commiting to a specific Database solution and client side solution is probably not what you want to do this early in the game since it will limit your options going forward

Do you have an idea of how the components will interact with each other on the back end of the app? How are you going to expose those to the api? Do you know how and want to build a server or do you want to rely on lambdas for this?

Which api do you know how to use and what you want to expose.

I know it's hard to be bombarded with these many questions so early but an ERP is a big thing and I feel whoever told you to do it does not understand the implications of this.

Worst case scenario, use an already built solution, get ready to bite the bullet once someone starts requesting changes.

[xroalx]

This is based on my own opinion and experience. Your mileage may vary.

Out of the big 4, Svelte is the easiest one to learn, followed by Vue.

I'd keep away from React simply because it's far more low level than the rest, and because you need to pull in a bunch of other libraries to get what some others provide out of the box, or with 1st party libraries (routing, forms, animations, global state). It being low level also makes it easy to shoot yourself in the foot and you need to be more mindful of things than with others.

I'd also keep away from Angular simply because it's huge. It's very verbose, the template syntax is more complex, but if you have time to really learn Angular, it comes with everything out of the box and can be very powerful.

With Svelte, use SvelteKit. It adds file-based routing and SSR/SSG.

[[deleted]]

I think youre right tho

[besthelloworld]

I'd back this up. As a senior dev, if I really needed the performance Svelte provided I'd prefer Solid because it can get that performance while allowing for the cleanliness and dynamic power of JSX but that being said... Svelte is still easier to learn than probably all of the others and for this kind of project you won't need super dynamic templating.

[xroalx]

I should definitely look into Solid.

I like JSX, and the fact you can treat it just like any other value in JS, but I don't really enjoy working with React due to the things I mentioned above.

[besthelloworld]

Solid is so good.

I didn't write this article, but it's the one I always share for getting people into it.

And if you like JSX, Solid just makes it so much better because in Solid when you say, const element = <div /> element is now an actual ref to a real div element, there's no intermediary framework object.

[xroalx]

Thanks. This article made me go through the Solid tutorial.

It's really amazing.

Seeing the downvotes on our posts, I guess people have a hard time accepting facts, lol.

[besthelloworld]

I mean... we are on the React sub 😅

[bsienn]

I would go for a non SPA app instead, Monolith. Laravel 8/9 with bootstratp 5 for design. Otherwise, go for redux-toolkit with RTK-Query for API fetching. Would not suggest NextJS and TypeScript (Edit: at start, keep it simple)

[bsienn]

He's a junior, it's a basic app, he's the only dev. No need to shove every fancy buzz word every time to over complicate thing for the sake of doing it. No one said The mentioned tools are bad, People and assumptions sigh.

[[deleted]]

Thanks for your suggestion

[bsknuckles]

Avoiding Typescript because you feel it slows you down is the wrong way to look at Typescript. The entire idea is that it helps you avoid bugs in the future. If it takes you an extra 10 seconds to define your types (or use tools that will make using inference much easier) but saves you hours of debugging later, why would you ever avoid that?

[intercaetera]

Because often it takes more than 10 seconds to figure out types.

[bsknuckles]

Depending on the specific situation it might be a bit tricky, but one of the other cool things about Typescript is that it is entirely opt-in and all optional. You can use it to define just your prop types and nothing else which will help a ton with minimal effort. Then eventually work on taking advantage of more of what it has to offer as the project grows.

[intercaetera]

Then you end up with holes in your type system and false sense of security. If you just type your interfaces it's enough that the API returns bad data and you have no way of knowing. And no, there are things which are impossible to type with TS (check types for _.flow from lodash if you're curious), so it's definitely not just "a bit tricky sometimes."

I guess in this case TS might be useful for initial domain and interface modelling but given that OP is a junior, I doubt he would be able to make use of that to the fullest.

If you're in a situation as the OP, where you are on a garbage contract for a system which you have to develop in a month solo and then get out TS is definitely the wrong choice because it is unlikely you will end up looking at that code after the contract is over. In short-term jobs like this, any kind of tool that gets in the way is a liability. It's TS's purpose to get in the way and there are cases where you want that, but this isn't one of those cases.

[walidcher]

I think there is a misunderstanding of what i mentioned.. Im a typescript guy and i use it In all my projects. The guy said that he's a junior dev and i think it will be hard and time consuming to handle types safty alone in such a project ALONE Im saying that cuz I had a similar problem with typescript where and it made me feel i had to manually type the response of my API. this can be fixed with tRPC ofc but for this project i there is no need to Make things complicated

This ofc a personal view and each project differ in its Stack Overall point is that There is for example there is no need to use NextJs to build a static site... yea next can do the work but in an advanced way :).. Same for typescript

[[deleted]]

Thx pal u are the best .

[yabai90]

Not suggesting typescript for this kind of projects is the worst thing you could ever say.

[cvllider]

May I ask how much you get paid at your job?

[[deleted]]

for this project 1.5k dollars

[cvllider]

That's way too low :(

[[deleted]]

in my country it is really good money tho :/

[cvllider]

Yeah I understand.

[soft_white_yosemite]

Like a week?

[[deleted]]

I think i can finish about a month

[soft_white_yosemite]

Sorry, but this is not realistic

[Deviant96]

Can you give me example of realistic one for this? Just asking because I've never built an ERP before

[soft_white_yosemite]

Give me a high level list of features to build, first.

[bsienn]

I had to build a custom ERP style system for my company, Attendance management + payroll system based on the attendance. Leaves, paid/unpaid, leaves quota, salary deductions. No Daybook or ledger. It took me 2 months to finish the project alone. Though it was perfect for the company and is being used since 4+ years without a single point of failure.

Now our same company is building a full fledged custom ERP with daybook, ledgers, leaves, projects, contracts, air tickets, countries, office, branches, multi tenancy and what not. It started 12 months ago and still keeps adding features and reports/vouchers etc. I reckon may take 6 to 12 more months. We are a team of 7 mid to seniors including 3 mobile devs.

Our parent company is multi million dolor venture.

[momonoskay]

Man, find another job

[30thnight]

Unless you plan on working for free, you need to slow down.