One of my favorite things about the Android team is that we are all so enthusiastic about the technology we work on and about helping developers use it that we push information of all kinds (libraries, articles, samples, codelabs, videos, tweets, blogs, etc.) constantly and independently. Which is… awesome; I much prefer this model to one where everything goes through some sort of corporate funnel, resulting in a slow drip-drip-drip of formal, company-sanctioned artifacts.
Checked exceptions are a concept that exist only in the Java compiler and are enforced only in source code. In Java bytecode and at runtime in the virtual machine you’re free to throw checked exceptions from anywhere regardless of whether they’re declared. At least, anywhere except from a instance created by a Java Proxy.
Jetpack Compose is declarative component-based UI runtime for Android. With compose you can build your UI with functions in Kotlin to easily “compose” what your UI would look like.
Represents an operation that accepts a single input argument and returns no result. Unlike most other functional interfaces, Consumer is expected to operate via side-effects.
On July 19th, 2019 Capital One got the red flag that every modern company hopes to avoid - their data had been breached. Over 106 million people affected. 140,000 Social Security numbers. 80,000 bank account numbers. 1,000,000 Social Insurance Numbers. Pretty messy right?
