17 Jan


Welcome to Standard Operating Procedures 4 Java (SOP4J). The purpose of this blog is 3-fold:

  1. Provide an opinion on the technology or method to use to accomplish a given task.
  2. Provide complete code examples that people can comment on and submit patches to.
  3. Serve as a reminder to myself for how I figured out some difficult or intricate piece of code.

Why create such a blog? Simply because I could not find something that accomplished these tasks already on the web. Stack Overflow is great for #3. You can search for people who have had similar issues and what they did to get it to work, but it lacks complete code. Also, you’re often looking for advice on what technology to chose and while blogs/sites will review and compare technologies, they won’t necessarily provide you will full code examples to help you get started with the technology they recommend.


The opinions I provide on this blog are from my own personal experience as a Java programmer and a submitter to several Apache projects. I’m sure people will disagree with the opinions I provide, and that is fine… hopefully it will spur discussion in the comments and make us all better programmers. Also, there is often more than one way to do something; however, the point of this blog is to provide you only one way to do most things, and provide enough code in the examples for you to accomplish your task with the technology recommended.


Nothing is more frustrating than seeing a snipit of code that is missing import statements or does not include the version of the dependency used. To avoid all of this, all source code examples will be posted on my GitHub account. You can easily browse the code online without needing to download all of the source (I hate when I have to do that only to find it’s not what I needed). Because the projects are complete, you can run them yourself or use it as a jumping-off point for your own code. All code will be released under the Apache 2.0 license so you’re free to do whatever you’d like with it, but in accordance with that license you must provide the Apache 2.0 license for any derived works (I’m not a lawyer, that’s just my understanding). Also, because the code is on GitHub you’re free to fork it, make changes/improvements, and then submit a pull request. This way we can all become better programmers as I’m well aware I don’t have all the answers.


I’m not delusional. The chances this blog has main-stream success is slim to none. Therefore, if no one else reads this blog, at least it will stand as a reference for myself to remind me how I accomplished some intricate task.


This is my first post in what I hope will be a series of posts. If there is any particular topic you’d like see, please use the comments section below. Thanks for reading…

Leave a Reply

Your email address will not be published. Required fields are marked *