Standard Developer Toolkit - 2010 version


I don't know if it is because I am getting older but I am starting to record my thoughts online or digitally so that I can easily go back to that record. I do this by posting blog posts on blogspot and through other subversion code repositories.

One task that I have long neglected is creating a list of common developer tools. The toolkit suite contains a list of common software applications that a developer of any language or environment would need. Most of the software is open source of freely available. Obviously, different developers want or need different tools. Here is the list of packages that are essential for what I need. Yes, the list is bias with a emphasis on Java development. I marked the critical applications in bold. I would typically install of all of these tools on one machine over a long time period. Some of the tools seem similar in nature, for example, I do install Netbeans and Eclipse on the same machine. I may swap between the IDEs if there are tools built for one platform not available in the other environment.

Operating Systems:
- Use both WindowsXP/Windows7.
- Cygwin
- Use VMWare and an Ubuntu 9+ Image (only VMWare player is needed for win32)
- VMWare Fusion if you use Mac
- Ubuntu 10+ on a standalone machine (AMD64bit or Intel machine)

Programming Languages and Environments:

- Java (Java JDK from Oracle on Win32, possibly OpenJDK on Windows)
- Scala (JVM language for Java)
- Clojure (JVM language for Java)
- Python (install on both win32 and Linux)
- Perl (for some scripting)
- Haskell

Developer IDE Tools:

- Eclipse (you can easily install/setup multiple versions of Eclipse)
- Eclipse CDT for any C++ Development
- Eclipse PyDev for Python development
- IntelliJ IDEA (Great for Scala development, rapid Java development)
- Netbeans
- Emacs

Misc Developer Tools:

- Subversion client
- Git client
- Mercurial client (optional)
- Maven (for Java development)
- Ant (for Java development)

Text Editors:

- Vim (install on Cygwin if using Win32)
- Emacs (I prefer Emacs over XEmacs and use the Emacs win32 version)
- TextPad
- Notepad++ (notepad++ is open, textpad isn't, I like both)
Word Processing:

- Open Office
- Microsoft Office (I prefer older versions of the Microsoft Office suite. If you have the money, I would consider purchasing the software).

Web Browsers:

- Mozilla Firefox
- Install Firefox Firebug plugin
- Install Firefox Tamper data plugin
- Google Chrome

Network Tools:

- WinSCP (Win32)
- FileZilla (Win32)
- XChat (or XChat2)
- VMWare Player

Graphic Tools:

- Gimp

Misc Tools:

- 7zip
- WinMerge (open merging software, very useful)
- R (google R statistics application). Useful for charting data

Cygwin Installs

- Install Cygwin
- Download or make sure that these are installed: vim, find, grep, wget, gcc, g++, gtk libs, openssl libs, gnuplot

Eclipse Plugins for Java Development

- Subclipse
- Maven Plugin (m2eclipse)

Java Frameworks

- Spring Framework, Google's GWT, Apache Wicket, Hibernate, iBatis ORM, Lucene, AspectJ, ASM, Antlr

Comments

Post a Comment

Popular posts from this blog

Is Java the new COBOL? Yes. What does that mean, exactly? (Part 1)

Image
"If you want to know the past, look at your present. If you want to know the future, look at your present." -- Gautama Buddha Java is the new COBOL, whaaaat?     If you are software developer that mainly writes applications for the web; even if you aren't a Java/J2EE developer, you have probably heard the new meme circulating the web and blogosphere. "Java is the new COBOL" . Most blogs and technical writers regurgitate that statement and follow-up by saying that EJBs suck, and some companies are considering Ruby on Rails. I didn't really think much of these posts. I get the impression that a lot of these "managers" don't write any Java or COBOL code. They are really not highlighting the seriousness of the problem. COBOL development has remained stagnant for decades. Java may see the same problem in the future. The Pentagon/DOD has a trillion dollar COBOL problem because it is so difficult to change their ancient infrastructure. Anyon
Read more

On Unit Testing, Java TDD for developers to write

It has been a while, let's kick off 2017 with a blog entry. I have read and I am reading about four or five posts a day about unit testing. It really has been a long time obsession for me. I have moved past the technical and practical considerations on unit testing frameworks and done with the debates with "should you use Junit or Mockito or Karma?" I am more interested in the psychology of unit testing, who does it, likes it, hates it? It really is one of those easy to learn, hard to master concepts. For example, many many may play chess when they are young and can end up being horribly chess players most of their life, I am part of that majority. Unfortunately, I have never played chess and sat down for hours and tried to master it. I never see the common patterns or have a developed end game. I mostly just play with a knowledge of the basic rules. Following good unit testing practices within your software development shop is a lot like playing chess. It is easy to le
Read more

JVM Notebook: Basic Clojure, Java and JVM Language performance

Image
"Measure, don't guess. The primary goal of all performance tuning exercises should be maximize the end user experience given the resource constraints." [1] "It isn't so much a "farewell to the J" as an expansion of the platform opportunities Java provides. Sun's investment to power ongoing development of JRuby and Jython broadens the range and reach of Java, as a whole." -- Rick Ross Overview and JVM Languages    One of the exciting trends to recently emerge from the Java community is the concept of the JVM language. These technologies are all that you would expect them to be. They are implementations of languages that run on the Java Virtual Machine. Some are newly created and some are based on existing, more mature languages. JRuby, Jython are two JVM languages based on CRuby and CPython. Groovy, Scala, Clojure are three completely new JVM languages that were created to add new language features that weren't supported by the core Ja
Read more