urn:lj:livejournal.com:atom1:bighairybaldgee Everything that's too geekly to print :) Big Hairy Bald Geek 2004-03-23T03:57:17Z urn:lj:livejournal.com:atom1:bighairybaldgee:1471 2004-03-23T03:57:17Z 2004-03-23T03:57:17Z My team has been in severe death march mode for the last 3 months or so.&nbsp; We're all working so many hours that getting sleep and seeing the people we care about once in a blue moon are about all we can manage outside of work.<br /><br />Personal geekly projects are a million miles away :)<br /><br />I'm studying for the Java Programmer's Certification test with friends and boy let me tell you it's a ball buster.&nbsp; It is HARD.<br /><br />Hopefully if I get laid off though this will give me some leverage towards starting a new life somewhere as a Java developer.&nbsp; I really enjoy working in the language and it's a world away from the endless shell script heque I'd been trapped in for the last few years.<br /><br />Also I'm installing Gentoo Linux on this box and so far the process has been pretty darn painless, we'll see how it all pans out :)<br /><br />Anyway, I should go study Java.&nbsp; Be well all! urn:lj:livejournal.com:atom1:bighairybaldgee:1147 2003-11-26T00:24:01Z 2003-11-26T00:24:01Z A piece of all this I forgot to mention in the last entry that I think is rather crucial is the object bus.<br /><br />It's important that every piece of this project be able to communicate with every other without specific knowledge as to that piece's identity.<br /><br />So I'm envisioning the front end encapsulating requests in object form and placing them on the bus with only generic destinations being specified (e.g. this is for the back end, etc.)<br /><br />Whatever we use for this should be language and OS independent and be as lightweight as possible. People are telling me that SOAP is the way to go but I have yet to understand it well enough to be sure that this in fact will do what we want.<br /><br />Again, this is all very hazy arm waving at this point but it's important to get the key pieces down I think, even just to provide a framework for further research. urn:lj:livejournal.com:atom1:bighairybaldgee:848 2003-11-25T22:36:19Z 2003-11-25T22:36:19Z So as I said previously work has been busy. I've in fact been learning new tech and such but it's all very... Constrained :) Being in a release engineering capacity rather restricts the sphere of the apps I work on to a great extent.<br /><br />It's time I actually did something outside of work to keep my overall geek skills fresh and also to keep my resume glowing with that healthy zeal I've come to expect from myself throughout the years but have of late been sidetracked away from.<br /><br />Over the long weekend vacation I just took a good friend of mine reminded me of an idea I've had for years but never managed to implement.<br /><br />What I've really wanted for years is a pluggable system for processing mail. What I mean by this is a set of mix and match 'components' which can be plugged together with a modicum of configuration (Something an installer could do for an end user very easily after collecting their preferences) that would support the wide variety of environments people work in.<br /><br />For instance I envision a number of different front and back ends, each tailored to a specific category of user:<br /><br /><u>Front Ends</u><br /><ul><br /><li>Rich local GUI client (written in something like Java or Ruby)</li><br /><li>ASCII based client for use over ssh connections or in text only environments</li><br /><li>Web/CGI based client a-la Hotmail or Yahoo! Mail</li><br /><li>Tiny client for PDA's and other small devices like cellphones</li><br /></ul><br /><br /><u>Back Ends</u><br /><ul><br /><li>Simple plain text based storage. Slow limited searching. Near zero setup time and pre-requisites</li><br /><li>SQL RDBMS for much faster searching, better indexing and more automated infrastructure for doing back ups, replication, etc.</li><br /><li>Some sort of object repository?</li><br /></ul><br /><br />Ideally the front and back ends could exist on separate machines. So for instance you could run your front end (client) at work and have it readily communicate with the back end running at home, automagically slurping up and indexing all your mail.<br /><br />I can hear people asking why this new architecture when things like IMAP get you 50% of the way there today? The answer is that we're looking for a much richer level of interaction between user and mail.<br /><br />I personally think that the current systems in place for organizing mail are too flat. Often times merely siphoning it into folders can help solve the problem, but in my opinion what's needed is something more than that. As a start a more hierarchical, keyword based organization would help I think. The ultimate idea here is similar to what I've seen called agents. You could ask questions like "What was that piece of e-mail that had to do with X that I saw sometime last year?" and the back end would spit back an appropriate set of objects for your client to display containing a list of likely messages.<br /><br />Right now I'm thinking of trying to implement this in Ruby, however whatever communication mechanism we pick should be language independent and be able to exchange data/messages as objects. After consulting a mailing list or two people are saying that either CORBA or SOAP are the way to go for this.<br /><br />I realize this is a lot of mere arm waving at this point. I feel like I need to do some research on SOAP before I can comment intelligently any further. Once I have my head wrapped around all the necessary infrastructure I'll come up with a more concise, detailed write up and put it here.<br /><br />Until then though comments are welcomed (all but the "This is stupid why not just use existing tool X?" line which are less than helpful unless something REALLY does what we're trying to do already :). urn:lj:livejournal.com:atom1:bighairybaldgee:548 2003-10-23T05:34:53Z 2003-10-23T05:34:53Z "Working in high tech is like riding on the back of a headless chicken."<br />-Jon Forsyth<br />------<br />(Ed. Aside - I have been working <b>alot</b> lately. I'm purposefully throttling back for the sake of my health and sanity, but even at a more measured pace things are pretty hectic. The good news is that I've been doing that forced-in-the-heat-of-battle skill set building thing and so the dust settles, watch this space for my take on Java, Eclipse, XML and Perl as well as more general geekly topics of note.) urn:lj:livejournal.com:atom1:bighairybaldgee:431 2003-08-09T08:18:28Z 2003-08-09T08:18:28Z silence Ever since the shrub got elected and the economy went down the shitter I've been experiencing the rather unusual (for my industry anyway) phenomenon of being one of the few people still at the same job I started with before the dot boom went dot bomb.<br /><br />These folks are having (on the whole) a great deal of trouble finding jobs again, which isn't all <b>that</b> surprising because the number of jobs overall has in fact declined quite a bit.<br /><br />What <b>is</b> surprising, to me anyway, is the tail spin into total stagnation that I see happening with <b>WAY</b> too many of these folks.<br /><br />"Have you considered re-casting yourself into another position using the skills you have, and maybe taking advantage of this time off to gain some new skills entirely?"<br /><br />The reactions I get to this just blow my feeble mind. The amount of resistance to change I see these people exhibit regularly make me wonder if I was raised on another planet or something.<br /><br />Maybe it's because I was born on the wrong side of the tracks, raised by a working class family and taught that you do <b>whatever</b> it takes to earn your keep. Too hard to learn a new programming language or a new set of platform and tool skills? Tough shit. While I do have some college I am entirely self taught where tech is concerned so honestly I have very little sympathy for anyone who's too lazy to get off their ass and read a book or a web page and do some real hard work for a change.<br /><br />My mom made buttons at pennies on the gross and my dad shoveled snow at Hanscom field till the day he had a heart attack and died. You want hard? Talk to our parents and their parents before them. Most of us (myself included) are a bunch of out of shape couch potatoes and wouldn't know real hard work if it bit us. I did manual labor for one summer at UPS shoveling dirt and I thought I'd never make it :)<br /><br />As suckful as the economy is right now there are <b>so many</b> excellent opportunities for geeks with time and clue it's disgraceful for all these capable folks to be wallowing in their misery, passing the time playing the interview game and doing not much else. Get involved in an open source project! Write some code, invent something cool! Go for the gusto! What the frigging hell do you have to <b>lose</b> exactly?<br /><br />This is not an indictment of anyone nor is it a trivialization of so many people's very real sorrows and pain. My heart goes out to everyone tossed out in the cold - we've all been there in our lives but that was winter in Boston, now we're at the North Pole.<br /><br />I just wish people would come out of their holes and start taking advantage of some of the excellent things they <b>could</b> be doing rather than being paralyzed by the horror of it all.<br /><br />You may have to change the way you think and work. For instance the "Java sucks" crowd may have to suck it up and realize that it represents a huge step up for the average developer - and that there are jobs and money being made with it, regardless of how you view it technically). <br /><br />In the end analysis I say a proven success record on the battlefield of open source is vastly preferable to big gaps in your resume. Which would you rather see as a prospective employer? A portfolio filled with code samples and project docs, or a blank resume and some witty lines you hope will cause them to fail to notice?