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?
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.
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.
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.
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?