José Mota — Web engineer & architect

Categorized under Design

A perspective on the state of education (of the Web)

This is a challenge by Molly Holzschlag concerning how the Web is taught around here. Even though I tend to be opinionated, things have been happening that I consider important to a better future.

Learning the craft of the Web has always been hard. It has taken a lot of blog posts, trial and error, inspiration, books, etc. to slowly progress; all of this… after hours.

You must get things done at daytime. Innovation costs time that doesn’t exist. At least that’s what most companies believe around here in the last 5 years. Money is all leaders see, there’s not the time nor the money to delve into a better process or a better performance. Why bother if the pay is low and things are steady? This is a cultural issue and that might just be the hardest impediment that our people has to clear.

Read the rest of this entry »

December 26th, 2011 — 1 comment so far

O lamento de um designer

Há cerca de dois anos eu concorri para o projeto Zizuzi, um conceito de rede de emprego, com contratandos e contratantes. Quando vi o documento de aproximadamente 17 páginas de conteúdo relativamente preciso e bem organizado, eu pensei que iria participar num projeto inteligente.

Ontem tive curiosidade de ver como estaria o projeto. Morri. Vejam por vocês.

Sem informação para quem entra, sem forma de registo, nada. E isto é só a página de entrada. Eu até tremo de pensar o que estará lá por dentro. Expresso as minhas condolências pela pobre alma que inventou o nome Zizuzi; em nada sugere “rede de procura e oferta de emprego”.

May 26th, 2010 — 3 comments so far

HTML Semantics: br’s & control labels

<br /> elements break content. They don’t space it.

This gave birth to a nice debate. I threw that tweet because I was facing a terrible blunder from a fellow designer. He was using <br />'s to wrap an <hr /> just to give the ruler some space — instead of adding margins to it —. Paulo Zoom and Levi Figueira propelled the whole thing and I kinda moderated it. The end result was quite satisfying.

Read the rest of this entry »

April 29th, 2010 — 1 comment so far

Tear up your client’s proposal in half!

Just picture it: you are about to welcome your client into your office for a first meeting. You are excited to know what he wants. He brings his suitcase. Both of you happily sit down and he takes the project briefing out of the suitcase and hands it to you. This is what I want. Please take a look., the client happily states, confident in his effort to provide a solid brief for you to work on.

Take the briefing and tear it up in half!

Read the rest of this entry »

April 26th, 2010 — Leave a comment!

To show or not to show [registered user only actions]

Last week I struggled with a design decision that really caught my attention. Consider this:

  • You have a user driven app on the web.
  • You also provide some actions for guests.

What you would do? Either:

  1. Don’t show the user only actions? (my opinion: this one reduces clutter on your interface).
  2. Or do show them and when the user clicks the links/buttons, the user gets a login redirected page for every new click?

My pick would be number 1. Why?

I’d rather have a welcome page that showed you what to use in case you signed up. Actions such as creating a new item on a product list and message sending that apparently require a sign up are confusing for a guest. Besides, clicking on such an action and redirecting you to a login page several times is not that much of an engaging experience.

Feel free to add up on this thought.

April 20th, 2010 — Leave a comment!