Android Expert·Oct 16Create Now, Create on First Touch, Create When I Say So: What val, by lazy, and lateinit Really DoWhy “lazy means initialize later” fails interviews, and the production bugs each Kotlin property form hides behind its syntax.
Muhammad Ali Dev·Aug 8Lazy initialization in KotlinIn Kotlin, lazy initialization is a design pattern that delays the creation of an object or computation of a value until the exact moment…
inside Nikita's Mind·May 31Java Finally Fixes Lazy Initialization: Meet LazyConstantOur payment service had just restarted after a deployment. For 43 painful seconds, every request that hit a critical @Lazy bean caused a…
Varun Tewani·Mar 22Part 7 — Lazy Loading vs Eager Loading in Hibernate (And Why LazyInitializationException Happens)Introduction
InDevSpherebyAsian Digital Hub·Jan 14Stop Bootstrapping Everything → Lazy Initialization Makes PHP FasterYour PHP app wakes up every request like it’s preparing for war. Containers loaded. Services wired. Config parsed. Providers registered.
Syed Ali – Senior Android App Developer·Dec 22, 2025Android App Startup Time Optimization: Complete Guide for Faster LaunchApp startup time is one of the most important performance metrics in mobile development. When your app launches slowly, users immediately…
Muhammad Omer Shafique·Aug 13, 2025Lazy Initialization in Python — Real-World Applications & Deep DiveIntroduction
Dilip Patel·Jul 18, 2025lateinit vs lazy in Kotlin: The Tale of Two InitializationsIn the magical world of Kotlin, two charming spells help developers manage variable initialization: lateinit and lazy.
InsoftAai Blogsbyamol pawar·Jun 19, 2025Lazy Initialization in Kotlin Explained: Boost App Performance with Minimal CodeEver heard the phrase “don’t fix what isn’t broken”? In coding, a similar mindset applies: don’t load what you don’t need. This is where…
Dilip Patel·Jun 8, 2025How I Stopped Worrying and Started Using lateinit in KotlinWhen I first started writing Kotlin, I loved how it handled null safety. Finally, no more surprise NullPointerExceptions — or so I thought.
