(banding External Hemorrhoids)

becoming an administrator - Programmer

Go title.

Dedicated to all those who ask me for the title of this note. I have no magic recipe, but there are some tips that have helped me:

The strategy rests on two fronts:

Compress and find free time, without sacrificing the one for the family.

• ($$$) stay alive while learning. Rule: all the time we mantenermos updated, so
• learn all the time. The Google Reader and Twitter are the best tools to keep up.

  Steps

buy some books and magazines in the collection of kid-Proof, Publishers Users. They are cheap and very good to begin with networks, service, etc. They are available in tematika.com, or the site of the magazine. By the way, here is the one I wrote for "torturing" my students and Operating Systems Networking

www.bunker.org.ar / incubator / redes.pdf

1. Get a job. Obviously related to computers. Become

2. essential. Be of service to users. Demonstrate genuine interest in their pathetic data. Aiding and abetting. Teach, share. Get

3. a del.icio.us account, download the plugin for firefox, tagging and go places where we find solutions to problems. If you must return to search google a previous solution discovered years ago, sir, you are an idiot.

4. Get the position of System Administrator, or become his right hand. The thing is very simple: on personal slitting, the nerd survives.
5. Never fight with anyone, maintain good relationship with the DBAs and programmers.
   Never give up the hard way. Of any company is going with a handshake and with heads held high: the ICT sector is very small elite, and will soon need recommendations.
   understand how ssh, tunnel, vpn, terminal server, permissions, domains. The trick to realize that we have reached a good level of administrator, and read well, is that you do not "need to move your ass to solve a problem." The problem is fixed from where you sit: at most, remotely accessing the server and solving the problem. Again, here's literature to get started:
www.bunker.org.ar / incubator / redes.pdf

6. Format only as a last resort. First you find the error. Format is for losers.

To learn how to program from the desktop systems:

manage to get time off. Strategy:

Using all free software as possible. The other is very wrong, users get into trouble, pollute, spoil everything. You lose time looking for passwords, disinfecting the cracks, crap and an indignity to the profession. The GUI also suck. If you fix everything with the mouse, perhaps you should not continue reading.

• Using Linux on servers + W2003. Learn to use the terminal and openoffice. The first is a Swiss army knife, and the second is an excellent tool for data mining and conversion. Openoffice goes well in Windows, and you can get a semblance of a terminal using cygwin, very useful for scheduling backups, tunnels, etc.. Linux is a crutch for Windows servers.

• If you must use Windows at stations, that is as much as possible, with a firewall that does not laugh at the Trojans, like ZoneAlarm, or Outpost.
• Forget the antivirus, that's a myth, and Anthrax
  agrees with me. Freezer
  stations and manage shared data network, at some Samba. Use

• intranets: Apaches and simple programs solve simple things. PHP is handmade and cute to begin with. Virtualize Windows servers.

When everything goes like clockwork, the stations do not fall, and users are moderately happy (they are never happy), the time has come free. The problem is to use it effectively. Organize

2. on using Google Calendar or similar.

3. Fuck off Facebook and MSN. Instead it is preferable to Twitter, Buzz or Google Talk. Follow (follow) only intelligent and inspiring people, not idiots who tell their experiences. Close distractions, powerpoints, chains, using the special "spam score." Put recurrent post filters. If you really enjoy social networking, switch to a professional network like LinkedIn, or osun.sun.com

4. 
   

   Use scientific techniques of research: formulating hypotheses, conducting experiments on a station reserved for this purpose, or virtual machines. Use it to solve recurring problems of users, automated backups, simple data mining, etc.

5. Join mailing lists we want to learn the language. Ask and help. Learning to use the IRC, part of a network of freenode, as # Lugmen, # lugfi, # java, # ruby, # ruby-es, etc.

6. Read in English, beginning with simple tutorials. Get writers novels for children, such as Jules Verne, Jack London, or literature-shirt, as Stephen King. The books are getting cheaper in the libraries. I got a Palm used on Ebay, and crammed with books by Ursula Le Guinn. The most precious gems are bilingual texts, which enjoyed a lot.
The slogan read for fun.
7. Making the new wave of phones with large screens, and ebooks innmimentes readers.

   These are not used to read source code examples, so in texts on programming, go to the paper:
   

   Good programming texts are in English. Search recent
8. those issues, and hands a bit to download. Link:

   www.pdfchm.net

   Mood: a little reading, English writing is a skill that develops very quickly. The magic word in Google is "tutorial." Example temples do any of the tutorials present in netbeans.org

9. 
   

   spend $ 400 on a laser printer B / N, and intended only to print PDF. Banding, or learn directly to file away (find videos on youtube).
10. At least once a year, buy a helluva text. This year I bought

    http://sharanamshah.wordpress.com/2010/01/13/java-ee-6-for-beginners/

    , on Amazon, at $ 300, and is truly an investment. Last year I bought a $ 240 Agile Web Development with Rails (

    www.pragprog.com/titles/rails3 ) and not a day goes by without the redemption. Only we must ensure that it is a current issue of no more than one year window, and seriously: you pay alone.

    Once we take a few months reading in English, and we understand the invaluable
screencastings you there on the Internet. My favorites are in netbeans.org, and

11. railscasts.com

    Join Monster, elance, etc, looking for freelance work on which we can test our skills. By the way, we can only ethically elbowing other customers
12. from home, never inside the company where they are investigating. Otherwise, you're stealing. Maintain a portfolio of work where we can see and hire. These sites are set far in the experience.

    Nobody hired him? Perhaps not appropriate language learning. To my taste: Java and PHP if you need the money. Python or Ruby if you want to have fun. Over time clients will take you to need to learn some meta as SQL, XML, XHTML and Javascript. Beware of proprietary languages \u200b\u200band libraries. Once you've mastered the language properly, do not spend many days to deploy a project using a CMS, or better yet, a Framework. My favorites: Ruby on Rails, JSF or Spring.

13. 
    If we develop a skill, this should be useful for the company. And explain clearly. Only companies that maintain a research wing are progressing. What about yours, how many employees are research and training on their own? The ideal is to begin to train co-workers, so that the company did not interpret our research as a waste of time. Present papers at conferences to bring our findings with the company name as a flag. Explain to our bosses, who in this way the IT department the company is enhanced. Sometimes even the company pays per diem.

14. rid of unproductive people, negative. A co-worker or friend is most useful if you have a healthy psychopathy and work-related. To talk nonsense, this street. There are colleagues who unfortunately are a black hole of productivity, or only serve to bring us down. If one partner did not study specifically for the position they hold, and is only there for the paycheck, is a likely liability.

15. 
    

    After the first failed contracts and weaknesses, learn to negotiate with the client a flexible delivery rate
(
16. http://

    es.wikipedia.org / wiki / Desarrollo_ agile _de_software ) , approx Scrum ender a little and use some driver versions to avoid damaging code. I like GIT. Self-documenting everything step by step "and become their own guides.

    Well, that's all. I hope someone serve.