Friday, August 29, 2014

Apache Tomcat tips for servers

1. Click on the "Archives" on the "Quick Navigation" and download tomcat from Apache's web site. Other wise your downloading from an unknown third party mirror.
2. ALL WAYS scan stuff you download for viruses.
3. If this is a system that you are putting on the Internet NEVER put your web server on your boot or OS partition of your hard drive.
4. The standard name for the location of Java is "JAVA_HOME" not "JRE_HOME".
5. If this is on a server you should use the windows version, because it will add a service to windows to startup tomcat when windows starts.
6. NEVER run tomcat as a front end web server on the Internet. Use either Apache HTTP server, or IIS.
7. Run the tomcat service as a user that doesn't have any administrative, or root permissions.

Tuesday, August 26, 2014

What's the difference between advanced Java and core Java?

I have seen this question a lot in facebook groups.
And it has to do with two books that Sun Microsystems supported as the books to learn Java from. Oracle(the company that bought Sun Microsystems) no longer supports these books, and instead supports the Java tutorials on their web site.
http://d.gr-assets.com/books/1181178258l/1122851.jpg
http://freeebooksearch.net/pics/d909a_java_51I6-FPefnL.jpg

Saturday, August 23, 2014

Java core Vs Java SE

Java core also known as "core java" is an old term and only includes a few foundation packages.
Java SE includes Java core and all the rest of the packages.
AND core java DOESN'T include the DESKTOP.
Java Core
Yellow are Java Core Packages

Wednesday, August 20, 2014

Do your own research! !!

Recently I have been doing research on a new system with two other people.  And without them even installing and running the system they both used someone else's research like it was their own to come up with a conclusion. Don't get me wrong they did have references to that other work. But, when did research mean steal someone else's stuff without studying for yourself first?

Friday, August 8, 2014

Monkey Code


Monkey code not to be confused with code monkey is referring to programming code that isn't optimized for CPU, memory, and data communication usage. Using the same though that 'Infinite monkey theorem' “Given enough time, a hypothetical monkey typing at random would, as part of its output, almost surely produce all of Shakespeare's plays.”
Monkey coder is a person that writes monkey code, or non-optimized programming code.
Typical monkey code or coder wouldn't do the following:
  1. Think.
    Analyze everything you code.
  2. Work smarter to not harder.
  3. Start at the beginning or the end, but not in the middle.
  4. It is the little things that make all the difference.
  5. Think out side the box.
    Glass half full, half empty, or etc.
    The glass is full, because the the glass is half filled with water, and half filled with air.
    The glass is 99.99% nothing, because atoms are 99.99% nothing.
  6. Chris's first rule: Computers are dump.
    Computers will only do what they are told within their physical and virtual environmental limitations.
  7. Keep It Simple Stupid (KISS)
  8. Use the Right Tool for the Job
    A hammer is a great tool for hitting nails, but it sucks at hitting screws.
  9. Current/Modern Computer Design.
    Current computer design has input, process, and output in that order.
    Modern computer design has input, data communication from input to process, process, data communication from process to output, and output.
  10. Use the closest system to the data to do your query filtering/calculations.
  11. Use asynchronous objects as much as possible instead of synchronized object for better performance, and know the difference between them, know when and where to use synchronized objects.
  12. Follow my Programming and Language Best Practices.(Will be discussed later)
  13. Remember there are three main part of a computer:
    1. CPU
    2. Memory
    3. Communication/Data transfer


I am exactly where I started.

My first software engineering position I was creating dynamic websites using ASP and at the time VBS wasn't advanced enough to handle full object design, and many of the Active X components that were needed to be used. So rather than using VBS I used Jscript which was m$ implementation of Javascript.
And now after over 15 years I am programming in Javascipt once again in Node.js. Although it is easy to use. Node.js is lacking in enterprise support and  standardization, program flow, and all out system processing.
I feel like I am back when vary little databases supported JDBC. But worse because Node.js hasn't standardized any database abstraction layer.