9/13/2023 0 Comments Wikipedia intel tick tock![]() ![]() ![]() Therein lies the cycle: 4-5 weeks of maintenance updates are followed by 2-3 weeks of feature releases and patches or a lull.Ĭoincidentally, this is very like Intel's tick-tock model. The low intensity period provides an incentive to produce quality code. Even if there are no issues with the feature, the development team is encouraged to "take it easy" during this hold period.This provides insurance for the release, should something go wrong. The development team that coded the feature is on hand to solely dedicate themselves to related bug fixes.However the development team that coded the feature for that release, would not take on another for up to 2 weeks after. The team would effectively be "on hold". Each feature's development cycle was staggered such that for every 4-5 releases, 1 of them was a feature. Whenever a development team completed a feature, it was rolled out the following day after integrated testing. Occasionally, releases occurred twice in a week if a critical issue arose. Each week, the production support team pushed a new update to production. In effect, at any one time, multiple teams were working on feature development while a dedicated production support team focused on resolving bugs. R&D utilized a Lean software development with very short release cycles. The Research and Development (R&D) department had an interesting approach to software lifecycles. In this particular company, we had a release once (and occasionally, even twice) a week. Many corporate companies do have periods of trouble-free releases over months. Now in most cases, a timeline like this is not surprising. Months of releases were, pun intended, clockwork. But it was not the use of the strategy that was remarkable.Įvery single release was smooth. Has it been done before?Ī startup-style company I worked at previously, employed this very concept while unaware. Would this strategy work for software as well as hardware? It all seems so familiar. A "tick" sounds exactly like a maintenance release while a "tock" resembled a feature pack. When I first read about this strategy, I drew parallels with my experience in software development lifecycles. This is often rewriting the entire design of the chip, adding new functions and instruction sets. It usually involves a shrink in the manufacturing process as well as correction of errata discovered since the microarchitecture release.Ī "tock" is an overhaul or development of new microarchitecture. Intel's success and dominance in the mid 2000s is sometimes attributed to their famous tick-tock model.Ī "tick" is an improvement of the microarchitecture. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |