+1. Thanks ! -- Pierre Sahores mobile : 06 03 95 77 70 www.sahores-conseil.com
> Début du message réexpédié : > > De: Bob Sneidar <[email protected]> > Objet: Rép : [OT] Good Read/View on The Uncertainty Of The Future > Date: 17 septembre 2015 19:02:45 UTC+2 > À: How to use LiveCode <[email protected]> > Répondre à: How to use LiveCode <[email protected]> > > Excellent post. I think this mail list actually is one of the great examples > of collaboration I have yet seen. We have graphic guys, core developers, > database guys, interface guys all cooperating and communicating and helping > one another, but not for a specific company, but rather for the love of the > development environment itself. > > I also think that Livecode is a fairly good example of what he is talking > about. It provides us with a series of objects that can be put together as we > see fit. Of course, dealing with the issue of being compatible with current > and future devices is, as the author concedes, an ongoing one, and while > improvements can and perhaps should be made to the geometry manager (as an > example) the problem of open scaling is really one that if you think about it > an extremely complex one. > > I don't see how we can ever get away from special case development to be > compatible with all potential devices, even from a web based perspective, as > powerful as the tools presently available and soon to be available are. We > will never be able to design for a full sized monitor on a high end > workstation and expect to scale to a watch on someone's wrist, or vise versa > for that matter. The problem is not just one of scale, but of ability. There > are simply some things that cannot be done on a watch based browser. > > But I really like the bit: > > Great minds discuss ideas. Average minds discuss events. Small minds discuss > people. Henry Thomas > Buckle<http://quoteinvestigator.com/2014/11/18/great-minds/> > > I have expressed to up and coming IT people who are struggling with the vast > amount of information and learning that seems to be so oppressive, that the > trick is not learning everything about a particular system, but rather > understanding the system itself. What are the problems the system is > addressing? How do the components of the system interact with each other? > When I went through Naval training on the radar system I was to operate and > maintain many years ago, their approach to the training was top down, > starting with the major components, the operator console, the director, the > CW and pulse transmitters etc. Then they went into each major subsystem and > broke that down until we were looking at individual circuit boards. Because > we got that overview first, we were able to understand each subsystem and how > each component integrated with the whole, and why. > > I read in a really good book once, "Get knowledge. And with it, get > understanding." > > Bob S > > > On Sep 16, 2015, at 15:42 , Scott Rossi > <[email protected]<mailto:[email protected]>> wrote: > > A video with transcript by web designer/consultant Brad Frost. The talk > is targeted at web developers, but the concepts are applicable to any > coder or application developer. > > I Have No Idea What The Hell I Am Doing > http://bradfrost.com/blog/post/i-have-no-idea-what-the-hell-i-am-doing/ > > > Regards, > > Scott Rossi > Creative Director > Tactile Media, UX/UI Design > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
