If you have no previous work experience , you may want to consider adding in volunteer work , projects good for design , tech industries or other relevant experience you may have . And you should continually based on the job change the courses you present and what you learned based on the job you ' re looking at . For example , if you ' re applying to a Web Development backend role , you don ' t start listing off all the frontend experience and design you got through college . You would focus specifically on stuff relating to backend . <| sep |> Thanks for the advice ! When you do cleaning maintenance , what do you use to clean off the dust effectively ? Thanks ! <| sep |> Hehe . yer right . VT 100 Z is not WELL defined yet . But you are certainly smart enough to know that there is nothing to prevent us from well defining it right ? I am NOT challenging curses because it is NOT in the same problem class . Curses was designed to encapsulate all of the hardware terminal types into a normalized interface for the app . We don ' t use hardware terminals anymore do we ? And in fact we are discussing the act of actually defining a distinct software terminal called a VT 100 Z . Defining that VT 100 Z terminal would not prevent curses from writing to it right ? A VT 100 Z sits underneath curses regardless of whether or not curses is used . Curses is not a terminal type . It is an abstraction that normalizes terminal types . I have no desire to emphasize future normalization with curses . It is NOT as portable and friendly as you ' d like to believe . FYI In case you had not noticed . the VT 100 Z initiative is NOT about continuing to favor an ASCII presentation on the client side . THOUGHT EXPERIMENT Imagine we could time travel to the past and define the terminal type that we ' d all favor right now today such that we ' d not need any other kind of terminal to do everything NH is ever going to do .