Thats context my guy. You an old azz nikka who makes 127 which is great. Like you said you have mad experience and you are an architect if youve done it before. As a developer you really gotta boss up to get paid like directors and shyt from my experience. Youve pretty much bossed up so you are not the norm. Im an RTE/Program Manager by the way.
How many oval shaped wheels have your guys manufactured?
Breh, exactly. These guys need to think about it from the perspective of someone running a business. You have to make tradeoffs. A framework may be more overhead, but it helps the whole team to speak a common language. It helps with hiring, because if a person knows the framework you know they can hit the ground running or be changed out with someone else relatively easily. It cuts down on boilerplate and reinventing the wheel. It helps with problem solving because millions of developers have already tackled the problem you're facing. For the vast majority of applications where high performance isnt crucial, a framework as robust as spring is fine. And even then, high performance stuff can be done from within it. There is a reason the shyt is ubiquitous in the industry. (Not saying there are no issues with it, obviously.)
Breh, exactly. These guys need to think about it from the perspective of someone running a business. You have to make tradeoffs. A framework may be more overhead, but it helps the whole team to speak a common language. It helps with hiring, because if a person knows the framework you know they can hit the ground running or be changed out with someone else relatively easily. It cuts down on boilerplate and reinventing the wheel. It helps with problem solving because millions of developers have already tackled the problem you're facing. For the vast majority of applications where high performance isnt crucial, a framework as robust as spring is fine. And even then, high performance stuff can be done from within it. There is a reason the shyt is ubiquitous in the industry. (Not saying there are no issues with it, obviously.)
Got management looking at them like
We really need to do some self reflection sometimes, I agree.
Spellcheck dumbowhy would you think a developer would make bread like a director over developers?
Breh, exactly. These guys need to think about it from the perspective of someone running a business. You have to make tradeoffs. A framework may be more overhead, but it helps the whole team to speak a common language. It helps with hiring, because if a person knows the framework you know they can hit the ground running or be changed out with someone else relatively easily. It cuts down on boilerplate and reinventing the wheel. It helps with problem solving because millions of developers have already tackled the problem you're facing. For the vast majority of applications where high performance isnt crucial, a framework as robust as spring is fine. And even then, high performance stuff can be done from within it. There is a reason the shyt is ubiquitous in the industry. (Not saying there are no issues with it, obviously.)
Got management looking at them like
We are literally saying the same thing.
Why are you intentionally misinterpreting what I am saying? Or is it unintentional? Wtf
