Notes on Web and Mobile App Development

https://www.quora.com/Is-Google-Translator-the-best-among-all Does it work and how? However, whatever the technology is used for development of Google Translate software, the quality of the outcome depends on several factors.     Language Pair or language combination. Why? Because Google does not so much generate some tricky and fancy translations out of nothing. It has a database of ready made translations. Where they were all taken from? They were all taken from works done by real translators. And the more translators available for particular language pair the higher quality of translation can be. English to German translation or English to French translation can be a good example of better quality in Google Translate. The rest of languages can leave much to be desired, like in case with English to Russian translation or English to Turkish translation.     Subject matter. The quality of specific translation also depends on the language pair. The more pr...

http://martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf The best part I liked about it was this statement: Software is not limited by physics, like buildings are. It is limited by imagination, by design, by organization. In short, it is limited by properties of people, not by properties of the world. “We have met the enemy, and he is us.” This seems very true; I have heard many senior architects resembling software architecture with a Building Construction during their presentations, while I tend to agree on some of the aspects like creating a blue print before implementing the building but I do feel that building a software and constructing a building don’t make a fit analogy. As martin mentions in his article, once you have designed a building it is very difficult to change the basement, on the other hand if you have layered your software well and applied the relevant design patterns you can still make shifts to your foundations without impacting the entire software sta...

Martin Fowler Software Development in the 21st Century. Software Development in the 1990s Late Projects          Unhappy Users                                              The Cure is                          Bloated Projects                                       Plan-Driven                                                                                     Processes                      Buggy Software  ...