 School of Hard Knocks
Curtis Yanko is a Configuration Manager at a fortune
100 company in Hartford CT. Thrown in to SCM work as junior developer
in 1995, I have learned everything I know in the School of Hard Knocks.
Having never been in a position to specify a comprehensive SCM
solution I have always had to carve a niche within existing tools and
processes while slowly changing the Software Engineering culture from
within. In this blog I will share observations and musings from the
front lines of Enterprise SCM where: Nothing is Easy and the Devil is in the Details as we earn credit hours in the School of Hard Knocks.
|
|
Wednesday, 27 August 2008 |
Hard Knocks 201
It's been a while but then I was lucky enough to catch the corporate winds of change to embark on a new project, the enterprise build system. After years of a full-speed-ahead culture we finally experienced enough pain to consider the merits of quality. So, like my Give 'Em What They Want piece, I recast the value of the enterprise build system in the light of quality improvement and was heard.
|
|
Last Updated ( Wednesday, 01 October 2008 )
|
|
|
Tuesday, 25 September 2007 |
While attending SB Best 2007 it became painfully apparent that the Build & Deploy track just wasn't delivering the goods to it's audience. Sitting in the seats were programmers, release managers, QA folks and a buildmeister or two all looking for something to sink their teeth into. Everyone wanted that answer to "How do I... <insert typical question here>" to which we invariable don't answer. Instead the answer begins with, "Well... it depends..." and once pressed for an answer the solution doesn't seem to fit since their problem is bigger or just different and unique.
|
|
Last Updated ( Wednesday, 01 October 2008 )
|
|
|
Thursday, 24 August 2006 |
|
No matter what facet of IT work you are involved it will
always be important to keep the big picture in mind. In this entry I
will give you my take on the roll of IT in the enterprise.
No matter what sector your company is in the role of IT is fundamentally the same. This role should serve as a constant reminder
of who we are and just what it is we are supposed to be doing every time
we undertake an initiative.
|
|
Last Updated ( Wednesday, 01 October 2008 )
|
|
|
