Salakhetdinov Shamil
mcp2004 at mail.ru
Thu Feb 14 00:14:44 CST 2013
Hi Hans -- There is no way to be good (I mean competitive) at many (programming) technologies, especially modern programming technologies. That conclusion comes from experience of many developers. One thing is to have a good understanding - and a very different thing is to have a good *working experience* - it takes years to master the latter. What a specialist will make in hours will require days from a "jack of all trades". So "high rates" of specialists would be more than affordable - in fact they will be the one of the main "drives" of the economy. Period. Thank you. -- Shamil Среда, 13 февраля 2013, 18:24 -08:00 от Hans-Christian Andersen <hans.andersen at phulse.com>: >I have to disagree. In fact, I think that is the world we came from and these days technology is evolving at such a pace that it is impossible to be a specialist in anything. > >It is far more desirable to have someone who has a decent understanding of many things and be able to wear many hats. Someone who knows enough to be easily be brought up to speed on your project. > >And this can also be reason based purely on economic factors. A specialist can demand far more in compensation and, in economic times like these, companies and startups are a bit more spend thrift. > >- Hans > > >On 2013-02-13, at 12:16 PM, Salakhetdinov Shamil < mcp2004 at mail.ru > wrote: > >> Hi Jim -- >> >> <<< >> Mixing, matching and mashups is the new tech future. >> Agreed. >> >> But one cannot be a good, even satisfactory, "jack of many (software development/tech.) trades". >> The tech. future IMO are standards, industrialization and specialization. >> Industrialization doesn't mean (here) that there will be no place for "one jack"/SMB software development/tech. companies - industrialization means that custom software development to be competitive will have to be driven by well educated in computer science and application development (process) engineers and managers, engineers and managers who will be taught to use "the right tool for the right job" and when for a certain project/task they will find they aren't skilled enough to apply the most suitable tool(s) they will effectively delegate that project/job to a third-party and acquire/integrate the results of their work via standard/custom (web) APIs. >> >> -- Shamil >> <<< skipped >>> >