Live data from Hacker News

Feynman: I am burned out and I'll never accomplish anything (1985)

asc.ohio-state.edu

121–130 of 285 posts

Re: Feynman: I am burned out and I'll never accomplish anything (1985)

#122

You get a couple of lines in, and it’s painfully familiar, since it’s sadly so incredibly similar to my waning love of programming... It’s wildly destructive for society to have these completely devoid of ethics, fascist-style assholes with capital/power, that can dictate what what more useful people than can spend their time thinking about, yet no-one even thinks it’s a problem. Although to be fair it’s just a sub-p…

So the solution is ... ?

Re: Feynman: I am burned out and I'll never accomplish anything (1985)

#123
post #17

I read (listened to, technically) this book a few weeks ago because I've always been inspired by the idea of Feynman and didn't know much about him. Honestly, I actually like him less after having read it. As I guess I should have expected, because its subtitle is "Adventures of a Curious Character", it's unfortunately for me filled with many more random personal anecdotes, often involving naked women, prostitutes, g…

What is it about those anecdotes that makes you like him less?

Dude was smart, but definitely a sexist. He didn't believe that women would be as capable of doing physics and engaged in some really awful behaviors that were weird even at the time (having meetings at a strip club? asking to paint students in the nude? really?).

The lockpicking stuff in "Surely..." is a really fun chapter but also makes it clear that Feynman does not actually care that much about inconveniencing others. It was a fun intellectual exercise but actually harmed other people, which is pretty shitty behavior.

It is just a little hard to read a book when assholish behavior just shows up with such frequency. Feynman was a genius, a great storyteller, and a lot of the content in his books is fabulous. But some of the material sours it.

Re: Feynman: I am burned out and I'll never accomplish anything (1985)

#124
post #46
post #44

Goal-oriented work, creativity and motivation definitely have a difficult relationship. In programming, I learn the most things simply by experimenting at home on my own. I'm thinking about switching jobs, so I wanted to learn some new frameworks and concepts to help with that, and I decided to make my personal projects a bit more "professional". Use continuous integration, focus more on web stuff, build and automati…

Your cognitive workload is too high. There are three forms of cognitive workload: Intrinsic, External and Germane. Intrinsic is things you just *know*. How to write a class in java, how to write a query in SQL, ... External is stuff you only need occasionally, and need to look up every time: How to deploy to X, how to set up CI/CD, ... Germane is context knowledge. Usually referred to as business knowledge. You want…

I tried that, and at first it almost worked. But that scaffolding just kept breaking. TeamCity doesn't want to execute my unit tests since I've upgraded to .Net 5.0, I still don't get how that docker "latest" tag works, my Ubuntu-TeamCity-Agent refuses to acknowledge it's running in Linux and that it has access to docker. After a while I realized I was wasting precious free time.

But I agree about the cognitive load. I have ADHD so in order to qualify as "high functioning" I need to continuously improve my coping strategies when it comes to keeping that load low. I write everything down. My thought process is anchored in long text files with hundreds of indented lists. My programming style is super verbose and perhaps a bit enterprisey, but each class does one thing and I always spend extra effort making sure the things I can re-use work well enough that it's safe to forget how they work.

Oddly enough, my reserves are much bigger when it comes to programming. I remember having trouble with some linear algebra homework - it involved a lot of matrix calculations, and my results just didn't make sense, and I couldn't focus long enough. So I programmed it instead, and it worked immediately and solved my homework. I think it was about change of basis, which actually got me side-tracked because I realized the same code could be used for a simple 3D renderer. And that's what got me into computer graphics. What was the topic again?

Re: Feynman: I am burned out and I'll never accomplish anything (1985)

#125
post #44

Goal-oriented work, creativity and motivation definitely have a difficult relationship. In programming, I learn the most things simply by experimenting at home on my own. I'm thinking about switching jobs, so I wanted to learn some new frameworks and concepts to help with that, and I decided to make my personal projects a bit more "professional". Use continuous integration, focus more on web stuff, build and automati…

> I'll come up with my own tools. They won't be great, but... They WILL be great. They'll do exactly what YOU need them to do, and nothing else. Software at present is a disaster, partly because we're just piling on complexity all the time, thinking only of the benefits and never of the huge downsides ("fighting with tools").

That's true, and personally I'd much rather fight with my own code since I usually 100% understand what it does.

In a team of course it would be different - unless I perfectly document my own code, my colleagues would be better off with something they can actually google.

Re: Feynman: I am burned out and I'll never accomplish anything (1985)

#127
post #44

Goal-oriented work, creativity and motivation definitely have a difficult relationship. In programming, I learn the most things simply by experimenting at home on my own. I'm thinking about switching jobs, so I wanted to learn some new frameworks and concepts to help with that, and I decided to make my personal projects a bit more "professional". Use continuous integration, focus more on web stuff, build and automati…

I love your "it adds up" comment. I will steal this. It is very true for me as well.

Several years ago, I started using make extensively. Not to compile, but to automate. Make understands failing and dependencies. Also, bash and zsh have wonderful completions.

I used to write a bash or python script to do this. They often turned into their own projects and were painful to document.

A great make example (thanks Aaron) is on YT: Using Terraform, Packer, and Ansible Together": https://youtu.be/pkEezNSFWtA. Aaron automated it all with make.

Ya, I know... Make was created in 1976 to compile Fortran. It's old school. I love it.

I use it to test my kubernetes CSI driver on 5 versions of k3s with a single make call. That call is the tip of a dependency tree. The leaves end up being a line or three of bash running Ansible, Go, Helm, etc, but could be anything.

Documentation is simple because the make dependencies are so easy to follow. They are much of the documentation. The docs are correct because we execute them.

Re: Feynman: I am burned out and I'll never accomplish anything (1985)

#128
post #109
post #74

Earlier quoted context omitted.

Not everybody is Feynman ofcourse. You have to accept the risk that giving freedom for creativity won't end up with anything useful.

True. I think most people can benefit from a bit of this at least. Ie. Speaking of software engineering, at work our 10% time is for us to do as we please. A lot of good things come from that. Maybe 50% time would be too much for most though. Google's 20% is probably the maximum I'd opt for if I were a CEO.

For me setting 10% aside as "do as you please" feels like a restriction on creativity as well. It's hard to "plan" creativity. I think culture and trust is much more important than setting a number.

Re: Feynman: I am burned out and I'll never accomplish anything (1985)

#129
post #44

Goal-oriented work, creativity and motivation definitely have a difficult relationship. In programming, I learn the most things simply by experimenting at home on my own. I'm thinking about switching jobs, so I wanted to learn some new frameworks and concepts to help with that, and I decided to make my personal projects a bit more "professional". Use continuous integration, focus more on web stuff, build and automati…

Hah sounds like you described me perfectly. But I do have to say, ever since I'm programming full-time I seem not to be able to just code for fun anymore. I used to program all day long.. and I guess I still do, but now it's for work, and after 8h of work I'm just done, you know? The "stuff I want to look at" list is growing longer and longer and there's no hope of me ever catching up. (I can't imagine how it is for…

As a father of two I can relate with some of the answers here, but I'd like to add an alternative viewpoint here just to give young dads some glimmer of hope.

For the first and a half or so we've had a difficult life with the first kid. To be honest, there is just no way around it. Especially your first kid. The SEAL-level sleep deprivation and complete lack of "me time" really takes it toll. I'm also not the type of dad to let mom handle everything. She also has a career and, to be honest, a better one too. So I was regularly up at 2AM, 4AM and 6AM. Then a workday. :) (If you have young parents around you, please try to be compassionate.)

But for some reason I'm more effective now than I ever was. I can remember "not having enough energy" to complete some project for as long as I am alive - even when I was alone. It is clear to me this had very little to do with my actual life and more with my attitude. My life is more complex and demanding than it used to be but somehow I still managed to lose 60lbs, learned to read Latin, took guitar lessons and started a business. Every single one of these items never would have left my todo list without my family. They have endowed me with a keen sense of priority which made planning my life quite easy to be honest.

I know those achievements I listed are not that hard, but for me they are significant. I've found most things in life don't require your eternal soul as a sacrifice, they just take (usually a lot of) time and so you need to be strategic about your goals. Take it slow, don't burn yourself out, but also don't stray from left to right unnecessarily. Keep your eyes on the ball. Don't shift from "write a compiler", "read latin", "write toy OS", "build cpu from nand-gates" to "learn german" and back to "learn to draw realistically" in a month. Focus. A dirty word, I know, but a powerful one.

Post reply on HN