Tumblelog by Soup.io
Newer posts are loading.
You are at the newest post.
Click here to check if anything new just came in.

December 23 2010

11:02

THE BEST MULTIMEDIA JOURNALISM EDUCATION STILL IS A STRONG LIBERAL ARTS CURRICULUM

Professor Jay Rosen says that Journalism Schools are increasingly becoming R&D labs.

First, I am not sure about that. Second, If yes, I say no.

I don’t have any problem with universities and professors doing research.

More than that: without research, teaching and education are very poor.

But the idea that our Journalism Schools have to become R&D Labs is wrong.

The best Journalism education still is a strong Liberal Arts curriculum.

Reading, Thinking & Writing, are more important than playing and doing.

You will spend the rest of your life playing and doing.

So you better spend your College years using your brain, not your hands.

For many years Journalism Schools were focused on just print media.

Then, broadcasting programs came.

Later, public relations & advertising… and integrated marketing communications!

Yes, I know, mutimedia is here and now our old fashioned Journalism Schools want to catch the future just becoming R&D Labs…

What all these professors don’t know is that the problem are them, not the students.

The new generations of students are “digital multi-media-tasking natives” so they don’t need more technical training because they are fully trained before they enter in the schools.

These professors and administrators eager to get funds for R&D Labs are the ones needed of this training.

What good students are looking for is for challenging thinkers, first class teachers, inspiring personalities, and not IT amateurs.

Let’s be serious:

You still learn more about new narratives reading Antigone than spending hours in front a computer.

Specially now when you can read Antigone in an iPad!

November 04 2010

14:10

A Six-Step Process for Managing Web Projects

After years of intensive work in the IT industry, I've put together a practical guide to project development that my company uses for 99 percent of our projects. So far we've done amazingly well with this approach. Once you know it, it feels so simple and natural that you don't even know you know it. In the interest of helping other folks with their development projects -- and to encourage you to offer your tips and suggestions in the comments -- I offer our process.

Step One: Consultations

This is where you start brainstorming about the core idea, as well as any potential solutions and technologies. Capture all of the the ideas, solutions, and any relevant prices etc. You can only proceed with the next step when you feel ready to talk about specific functionality, prices and timelines.

Step Two: Planning

Make a list of all the features and functions you can imagine for this project. Then start estimating how much money and time it requires for each. Now go through your list and prioritize the functions to determine which need to be launched right away, and which are less important and can wait for a future update. Now you can begin to see how much time and money you need to build architecture, interface, design and do the bug-fixing and configuration. Move to the next step once you've established the development timeline and resolved that with the available budget.

Step Three: Wireframe

Take a blank piece of blank paper and sketch the basic structure of a website or application, and the relationships between its pages or sections. Draw your menus and the main elements. Go into as much detail as you consider important, but know that you don't have to plan through each and every element or establish every detail about how things will work and look.

Step Four: Interface

Using your wireframe as a guide, draw everything that has to appear in the final product, including everything that needs to be there. Figure out all the links, all the menus and interface methods, such as pop-up, drop-down, slider etc. You can still do this on a blank piece of paper, but I suggest to using software such as yED, which is a free download. Take your time with this stage. When you have it perfect, set it aside for at least one day and then examine it with fresh eyes. Try to find at least two places where you can save a click, make a more intuitive menu, or make something else better. Then print it out and you're ready to go with the next step.

Step Five: Design

If you haven't already begun working with him/her, begin meeting with your designer(s). Present wireframe sketches and the interface. Explain the tricky spots, explain why things are there as they are, and how your ideas have evolved. Now it's time to let them get to work.

Step Six: Programming

You should provide three things to your development team: the list of functionality, the interface outline, and the design. Now they work to make it all real.

Obviously, a lot more happens in the development and testing stage, and in future posts I'll share more advice and lessons about that and more. For now, share your thoughts and process int the comments.

14:10

A Six-Step Process for Managing and Developing Web/IT Projects

After years of intensive work in the IT industry, I've put together a practical guide to project development that my company uses for 99 percent of our projects. So far we've done amazingly well with this approach. Once you know it, it feels so simple and natural that you don't even know you know it. In the interest of helping other folks with their development projects -- and to encourage you to offer your tips and suggestions in the comments -- I offer our process.

Step One: Consultations

This is where you start brainstorming about the core idea, as well as any potential solutions and technologies. Capture all of the the ideas, solutions, and any relevant prices etc. You can only proceed with the next step when you feel ready to talk about specific functionality, prices and timelines.

Step Two: Planning

Make a list of all the features and functions you can imagine for this project. Then start estimating how much money and time it requires for each. Now go through your list and prioritize the functions to determine which need to be launched right away, and which are less important and can wait for a future update. Now you can begin to see how much time and money you need to build architecture, interface, design and do the bug-fixing and configuration. Move to the next step once you've established the development timeline and resolved that with the available budget.

Step Three: Wireframe

Take a blank piece of blank paper and sketch the basic structure of a website or application, and the relationships between its pages or sections. Draw your menus and the main elements. Go into as much detail as you consider important, but know that you don't have to plan through each and every element or establish every detail about how things will work and look.

Step Four: Interface

Using your wireframe as a guide, draw everything that has to appear in the final product, including everything that needs to be there. Figure out all the links, all the menus and interface methods, such as pop-up, drop-down, slider etc. You can still do this on a blank piece of paper, but I suggest to using software such as yED, which is a free download. Take your time with this stage. When you have it perfect, set it aside for at least one day and then examine it with fresh eyes. Try to find at least two places where you can save a click, make a more intuitive menu, or make something else better. Then print it out and you're ready to go with the next step.

Step Five: Design

If you haven't already begun working with him/her, begin meeting with your designer(s). Present wireframe sketches and the interface. Explain the tricky spots, explain why things are there as they are, and how your ideas have evolved. Now it's time to let them get to work.

Step Six: Programming

You should provide three things to your development team: the list of functionality, the interface outline, and the design. Now they work to make it all real.

Obviously, a lot more happens in the development and testing stage, and in future posts I'll share more advice and lessons about that and more. For now, share your thoughts and process int the comments.

November 10 2009

14:50

Sony Discontinues AIT Drives And Libraries

Sony gives notice that the AIT format has reached its End of Life
Tags: IT
14:50

Sony Discontinues AIT Drives And Libraries

Sony gives notice that the AIT format has reached its End of Life
Tags: IT
14:50

Sony Discontinues AIT Drives And Libraries

Sony gives notice that the AIT format has reached its End of Life
Tags: IT
10:29

22,000 Indians Are Driving Japan’s IT Industry

Japan's IT industry is increasingly Indian-driven
Tags: IT
10:29

22,000 Indians Are Driving Japan’s IT Industry

Japan's IT industry is increasingly Indian-driven
Tags: IT
10:29

22,000 Indians Are Driving Japan’s IT Industry

Japan's IT industry is increasingly Indian-driven
Tags: IT

November 06 2009

21:15

TwitterPeek: Will You Pay For Such A Device ?

My question for you is this: will you pay for a device that only sends and receives tweets ?
Tags: IT
21:15

TwitterPeek: Will You Pay For Such A Device ?

My question for you is this: will you pay for a device that only sends and receives tweets ?
Tags: IT
21:15

TwitterPeek: Will You Pay For Such A Device ?

My question for you is this: will you pay for a device that only sends and receives tweets ?
Tags: IT
14:19

Your Internet Accounts Stay Alive Even After Your Death

What happens to your belongings after you die is a separate story. Let us see what happens to your various major sites accounts on internet once you move away from earth.
Tags: IT
14:19

Your Internet Accounts Stay Alive Even After Your Death

What happens to your belongings after you die is a separate story. Let us see what happens to your various major sites accounts on internet once you move away from earth.
Tags: IT

November 05 2009

17:13

Microsoft Demonstrates "Heat of Recession" is Still On

Although Microsoft claims that its spree of cutting down 5,000 jobs (about 5% of 96,000 employees worldwide) before June 2010 is over but there is a doubt on that
Tags: IT
17:13

Microsoft Demonstrates "Heat of Recession" is Still On

Although Microsoft claims that its spree of cutting down 5,000 jobs (about 5% of 96,000 employees worldwide) before June 2010 is over but there is a doubt on that
Tags: IT
17:13

Microsoft Demonstrates "Heat of Recession" is Still On

Although Microsoft claims that its spree of cutting down 5,000 jobs (about 5% of 96,000 employees worldwide) before June 2010 is over but there is a doubt on that
Tags: IT
Older posts are this way If this message doesn't go away, click anywhere on the page to continue loading posts.
Could not load more posts
Maybe Soup is currently being updated? I'll try again automatically in a few seconds...
Just a second, loading more posts...
You've reached the end.

Don't be the product, buy the product!

Schweinderl