Why son, back in my day I remember havin ta trudge twenty miles through the snow just to get my hands on one of them struts 1.02 source files cos we didnt have no documentation back then!
Nope. None of that fancy (e)book learning for us son! Werent no struts classes we cud take either - an I means that in both senses as we didnt have class files like as ye hev now - we had to execute the code ourselves. None of them jvm things was invented yet. A'cos, once ye got yerself a source file, yer'd hev ta thaw it out afore ye cud read it. We didnt hev no fancy ant tasks for that back then. Nosiree - yed hev to use real fire and heat it real careful like, then ye cud load it into yer steam powered beta version of vi and work out just what that critter was up to. A'cos there werent no sruts list back then neither. Why - if we had us a question bout some source file - well we'd just hev ta trudge that twenty miles so as to send a telegram to Craig, and then we'd have to wait us a whole week and trudge us another twenty miles to get the reply. Mind you son - some things was better back then too. We din't hev no internet so's we din't need ta worry ourselves about writin' any of them fancy newfangled jayespees or html forms, and since we didnt hav ta do them, why them thar action classes seemed a lot easier to do too... Nows that I come to think of it, we spent pretty darn well most of our development time out in the snow - if we weren't cartin round frozen source code files then we was cuttin wood to thaw them out or to burn in the boiler so as we cud use vi to read em - did I mention as how it was steam powered back then?... ...hang on. This was like a few months ago and I live in the tropics. Hmm. Nevermind. -----Original Message----- From: Rick Reumann [mailto:[EMAIL PROTECTED]] Sent: Friday, 10 January 2003 14:58 To: Struts Users Mailing List Subject: Re: Struts Productivity Survey The problem with this survey is that the results you would get would not be accurate for assessing the time it would take new developers to catch on to using Struts at the present time. There is now a lot more documentation and examples out there to learn from than there was just six months ago. My biggest frustration in the beginning was the lack of examples and cohesive documentation of how all the different pieces fit together. Most of the learning took place by digging into the examples that come with struts and those on Ted's site and then asking questions. Now, however, there are several great books out there( Chucks, Ted's, etc.) and had I had them when I first started life would have been much easier. I think it's really going be difficult to get an accurate feel for how long it takes people to get 'up to speed' with struts since I think it's much easier now for new developers to learn struts simply due to the books and better documentation available. On Thu, 9 Jan 2003 21:20:00 -0600 <[EMAIL PROTECTED]> wrote: > I am conducting an informal survey to determine how difficult it is > for new developers with differing skills becomve productive with > Struts. This really only applies to those using 1.1x. Anyone who is > willing, please answer the following questions: > > 1. How long did it take you to get the Struts Framework up and > running for the first time? 2. How long did it take you to get your > first business component going in the Struts Framework (this involves > Action class, page, business objects, etc. from start to completion.) > 3. Would you describe your Software Development experience as a) > novice, b) advanced, or c) expert? 4. Would you describe your Java > competencies as a) novice, b) advanced, or c) expert? 5. Would you > describe your J2EE/servlet/JSP competencies as a) novice, b) advanced, > or c) expert? 6. What was the hardest part about learning Struts for > you? > > Thanks. If the response is interesting I'll compile it and post it > back to the list. Greg -- Rick -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
