archive-com.com » COM » I » INTEGRUMTECH.COM

Total: 312

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Why Merb Becoming Rails 3 is a Good Thing - Integrum
    wholly bad but at the very least creates a marketing problem they decided to now join forces Not a decision that was taken lightly I imagine So what happens to competition you say It still exists there are now many many Ruby Web Frameworks and many more will come even in the wake of this announcement There will always be people pushing the status quo there will always be ambitious hackers out there creating new and exciting things Those things will inevitably feedback into the dominant frameworks if not then the dominant frameworks will slowly die off as they should So why is this a good thing again Well because now the framework I love the framework that has changed my development life will now be even better The infusion of the quality engineering that has been displayed by the Merb team is the best thing for Rails long term viability Enterprise business want to jump on the Ruby bandwagon they are just scared of Rails and it s issues real or perceived Now Rails will become the Enterprise solution they have been clamoring for and that makes life great for all us Rails Development and Consulting shops out there Here s to a great New Year for Ruby PREVIOUS Screencasting as client documentation NEXT New Year New Site New Image 2 thoughts on Why Merb Becoming Rails 3 is a Good Thing Alan Hogan says December 23 2008 at 11 37 pm Makes a lot of sense to me My gut reaction was this would be a best of both worlds things too Reply Chris Kleeschulte says December 23 2008 at 11 37 pm The impression I got from this year s Rails Conf in Portland OR from the core Rails team was Rails is not holding our interest

    Original URL path: http://integrumtech.com/2008/12/why-merb-becoming-rails-3-is-a-good-thing-2/ (2016-04-26)
    Open archived version from archive


  • Episode #22 - Why Enterprises Crave Documentation Artifacts - Integrum
    are on another project As a developer you are working on another project potentially by the time I am doing a large portion of the QA or the enterprise architect is now on another project by the time it gets to it I think that there is something to be said for communication pathways I think large companies have larger teams which means it is harder to communicate face to face or person to person It is easier to say we need to write that down so that anybody on the team can have access to that even when we are on the same project But when I think you add in the silos and not being cross functional to me it really comes down to people are treated like resources instead of like people Managers treat everybody like a completely interchangeable widget that they are just pushing and plugging so it is really easy to say I really like the work that Roy is doing and I need Roy this week so I am going to pull him pull that widget out and plug him into this other product Now all your knowledge is gone and because now you are on another team it is no longer culturally acceptable for everybody on your old team to communicate with you to ask you information If you didn t leave a litany of artifacts and you hadn t been communicating with that team all of your knowledge is now gone The way managers try to protect themselves from that I believe is they want people to document absolutely everything so that they are guarded If their resources get taken away they ve got a backup plan or a transitional plan to bring on new resources Chris That goes so much back to silos Drew Yes I agree as well Even if there is a situation like you were saying how somebody is just kind of plug and play like a widget out from one team to another I still think that the need for extensive documentation is still not needed if the coders if the programmers write good tests write good code Sure maybe give a shorter overview of written documentation that is not part of the code or test as needed just for kind of a big picture But if they are doing things the right way then yes still extensive documentation extensive artifact extra artifacts are needed Roy Do you feel that it is necessary for large corporations to have all of these specialized rules Like people who are Derek No Roy Especially because I understand that if we take it to a tool shed metaphor If you have one employee who is good for everything something that is used for everything like a hammer that you can use for whatever tool It is great to have on hand because you can use it wherever you go but having a specialty tool is way more effective in those key circumstances Does that metaphor carry over into the business world or is that a broken idea Derek I don t think it does entirely because the two things that I think that it leaves out is one it leaves out what you get from somebody who is well rounded meaning that when you re really talking knowledge work it s not cutting dry of Here s the band saw I need Cut the band saw and now I m taking it over and using sandpaper and sandpapering it The work that teams do is dynamic enough that you really need to understand the whole concept of woodworking It s not just a matter of being able to understand like I m the best drill press guy in the world You re probably not making a whole lot of great furniture if you only know how to operate the drill press If you get to be a little more rounded you may not be as good as the guy who only works the drill press all day but you re now also be able to create things that somebody else that is unifunctional is not capable of doing I think that that s probably the biggest piece that to me pulls on to the second side and that is that you re not nimble if you have a bunch of specialist because you re limited by your resource allocation If I say I ve got one of these guys five of these guys six of these guys or eight of these guys and all of a sudden a competitor pops up and I need to handle something I need to extend the software I need to create a new project or do something and I don t have an enterprise architect ready right now Now I have to wait to when is the next time an enterprise architect s ready OK six months OK we can t start that project for six months Whereas if you got well rounded people it s a lot easier to be able to pivot and to shift because even though they might not be the best in a particular thing they re able to get up and running with that If you re in an environment where there s communication and self organization what I see is people make the right choices If I really suck at JavaScript and I m going in a project that s heavy JavaScript I could tag out and say You know what Drew you really need to be on this project I m not the right person for this We need to shift places If we re allowed to do that the right things happen Or Hey I need you to pair with me on this because I want to get better at JavaScript but I don t want to slow this project down or I don t have the expertise to do it I think if you let

    Original URL path: http://integrumtech.com/2011/07/scrumcast-22-why-enterprises-crave-documentation-artifacts/ (2016-04-26)
    Open archived version from archive

  • Episode #56 - Strengths with Scott Dunn - Integrum
    most and grow the most and perform the most The team can lean on it and these people will never get tired of doing that stuff That s one of the insights Each one of those will be like that I had a team member once and we were at a lull at work as a Web team I said Just take it easy Surf the Web No big deal Enjoy your paid time off here It turned out she got frustrated and left for another job and the reason was one of her strengths was activator The worst thing I could have done for an activator or I should say an achiever that s someone who loves to check off everything they ve done that day They love coming in that day and there are 10 things to do They get to check check check Look I ve been productive Look Scott that was driving her nuts She would rather have me just cook up some work or given her a checklist of things to do and say Hey could you just take a look at some of these areas in the code base and review it for areas for opportunity Anything I could have made it up For me that would have killed me For her it bugged her so much that she left for another opportunity where they would have kept her busier Those are a couple of examples of doing that Clayton I understand that it s a really good tool for figuring out what kind of jobs the members of the team can do that are personally motivating Do you find it s also a good tool to use to help team members discover their weaknesses So that they can try to round out areas they might not necessarily be proficient or necessarily enjoy as much Try to find enjoyment in areas where they don t excel so that the team can go more for that Everybody in our team is a well rounded individual Scott Right That s a great question That s a common one because most of our performance reviews are really spent like I see that you ve done this and this and this and this Thank you for your contribution Now let s spend the rest of our hour talking about these areas where you laughs suck Where you re not so strong where you failed or come up short or you just don t perform well Those areas where you re looking at the clock and say Is the clock broken I hate doing this anything but this Let me check my email one more time That type of work For me it was organization Here s our recommendation Use the DayRunner or why don t you try the PalmPilot I ve tried those things The truth is areas where we re weak those things that we do that just drain us that we loathe all the effort we might put in to try to get better at that will be a lot of pain and not much result If you look back over those areas and you might know what some of those are I certainly know some of mine I look and I have put a lot of time and effort over the years and I ain t much better I m about the same marginal improvement despite putting a lot of time and effort and money even at times What would be much better for me especially as a team member is to invest all that time and energy into my areas of strength where there will be leaps in growth much productivity and engagement I m better to be around Look for someone else in those areas where the team might need someone who is detail oriented who loves to check things off who loves to tackle the tough nuts Then find out where we can shift the work On these agile teams as a whole we should be volunteering We re self organizing We re self managing This is the perfect playground to say I love doing this The whole team wins when you do that I m not so good at doing this and someone else probably would like that and they would thrive Now you re not playing in areas where you just won t ever grow that much or do that well and getting not such positive performance reviews and someone else could They re not getting the opportunity to do more of what they would love to do We actually say Play to your strengths First of all discover them Find out what they are and begin carving out time each week to invest in learning about that activities that you could do to practice That s how we grow right We learn and we practice doing it Manage around your weaknesses On the ROI side it s just not worth putting time into your weaknesses Just work around them Clayton It sounds to me if everybody is playing to their strengths and doing the things that they re best at you will naturally have a tendency to form information silos and skill silos You ll start to form a team that doesn t pass the hit by a bus test Is that something that you ve seen happened How do you prevent that from being an issue Scott I would separate the difference of technology skill I m definitely one who really believes in generalists I don t want specialists and I really love breaking down silos But there s a difference between say technical knowledge your abilities and aptitude and what you actually are doing versus areas where you re playing your strengths so several people that might be developers might love development for those different reasons A lot of us in IT have the strengths around learning and input We love the process of learning and we

    Original URL path: http://integrumtech.com/2012/04/episode-56-strengths-with-scott-dunn/ (2016-04-26)
    Open archived version from archive

  • Special Episode : Ainsley Nies - Agile Chartering - Integrum
    of 2011 During the event we had the chance to be able to interview some of the attendees and talk to them about the Open Space that they had just facilitated Open Space Technology conferences are great events where the attendees get to create and completely control the content of the conference Enjoy this video as we talk to Ainsley Nies about her Open Space on Agile Chartering For more information on this event or their sister event Agile Open Northern California check out the site at www agileopencalifornia com PREVIOUS Special Episode Scott Dunn Strengths Based Team and Personal Growth NEXT Special Episode Chris Scripca Game Programming for Fun and Keeping Thousands of People Happy Join the conversation on Facebook Subscribe to the podcast Make your mark Get involved with the Agile Weekly Podcast by volunteering to be a guest recommending a speaker submitting a question or suggesting a topic Step up to the mic Build up your toolkit Learn new tips and tricks for empowering your team and transforming your business See the blog Hungy for More Info Agile Weekly is a quick way to stay up to date with the latest news techniques and events in the

    Original URL path: http://integrumtech.com/2011/09/ainsley-nies-agile-chartering/ (2016-04-26)
    Open archived version from archive

  • Screencasting as client documentation - Integrum
    combination of Parallels Ubuntu JeOS and Screenflow Rather than place everything into a word document we started with a base virtual machine created from Ubuntu 8 04 JeOS and proceeded to install everything step by step with Screenflow recording the process Now instead of delivering a handful of documents that most likely won t be read we re handing over a completely encapsulated development environment and the recorded process of how everything was put together If they have any questions they should be able to refer back to the screencast and see how we did it themselves PREVIOUS Integrum brings Merb training to Phoenix NEXT Why Merb Becoming Rails 3 is a Good Thing Step up to the mic Cancel reply Your email address will not be published Comment Name Email Website About the author Jade Meskill Chief Revolutionary Officer The new normal presents us with many extraordinary opportunities To accept the challenge is to lead the way to a new future made from embracing our humanity and engaging our spirit to succeed Subscribe to the blog Get inspired with an Agile Weekly Podcast Derek Clayton and Chris slowly remember what they were talking about Oh ya Culture Fit Including

    Original URL path: http://integrumtech.com/2008/12/screencasting-as-client-documentation/ (2016-04-26)
    Open archived version from archive

  • Agile 2011 Presentation - 'There is No Spoon' - Integrum
    in the Agile Manifesto to entire organizations seeing the values as applicable only to software and customers His presentation will encourage attendees to see Agile as it applies to entire communities systems and society collaborating towards a common purpose PREVIOUS Episode 22 Why Enterprises Crave Documentation Artifacts NEXT What Can Paintball Teach Us About Team Work Step up to the mic Cancel reply Your email address will not be published

    Original URL path: http://integrumtech.com/2011/07/agile-2011-presentation-there-is-no-spoon/ (2016-04-26)
    Open archived version from archive

  • Episode #55 - Lean Startup Principles and Agile - Integrum
    How do you maintain it Give freedom be creative Innovation team I m a special snowflake Executive support mandatory PREVIOUS Episode 54 Defects in the Sprint with Mike Vizdos NEXT Episode 56 Strengths with Scott Dunn Join the conversation on Facebook Subscribe to the podcast Make your mark Get involved with the Agile Weekly Podcast by volunteering to be a guest recommending a speaker submitting a question or suggesting a

    Original URL path: http://integrumtech.com/2012/04/episode-55-lean-startup-principles-and-agile/ (2016-04-26)
    Open archived version from archive

  • Special Episode : Scott Dunn - Strengths Based Team and Personal Growth - Integrum
    September 15th and 16th of 2011 During the event we had the chance to be able to interview some of the attendees and talk to them about the Open Space that they had just facilitated Open Space Technology conferences are great events where the attendees get to create and completely control the content of the conference Enjoy this video as we talk to Scott Dunn about his Open Space on Strengths Based Team and Personal Growth For more information on this event or their sister event Agile Open Northern California check out the site at www agileopencalifornia com PREVIOUS Special Episode Jason Kerney Using Creative Processes to Drive Development NEXT Special Episode Ainsley Nies Agile Chartering Join the conversation on Facebook Subscribe to the podcast Make your mark Get involved with the Agile Weekly Podcast by volunteering to be a guest recommending a speaker submitting a question or suggesting a topic Step up to the mic Build up your toolkit Learn new tips and tricks for empowering your team and transforming your business See the blog Hungy for More Info Agile Weekly is a quick way to stay up to date with the latest news techniques and events in the

    Original URL path: http://integrumtech.com/2011/09/scott-dunn-strengths-based-team-and-personal-growth/ (2016-04-26)
    Open archived version from archive



  •