Absolutely would call this a tech culture problem. Just like e.g. not writing tests because management doesn't want to spend time on that. Doesn't mean that individual developers are to blame for this kind of decision, but it speaks for the overall culture of the tech org. Yes, often driven by business objectives.