Engineers Don't Solve Problems (2018)

Post by gen220 » Tue, Jul 30, 2019, 11:08 PM UTC

Grimm1 wrote: post #50

la_barba wrote: post #48

Earlier quoted context omitted.

Sure, but there are several arguments for doing code reviews/QA/etc that are already convincing. Its interesting.. but I guess I don't see how we can use this new way of looking at code transformations to our benefit.

The thing is even if QA and testing is fine now as the business or domain needs evolve over the years just the fact the context has changed can lead that code to be a liability. I'm kind of tired from work so I hope I can make my point: As an example, let's say you have a billing system that allows anonymous payment that works fine it has thus far been an asset, but new legislation is released that states that all pu…

Interesting. I like this a lot.

All Code implements a process. If the requirements for that process change (due to shifting regulation, for example), the process is a liability until it adapts to those requirements, at which point it can again become an asset.

If a process has no artifacts for implementing it, it can’t be a liability.

That’s why we see so many companies offering regulatory compliance as a service, in the healthcare space for example (AHIP, NIPR). Because if every insurer had to write code that integrated with regulation, they would be writing a lot liability. Using a vendor allows them to offset that liability to a third party, whose whole purpose in existence is to maintain a nice liability:asset ratio.

Perhaps we’ve found a utility for my theory, in contributing to the build vs buy discussion :)

Post by proc0 » Thu, Aug 01, 2019, 5:52 PM UTC

rramadass wrote: post #47

proc0 wrote: post #34

I've been to Mexico DF once. I visited downtown and there was a literal mountain of garbage in the central plaza (easily two stories high). Maybe Mexico City engineers are shit (pun intended), at least article implies it as it's the only example they give.

You are being flippant. The Mexico City problem is the author's research study (do a little bit of googling on the author) and therefore it is the example he knows best. The article also does not denigrate Mexican Engineers; you are reading it through your own unwarranted biases. And finally, just so you know this is a problem with all major urban centers throughout the world. Here is a scary report on India - https:…

To be clear, I was only talking about this particular problem, and engineers who might deal with it, not engineers in general. That was my experience when I visited, and apparently at the time the problem was not being dealt with properly. India is probably not a good example of how this happens in a lot of cities either, but I'll grant that Mexico DF has location problems from being on top of a lake etc.

Re: Engineers Don't Solve Problems (2018)

Re: Engineers Don't Solve Problems (2018)