There seems to be a lot of OOP-bashing lately, which I’m not a fan of, but this article titled Goodbye, OOP makes decent points about the problems with inheritance, encapsulation, and polymorphism. IMHO, OOP still makes sense in certain areas, including GUIs like Java Swing and JavaFX, so I’m not ready to throw it out completely or bash it.
Generating a list of URLs from Apache access log files, sorted by hit count, using Apache Spark (and Scala)
I don’t want to make my original Parsing Apache access log records with Spark and Scala article any longer, so I’m putting some new, better code here.
Assuming that you read that article, I’ll jump right in and say that I use this code to load my data into the Spark REPL:
I just picked up an old college textbook named Applied Numerical Analysis, and curious to see what the Interval Halving method (also known as the Bisection Method) would look like in Scala, I decided to code it up. Considering that Scala is similar to the Java programming language, if anyone else needs the Interval-Halving method in Java, this code can easily be adapted to Java as well.
Yikes, I fixed a lot of the formatting of my "Introduction to Function Point Analysis" tutorial. I didn't realize how terrible the formatting was before. I still need to style it up a bit more and create a print style sheet, but at least you can read it now. Ugh, that was bad.
This page is sponsored by Sleetmute.com: Free Function Point Analysis Software
Here are a couple of notes I just sent someone on how to get started writing a software requirements specification.
They may be a little vague, but I hope they show my intent, or perhaps my frame of mind, when writing a software specification.
Here are two notes on my mental approach when writing software requirements specifications:
Here are a few links that I've been reading today:
- Alice in Use Case Land
- Data Flow Diagrams vs UML Functional Analysis Techniques
- Software development cost estimating tools
Here are a couple of quick links to articles to the Joel on Software site:
I'm heading into three straight days of intense requirements meetings, do I don't expect to offer any more updates until at least Thursday. Have a good few days ...
Here's a link to a sample 242-page requirements document. This is a real world example, full of use cases, requirements, and a few other things.