This presentation discusses things that affect (CPU bound) performance of Java code. A key message is that Java developers DO need to worry about memory, even if garbage collection rarely is a problem.
Learn to write Java code faster so that you can experiment more with the design and find the simplest solution to your problem.
Have you ever gone through a Java technical interview only to realize how horribly broken the process is? Do we really need to know the Big-O runtime of our code on a day-to-day basis, or is there a more practical way we can test this knowledge?
Do you build Java systems that can be hacked? Want to lower those odds? In this presentation, you will learn the basics of security vulnerabilities and evasive coding maneuvers that can make your software more secure, every time.
When Java developers and operations are asked what their biggest performance bottleneck is, it is rare that memory inefficiency comes up as an answer. Unfortunately, this runs counter to the observation that 60% of all applications are memory-inefficient.
‘Entropy is the price of a Structure ‘. But sometimes, the price turns too high to pay. Is your Java codebase turning untestable, unreadable, and unmaintainable? Does your costs to add new features aren’t meeting the ROI?