• From: Tei <oscar.vives@g...>
• To: xml-dev@l...
• Date: Tue, 3 Jan 2012 18:10:22 +0100

I think is a good suggestion, for newbie programmers, to get better at
his craft. To learn, write a lot of code, read good code from other
people. Maybe buy some book about good guidelines (metodologies).
Release something to the public, and see how real humans collide with
his software.   I think a lot of programmers are just hired for a job,
and do it X hours, then get home to do any random not-programming
related task. And this is Ok, but I have a problem.  Programmers must
live with the code that create, if the code is bad, is like living
with pigs in the mud;  so programmers (of course) want to live with
code that have a standard of quality that make working with it sweet,
and not a futuristic self-inflicted torture.  If you work "massaging
code", you want code to be good, because "massaging [expletive deleted]" sound like
something you don't want to do all day long.

I have a friend that is unemployed, and I have suggested him to make a
iPhone app. He has learned Java in the university, he probably has not
other real world tool in his toolbar. My logic is, don't go to
interviews naked, being "another" like the one before you, and the one
after you. Be to these interviews being more than that. Being smelling
good, and having things and skill the company may be interesting, you
are the product, the tool, machine, writter, composer, translator,
etc.. that the company is buying.  Perhaps the company is just
searching for a java dev, and ask for a java dev (but is planning to
in the future make iPhone apps),  if you come as a java dev that has
iPhone apps in the apple marketplace, you are more. More than the
next, more than the one before you. Perhaps the odds are better.  If
some people say "you are what you eat", I think make sense to say "you
also are what you write", so you have to go, and actually write good
stuff, and release to the public. Because things that are not released
are not complete.


--
--
ℱin del ℳensaje.

• Follow-Ups:
  • Re: Engineering versus Science, Anecdote versus Evidence... [Was: Designing an experiment to gather evidence on approaches todesigning web services]
    • From: Andrew Welch <andrew.j.welch@g...>