in

Utah .NET User Group

Home of Utah's professional .NET developers.

Bryan Hinton's Blog

July 2006 - Posts

  • Tables in Excel

    It is a common joke at Intel about how Excel is used to run the company - in my experience that often doesn’t seem to be very far from the truth. I have been evaluating Office 2007 recently and have found a lot to like about it. The new UI was expecially nice and it seemed in my limited use to make it “easier” to do things. The only downside was that while I love the enhancements to Outlook - the thing isn’t stable enough to use for long periods of time - at least for me.

    Okay - back to Excel - in 2007 - they are introducing the concept of tables in Excel - this link has a great screenshot tutorial/overview of the capability. Basically the idea is that when building formulas and calculated columns you no longer have to use cell references, but you can use columns names outlined in a header row. So if you have two columns named Out_Date and PrevOut_Date - you could add a third column called Cycletime which took Out_Date - PrevOut_Date as the formula - no A3, B7, etc.. References.

     

    Technorati tags:
  • Intel’s Conroe processor blasts AMD

     Working for Intel has been a lesson in humility the past year or so especially as AMD has really kicked sand in our face. It was great to read Tom’s Hardware ‘s review of the soon to be released Conroe processor - http://www.tomshardware.com/2006/07/14/core2_duo_knocks_out_athlon_64/ . Now I realize the fight is far from over and hope that our chip designers (I develop software for the manufacturing side of the house) continue to crank sweet new processors out. But the bet the company made over the last two years to move to the Core architecture is starting to pay off. You combine that with a much needed repurposing (and resizing) and hopefully we’ll be better positioned to be the tech leader going forward.

     

     

    Technorati tags: , ,
  • Team Dynamics – the weak weed out the strong?

    David Anderson has an interesting post about a book he recently read that suggests “In flat structures with highly empowered, self-organizing teams (Farson calls these highly participative teams) the team members will tend to attack and weed out the strongest (or stronger) member(s), often the leader. In hierarchical structures, with command and control structures, the members will tend to attack and weed out the weaker members.” David then makes some conclusions about what this would mean if it were true for Agile development teams (which tend to be more flat than hierarchical). He suggests that if the book’s author is correct than team membership would be better served to be grouped according to technical ability (with the groups being based on like ability) rather than spreading the weaker technical members around.

    At Intel I am not sure how I see this playing a part – our culture is hierarchical by nature and so even in the Agile teams command and control structures exist. Also it becomes a little more difficult because you always have to factor in politics into team dynamics at companies as large as Intel. Weaker technical people may be much better at playing the politics and that muddies things because in a lot of cases weaker technical skills can be masked by playing a good political game.

     

    Technorati tags:
Copyright © 2000-2007, Utah .NET User Group
Powered by Community Server (Commercial Edition), by Telligent Systems