287 karma · joined September 14, 2016
As it stands, with what I've seen and heard about microservices, I'd say the best way to deal with micro service anything is to use a monolith 90% of the time and for the rest of the time make sure your micro service could stand as it's own SAAS if given enough love.
Not a direct solution to your problem but might be an indirect one.
PHP is a language among many languages which can be used on the backend. JS, Java, C#, Python, Ruby, Elixir,hell even Perl has a web framework. Not really a fair comparison.
I would love to see a sample of this code.
I've seen more issues because of nonsense like that, or people insisting that code should be DRY and making ridiculous mental contortions in the name of a three letter acronym, or personal taste (the amount of fashion in software development is insane) but I've yet to see a project truly fail because someone cobbled something together quickly, and introduced tech debt. So far anyways.
Also, as an aside, I wouldn't call DRY a 'rock solid foundation' of programming. People do some weird contortions to make code DRY that end up causing my harm then good. Separations of Concerns is far more important. DRY is fine when applied within the scope of a feature, but not cross features. Otherwise you end up playing wack-a-mole when you fix a bug in one place only to make a new one somewhere else.
It certainly does make sense that intelligence has an effect on social-economic status, since intelligence is valuable.
How do you suppose we confront "the IQ problem"?
This is very different than having your father die while you're young and promising to be the woman of the house and take care of your sick mom and baby sister.
Some people are poor because of their situation and some situations are more difficult to escape than others.
Some people are poor because of their habits and inclinations and they just don't change those habits (for one reason or another), so they stay poor.
The issue here is developers don't have a sense for economics. Diminished returns, marginal utility, and opportunity cost should be studied by ALL.
The real take away here is that real (objective) mess hurry-hackjob code bases are good enough to last many years so you probably did the right thing.