Iran Military Forum

-14 fighter aircraft 12 years ago because of severe damage to all major parts of it had vanished, Professionals working with base operations and flight test successfully completed.

General Amir Ali minimal second pilot said base of professionals with more than 47 hours to produce 550 thousand pieces of tender, the aircraft flew again returned to the battalion.

vedio link : http://www.militaryparsi.ir/gallerys/viewvideo/49/هواپیماهای-جنگنده-،-بمب-افکن-،-اکتشافی/ویدیو-تعمیر-اساسی-اف-14-پس-از-12-سال-زمین-گیری.html

download video : http://www.militaryparsi.ir/hwdvideos/uploads/du3h6yau4yamx5.flv

http://it.toolbox.com/blogs/lim/fa18-has-50-less-parts-than-f14-24890

   
F/A-18 has 50% less parts than F-14


This weekend I was watching the documentary on F/A-18 Super Hornet. At one point presenter in the show was comparing F/A-18 with a "legend of the fleet" F-14 Tomcat, and speaking in favor of F/A-18 he said that "in comparison to F-14, F/A-18 has 50% less parts which just by itself makes it more reliable and simpler platform to maintain due to less components that can fail."

There is something here that most in IT often lose out of sight. All engineering fields, including software engineering, tell us that smaller and simpler engineering products have lower likelihood of failure and that they are simpler to maintain.

I seek this principle in all aspects of my work, even when writing, or learning. Complicated SOA diagrams or hyper-wired UML diagrams worry and trouble me.

I like small, simple but smartly implemented components. I like ideas behind and the implementation of UNIX kernel, HTTP protocol, REST web services and SQL just for these reasons.

In engineering smaller and simpler is better (for as long as it is a complete solution).