Development Stack

Developer must have some unique way he used all the time once he faced by development cycle. And sometimes it would be related to some tools. Maybe the definition i gave here is not quite right but it is what i feel. I called them (related tools to development cycle) as development stack.

And here it is, for your information, my current development stack:

Presentation Layer:

Presentation layer is layer of application which the closest layer to users. Term user here is person, party, or even another machine which asks for and uses service served by application.

Currently, I often faced to different type of developments which is usually only web presentation layer.

Php – CakePhp (best price and robustness)
Java – Struts 1.2 (old school fashion)
Java – JSF (better approach) with JBoss RichFaces

Ajax:

Ajax implementation used to leverage user experience to web application as desktop application as well.

Currently, light weight implementation of ajax used on my development stack, using simple javascript as:

Javascript – PrototypeJS
Java – DWR
Javascript – EXTJS
Javascript – JQuery

Business Layer:

Business Layer is layer to process business logic of the application.

Php – CakePhp (its model)
Java – Spring
Java – EJB 3

Data Persistence Layer:

Data Persistence Layer is layer to persist data to data source as database.

Java – JPA with Hibernate
Java – Hibernate

Project Management Tools:

Project Management Tools consist of wiki, issue-tracking system, and revision control system integrated.

maven, mainly as build tool
redmine, rubyonrails-based issue tracker
trac, python-based issue tracker very easy to use but hard to install

Revision Control System:

Revision Control System is the management of multiple revisions of the same unit of information.

svn (Subversion)
cvs, obsolete by svn i think

Unit Test:

Unit test is testing applied to each unit of application

Java – JUnit

IDE:

Integrated Development Environment mainly as editor, build, and run project.

Eclipse

Continuous Integration:

CI enable automated build in integration term, so any fallacies in each update can be immediate known.

Java – Apache Continuum

Like this:

Be the first to like this post.

About this entry

You’re currently reading “Development Stack,” an entry on reekodezz

Published:: May 14, 2008 / 12:33 pm

Category:: Framework

Tags:

About

reeko a.k.a reekoheek is a net-name. It begins long time before the author join and having interest on internet, let me say, reeko a.k.a reekoheek is destined to be here.

Years actively participate in writing codes, and now is about the time to write differently. Always fond of philosophy, as mother nature of human thought. As root of every single thing ever dangling in mind. As pounding sound on roll drums of ideas.

Jafar Shadiq a.k.a Ganesha DM reborn reekoheek as it shows. Since he is active and senior programmer (PHP and J2EE), doesn’t mean he is Smarty, Einstein, or God. He just humble person and sometimes makes stupid mistakes.

This is not about brilliant achievements. This is about most stupid things ever happen to the journeys of codes…

seseorang 9.29.08 / 10pm

As you have foremost mentioned about how it may be unique for each developer or project to have their own development cycle, I must praise you for sharing your version of -though short yet thorough- guideline of development aspects.

And just by seeing what you’d care to share here, I can tell that you are in an advanced developer level. While entry level developers (even maybe starter teamleaders) may put attention on the IDE and enhancements of it, or maybe even still having to struggle with an acceptable design (*where you would put) in data Persistency Layer, YOU however, have escalate it to the next level by giving concerns to even wider aspects such as PM Tools and Revision Control System (*I recommend u TortoiseSVN). Also, in your stacks above, you have created a great deal of possibilities and anticipation by presenting selections of some of the most flexible platforms. Hence, you covered every aspect of development which may be applicable to any scale of software development that I could think of.

I, however, would suppress a little bit more on the construction of Business Layer since the difference in business logic between a barely adequate one, or a simply fulfiling basic requirement one, and of course the darn good one, would crucially determine the efectiveness and scalability of our application, which (all of us would’ve guessed) furthermore would affect the productivity of the rest of the business elements that has -or even has no- conjunction with the application at hand.

all in all, thanks reekodezz

reekoheek 10.1.08 / 4am

about TortoiseSVN i think it could be alternative for accessing svn server, but i prefer using eclipse-plugin for svn

thanx for your comment, seseorang.

reekodezz

Development Stack

Like this:

About this entry

2 Comments

Leave a Reply Cancel reply

About

Recently

Monthly Archives

Categories

Follow “reekodezz”

reekodezz

Development Stack

Like this:

About this entry

2 Comments

Leave a Reply Cancel reply

About

Recently

Monthly Archives

Categories

Blogroll

Follow “reekodezz”