The work #5

We are all many things. We all do many things. We will do many more things throughout our lives. Yet, when we are gone, most will primarily remember only one of them. They will pick from the lot and remember you as that. What they pick will, in their mind at least, be all that you are. Therefore, it is our job to ask ourselves with all the things we allow ourselves to do, with each and every one, “Is this something I want to be remembered for?”

— Patrick Rhone, “What Will You Be Remembered For?”



More:

The work #4

Your code isn’t important: what matters are the ideas your code brings to life. Shitty code that makes a point is better than perfect code that proves nothing.

Don’t waste your short life getting lost in the geeky details of the toolkit du jour. Spend it using your skills to create something that matters to you, that may even last longer than you.

Most developers have far more power than we realize but too many of us squander it building things we don’t care about. Now is your time to make a difference. If you don’t do it now it may never happen.

— Nick Bradbury, “Code is Temporary”



More:

The work #3

Some mornings, in a perfect world, you might wake up, have a coffee, finish meditation, and say ‘Okay, today I’m going into the shop to work on a lamp.’ This idea comes to you, you can see it, but to accomplish it you need what I call a ‘setup.’ For example, you may need a working shop or a working painting studio. You may need a working music studio. Or a computer room where you can write something. It’s crucial to have a setup, so that, at any given moment, when you get an idea, you have the place and the tools to make it happen.
If you don’t have a setup, there are many times when you get the inspiration, the idea, but you have no tools, no place to put it together. And the idea just sits there and festers. Over time it will go away. You didn’t fulfill it – and that’s just a heartache.

— David Lynch, “Catching the Big Fish”




More:

The work #2

Of the hundreds upon hundreds of programmers we’ve worked or spoken with in the past year, I can’t think of a single time when the existence or absence of a degree made any difference. Anecdotally, we’ve seen little correlation between being a good programmer and having a degree in computer science (yes, even when it comes to understanding stuff like the growth of functions or tail-call optimization). There does, however, seem to be a strong correlation between writing lots of code, loving programming, and being awesome.

— Nick Bergson-Shilcock



More:

The work

 
This.

One could argue we should consider the good-enough-to-get-a-job skills to be the “baseline.” But there are a whole lot of front-end jobs to choose from, and getting one doesn’t establish much of a baseline. For me, I don’t want to get a job; I want to get invited to great jobs. I don’t want to go to work; I want to go to work with talented people. And I don’t want to be satisfied with knowing enough to do the work that needed to be done yesterday; I want to know how to do the work that will need to get done tomorrow.

— Rebecca Murphey



More: