Friday, March 12, 2010

Designer or Engineer, Artist or Painter

January 19, 2010 by Greg Ferro · 6 Comments 


If you were a Painter, a really good painter, you would have skills and expert­ise in paint­ing. You might under­stand your brush, how to make one, what hair is the best type for a given fin­ish. You might prac­tise on using dif­fer­ent shapes, dif­fer­ent hair and dif­fer­ent move­ments. You might also be able to make your own paint, mix­ing the raw mater­i­als to pro­duce the dif­fer­ent col­ours. You could grow your own herbs, gather your own min­er­als and grind /​ boil and fix them to make your own paints. Your exper­i­ence knows how to apply the paint, to com­bine your phys­ical move­ments with the nature of the paint, sur­face and other factors to .

But to be an Artist, you would also need to under­stand shape, form and col­our. You would spend time think­ing about com­pos­i­tion, and rela­tion­ships, and cre­at­ing a nar­rat­ive within the pic­ture frame. You would con­sider and prac­tice, draft and draw ele­ments of the pic­ture, carry out pre­lim­in­ary sketches and form draw­ings until you cap­tured the essence, the very spirit of your art. You would also need to have a rela­tion­ship with those who might buy, or dis­play, or com­mis­sion you work — you won’t be a ser­i­ous artist if you can’t sur­vive, and you won’t be ser­i­ous if you don’t prac­tice your art every day.

A Network Engineer, a really good engin­eer, should have skills that knows how to trace, to detect, to debug. You should know how the net­work is con­nec­ted, and why data flows that way, and not this way. What is its pur­pose ? What are the ele­ments that join together, that are mixed, to provide the data flow from end to end. And then, make the fix.

But to be a Network Designer, a really good designer, also needs to under­stand the net­work, the entire net­work, and all of the ele­ments that make it up. You should see the form and shape of the entire sys­tem, and the external factors that make it the way it is. You should under­stand what the you can do, with the mater­i­als avail­able, and how you can touch-​​up the pic­ture, to change that shape, to add a little char­ac­ter there. The busi­ness factors that cre­ated the oppor­tun­ity, and restrict the pic­ture from being great.

That’s the dif­fer­ence between a good Network Engineer, and a good Network Designer.

Footnote

I ori­gin­ally pub­lished this in March 2009, but felt moved after a recent dis­cus­sion to post it again. Please indulge me if you have already read this.

Please rate this post:

  Why Rate Posts?
1 Star - It\\\'s Crud2 Stars - It\\\'s Tosh3 Stars - Something\\\'s missing4 Stars - Needs works5 Stars - Good Enough6 Stars - Good7 Stars - Excellent8 Stars - Brilliant9 Stars - Astonishing10 Stars - Awesomely Godlike? (5 votes, average: 5.00 out of 10)
Loading ... Loading ...

Comments

6 Responses to “Designer or Engineer, Artist or Painter”
  1. Design is also some­what of a Philosophy. There are cer­tain accep­ted prac­tices but there is alot of room to inter­pret how things should be done. You get two Engineers in the same room and ask them to come up with a design and you might see two dif­fer­ent ways of accom­plish­ing the same thing. I think design­ers have become some­what defens­ive about a net­work because they have to con­tinu­ally defend their decisions. Not only to Peers (read any forum that asks for help), but to man­age­ment who really doesn’t understand.

    • Greg Ferro says:

      Wherein lies the dif­fer­ence between art and engin­eer­ing. Art is cre­at­ive and non-​​deterministic, Engineering is dir­ec­ted and lin­ear. And like Art, the com­mu­nic­a­tion is a large part of pro­cess. Getting your art recog­nised requires influ­ence, com­mu­nic­a­tion, rela­tion­ships to get people to “see” your vision.

      Lots of sim­il­ar­it­ies really.

      • rodney says:

        So do you think that move from engeer­ing to design is a pro­gress­tion, like the move from being a painter to a artist?

        • Greg Ferro says:

          I think that some people want to cre­ate, and other people want to build. It’s not a pro­gres­sion but a choice that people make.

          Creative skills are rare in the IT industry, and thus good design­ers /​ writer /​ com­mu­nic­at­ors are hard to find, and lead to higher pay rates. Not because they are bet­ter, just because their skill set is harder to find.

  2. steve says:

    I can’t think of an instance where you can sep­ar­ate design from engin­eer­ing, at least where qual­ity is con­cerned. An engin­eer must know debugs and traces within the con­text of the net­work design. I have to know what traffic beha­vior is expec­ted to recog­nize a devi­ation in that beha­vior. Similarly, if I don’t pos­sess solid engin­eer­ing skills, I can­not per­form needs ana­lysis and gen­er­ate con­fig and test plans for a net­work tech to execute. Anything less is an account man­ager, someone who has a copy of Visio and thinks put­ting shapes on a sheet with con­nector lines equals “pre­lim­in­ary design”.

Trackbacks

Check out what others are saying about this post...
  1. […] sys­tems. As a res­ult, as much as he occa­sion­ally dips into the lower levels of the ISO model, he also writes about the rest of what it is like to be a net­work archi­tect and designer. It is a site that is worth a […]



Speak Your Mind

Tell us what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!