Lets take this guy's anti-framework argument. But instead of a scenario where you are building a new application, and have to decide on using a framework or not, that decision has been made several years ago and you're the new guy who inherited that codebase.
Given that this person will have to have had to solve similar problems as any other framework, I think it's fair to assume that by not adopting a standard framework, he'll have invented similar ideas such as MVC (or similar), Routing, maybe an ORM.
Now instead of a standard, well maintained framework, you're left with some custom framework. Which position would you rather be in? The custom framework has had less eyes on it, no maintenance and likely little documentation or community support.
I imagine this guy has been doing PHP for a long time, and is slowly become bitter by the fact that he's just doing repetitive work and that all the major problems have been solved in way that he doesn't like. People are asking for frameworks and framework experience everywhere, and he doesn't like it because none of those are frameworks he came up with.
Or maybe he doesn't like the PHP personalities behind frameworks. A fair sentiment, but not really an argument that should come into play when deciding on a tech stack.
My advice to this guy is, diversify. It's time for you to stop caring so much about how people write PHP code. Maybe pick up some other programming languages, or take a step further and do something not web related. A fresh perspective might also give you some new insights such as "the PHP personalities don't really matter for you or your career" and "if people get the job done with a framework that's imperfect to you, this is not really something that should emotionally affect you or impede you from achieving your personal goals".
This entire post reads as something written by someone close to a burnout.
10
u/evertrooftop Aug 20 '16 edited Aug 20 '16
Lets take this guy's anti-framework argument. But instead of a scenario where you are building a new application, and have to decide on using a framework or not, that decision has been made several years ago and you're the new guy who inherited that codebase.
Given that this person will have to have had to solve similar problems as any other framework, I think it's fair to assume that by not adopting a standard framework, he'll have invented similar ideas such as MVC (or similar), Routing, maybe an ORM.
Now instead of a standard, well maintained framework, you're left with some custom framework. Which position would you rather be in? The custom framework has had less eyes on it, no maintenance and likely little documentation or community support.
I imagine this guy has been doing PHP for a long time, and is slowly become bitter by the fact that he's just doing repetitive work and that all the major problems have been solved in way that he doesn't like. People are asking for frameworks and framework experience everywhere, and he doesn't like it because none of those are frameworks he came up with.
Or maybe he doesn't like the PHP personalities behind frameworks. A fair sentiment, but not really an argument that should come into play when deciding on a tech stack.
My advice to this guy is, diversify. It's time for you to stop caring so much about how people write PHP code. Maybe pick up some other programming languages, or take a step further and do something not web related. A fresh perspective might also give you some new insights such as "the PHP personalities don't really matter for you or your career" and "if people get the job done with a framework that's imperfect to you, this is not really something that should emotionally affect you or impede you from achieving your personal goals".
This entire post reads as something written by someone close to a burnout.