Elizabeth
@liz.ski
Opinions and thoughts expressed on this account are solely my own and are not representative of my employer. she/her/hers
Software Engineer📍Boston
Software Engineer📍Boston
Reposted by Elizabeth
Updating from #Java 21 to 25 is a smooth experience. Mostly - a few details changed: annotation processing, inner class constructors, file operations, the removal of old technologies... Watch our first #RoadTo25 video to learn everything you need to know:
www.youtube.com/watch?v=9azN...
www.youtube.com/watch?v=9azN...
How to Upgrade to Java 25 #RoadTo25
YouTube video by Java
www.youtube.com
August 26, 2025 at 9:17 AM
Updating from #Java 21 to 25 is a smooth experience. Mostly - a few details changed: annotation processing, inner class constructors, file operations, the removal of old technologies... Watch our first #RoadTo25 video to learn everything you need to know:
www.youtube.com/watch?v=9azN...
www.youtube.com/watch?v=9azN...
Every so often, I think back to this presentation about the legacy of null.
I first watched this back in college, and it is absolutely fundamental to how I (try to) structure my code to this day, especially when a language has little-if-any null safety built-in.
I first watched this back in college, and it is absolutely fundamental to how I (try to) structure my code to this day, especially when a language has little-if-any null safety built-in.
Null References: The Billion Dollar Mistake
Tony Hoare introduced Null references in ALGOL W back in 1965 "simply because it was so easy to implement", says Mr. Hoare. He talks about that decision considering it "my billion-dollar mistake".
www.infoq.com
August 7, 2025 at 5:49 PM
Every so often, I think back to this presentation about the legacy of null.
I first watched this back in college, and it is absolutely fundamental to how I (try to) structure my code to this day, especially when a language has little-if-any null safety built-in.
I first watched this back in college, and it is absolutely fundamental to how I (try to) structure my code to this day, especially when a language has little-if-any null safety built-in.
👀 Incredibly interesting trial. I always enjoy seeing expectations thoroughly smashed, and this is no exception.
We ran a randomized controlled trial to see how much AI coding tools speed up experienced open-source developers.
The results surprised us: Developers thought they were 20% faster with AI tools, but they were actually 19% slower when they had access to AI than when they didn't.
The results surprised us: Developers thought they were 20% faster with AI tools, but they were actually 19% slower when they had access to AI than when they didn't.
July 10, 2025 at 8:56 PM
👀 Incredibly interesting trial. I always enjoy seeing expectations thoroughly smashed, and this is no exception.
Reposted by Elizabeth
