Mental attack? What did your brother do?

Get a load of this guy, thinking containers are more of a hassle than VMs!

There’s a million layers of nuance to every situation.

Sure, but if you don’t escape the \ then you likely won’t even be able to get the name into the first system. You need the name to contain \n so that it gets passed correctly to other systems, otherwise his name may wind up just being “John” .

Probably have to escape it so it will work properly: John\/nDoe

A foot and a half of Subway sandwiches and two bottles of pop is $29 in my country

Sure, but how many foods are we talking here? This sounds like probably <20 rows on a sheet, with columns for ingredients.

Tracking a single cat doesn’t seem like DB work

Why wouldn’t a simple spreadsheet and some pivot tables work?

8 billion stupid monkeys

There’s not much cost with S3 object. It’s just a file system in Linux, and replication is a protocol standard.

Use object storage for media and backups, then use s3 replication to put a copy somewhere else.

Ask it to make a function, then do some other function, then make them work together etc. Making it write a lot in one go won’t work. It’s more pair programming than having it write for you.

I use it to write code, but I know how to write code and it probably turns a week of work for me into a day or two. It’s cool, but not automagic.

Because of nuclear non-proloferation treaties. You can’t run a “recycling” program without also being able to make plutonium for bombs.

If you have enough users and systems that this is a problem then you should be centrally managing it. I get that you want to inventory what you have, but I’m saying that you’re probably doing it wrong right now, and your ask is solved by using a central IAM system.

It sounds like you’re probably looking for some kind of SAML compliant IAM system, where credentials and access can be centrally managed. Active Directory and LDAP are examples of that.

Well, 1ms of latency is 300km of distance, so unless you have something really misconfigured or overloaded, or you’re across the country, latency shouldn’t be an issue. 10-20ms is normally the high water mark for most synchronous replication, so you can go a long way before a protocol like DNS becomes an issue.

Go to the interview and get the practice, or try something new. Make outrageous demands, tell them they do things wrong etc.