RSSGo process!
Feb 11
Nazistic proxy love that is.
For the first time in 5 years in the company I finally experienced being ‘benched’. That is the local term for any resources who are in-between projects. After going through several mind-benders, I figured this is a welcome opportunity to get some training done.
I have two options, either go for the trainings in the company online learning repository or pursue more job-directed tutorials that proliferate the net. In my perspective the second option means a wealth of information right in my fingertips as soon as I get clearance from my superiors that I can do so. First I have to make sure that I have completed all of those mandatory trainings. Ok, fair enough. I even tried taking some of the available CBTs to (in the words of my counselors) “round-up my non-technical skills.” Being a geek by nature, I can describe those trainings in two words: boring and under-estimated. Boring does not need further explanation and yes I already sent the proper feedback. Under-estimated means that the allocated time to complete each course is severely underestimated. My impression is that whoever timed these courses have used people gifted with super-human reading and compression skills. For the rest of us, good luck in finishing the courses in the allocated time. Think about what you can remember on the course on your way home.
After the non-technical traiing torture has ended, I set my sights on these cool Java frameworks and technologies that I kept promising myself that I would get an overview. I am talking hibernate, spring, struts, aspect oriented programming, design patters, eclipse framework, and what have you. The mere thought makes me salivate. 😀
First in line is the spring framework as this is being touted as the emerging de facto standard for J2EE development. The spring home site has a nifty tutorial that is easy to follow. Since the tutorial uses Apache Tomcat for deployment and testing and I am using Eclipse as my IDE, it makes logical sense to install an Eclipse plug-in to manage the Tomcat start/stop process. That is the goal of IDEs in the first place: so you have a one-stop shop for all your development needs.
Ok, now to put the good idea in practice: Fire up google, search for “best eclipse tomcat plugin”. What do you know, the first few hits lists the eclipse plug-in central site. The cherry is that you can sort based on rating and the best one is the sysdeo plugin which I remember using eons ago. This is where the love entered the scene: clicking the plug-in homepage returns a proxy blocked page because it is classified under “Freeware and Software Download”. Very nice. /roll-eyes
And now in order to use this “should-have-been-a-great-idea” I need to secure a manager’s approval, hunt down whoever is managing the elusive Websense white-list, make the actual appeal, probably need to secure a local security exception for something that common sense should dictate as something useful, which in turn would probably result to securing a global exception, and then doing the whole red-tape-esque dance of e-paper processing. Assuming my request gets approved I guess my grandchildren who would be in the company by then be able to use an Eclipse Tomcat plug-in if I am careful enough to word it that the request is not version-constrained. 🙁
Or I can circumvent the process by downloading the plugin from outside the external network and then send it in.
Or revert to using one command terminal to start tomcat, and then my IDE for development.
Guess which one won? Yay for progress and efficieny. CLI rules. 🙁
ciao!