Exactly, this is a pretty bad sign for a senior dev, to just blurb out a number. What is the connection used for? End users, a backoffice tool, or a batch process? then he should have asked: what is our SLA? What's in the DB, how big are the objects, the queries? How frequent are they?
Even so, I wouldn't venture any number if you don't do some profiling or at least some tests with the most common data, and with edge cases. It can be anywhere between milliseconds and full seconds, maybe more?.
Reminds me of an interview once, I asked: the website is slow, you're in charge of it, what do you do? He just said "buy more servers"...slow down there, Rockefeller.
Of course it does, Christianity must have appeared progressive in the first few centuries...now it's as conservative as you can get, at least in the Western world.
Eugenics and communism were both seen as progressive at the time, at least by their supporters. The conservative take on communism was we should preserve the existing order, that the progressives wanted to disrupt and replace.
This makes no sense, by definition it was a progressive movement at the time: for as long as we know, people drank alcohol, and then you get these progressive people (many of them women) trying to change the society for the better. It was a failed progressive policy, that if it stuck we would have seen it as a good thing in retrospect and call it progressive - just like banning opium in cough medicine.
Conservative means keeping the old way, in this case: keep drinking alcohol freely.
One of the the points of "clean code" is to make it easy to find the hotspots and optimize those. Write the codebase at a very high level, plenty of abstractions etc. and then optimize the 1% that really needs it. Optimizing a small piece of software is not going again clean code, on the contrary, it re-enforces it: you can spend the time to optimize only what is necessary.
It's like we're reaching the times when we should again start thinking more for ourselves, given the information at hand: make assumptions, try to prove them, try a reductio ad absurdum etc.
But unfortunately people's brains are fried because of the constant social media bombardment.
Even so, I wouldn't venture any number if you don't do some profiling or at least some tests with the most common data, and with edge cases. It can be anywhere between milliseconds and full seconds, maybe more?.
Reminds me of an interview once, I asked: the website is slow, you're in charge of it, what do you do? He just said "buy more servers"...slow down there, Rockefeller.