As one of the 60%, its not about deity worship, but more about a sense of stability. Especially where the monarchy has effectively zero involvement in daily life. When looked at from a P&L basis the crown is pretty good value. Certainly compared to all the alternatives that have been tried.
Replace the commons with PR (STV on constituencies c. 6 times the size), replace the lords with people who have been in the commons for 20 years. Ensures fresh blood in the commons and removes the need to pander to the short term elections in the lords.
I think there's value in having an unelected second chamber, because the lords are freer to broach unpopular but important subjects. Nevertheless imo it would be much better to have them randomly chosen from society.
I had a large tree in the garden of my previous house. I used to make significant quantities of medlar jelly every year and give the jars away to family and friends. The house was 400 years old, but the tree was significantly younger.
> Davis Adams, who works at Honda and drives an S2000, told me about a Lotus Elise he used to own that had a motion sensor. "If you locked the door, and moved your hand in the open air," he said, "the alarm would go off. So if you left a dog in the car, or someone leaned in the open convertible to look, it'd trigger the alarm."
20 year Lotus Elise owner here. I have had thieves slash the roof and and steal items. And I would never leave a dog alone in it.
These corporate phishing test emails come from phishd and similar services. Very easy to fingerprint them with smtp headers and set up mail rules to bounce them to your corporate phishing sink...
For those that have access to Menlo Security’s safe browsing saas service, it’s worthwhile analysing what client side JavaScript can tell you about the runtime environment. Device aspect ratio is just one of the strange things reported.
Perfect example of the trough of disillusionment. The ORM slope of enlightenment comes when you realise the power of the unit of work, not just a single query. But that was then, and microservices mean we no longer use large units of work. So ORMs without complex UoW make less sense.
This is I think primarily related to transaction boundaries and tracking changes. You can read https://www.martinfowler.com/eaaCatalog/unitOfWork.html as a starting reference. I haven't heard this phrase much lately to be honest. ;)
In 'typical' Java application (since many comments here as well as the original article mentions Hibernate...) you will likely use annotations like @Transactional to mark your transaction boundaries (likely with default propagation and isolation levels...) and then Hibernate will track any changes ('dirty checking') to objects you asked him to fetch and then at the end the transaction Hibernate will issue whatever DML commands (INSERT, UPDATE, DELETE) needs to be issued in an appropriate order.
In a galaxy far, far away i.e. before Java 1.5 instead using @Transactional you would maybe use (write) some object like TransactionManager which provides an execute() method that receives a block of code in a form of a interface implementation (no closures for you!). This part is relatively straightforward. Tracking changes in any semi-automatic way was always messy...
