Not if all the slots are booked up online. Look at what happened with driving tests. They moved it online and all the tests are booked by bots and sold to the highest bidder.
It likely won’t meet European safety standards so there’s a whole market it will just miss. But maybe it’s too big to be practical in European cities anyway.
I’ve had ads for drugs, cloned credit cards and devices for stealing cars with keyless entry all in the last month on a major social network.
Reported, but they don’t seem to care.
Parties are not the problem. Damages, illegality and annoying the neighbours are what they should be trying to detect. It's a shame that people planning a small get together with friends should have to suffer because some idiots like to trash places.
I've definitely seem benefits from working in open plan. Sometimes it's helpful to overhear what others are doing because maybe they're lacking some information or maybe that thing has already been done elsewhere. Does a fresh graduate with no experience really want to be in an environment where everyone is shut in an office?
Equally, sometimes it's better to be quiet. Sometimes, quiet can be at home but sometimes homes are not quiet or uninterrupted.
Flexibility would be great, but I think a private office will always be seen as more prestigious, so those with that facility are unlikely go give it up so sit in a cube / open plan with the team, even where that would actually be beneficial.
My views are my own and as such I do not disclose my employment or otherwise on here.
I did think twice about posting it, as I don't usually but it's relevant and i might be helpful so why not? If you don't like it, thanks for the downvote.
I’m sure you know this but the reason for taking computation off the database is that it’s much easier to horizontally scale a stateless middle tier than it is to scale a sql database.
Some DBAs I’ve worked with even advocated for taking sorting off the database. I wasn’t entirely convinced by that one.
My server side language in this case was Scala, so it wasn’t slow, just memory hungry.
I think it started as pretty much crud and then just grew features that were more complex backend logic. But I was the one brought in to fix it, not the original architect - he had left the company at this point so I don’t know the whole history.
The only postgREST app I ever worked on was awful. Why? Because like most of these ‘simple’ frameworks it’s only simple until your requirements get complicated. Then the original authors had to resort to writing a ton of stored procedures on the database to get back the results they wanted and that led to scalability problems. The solution, as always, is go back to SQL.