Profile_bird

Hey there! michaelajamie is using Twitter.

Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What's happening? Join today to start receiving michaelajamie's tweets.

Already using Twitter
from your phone? Click here.

michaelajamie

  1. Been teaching Carter & Joey about harmonics with lasers, mirrors, mixing bowls & plastic wrap! 11:23 PM Nov 23rd from web
  2. Up late working. gotta plan T-Day meal. Angela recouperating. Boys are off-track from school & stir crazy! 11:22 PM Nov 23rd from web
  3. There are lots of famous examples. More commonly we experience inefficient & bogged down systems. Good CM avoids much of this. 8:44 PM Oct 21st from web
  4. Ex. 2: IADB VP & developers conspire to steal from the bank by diverting funds. 8:42 PM Oct 21st from web
  5. and, left to chance or momentum, CM issues can endanger the org... Ex. 1: NASDAQ deploys incorrect software rev.s causing 3 hr crash. 8:39 PM Oct 21st from web
  6. The problem is getting senior mgt to accept that a "development tool" like version control will shortly become a mission critical component. 8:34 PM Oct 21st from web
  7. large teams solving immense & complex problems do so with the assistance of a well planned & designed CM system. 8:31 PM Oct 21st from web
  8. I might be inclined to accept that this is just a fact of software development, except that I have seen dozens of environments where --> 8:29 PM Oct 21st from web
  9. and enormous schedule & failure risk in aggregating, building & deploying applications. 8:27 PM Oct 21st from web
  10. This is a long winded way of saying that an improperly designed CM system equates to significant labor costs, higher skill requirements--> 8:25 PM Oct 21st from web
  11. completely ignored, because they do not represent real world processes. 8:21 PM Oct 21st from web
  12. System performance suffers. Change process does not meet the needs of the organization. Often, automated workflows & notifications are --> 8:21 PM Oct 21st from web
  13. But, after a short while these chickens come home to roost. Build & deployment processes become labor intensive & unweildy.--> 8:19 PM Oct 21st from web
  14. We ignore scalability in system configuration, security, process flow, nomenclature, etc... This works fine for pre-production work... --> 8:18 PM Oct 21st from web
  15. it's understandable. We tend to implement systems similar to what we know... i.e. - basic version control, tip releases, etc. --> 8:15 PM Oct 21st from web
  16. I've noticed common prob.s in org.s new to CM systems. It's common to ignore process scalability in favor of rapid deployment... --> 8:14 PM Oct 21st from web
  17. Most of my work is really team coordination & mentoring! 8:46 AM Oct 17th from web
  18. Back home in Colorado. Designing enterprise build & deploy system for client on Long Island. Working from home this week. 8:44 AM Oct 17th from web
  19. I think we're gonna go with cmcrossroads for this particular forum. I've contributed many times... But, I've never started a forum. 10:33 AM Oct 1st from web
  20. Hmmm... I'm thinking about where to place a blog with advice, warnings, procedures, etc. for Serena Dimensions uploads. Thoughts? 9:07 AM Sep 30th from web
  • Name Michael Ajamie
  • Location NYC & Denver
  • Web http://www.cm-pla...
  • Bio This Twitter is for CM professionals & addresses CollabNet & Serena products.
4 Following 6 Followers 1 Listed
Serena Software Jack Repenning Guy Martin CollabNet Inc