Hey @volklub,
Thank you for your great service to the car community.
What would you suggest if the budget is 10L, preference is diesel for mostly city drive. Currently exploring Tata Altroz Diesel, Mahindra XUV 3XO Diesel, Kia Sonet Diesel.
You can view the (limited) results here
https://t.co/IHn3WtZs06
I will be adding more to it in coming days.
All results have information regarding how long it took, how much API costs $$$ it incurred, and exactly which 'mode' of the tool was used.
๐ง Software Engineering in a Nutshell
At its core, software engineering is about taking a large problem, breaking it into smaller manageable problems, solving those individually, and then integrating the solutions to address the original challenge.
Sounds simple, right? ๐
In practice, the real difficulty lies in knowing how and when to split a problemโand when not to. An even bigger challenge is understanding the trade-offs between different ways of integrating those smaller pieces and choosing the one that is feasible in your context.
Techniques such as Microservices, Modular Monoliths, and Package-by-Feature help us split large systems into smaller parts. Techniques like CQRS, Event Sourcing, and Event-Driven Architecture help us integrate those partsโeach with its own trade-offs.
๐ฏ The true value of a senior developer is in anticipating the challenges that may arise down the road and choosing an approach with a clear understanding of its trade-offs rather than just following trends or defaults.
@Hiteshdotcom As cliche as it sounds but "it depends".
User A, he is battle tested and he has faced real world problems.
User B, has better knowledge and ability to learn, presuming if actually knows what he has done and how under the hood things are working (not just a vibe coder).
Virtual Threads: Introduced in Project Loom, are lightweight and can be created in large quantities. They are ideal for I/O-bound tasks because they consume fewer resources compared to traditional platform threads, allowing for better scalability and efficiency. (3/3)
Things about Threads:
1. CPU Intensive Tasks: CPU-intensive tasks are limited by the number of cores available. Java threads performing CPU-bound operations will be constrained by the physical cores, as they need to perform computations directly on the CPU.(1/3)
High I/O Response Time: Threads handling I/O operations are often waiting for external resources (like disk or network), so they don't need constant CPU time. While one thread is waiting for I/O, other threads can utilize the CPU, improving overall system throughput. (2/3)
JDK contains โ JRE contains โ JVM
The Java program, written by the developer using libraries like java.util.* (which is part of the JRE), is compiled by the JDK using javac, generating platform-independent bytecode. JVM does bytecode execution, memory management, GC etc (2/2)
Note to self:
- JVM: executes byte code does memory management and garbage collection
- JRE: provides run time environment by providing core libraries like java.util.*. Collection framework is also part of it.
- JDK: it has compiler and debugger and JRE (1/2)
๐ The Memoryโs Eternal Dance: Java Threads & the Java Memory Model
Java multithreading is powerful but comes with its own set of challengesโrace conditions, memory visibility issues, and thread synchronization.
https://t.co/t68oWltYgD
@sivalabs@rajadilipkolli indeed great reference point for someone who wants to see how production ready code should be written. Bookmarked it. definitely gonna refer in future.