SKU: 43645770273

COMP Cams Camshaft FC 287T H-107 T Thumper

Sale price$211.95 Regular price$235.50
Save 10%

Shipping Estimate
USA
  • USA
  • CAN

Ships within 48 hours · Estimated delivery Jul 12 - Jul 17

Promo Codes Available:

For Your Every Summer RSVP, with Code: SUMMER15

Description

COMP Cams Camshaft FC 287T H-107 T ThumperMutha' Thumpr 234 249 Hydraulic Flat Cam for Ford 351C, 351M 400M. High performance street strip, needs 9: 1 compression, 2500+ stall, intake, Gears and headers, rough idle. Catalog User 1 This Part Fits: Year Make Model Submodel 1971 1974 DeTomaso Pantera Base 1981 1985 DeTomaso Pantera GT5 1984 1986 DeTomaso Pantera GT5 S 1981 DeTomaso Pantera GTS 1978 1982 Ford Bronco Custom 1978 Ford Bronco Northland 1978 1981 Ford Bronco Ranger XLT 1982 Ford

Mutha' Thumpr 234/249 Hydraulic Flat Cam for Ford 351C, 351M-400M. High performance street/strip, needs 9:1 compression, 2500+ stall, intake, Gears and headers, rough idle.

Catalog
User 1

This Part Fits:

Year Make Model Submodel
1971-1974 DeTomaso Pantera Base
1981-1985 DeTomaso Pantera GT5
1984-1986 DeTomaso Pantera GT5-S
1981 DeTomaso Pantera GTS
1978-1982 Ford Bronco Custom
1978 Ford Bronco Northland
1978-1981 Ford Bronco Ranger XLT
1982 Ford Bronco XLS
1982 Ford Bronco XLT Lariat
1969-1974 Ford Country Sedan Base
1969-1974 Ford Country Squire Base
1969-1972 Ford Custom Base
1969-1977 Ford Custom 500 Base
1980-1981 Ford E-250 Econoline Base
1980-1981 Ford E-250 Econoline Chateau
1980-1981 Ford E-250 Econoline Custom
1980-1981 Ford E-250 Econoline Club Wagon Base
1980-1981 Ford E-250 Econoline Club Wagon Chateau
1980-1981 Ford E-250 Econoline Club Wagon Custom
1980-1981 Ford E-350 Econoline Base
1980-1981 Ford E-350 Econoline Chateau
1980-1981 Ford E-350 Econoline Custom
1980-1981 Ford E-350 Econoline Club Wagon Base
1980-1981 Ford E-350 Econoline Club Wagon Chateau
1980-1981 Ford E-350 Econoline Club Wagon Custom
1975-1976 Ford Elite Base
1977-1978 Ford F-100 Base
1977-1979 Ford F-100 Custom
1977-1978 Ford F-100 Northland
1977-1979 Ford F-100 Ranger
1978-1979 Ford F-100 Ranger Lariat
1977-1979 Ford F-100 Ranger XLT
1977 Ford F-100 XLT
1977-1978 Ford F-150 Base
1977-1981 Ford F-150 Custom
1977-1978 Ford F-150 Northland
1977-1981 Ford F-150 Ranger
1978-1981 Ford F-150 Ranger Lariat
1977-1981 Ford F-150 Ranger XLT
1977 Ford F-150 XLT
1977-1978 Ford F-250 Base
1977-1981 Ford F-250 Custom
1977-1978 Ford F-250 Northland
1977-1981 Ford F-250 Ranger
1978-1981 Ford F-250 Ranger Lariat
1977-1981 Ford F-250 Ranger XLT
1977 Ford F-250 XLT
1977-1978 Ford F-350 Base
1977-1981 Ford F-350 Custom
1977-1978 Ford F-350 Northland
1977-1981 Ford F-350 Ranger
1978-1981 Ford F-350 Ranger Lariat
1977-1981 Ford F-350 Ranger XLT
1977 Ford F-350 XLT
1969-1970 Ford Fairlane 500
1969 Ford Fairlane Base
1970 Ford Falcon Base
1970 Ford Falcon Futura
1969-1974 Ford Galaxie 500 Base
1969-1970 Ford Galaxie 500 XL
1972-1976 Ford Gran Torino Base
1973-1976 Ford Gran Torino Brougham
1974-1975 Ford Gran Torino Elite
1972-1975 Ford Gran Torino Sport
1972-1976 Ford Gran Torino Squire
1969-1978 Ford LTD Base
1970-1976 Ford LTD Brougham
1985-1986 Ford LTD Country Squire
1986 Ford LTD Country Squire LX
1985-1986 Ford LTD Crown Victoria
1986 Ford LTD Crown Victoria LX
1975-1978 Ford LTD Landau
1977-1979 Ford LTD II Base
1977-1978 Ford LTD II Brougham
1979 Ford LTD II Landau
1977-1979 Ford LTD II S
1977 Ford LTD II Squire
1969-1973 Ford Mustang Base
1971-1972 Ford Mustang Boss 351
1970-1973 Ford Mustang Grande
1970-1973 Ford Mustang Mach 1
1969-1974 Ford Ranch Wagon Base
1970 Ford Ranch Wagon Police Cruiser
1969-1979 Ford Ranchero 500
1969-1971 Ford Ranchero Base
1969-1979 Ford Ranchero GT
1970-1979 Ford Ranchero Squire
1972-1974,1977-1979 Ford Thunderbird Base
1978 Ford Thunderbird Diamond Jubilee
1979 Ford Thunderbird Heritage
1978-1979 Ford Thunderbird Town Landau
1971 Ford Torino 500
1970-1976 Ford Torino Base
1970-1971 Ford Torino Brougham
1971 Ford Torino Cobra
1970-1971 Ford Torino GT
1970-1971 Ford Torino Squire
1970-1974 Mercury Colony Park Base
1969 Mercury Comet Base
1970-1973,1977-1979 Mercury Cougar Base
1977 Mercury Cougar Brougham
1977 Mercury Cougar Villager
1970-1979 Mercury Cougar XR-7
1969-1971 Mercury Cyclone Base
1970-1971 Mercury Cyclone GT
1970-1971 Mercury Cyclone Spoiler
1975-1978,1980,1986 Mercury Grand Marquis Base
1980 Mercury Grand Marquis Colony Park
1986 Mercury Grand Marquis LS
1970-1974,1978,1980 Mercury Marquis Base
1970-1974,1978,1980 Mercury Marquis Brougham
1969-1976 Mercury Montego Base
1975 Mercury Montego Brougham
1972-1973 Mercury Montego GT
1969-1976 Mercury Montego MX
1970-1974,1976 Mercury Montego MX Brougham
1976 Mercury Montego MX Villager
1970-1975 Mercury Montego Villager
1970-1974 Mercury Monterey Base
1970-1974 Mercury Monterey Custom
Shipping Notes
  • Free Standard Shipping on $100+ Orders to the USA.
  • Except Preorder products are shipped in 48 hours.
  • Delivery to the USA:
  1. Standard Shipping : 3-10 business days
  • If time is of the essence, please consider selecting expedited delivery for faster service.
Exchange/Return Notes
  • We offer a 30-day return/exchange service after receiving.
  • Final sale items are not eligible for returns or exchanges.
  • To process your return/exchange, please contact us at [email protected]
  • Please click here for more details>>> Return & Exchange Policy
SKU: 43645770273

Discover Niche Categories That Outsell

Top-Converting Item to Boost Your Average Order

4.1 ★★★★★
Based on 1996 reviews
Sort
Highest Rating
Newest First
Oldest First
Product Reviews
C
Verified Purchase
cloud-learner
Bozeman, US
★★★★★ 3
have some good contents but too general
Format: Paperback
The book covers some good points, but overall, it's too general.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on June 28, 2024
E
Verified Purchase
Engineer Dude
Grantham, US
★★★★★ 3
Why Politics in a Tech Book????
Format: Kindle
Well... I'm surprised to see the book blatently calls out its dedication to Black Lives Matter, which is in all caps so I assume it's referring to the political organization. It goes on to speak of 2020 being the year of an "awakening of injustices of systematic racism"... I thought I was buying a technical book??? Had I known this political bs was included I wouldn't have purchased it! However, I bought and I'm still reading it. If the politics goes away and the TECHNICAL content is good I'll update my review.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on December 13, 2020
P
Verified Purchase
PeaceBee
Pawtucket, US
★★★★★ 2
Not good use of time
Format: Paperback
It’s not clear who this book targets - neither experts nor novice will benefit. There are expert perspectives, only few of these are helpful, rest are too generic to be of any use. For instance the last entry is one an engineer who shares how she went from zero to expert in cloud engineering in six months but fails to mention a single resource or pathway for others to follow.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on April 2, 2022
N
Nilendu Misra
Phoenix, US
★★★★★ 3
Uneven compendium of tips and insights, but still very useful
Format: Kindle, Format: Kindle
“In theory, theory and practice are the same. In practice, they are not" is why such bottom-up insights and lessons from the field are the fastest way to learn real life stuff. This series had a GREAT start with "Engineering Management" - I guess because it is way more subjective than Cloud Engineering and offered a variety of non-overlapping POVs. This one is a mixed bag, perhaps because "Cloud Engineering" was perceived amorphously by the authors. The scope was broad - from cloud-native (architecture), to cloud-ready (topology), to cloud-operations, to choosing tech (e.g., Lambda/serverless), to -ilities and economics -- it is like celebrating Halloween, Christmas and Labor Day together in a single long weekend. I would give it 4/+ stars if at least 25% of such a book was "superb", giving 3 because about 10% of the book is. That still leaves 10 solid insights or learning that would otherwise take many failures to learn. And failures, especially in this emerging domain of complexity, is VERY expensive. Would love to see more books like this. Let's summarize some key insights - -- Real-time visibility across the entire DevOps lifecycle is key to winning in cloud. -- Operations, especially operations at scale, is extremely hard. So, wherever possible, use Managed Services. -- Distinguish between "availability" and "uptime" and measure each separately, and concretely. -- In FaaS/Serverless, calling a function synchronously increases debugging complexity. -- Good code is like good joke - it needs no explanation. -- "Building your app or platform on top of the abstractions that a cloud provider gives you does not make the underlying layers stop existing. In many cases, it makes them even more important." That makes the failure modes LESS obvious than we were used to. Therefore having "extreme visibility" into your systems will help "separate the issues at the layer you're focused on from the fundamental system issues". i.e., just because what was under the hood is now even less visible, don't forget them. Many recent "cloud failures" have been in networking fault domains. -- Cloud is not optimized for replacing static infrastructures. -- Containers, service meshes and serverless jumpstart dev productivity but they also change the attack surface of apps and infra. -- "Number of containers that are alive for 10 sec or less has doubled to 22%". 73% of all containers live for 30 minutes or less. -- Adopt an "assume breach" stance for everything. Have a break-glass account. -- Ensure you have a thorough understanding of where and how secrets are secured. -- Grey failures (transient degradation of services) are often worse than complete crashes, since the latter have a short feedback loop. -- Resilience engineering has existed as a sub-discipline within safety sciences. We just recently started applying its concepts in technology. Resilience can be thought of as a "socio-technical system" with Robustness ("system X has property Y that is robust in sense Z to perturbation W"); Reliability (consistent operations or service levels); Rebound (ability to deal with a chaotic situation using structures developed AND deployed BEFORE the chaos). In other words, robustness protects systems against a SPECIFIC type of failure mode. When a system is robust in many dimensions, it approaches good resilience to failure. -- Resilience is something you "do", not something you "have". Resilience is a verb. -- Moving from one class of nines to the next is 10 times more expensive. -- Production System really means "system that someone else, anyone else, can hold you accountable for". -- Most common theme across incidents is that something, somewhere was surprising. -- Incidents are unplanned investments...your challenge is to maximize ROI. -- We used to think of scale in two dimensions - horizontal (more) and vertical (bigger). In cloud, think of "scale out" (when demands increase) and "scale in" (when demand decreases). -- Architecture diagram is also a map of failure modes. -- Async communication is a friend of Cloud Reliability. -- Test in production is a competitive advantage. The complexity of traffic patterns going through high-scale production systems is increasingly harder to reproduce in a controlled env. -- Hundreds of open issues is fine, but if the repo has gone months (or, years!) without a release, THAT is a warning sign. -- It is hard to write good tests for bad code. -- Platforms come and go. But first principles and patterns will always exist, because they are the ones and zeros.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on November 6, 2023
M
M. Klocker
New York, US
★★★★★ 2
Shallow, biased and significantly overpriced
Format: Paperback
Well, this purchase was a disappointment. 20% of the pages are dedicated to just highlighting the bios and backgrounds of the many different authors that contributed this great wisdom. And let me be clear, the authors are solid. They are professionals with credible backgrounds and experience. But it's the format and constraints of this book that makes it virtually impossible for that to shine through. Because the rest of the book (80%) is dedicated to the so called "97 things every cloud engineer should know". And unfortunately the average length of one of these "things" is about 1.5 pages long, and as such extremely shallow and in about 30% of the cases straight up promotions for specific company services. You will find Google cloud advocates telling you to use managed services, of Google of course. AWS engineers telling you to avoid them and use IaaS. LaunchDarkly employees telling you to use feature flags. The list goes on. The TL;DR: here is that if you have built anything on the cloud in the last 2 years, this book is going to be a waste of your time and money. You are better of googling: "cloud best practices" and dedicating 2h to reading the first 10 non-ad related search results.
WAS THIS REVIEW HELPFUL?YesReportShare
Reviewed in the United States on March 23, 2022

recommand products