It seems that most people miss the point. The software we create is a direct reflection of the problem that is being solved. If you are hired by a small 3 pers

It seems that most people miss the point. The software we create is a direct reflection of the problem that is being solved. If you are hired by a small 3 person startup company to help them build an MVP on a budget for an untested business model, then you _should_ expect garbage, because that is precisely what is being asked/paid for. Writing systems software for flight controls or similar use case where loss of life might occur? Well then you are _still_ being persuaded by a project manager and senior leadership to find a balance between cost and quality... but since lawsuits get more expensive when lives are lost, you have more quality control (yes, ethics should be more important than money, but that is not the case). The _business_ makes the bulk of the decision on quality and safety, NOT the person in front of the keyboard. In most cases (web, e-commerce, SaaS, games, etc.), there is more business value to be had from releasing buggy garbage _fast_ rather than thoughtful and well tested features. You can always roll out a fix next sprint. Our profession _is_ full of immature practitioners, and it has a long way to go if we are going to fix this, but there are powerful market forces at play currently and for the vast majority of us it makes more sense to _swim with the current_ and extract as much value from your career as possible... and if we can be spoiled brats that demand more vacation and free food/drinks, why not? It's difficult to say which is better, 20 years ago we were more professional, but today we have a lot more leverage. I miss the professional attitudes and behaviour, but I've gotten used to the outsized compensation and easy job market, and in all honesty, wouldn't turn back. ¯\_ (ツ)_/¯