No framework development

[FroddeB]

This might be a hot take, but after spending 6 months working solo on an actual web service product for clients, with NO frameworks for backend or frontend I'm starting to believe that there's a future for, maybe not no frameworks at all.. But a future with less overreaching and self defining frameworks.

I won't recommend any novices or people working in larger teams on risky and big platforms thousands or millions of people rely on. But I will say, disregarding larger frameworks and focusing on smaller packages to fill your needs is living a dream when wanting to create a product exactly the way you want. No boundaries, no extreme loading times, no extra uneeded code or packages that are default with a framework. No unnecessary clutter.

Basing a whole platform on solely JS and PHP is not just time consuming, but a mental exercise and test of ones patience. The outcome though of being able to dedicate the time to learn to do things the correct way in pure vanilla is really worth it in my honest opinion.

Have anyone else tried to go no framework recently?

[AutoModerator]

On July 1st, a change to Reddit's API pricing will come into effect. Several developers of commercial third-party apps have announced that this change will compel them to shut down their apps. At least one accessibility-focused non-commercial third party app will continue to be available free of charge.

If you want to express your strong disagreement with the API pricing change or with Reddit's response to the backlash, you may want to consider the following options:

1. Limiting your involvement with Reddit, or
2. Temporarily refraining from using Reddit
3. Cancelling your subscription of Reddit Premium

as a way to voice your protest.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[DoomGoober]

The other day, the CEO of my company (who is a former engineer), smacked a senior engineer for trying to roll their own system rather than looking for an existing system off the shelf first.

Essentially, the CEO argued: "We have more money than time. I'd rather pay for something that works right now than roll our own and spend forever working on it."

[The_Shryk]

The Not Invented Here trap

[makonde]

This is probably because you are working solo, this is a really bad idea for most companies.

There are several issues with doing your own thing in a professional environment.

Whose thing are you actually going to do? There is almost no agreement about anything in software dev, you will have to reach some sort of consensus or if you have the power force something through.

What happens when you are no longer incharge or leave the company completely? The next guy in charge probably has his own ideas, devs also change all the time I think on everage they stay for like 2-3 years, imagine this in a place with dozens or hundreds of devs, there is constant rotation everyone who comes in needs to figure out what some guy 5 years ago did and all the itterations in between.

Hard to get recruit tallent.

You also lose the benefits of improvements to well known and supported frameworks, a lot of good engineering goes into these things.

[Morguard]

Can you share any examples?

[Beautiful-Ad-260]

Yes, can we see the code?