The image shows how Scala 3 (Dotty) enums expand into other Scala code. I thought that was interesting, and you can learn more at this URL.
The first thing you do is create a new Gradle/Java project with these commands:
mkdir MyProject cd MyProject gradle init --type java-application
With that project created you can begin creating some Java/RxJava code.
If you like reading PDFs of presentations, here’s a PDF from a Twitter employee named How We Built Tools That Scale to Millions of Lines of Code.
The source code for Beginning Java Game Development with LibGDX is at the URL shown.
“Show me your flowcharts (source code), and conceal your tables (domain model), and I shall continue to be mystified; show me your tables (domain model) and I won’t usually need your flowcharts (source code): they’ll be obvious.”
~ Fred Brooks, “The Mythical Man Month”
Sometimes I think working with LaTeX is like sitting at the controls of the Nebuchadnezzar in The Matrix.
I don’t have any major conclusions to share in this blog post, but ... what I was curious about is how Scala implements “lazy val” fields. That is, when the Scala code I write is translated into a .class file and bytecode that a JVM can understand, what does that resulting code look like?
As a quick note, if you want to embed a Scala source code example in your Scaladoc comments, just put the source code block in between
}}} characters in your comments, as shown in this example:
This link has the source code for the online book, The Busy Coder's Guide To Advanced Android Development.