I like your honest tone and upfront attitude. As someone who left the industry because of this type of thinking I’d like to say it’s half-correct.
Patterns and anti-patterns are something which help make useful software. Not only architecture patterns like MVP or MVVM, but design patterns like a factory or builder etc.
It’s my belief there are also developer patterns and anti-patterns. The slacker pattern isn’t an anti-pattern, but often can incur the team pattern of daily iteration vs. bursts of work.
Most of what you’re discussing seems slated towards the anti-pattern of “words without code”. Which personally I believe is also an anti-pattern. The code must come, otherwise it’s not work, right?
But when you talk about these people “they hate tests” “doesn’t want to do X and Y perfunctory thing” your team isn’t presenting the value of those things first and foremost. Have you tried putting a “sheep” and a “slacker” together?
I graduated from Bob Jones University. During my time there, BJU was Nationally Accredited and not Regionally Accredited.
This didn't personally affect me very much, but I know of many people who had difficulty getting into graduate school or professional work because of this.
A degree from a nationally accredited university limits your options. I'm not saying you'll be completely screwed if you get it, but not as many graduate schools will consider you.
I think what they are referring to is that Postgres and most other databases were built in the before time, the long long ago when every connection was a process and you limited concurrency of connections in the configuration file. If you have a 1000 concurrent calls on lambda you aren't going to be able to have them all talking to the same database at the same time. You'll run out of connections and the application will crash. Same reason you see this happen to PHP web applications when HN or Slashdot is pointed at them and they say they can't connect to the database. They have hit the concurrency limit. Connection pooling solves this problem but currently requires another layer between the application and the database.