Not sure if this is a valid answer but humans for me are the worst kind of bugs. Not consistent in the response and almost impossible to debug.

@uuid I agree with most of your points. It happens to me too, I don't like reinventing the wheel, if an app works and I don't have enough ideas to bring something new or make it 10x better I try to stay away from developing.

But that said some apps depend on your location as well, globally there maybe an app v strong in the market , but in your location/country it might work if you identify the problems and fix it and market it for your country.

If you have an idea identify the merits, issues and do a small market analysis where you talk to some normal users (not devs) and get some feedback and it may help you decide.

Hope it helps and hope I see some projects by you I the near future.

If php is good enough for your needs stick with it, I do like JavaScript for reusing codes in both server and interface.
If u are planning on dev works with a strict timeline stick to php else choose golang or nodejs (my preference).

I have noticed that some devs tend to act that way (ego issue/God complex), but some are v friendly, willing to learn and teach others. However, I have also noticed that most devs tend to work alone, not willing to join up with another group of devs (new startup company, or with friends) but start their own company (most devs prefer seperate companies it seems with majority share) to change the world or join one of the larger companies.
But I think if you do tell your mentor that he is acting that way he might change cause maybe he is not aware that it is frustrating for others.

@zickig yeah flexible architecture and customization workflows are possible (good points). But not having the full scope of the project identified and devs quoting for the identified scope will tend not to prepare for major changes. (and most projects here dont have a service contract as well)

Also even if we can set custom plugins I believe it should not be within the current project budget and timeline.

Agree, and do check the Google I/O talk - The myth of the genius programmer.

Devs tends to want to create perfect systems / best codes. But most of the time we make mistakes and can learn from the most junior staff as well. And we must learn to accept that.

accurate . maybe next time ill show this to the client before starting to collect the requirements (maybe something like this will make them understand)

Need to take a look into nuxtjs. Is it stable? And how is the community?

In my opinion, selection of framework is mainly based on your preference and your skill levels. I would recommend vuejs or reactjs simply because of the active community and dependability (unlike angularjs to angular or to latest angular version).

For me node libraries needs to be better, there are so many dependencies in some libraries that sometimes a small change in a simple library (to do a simple task) may throw errors when building.

@nanl I think devs need to show the importance of requirement analysis stage and not accept any changes after .

For me problem is that some devs accept major changes and when other teams don't accept they will complain, terminate contracts or hold payment.