recentpopularlog in

robertogreco : johnmaeda   29

The Jacob’s Ladder of coding — Medium
"Anecdotes and questions about climbing up and down the ladder of abstraction: Atari, ARM, demoscene, education, creative coding, community, seeking lightness, enlightenment & strange languages"

"With only an hour or two of computer time a week, our learning and progress was largely down to intensive trial & error, daily homework and learning to code and debug with only pencil and paper, whilst trying to be the machine yourself: Playing every step through in our heads (and on paper) over and over until we were confident, the code did as we’d expect, yet, often still failing because of wrong intuitions. Learning this analytical thinking is essential to successful debugging, even today, specifically in languages / environments where no GUI debugger is available. In the late 90s, John Maeda did similar exercises at MIT Media Lab, with students role-playing different parts of a CPU or a whole computer executing a simple process. Later at college, my own CS prof too would often quote Alan Perlis:
“To understand a program you must become both the machine and the program.” — Alan Perlis

Initially we’d only be using the machine largely to just verify our ideas prepared at home (spending the majority of the time typing in/correcting numbers from paper). Through this monastic style of working, we also learned the importance of having the right tools and balance of skills within the group and were responsible to create them ourselves in order to achieve our vision. This important lesson stayed with me throughout (maybe even became) my career so far… Most projects I worked on, especially in the past 15 years, almost exclusively relied on custom-made tooling, which was as much part of the final outcome as the main deliverable to clients. Often times it even was the main deliverable. On the other hand, I’ve also had to learn the hard way that being a largely self-sufficient generalist often is undesired in the modern workplace, which frequently still encourages narrow expertise above all else…

After a few months of convincing my parents to invest all of their saved up and invaluable West-german money to purchase a piece of “Power Without the Price” (a much beloved Atari 800XL) a year before the Wall came down in Berlin, I finally gained daily access to a computer, but was still in a similar situation as before: No more hard west money left to buy a tape nor disk drive from the Intershop, I wasn’t able to save any work (apart from creating paper copies) and so the Atari was largely kept switched on until November 10, 1989, the day after the Berlin Wall was opened and I could buy an XC-12 tape recorder. I too had to choose whether to go the usual route of working with the built-in BASIC language or stick with what I’d learned/taught myself so far, Assembly… In hindsight, am glad I chose the latter, since it proved to be far more useful and transportable knowledge, even today!"

"Lesson learned: Language skills, natural and coded ones, are gateways, opening paths not just for more expression, but also to paths in life.

As is the case today, so it was back then: People tend to organize around specific technological interests, languages and platforms and then stick with them for a long time, for better or worse. Over the years I’ve been part of many such tool-based communities (chronologically: Asm, C, TurboPascal, Director, JS, Flash, Java, Processing, Clojure) and have somewhat turned into a nomad, not being able to ever find a true home in most of them. This might sound judgemental and negative, but really isn’t meant to and these travels through the land of languages and toolkits has given me much food for thought. Having slowly climbed up the ladder of abstraction and spent many years both with low & high level languages, has shown me how much each side of the spectrum can inform and learn from the other (and they really should do more so!). It’s an experience I can highly recommend to anyone attempting to better understand these machines some of us are working with for many hours a day and which impact so much of all our lives. So am extremely grateful to all the kind souls & learning encountered on the way!"

"In the vastly larger open source creative computing demographic of today, the by far biggest groups are tight-knit communities around individual frameworks and languages. There is much these platforms have achieved in terms of output, increasing overall code literacy and turning thousands of people from mere computer users into authors. This is a feat not be underestimated and a Good Thing™! Yet my issue with this siloed general state of affairs is that, apart from a few notable exceptions (especially the more recent arrivals), there’s unfortunately a) not much cross-fertilizing with fundamentally different and/or new ideas in computing going on and b) over time only incremental progress is happening, business as usual, rather than a will to continuously challenge core assumptions among these largest communities about how we talk to machines and how we can do so better. I find it truly sad that many of these popular frameworks rely only on the same old imperative programming language family, philosophy and process, which has been pre-dominant and largely unchanged for the past 30+ years, and their communities also happily avoid or actively reject alternative solutions, which might require fundamental changes to their tools, but which actually could be more suitable and/or powerful to their aims and reach. Some of these platforms have become and act as institutions in their own right and as such also tend to espouse an inward looking approach & philosophy to further cement their status (as owners or pillars?) in their field. This often includes a no-skills-neccessary, we-cater-all-problems promise to their new users, with each community re-inventing the same old wheels in their own image along the way. It’s Not-Invented-Here on a community level: A reliance on insular support ecosystems, libraries & tooling is typical, reducing overall code re-use (at least between communities sharing the same underlying language) and increasing fragmentation. More often than not these platforms equate simplicity with ease (go watch Rich Hickey taking this argument eloquently apart!). The popular prioritization of no pre-requisite knowledge, super shallow learning curves and quick results eventually becomes the main obstacle to later achieve systemic changes, not just in these tools themselves, but also for (creative) coding as discipline at large. Bloatware emerges. Please do forgive if that all sounds harsh, but I simply do believe we can do better!

Every time I talk with others about this topic, I can’t help but think about Snow Crash’s idea of “Language is a virus”. I sometimes do wonder what makes us modern humans, especially those working with computing technology, so fundamentalist and brand-loyal to these often flawed platforms we happen to use? Is it really that we believe there’s no better way? Are we really always only pressed for time? Are we mostly content with Good Enough? Are we just doing what everyone else seems to be doing? Is it status anxiety, a feeling we have to use X to make a living? Are we afraid of unlearning? Is it that learning tech/coding is (still) too hard, too much of an effort, which can only be justified a few times per lifetime? For people who have been in the game long enough and maybe made a name for themselves in their community, is it pride, sentimentality or fear of becoming a complete beginner again? Is it maybe a sign that the way we teach computing and focus on concrete tools too early in order to obtain quick, unrealistically complex results, rather than fundamental (“boring”) knowledge, which is somewhat flawed? Is it our addiction to largely focus on things we can document/celebrate every minor learning step as an achievement in public? This is no stab at educators — much of this systemic behavior is driven by the sheer explosion of (too often similar) choices, demands made by students and policy makers. But I do think we should ask ourselves these questions more often."

[author's tweet: ]
coding  via:tealtan  2015  abstraction  demoscene  education  creativecoding  math  mathematics  howwelearn  typography  design  dennocoil  alanperlis  johnmaeda  criticalthinking  analyticalthinking  basic  programming  assembly  hexcode  georgedyson  computing  computers  atari  amiga  commodore  sinclair  identity  opensource  insularity  simplicity  ease  language  languages  community  communities  processing  flexibility  unschooling  deschooling  pedagogy  teaching  howweteach  understanding  bottomup  topdown  karstenschmidt 
december 2015 by robertogreco
DE$IGN | Soulellis
"I’ve been thinking a lot about value and values.

Design Humility and Counterpractice were first attempts to build a conversation around the value of design and our values as designers. They’re highly personal accounts where I try to articulate my own struggle with the dominant paradigm in design culture today, which I characterize as —

the relentlessness of branding
the spirit of the sell
the focus on product
the focus on perfection

and they include some techniques of resistance that I’ve explored in my recent work, like —

slowness (patience)
chance (nature, humility, serendipity)
giving away (generosity echo)

I’ve been calling them techniques, but they’re really more like values, available to any designer or artist. Work produced with these criteria runs cross-grain to the belief that we must produce instantly, broadcast widely and perform perfectly.

Hence, counterpractice. Cross-grain to common assumptions. Questioning.

And as I consider my options (what to do next), I’m seriously contemplating going back to this counterpractice talk as a place to reboot. Could these be seen as principles — as a platform for a new kind of design studio?

I’m not sure. Counterpractice probably need further translation. An idea like ”slowness” certainly won’t resonate for many, outside of an art context. And how does a love for print-on-demand and the web fit in here? Perhaps it’s more about “variable speed” and the “balanced interface” rather than slow vs fast. Slow and fast. Modulated experience. The beauty of a printed book is that it can be scanned quickly or savored forever. These aren’t accidental qualities; they’re built into the design.

[image by John Maeda: "DE$IGN"]

I’m thinking about all of this right now as I re-launch Soulellis Studio as Counterpractice. But if there’s anything that most characterizes my reluctance to get back to client-based work, it’s DE$IGN.

John Maeda, who departed RISD in December, where I am currently teaching, recently delivered a 4-minute TED talk, where he made this statement:

“From Design to DE$IGN.”

He expands that statement with a visual wordmark that is itself designed. What does it mean? I haven’t seen the talk yet so I can only presume, out of context. These articles and Maeda’s blog post at Design and Venture begin to get at it.

Maeda’s three principles for using design in business as stated in the WSJ article are fine. But they don’t need a logo. Designing DE$IGN is a misleading gesture; it’s token branding to sell an idea (in four minutes—the fast read). So what’s the idea behind this visual equation? As a logo, it says so many things:

All caps: DE$IGN is BIG.
It’s not £ or ¥ or 元: DE$IGN is American.
Dollar sign: DE$IGN is money.

DE$IGN is Big American Money.

and in the context of a four-minute TED talk…

DE$IGN is speed (four minutes!)
DE$IGN is the spirit of selling (selling an idea on a stage to a TED audience)
DE$IGN is Helvetica Neue Ultra Light and a soft gradient (Apple)
DE$IGN is a neatly resolved and sellable word-idea. It’s a branded product (and it’s perfect).

In other words, DE$IGN is Silicon Valley. DE$IGN is the perfect embodiment of start-up culture and the ultimate tech dream. Of course it is — this is Maeda’s audience, and it’s his new position. It works within the closed-off reality of $2 billion acquisitions, IPOs, 600-person design teams and Next Big Thing thinking. It’s a crass, aggressive statement that resonates perfectly for its audience.

[Image of stenciled "CAPITALISM IS THE CRI$IS"]

DE$IGN makes me uneasy. The post-OWS dollar sign is loaded with negative associations. It’s a quick trick that borrows from the speed-read language of texting (lol) to turn design into something unsustainable, inward-looking and out-of-touch. But what bothers me most is that it comes from one of our design leaders, someone I follow and respect. Am I missing something?

I can’t help but think of Milton Glaser’s 1977 I<3NY logo here.

[Milton Glaser I<3NY]

Glaser uses a similar trick, but to different effect. By inserting a heart symbol into a plain typographic treatment, he too transformed something ordinary (referencing the typewriter) into a strong visual message. Glaser’s logo says that “heart is at the center of NYC” (and it suggests that love and soul and passion are there too). Or “my love for NYC is authentic” (it comes from the heart). It gives us permission to play with all kinds of associations and visual translations: my heart is in NYC, I am NYC, NYC is the heart of America, the heart of the world, etc. .

Glaser’s mark is old-school, east coast and expansive; it symbolizes ideas and feelings that can be characterized as full and overflowing. And human (the heart). It’s personal (“I”), but all about business: his client was a bankrupt city in crisis, eager to attract tourists against all odds.

Maeda’s mark is new money, west coast and exclusive. It was created for and presented to a small club of privileged innovators who are focused on creating new ways to generate wealth ($) by selling more product.

Clever design tricks aside, here’s my question, which I seem to have been asking for a few years now. Is design humility possible today? Can we build a relevant design practice that produces meaningful, rich work — in a business context — without playing to visions of excess?

I honestly don’t know. I’m grappling with this. I’m not naive and I don’t want to paint myself into a corner. I’d like to think that there’s room to resist DE$IGN. I do this as an artist making books and as an experimental publisher (even Library of the Printed Web is a kind of resistance). But what kind of design practice comes out of this? Certainly one that’s different from the kind of business I built with Soulellis Studio."
paulsoulellis  2014  conterpractice  design  humility  capitalism  resistance  branding  speed  slow  consumerism  sales  salesmanship  perfection  wabi-sabi  thingness  longevity  slowness  patience  nature  chance  serendipity  generosity  potlatch  johnmaeda  questioning  process  approach  philosophy  art  print  balance  thisandthat  modulation  selling  ted  tedtalks  apple  siliconvalley  startups  culture  technology  technosolutionsism  crisis  miltonglaser  1977  love 
june 2014 by robertogreco
Seven-second review of John Maeda’s The Laws of Simplicity | Speedbird
[I pulled this up today to illustrate a point elsewhere, time to bookmark it.]

[Look into the comments: ]

"nicolas, precisely. I was shocked at the overweening self-regard that rolled off just every page of this book (and yes, I did actually read it through to the end).

I was shocked at the amount of self-indulgent, meandering filler; I was shocked by the patronizing admonitions that “nobody likes a potty-mouth” as justification for the persistent bowdlerization of time-honored, pungently useful phrases like “RTFM”; I was shocked at the level of insight being presented as somehow novel or interesting.

And what’s up with all these turgid acronyms? SHE? SLIP?? It’s deafeningly tin-eared. Maeda’s become the Thomas Friedman of design.

If I can venture an opinion as to what happened: Maeda has Become A Sensei. This is something that seems to confront a great many talents at mid-career; the tendency is not in any way exclusively East Asian, but the syndrome does seem to reach its crispest expression there. He’s entered a realm in which his prior body of achievement, and the regard it’s earned him, pre-validates just about anything he sets his hand to, and there’s nobody in a position to remind the emperor that he’s leaving the house nekkid.

If you or I or anybody we know had submitted this flyweight thesis to MIT Press – a thesis which manages to be painfully redundant, even over the length of its 100 pages – we’d have been laughed back to the Neolithic. But because it’s the issue of a certified Master…well, it must be OK. (If I sound bitter, it’s only because I was fooled into dropping fifteen bucks on this egotistical display that could have been much better spent…on toothpaste, or perhaps on toilet paper.)

The most egregious aspect of the Sensei Syndrome, by the way, is only partly the individual’s fault: reporters and other supplicants will turn to Sensei as a kind of Intellectual, Public, General Purpose (1), and ask for comment on something outside the domain of their expertise…which is then duly provided.

When all of you guys are legendary in your fields – and I have no doubt that you will be – you must promise me that when somebody comes along and asks you for such a quote, you’ll err on the side of discretion. Mommas, don’t let your babies grow up to be Senseis…"
johnmaeda  adamgreenfield  2007  senseis  acheivment 
february 2014 by robertogreco
Education Week: Why Make Reform So Complicated?
"In the realm of organizational improvement, complexity kills. It demoralizes employees and distorts the critical connection between effort and outcomes. It is the enemy of the most indispensable elements of improvement: clarity, priority, and focus.

That is the message of multiple prominent studies, from Jim Collins' 2001 best-seller Good to Great to more recent books like The Laws of Simplicity, by John Maeda, and Simple: Conquering the Crisis of Complexity, by Alan Siegel and Irene Etzkorn. These experts implore us to simplify: to prioritize, minimize, and employ only the clearest language in the service of focus. Only this will allow teams and individuals to understand, practice, and perfect those few, highest-priority skills and actions that are most critical to progress.

Education clearly doesn't get this. Perhaps no enterprise is more crippled by complexity than school improvement. For two decades, I've worked with educators in every kind of school and district. For every major initiative, a common theme emerges: There is simply too much to do, and most of it is maddeningly ambiguous and confusing.

Maybe it started with state-mandated strategic planning, which produced those book-length, jargon-laced documents with their impossibly long bulleted lists of goals, tasks, and action plans—which turned out to have no substantive effect on teaching quality.
Then came the standards movement."

"The transition to simple, priority-driven school improvement might require a kind of civil disobedience: a refusal, by a critical mass of educators, to implement anything unless it has been adequately piloted, amply proven, and then made clear and simple enough for educators to learn and implement successfully. If we insist on such conditions, we will move forward at a rate not seen before."
via:lukeneff  simplicity  education  policy  standards  commoncore  2014  complexity  organization  curriculum  mikeschmoker  standardization  leadership  administration  pedagogy  johnmaeda 
january 2014 by robertogreco
"In this climate of economic uncertainty, America is once again turning to innovation as the way to ensure a prosperous future.

Yet innovation remains tightly coupled with Science, Technology, Engineering and Math – the STEM subjects. Art + Design are poised to transform our economy in the 21st century just as science and technology did in the last century.

We need to add Art + Design to the equation — to transform STEM into STEAM.


STEAM is a movement championed by Rhode Island School of Design (RISD) and widely adopted by institutions, corporations and individuals.

The objectives of the STEAM movement are to:

• transform research policy to place Art + Design at the center of STEM
• encourage integration of Art + Design in K–20 education
• influence employers to hire artists and designers to drive innovation"
stem  steam  risd  johnmaeda  art  education  science 
july 2013 by robertogreco
Putting people first » Don Norman: John Maeda and I failed to connect
"As part of its Power of 10 lecture series, PARC Forum invited John Maeda, President of the Rhode Island School of Design, and Don Norman, Co-founder of the Nielsen Norman Group, last week for a dialogue on design and innovation.

The video is now online.

Here is what Don Norman had to write about it:
“It was a weird discussion. Although John and I have known each other for some time and started out in similar ways (he is a course 6 graduate of MIT — Electrical Engineering). So am I (my specialty was circuit design.) Both of us now consider ourselves to be designers. Moreover, I am a fan of his work. But it was difficult to engage.

I wanted to talk about complex design: interaction design, design planning, etc. He wanted to talk about the beauty of fonts, of knives, and even of the office chair. I tried to say these were simple products that barely needed any understanding of human behavior and cognition — I want to design the complex. He didn’t understand my point. In fact, when I specifically asked him how to design a networking connection scheme that would work for everyday people his answer was a long ramble that never even started to address the issue. Later, he admitted he had forgotten the question (which to me is evidence he either failed to understand it or didn’t care about it – I think the latter).

I agreed that form was not my focus. I guess he agreed that interaction was not his.

So we failed to connect. But many seemed to find the discussion of interest. Decide for yourself.”
designphilosophy  design  johnmaeda  via:mayonissen  donaldnorman 
august 2012 by robertogreco
Twitter / @johnmaeda: "Differentiate between har ...
"Differentiate between hard work and long work. Long work is just time-consuming." -from conv with Seth Godin
johnmaeda  sethgodin  work  working  effort  tcsnmy  unschooling  deschooling  rote  memorization  time  lcproject  learning  meaningmaking  rotelearning 
june 2011 by robertogreco
John Maeda Mulls RISD's Backlash Against His Cyber-Style Leadership | Co.Design
"Maeda acknowledges that he now understands social media can only take you so far in redesigning leadership. All those great hopes for leading by blogging, tweeting, & emailing proved inadequate to gritty business of persuading an actual living, breathing constituency to follow his direction…

Maeda has scaled back his blogging. He accepts that big Samsung screens he installed as a way to bring students together digitally, by allowing them to post new work, notices of events, & messages, never caught on. "Technologists believe that if they impose a solution, people will adopt it," he says. "But buy-in can't be bought."

Instead, he says, he's going about leading in old-fashioned way: building relationships one at a time, having coffee w/ faculty, jogging w/ students late at night, offering free pizza as an inducement to get them to show up & talk. These interactions are time-consuming, high-bandwidth, interactive, fiscally expensive for a busy president, & unscalable."
johnmaeda  risd  backlash  2011  learning  leadership  relationships  administration  management  duh  scalability  time  socialmedia  twitter  blogging  meaning  education  highered  highereducation  scale 
may 2011 by robertogreco
electronic computation is invisible: maeda at RISD (tecznotes) {best to read the whole thing, and also the Natalia Ilyin post]
"…post about Maeda’s difficulties at RISD is interesting, but I was particularly struck by broader resonance of this:

"The Medialab is much more random than that. This may help to illuminate why John’s approach is so alien to traditional art students. Paul Rand seems to think it’s John’s engineering background which interferes with his leadership ability at RISD, but I think it’s actually scarier. John’s approach is hands off & experimental. Anything goes. Confusing & startling people is valorized…

…NONE of these artists have managed to broach the basic limitation that electronic computation is invisible. All techno artwork thus far relies on impenetrable microchips which require observer/participants to form abstractions in order to appreciate them. Look how hard it is to teach art students to program…

…once you go back in time & look at a Maeda or PLW project & realize you can’t run their code anymore, the collapsing of reality can be devastating."
johnmaeda  michalmigurski  risd  2011  handsoff  leadership  management  disconnect  medialab  mit  engineering  confusion  experimentation  paulrand  computers  computation  art  electroniccomputation  invisibility  reality  collapsingofreality  administration  learning  change  abstraction  inpenetrability  technology  mitmedialab 
april 2011 by robertogreco
John Maeda at odds with RISD Faculty - natalia ilyin
"Maeda's made so many enemies and done so many wrong-headed things in such a short amount of time that I am reminded once again that IQ and intelligence are not the same thing. He's made many sweeping administrative errors, but it is this that bothers me: he thinks himself more intelligent than those who surround him and those who have gone before him. And since he believes himself more intelligent and advanced than the people that went before him, he assumes that what they believed is not true anymore, is outdated. This is a false syllogism.

John Maeda may think that because he has a smartphone and can process the video he is taking of you (while you are trying to converse with him) through html 5 and make it interact with objects in a cornfield in real time or some such thing, that somehow his vision of what art education is and should be is "more advanced" than that of the rest of the faculty at RISD, but in this thinking he is also mistaken. This logic is roughly equivalent to your saying that you can bake a better cupcake than I can because you use a silicone pan. The recipe and quality of ingredients, the baking time or general talent of the baker seem to have nothing to do with it.

We believed that Maeda could do for us that which we were too lazy to do for ourselves. We wanted him to somehow make what we teach seem new and shiny in the current era, without our really having to do anything about it. But we expected way too much from one man, and we did not understand that his great talent seems to be that of the person who first sees a shiny object in the marketplace and runs to get it. He is the earliest of adopters, the bell-weather of early adopters."
risd  designeducation  design  education  leadership  management  hierarchy  intelligence  interpersonal  johnmaeda  2011  noconfidence  faculty  administration  human  technology  change  highereducation  highered  arts  art 
april 2011 by robertogreco
On Meaningful Observation § SEEDMAGAZINE.COM
"Adding art and design to science education would put a bit of humanity back into the innovation engine and lead to the most meaningful progress."
design  art  education  science  innovation  stem  steam  johnmaeda  lcproject  teaching  tcsnmy  learning  schools  curriculum  progress 
december 2010 by robertogreco
Hurry Up and Wait - The Slow Issue - GOOD
"“The slow movement imagines itself to belong by rights to the cultural layer”—a slow-moving layer of society—“but it’s still in the layer of fashionable activism,” he says. “An earthquake is rapid and shocking, it seems, but the underlying forces are geologically slow. So it’s actually our perception of pacing that’s odd, not pacing itself.”"
design  futurism  brucesterling  goodmagazine  slowness  culture  slow  estherdyson  johnmaeda  julianbleecker  jamaiscascio  alexanderrose  creativity  environment  trends  ideas  2010  future 
january 2010 by robertogreco
John Maeda quotes
“Amidst all the attention given to the sciences as to how they can lead to the cure of all diseases and daily problems of mankind, I believe that the biggest breakthrough will be the realization that the arts, which are conventionally considered "useless," will be recognized as the whole reason why we ever try to live longer or live more prosperously. The arts are the science of enjoying life."
johnmaeda  well-being  happiness  art  science  quotes 
october 2008 by robertogreco
Technology Review: Blogs: John Maeda's blog: BGI = Before Google Images
"advantages of physically based approach are quite clear: 1) quality of images is better, as they've been hand-curated, 2) there is element of serendipity that comes from messiness of it all that leads to happenstance encounters of new inspiration."
messiness  serendipity  search  images  google  via:preoccupations  johnmaeda 
april 2008 by robertogreco
Putting people first » Four speakers debate the future of design
"Rawsthorn=design for underprivileged majority+dematerialisation Antonelli=3D printing+yearning for privacy Cottam=tackle social problems through mass collaboration Maeda=moral responsibility+appreciating beauty of everyday objects&places"
design  future  alicerawsthorn  paolaantonelli  johnmaeda  hillarycottam  education  society  change  collaboration  beauty  consumption  materialism  privacy  environment  sustainability  trends  opensource  technology  software  slow  policy  activism  gamechanging 
january 2008 by robertogreco
Generator.x » John Maeda kills his darlings
"For Maeda to place himself at the head of this column is pompous windbaggery at its finest. Maeda’s thoughts on simplicity read like the rantings of an old man waving his symbolic cane at the kids today"
johnmaeda  michalmigurski  history  visualization  graphics  computing  simplicity 
november 2007 by robertogreco
Maeda's SIMPLICITY: Clothing For The Mind
From "away messages" like earrings as an accessory, to MySpace or LinkedIn pages that constitute casual or business "mental attire," ...we live in a world where we put as much time into the clothing that we wear as we do our own online identities."
online  identity  expression  ambientintimacy  fashion  perception  internet  myspace  facebook  sms  texting  social  society  teens  youth  johnmaeda 
november 2007 by robertogreco
Maeda's SIMPLICITY: Openly Prioritize
"interesting distinction between fairness versus policy...clear policy usually makes everything open and transparent..real socialism at work, everyone gets same deal...closed process...possible to give different deals to different people"
administration  organizations  management  fairness  policy  work  gamechanging  johnmaeda 
november 2007 by robertogreco
Maeda's SIMPLICITY: Wisdom from Ghana
"Leader is future-oriented, mapping out a long-term direction for hir (his/her) team...often has abundant personal charisma that inspires...will remain free to envision the next stage, whilst reserving the option to lead by example."
leadership  management  administration  organizations  groups  business  education  schools  johnmaeda 
october 2007 by robertogreco
icon | 050 | august
50 manifestoes: maeda, koolhaas, acconci, wamders, mau, sagmeister, thackara, hadid, prince-ramus, mayne, FAT, antonelli, manaugh, holl, chalayan, rogers
design  manifestos  architecture  remkoolhaas  oma  amo  princeramus  vitoacconci  thommayne  jonmaeda  thackara  zahahadid  stevenholl  johnmaeda 
august 2007 by robertogreco
Maeda's SIMPLICITY: Boss Proverb
"Boss is waiter." = "a manager's role is to serve his or her team's needs in an ongoing and proactive manner"
leadership  administration  management  work  organizations  people  johnmaeda 
july 2007 by robertogreco
Maeda's SIMPLICITY: Within the Storm
Maeda learns these 3 secrets to life from a fellow MIT professor: "1. Take 24 uninterrupted hours of rest per week. 2. Don't travel as it wastes time. 3. Say "no" to meetings often."
advice  life  work  sleep  travel  time  meetings  johnmaeda 
february 2007 by robertogreco
Maeda's SIMPLICITY: Peek-a-boo I CC You
"I've been wondering how much my life would be simpler if I no longer received messages that are CC'ed to me."
culture  email  simplicity  etiquette  productivity  work  johnmaeda 
january 2007 by robertogreco
Maeda's SIMPLICITY: The Paradox of Classes
"Having more requirements (i.e. "classes") is good for a student because it forces them to learn an important set of specific knowledge....Having less requirements is good for a student because it gives them more opportunities to procrastinate."
classes  education  universities  colleges  learning  innovation  thinking  creativity  programs  altgdp  lcproject  balance  johnmaeda 
december 2006 by robertogreco
Maeda's SIMPLICITY: On Education
"I had the privilege of attending TED this year...greatest piece of wisdom, in my mind, came from Sir Ken Robinson who an eloquent no-visuals speech that, "Our education system exists to support the singular goal of entrance to university."
education  wisdom  society  politics  economics  learning  success  johnmaeda 
february 2006 by robertogreco
sascha pohflepp projects: design by politics - an interview with John Maeda
"I believe that creative thinking is rapidly disappearing, because business is so focused on measurable outcomes and the economy is known to improve if reading and mathematics are strong in society."
technology  design  culture  creativity  politics  society  computers  economics  education  learning  simplicity  johnmaeda 
january 2006 by robertogreco
Maeda's SIMPLICITY: Teach Less, Learn More
"Because the prof gave me so little information, I found myself working ten times as hard to learn the material. Whereas when I had the answers spoon-fed to me during accounting, I didn't really have to put up much of an effort."
learning  education  schools  teaching  children  johnmaeda 
november 2005 by robertogreco

Copy this bookmark:

to read