Re:A generalist software engineer can learn ${buzzword}
by hinkley on Saturday June 09, 2018 @02:27AM
(#17271821)
I was listening to some interview or podcast about a year ago and the line that really struck me, in the "I've always known this but didn't have the words" sort of way, was this:
How ages faster than Why.
Many of the tools we use are trying to wrestle with the same set of problems we've been dealing with since at least the early 90s. Physics and Information Theory don't change just because you found a new syntax for a programming language. Most of the 'novel' concurrency models people plow into their new framework were all documented by Tony Hoare over a five year period in the 70's.
And all of these libraries, with rare exceptions, are building over the same set of wire protocols and OS abstractions.
The challenge for any of us is staying committed to the work. You can get their by learning perseverance, or trick yourself into it with zeal. Amp yourself up with regrettable levels of excitement and dive in head first. But if you take that option, you're going to spend your whole career running from one thing to the next, until you get some perspective or get out.
Zeal is made uncomfortable by ambivalence, and it hates dissent.
The hard part is not learning the new way to do the same thing. Chesterton's Fence has your back. The hard part is telling an interviewer that what they're doing isn't all that novel without them getting offended or labeling you a wet blanket. But how else do you convince them you can come in 'cold', as they see it, and contribute, because it's not cold. The future is already here, it's just unevenly distributed.
I have a million things I want to get done that I only rarely get to work on because we're so busy dealing with distractions. I don't need buzzwords to do any of it, but I do need progress, and that's hard to find when everyone is running in circles.
How ages faster than Why.
Many of the tools we use are trying to wrestle with the same set of problems we've been dealing with since at least the early 90s. Physics and Information Theory don't change just because you found a new syntax for a programming language. Most of the 'novel' concurrency models people plow into their new framework were all documented by Tony Hoare over a five year period in the 70's.
And all of these libraries, with rare exceptions, are building over the same set of wire protocols and OS abstractions.
The challenge for any of us is staying committed to the work. You can get their by learning perseverance, or trick yourself into it with zeal. Amp yourself up with regrettable levels of excitement and dive in head first. But if you take that option, you're going to spend your whole career running from one thing to the next, until you get some perspective or get out.
Zeal is made uncomfortable by ambivalence, and it hates dissent.
The hard part is not learning the new way to do the same thing. Chesterton's Fence has your back. The hard part is telling an interviewer that what they're doing isn't all that novel without them getting offended or labeling you a wet blanket. But how else do you convince them you can come in 'cold', as they see it, and contribute, because it's not cold. The future is already here, it's just unevenly distributed.
I have a million things I want to get done that I only rarely get to work on because we're so busy dealing with distractions. I don't need buzzwords to do any of it, but I do need progress, and that's hard to find when everyone is running in circles.