You’ve finished this book and have decided to continue with programming. 

Maybe it will be a career for you, or maybe it will be a hobby. 

You’ll need some advice to make sure you continue on the right path and
get the most enjoyment out of your newly chosen activity. I’ve been programming for a very long time. So long that it’s incredibly boring to me. At the time that I wrote this book, I knew about 20 programming languages and
could learn new ones in about a day to a week, depending on how weird they were. Eventually, though, this just became boring and couldn’t hold my interest anymore. This doesn’t mean I think programming is boring, or that you will think it’s boring,
only that I find it uninteresting at this point in my journey. What I discovered after this journey of learning is that it’s not the languages
that matter but what you do with them. Actually, I always knew that, but I’d get distracted by the languages and
forget it periodically. Now I never forget it, and neither should you. Which programming language you learn and use doesn’t matter. Do not get sucked into the religion surrounding programming languages, as that
will only blind you to their true purpose of being your tool for doing
interesting things. Programming as an intellectual activity is the only art form that allows you to
create interactive art. You can create projects that other people can play with, and you can talk to them
indirectly. No other art form is quite this interactive. Movies flow to the audience in one direction. Paintings do not move. Code goes both ways. Programming as a profession is only moderately interesting. It can be a good job, but you could make about the same money and be happier
running a fast food joint. You’re much better off using code as your secret weapon in another profession. People who can code in the world of technology companies are a dime a dozen and
get no respect. People who can code in biology, medicine, government, sociology, physics,
history, and mathematics are respected and can do amazing things to advance
those disciplines. Of course, all this advice is pointless. If you liked learning to write software with this book, you should try to use it
to improve your life any way you can. Go out and explore this weird, wonderful, new intellectual pursuit that barely
anyone in the last 50 years has been able to explore. Might as well enjoy it while you can. Finally, I’ll say that learning to create software changes you and makes you
different—not better or worse, just different. You may fi nd that people treat you harshly because you can create software,
maybe using words like “nerd.” Maybe you’ll find that because you can dissect
their logic, they hate arguing with you. You may even fi nd that simply knowing how a computer works makes you annoying
and weird to them. To this, I have just one piece of advice: they can go to hell. The world needs more weird people who know how things work and who love to
figure it all out. When they treat you like this, just remember that this is your journey,
not theirs. Being different is not a crime, and people who tell you it is are just jealous
that you’ve picked up a skill they never in their wildest dreams could acquire. You can code. They cannot. That is pretty damn cool.

Advice from an Old Programmer的更多相关文章

  1. Zed Shaw:一位老程序员的建议

    Advice from an Old Programmer 原文:Zed Shaw,译文:外刊IT评论 导读:原文作者Zed Shaw是一位作家.软件开发人员.音乐人(下文中提到吉他手),于2010年 ...

  2. What technical details should a programmer of a web application consider before making the site public?

    What things should a programmer implementing the technical details of a web application consider bef ...

  3. The best career advice I’ve received

    I recently had an interesting discussion with a colleague. We were recounting our job histories and ...

  4. Advice on improving your programming skills

    Programming is cool. But behind the scenes it's also difficult for many people. Many people are defe ...

  5. The best career advice I’ve received --转载

    http://www.nczonline.net/blog/2013/10/15/the-best-career-advice-ive-received/ The best career advice ...

  6. 【转】The best career advice I’ve received

    原文地址:http://www.nczonline.net/blog/2013/10/15/the-best-career-advice-ive-received/ I recently had an ...

  7. Practical Go: Real world advice for writing maintainable Go programs

    转自:https://dave.cheney.net/practical-go/presentations/qcon-china.html?from=timeline   1. Guiding pri ...

  8. Spring 通知(Advice)和顾问(Advisor)

    AOP ( Aspect  Oriented Programming  面向切面编程)  在软件业,AOP为Aspect Oriented Programming的缩写,意为:面向切面编程,通过预编译 ...

  9. Spring的通知(Advice)

    Spring提供了5种Advice类型: Interception Around:JointPoint前后调用 Before:JointPoint前调用 After Returning:JointPo ...

随机推荐

  1. BZOJ1088或洛谷2327 [SCOI2005]扫雷

    BZOJ原题链接 洛谷原题链接 很容易发现答案就只有\(0,1,2\)三种答案,而且只要知道第一个格子是否有雷就可以直接顺推下去了. 所以我们跑一次首位有雷,跑一次首位无雷判断是否可行即可. #inc ...

  2. Spring Environment(三)生命周期

    Spring Environment(三)生命周期 Spring 系列目录(https://www.cnblogs.com/binarylei/p/10198698.html) Spring Envi ...

  3. Spring 系列教程之默认标签的解析

    Spring 系列教程之默认标签的解析 之前提到过 Spring 中的标签包括默认标签和自定义标签两种,而两种标签的用法以及解析方式存在着很大的不同,本章节重点带领读者详细分析默认标签的解析过程. 默 ...

  4. where

    (二)WHERE //where不单独使用,与match,optional match,start,with搭配 where 与match,optional match 一起用,表示约束 where ...

  5. 前端js数据排序

    销量统计系统中国地图热力分布图需要显示一个各省区销量列表,并按从多到少排序.本着轻易不修改后台数据源的原则,决定在前端进行修改实现.其实也容易实现,将数据存放一个数据<省区名称,销量>,然 ...

  6. canvas 实现微信小游戏

    var canvas = document.getElementById('canvas'); var cxt = canvas.getContext('2d'); var timer; var iS ...

  7. Python之tornado

    一.快速了解Tornado框架 1)tornado简介 Tornado 和现在的主流 Web 服务器框架(包括大多数 Python 的框架)有着明显的区别:它是非阻塞式服务器,而且速度相当快.得利于其 ...

  8. 取消IDEA中代码重复的检测

  9. 还一道区间DP -- MZOJ 1346: 不老的传说

    http://10.37.2.111/problem.php?id=1346 与上一道染色基本一样,就加了个限制条件(一次最多刷maxd) #include <bits/stdc++.h> ...

  10. 前端之前端介绍或html的常用标签1

    一 web服务器的本质 由浏览器发送一个请求.服务器接收到,然后在回应一个响应. 由于浏览器的不同,web服务器响应的内容不一定被浏览器接收. HTTP/1.1 201 OK\r\n\r\n需要发送的 ...