Quantcast
Channel: WinDev Forum
Viewing all articles
Browse latest Browse all 1914

Interesting reading IMO

$
0
0
Original jobs specs are here...

[stackoverflow.com]

I knew I was not qualified but the 'humble JAVA developer' caught my eye. I have never met a humble JAVA developer. Many think JAVA is (insert your favorite diety)'s gift to programming. You know, JAVA uber alles. So I applied.

On the refactoring test I reduced their 20 line JAVA procedure to just 2 lines.

PROCEDURE isNegative(Stringfield)
RESULT Contains(Stringfield,"[")

====
Their reply was predictable:

Hi Arthur,

We enjoyed your application, but you are no longer under consideration because you are not local and you do not have significant experience with Java. If you ever move to the DFW area, feel free to apply again to Smart Start, and good luck with your job search.

Sincerely,
xxxxxxxxxxx

-------
My reply might not have been as predictable... :p

Hi xxxxxxxx,

I really have to thank you for your response, I really did not expect any reply at all. The fact that you did speaks volumes as to your professionalism and integrity.

You are correct, I am no JAVA expert. As you can see my 'expertise' in JAVA is that I can read and refactor it into a language much better suited for applications like the ones you listed (interactions, reports, etc). While JAVA is a powerful general purpose programming language, sometimes there are better choices in tools to be made when addressing a certain niche. Like using a nail gun instead of a hammer to build a house.

My application to your company was a statement that there might be a better way to refactor your database applications than using JAVA and the laundry list of two dozen technologies that you must employ to produce what is essentially a simple product. While it may not have been apparent, refactoring a rambling 20 line JAVA procedure to one line was my way of showing that. It is my belief that your JAVA database applications can similarly be refactored.

Using a product and IDE that is tailor made to produce database applications would be much better suited to you stated goal of replacing legacy code that works 'mostly'. An experienced developer using a rapid database application development tool would make replacement much simpler, much faster and much cheaper than using JAVA.

Better. Faster. Cheaper. Pick three.

Admitting you have a problem is the first step. Selecting an appropriate tool to fix it is the second. Those are the signs of a humble company. If you ever need someone to refactor your applications correctly you know where to find me.

Best Regards,
Arthur Bonds

======
I can be a little prick sometimes... :D

Oh, and my wife says she has never met a humble developer...

Viewing all articles
Browse latest Browse all 1914

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>