Moving On

  • Comments posted to this topic are about the item Moving On

  • I read the title and went into a panic! Heh... don't scare us like that!

    We have room on our electronic timesheets to make notes for each entry. I basically keep a daily log there. Sometimes the entries only contain something simple like "Worked on ticket # 12345" and sometimes they contain a more descriptive narrative with other facts and opinions. It's not a diary but it is a place where I can call up important facts about the year.

    I also keep a running list of personal accomplishments, goals, and failures for the stuff that's useful on a review or to answer the "If you could change one thing, what would it be" question that I frequently ask myself. As with anyone and everyone else, I've had some rather tempting offers both challenge-wise and pay wise. I've also made some leaps in the past that didn't turn out the way I thought they should so I'm very careful about all temptations. Like you, I'm convinced that I've found/made my dream job and, although I'm reminded every day as to why it's my dream job (something or someone good happens more than once a day), I love the confirmation I accidently get when there's something new to add to the list.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
    "Change is inevitable... change for the better is not".

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

  • I wish we had a notes column on our electronic timesheets, but we don't, so I use my calendar for keeping track of what I do all day. I also have my running list of longer-term projects in case I ever get the time to work on them. This is typically the "if I have time, I want to change or fix this" list. I know that I'll never run out of these things to do, but as long as I keep making progress, that's what matters.

    I also feel I have a great job. I try to take time to review major accomplishments about once a quarter, usually around some significant date. On those occasions when I can't see the forest for the trees, the periodic review of big-picture accomplishments helps me keep perspective on things. This helps me maintain a positive attitude and refreshes it every once in a while. For me, it's time well spent.

  • An honest self evaluation is healthy. But I am against sending out an evaluation email as you cut and run. It is certainly one sided, does not allow rebuttal, and often is a slam against the company. That is why so many companies, once they know you are leaving, will escort you off the premises, never to touch one of their computers again, instantly locked out of their network. It is the exception rather than the rule when an employee is allowed to complete their two weeks, or whatever, with the company trusting that you will "behave" yourself in your final days.

  • Just had occasion to do some reflection for entirely different reasons.

    Just over a year and a half ago, our unit tracked labor using - brace yourselves - individual Excel spreadsheets and an Access application to process them once a month for billing to our clients. Keep in mind we had about 30 or so employees, each with their own spreadsheet, and 1000-odd sets of billing codes for their labor. I'm frankly amazed we billed anywhere near correctly each month.

    One day my boss - who processed billing each month - stopped by my desk and said, "I don't care how you do it, but we have to fix this." Last December I launched a solution using Access and SQL Server to centralize the whole shebang. It wasn't terribly complicated: Two main tables, some supporting tables and links to a couple existing tables in the database that houses it.

    Last week we just logged over two million minutes of labor for the year using this solution (about 16-17 FTEs). This month I also released a totally new .NET application to replace the Access portion. In developing training for the staff to use the new front-end, I took some time to look back on how this thing has evolved.

    It's been an interesting journey. This is one of those projects where you set out to solve one problem, then turn around one day and discover it's being used in ways you never really imagined and you find yourself thinking, "I built THAT? Cool." Instead of just recording labor data for billing we're actually now leveraging the data for reporting and project planning purposes - something which we've never been able to do.

    And this doesn't even consider all I've learned over the past year about .NET, VB, C#, T-SQL and SQL Server itself. I've gone to work every day and played with some neat toys to see what they can do...and they pay me for it.

    It's been a good year.

    ____________
    Just my $0.02 from over here in the cheap seats of the peanut gallery - please adjust for inflation and/or your local currency.

  • That is an interesting idea. Write a departure letter every year whether you are leaving or not. I think it is a good idea to keep a log and perspective of what has been done over the year. I had just never thought of it being a departure letter. This is one of those things that would work well with the annual (or more frequent) update of the resume. It makes sense and might be a good thing to do regularly.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • My last letter announcing my decision to leave had the following subject line:

    "Sorry, no more cookies"

    And then the announcement I had decided to leave. I think people where more upset that I would no longer bring in my wife's baked goods than upset at me leaving 🙂

    All but one job I have left have been on good terms. Most of the positions I am still in touch with the person that took over my job, and have helped them out with various items to get into the role.

    Don't think I have ever written a departure letter looking back at my time at a company though. But have had some frank discussions about where things where heading with certain stake holders (almost 2 hours with the CEO of one company....)

  • This is something I face this year. Looking forward, not back.

  • Just like Anders, I only have one place where I didn't leave on good terms. Some places I was really glad to be leaving but all except the one professionalism was maintained on both sides and often friendlier than that.

    As I work freelance I guess that my reputation is essential, however, I have found that people often show their true colours as they step out of the door without the social constraints of having to return regardless of how they were contractually related.

    I tend to reflect after each contract, sometimes at each point of renewal. This reflection tends to be half the story though. The other half, as eluded to already, is acting upon anything deemed necessary.

    Gaz

    -- Stop your grinnin' and drop your linen...they're everywhere!!!

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply