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”
(text in parentheses added by me)
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 {{{ and }}} 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.
I found this Apollo 11 source code tweet at this url, and the bug report and 100+ comments are here on Gituhub.
As a quick note and a little bit of source code sharing, I wrote the following Perl script to delete all of the binary files it finds in a list of files it’s given. I named this script deleteBinaryFiles.pl, and it should be called like this:
deleteBinaryFiles.pl listOfFilesToLookAt
where listOfFilesToLookAt is a file that contains a list of filenames, with one filename per line.
Given that brief introduction, here’s the source code: