Or it can mean that the engineer is tired of rewriting ORM generated queries into performant queries.
Sometimes it is better to use 'explain plan' once rather than cleaning up a generated sql filled with outer joins, table scans, and difficult to understand variable names.
The ORM code in this case can look more "pristine" but can cause the app to fail in production. If you are using createNativeQuery everywhere, what is the point of an ORM?
80% of the time, the queries the ORM produces are just fine. For the rest 20% left, I code them myself (I think senior engineers now how to distinguish these two scenarios). Now, what I don’t want to code myself is the transformation between rows and objects… that’s what an ORM is for.
The author presented their opinion as broadly stroked general advice and in that context it is poor. And, specifically regarding database/sql, creating a bunch of pointers to scan values into for every query you write is the definition of insanity in all but the most performance sensitive applications. We're talking microseconds (or even nanoseconds in some instances) on an operation typically measured in milliseconds.
You don’t need an ORM for that, though. I’ve used Scany in the past, and it was great. Raw, parameterized SQL that is easy to reason about and easy to scan into your structs:
These things exist on a spectrum of features but they are all mapping tables to objects at the end of the day at the bare minimum. Pedantry around what technically should count as an ORM is not super productive. The fact is that defining a schema in one place and getting a whole slew of features out of that automatically is multiplicative to productivity.
This is the sweet spot in my opinion. I haven't been in the .NET world for a few years but there's a very similar library called Dapper. Best "ORM" I ever used.
Improving the envelope is particularly important for geo heating and cooling. It makes sense to include that in the budget for a geo install.
I had a geo system installed last December (GeoComfort with 3 200 foot wells for a 120 year old, 1600 sqft house).
The system works great except that the point where the aux heat kicks in for my house is 25 degrees F. I am working this year to improve the envelope to reduce the need for aux heat.
I have had a Venta LW15 for a long time, and like it. I have gone through many humidifiers, and the LW15 is the only one that has lasted more than five years and does not require filters. It is expensive, even with cleaning>
It does require regular cleaning, though -- that can be a pain. It pulled minimal power, too.
I have switched to a whole house humidifier this year and I really like not having to change water every day. I am not sure how it will work in the long term.
I don't know if the LW15 has a different mechanism than the LW45, but it shouldn't be difficult to clean. The entire machine literally comes apart (https://youtu.be/-f2FAI70BSk?t=154), leaving only plastic pieces that can be hosed down.
It is probably the same mechanism. The only thing that took time was wiping down both sides of than fan blades.
I would still be using the venta if I didn't have a new geothermal system installed. The ultrasonic humidifiers I had before the venta didn't last more than two years.
Yeah after being an early customer who bought both the mac and iPhone licenses, I felt offended with the new plans/paid upgrades and decided to vote with my wallet.
I prefer the inconvenience of using an old version (which I have a license for) than paying the extorsion price of a paid only update, and with the nonsense of different platforms being sold separately.
I guess they're free to do whatever they want, and I guess sadly nowadays subscriptions do make sense from a SaaS/Developer POV, I just can't fathom it as consumer.
Sometimes it is better to use 'explain plan' once rather than cleaning up a generated sql filled with outer joins, table scans, and difficult to understand variable names.
The ORM code in this case can look more "pristine" but can cause the app to fail in production. If you are using createNativeQuery everywhere, what is the point of an ORM?
reply