From 4204132308748ba6ab642946d0d350a2b5df0f1b Mon Sep 17 00:00:00 2001 From: Rawley Date: Wed, 3 Jan 2024 19:32:39 -0600 Subject: [PATCH] add 2024 --- 2024.html | 59 +++++++++++++++++++++++++++ jpa-hibernate-stupid-performance.html | 4 +- 2 files changed, 61 insertions(+), 2 deletions(-) create mode 100644 2024.html diff --git a/2024.html b/2024.html new file mode 100644 index 0000000..d256baa --- /dev/null +++ b/2024.html @@ -0,0 +1,59 @@ + + + + 2024 + + + +
+ << back +

2024

+

+ 2023 was a good year, but now it's 2024. Here's some of my technical plans for 2024. +

+

+ NOTE: These are in no particular order. +

+

Technology I plan to use in 2024

+ +

Technology I want to learn more about in 2024

+ +

Technology I might learn in 2024

+ +

Technology I won't learn in 2024

+

+ It's not that I hate the following, it's just that they don't really interest me, + or the people behind them do not seem to value people using them (ala Rust). +

+ +

Have a safe an fun 2024.

+
+ + diff --git a/jpa-hibernate-stupid-performance.html b/jpa-hibernate-stupid-performance.html index ed36c16..42f21c5 100644 --- a/jpa-hibernate-stupid-performance.html +++ b/jpa-hibernate-stupid-performance.html @@ -50,8 +50,8 @@ public interface ARepository extends JpaRepository, JpaSpecificationExe

After applying these, the query time went down from 15 minutes to ... *drum-roll* ... 3 seconds. So please, for the love of all that is computationally efficient, force your JPA - to use 

OUTER JOIN
, or even roll your own SQL, ORM's really are one of the biggest trade-offs, and they really can bite you. This is why tend to - stay in the 
DBI
universe when I write Perl. It's funny shocking Ruby on Rails and Java developers with my ~15ms queries :D + to use OUTER JOIN, or even roll your own SQL, ORM's really are one of the biggest trade-offs, and they really can bite you. This is why tend to + stay in the DBI universe when I write Perl. It's funny shocking Ruby on Rails and Java developers with my ~15ms queries :D