Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

What Problems to Solve (1966)

genius.cat-v.org

Post reply on HN
Print view View original

51–60 of 65 posts

Re: What Problems to Solve (1966)

#51

Post by frumiousirc »

amelius wrote: post #47

> I have worked on innumerable problems that you would call humble, but which I enjoyed and felt very good about because I sometimes could partially succeed. For example, ... [list of many problems] ... Plus all the “grander” problems of quantum theory. I'm having difficulty understanding what is meant here. Does he intend to say that his student thinks quantum theory is a humble problem?

I don't know what the student thinks but "[list of many problems]" are in some ways less "grand" as they are less about fundamentals of nature compared to the problems in quantum theory. But then Feynman puts "grander" in quotes to reduce its power and imply that "grandness" isn't all that - well - grand. He does this as his advice is that all problems for which you can find solutions are indeed grand problems. That's how I read it.

Re: What Problems to Solve (1966)

#53

Post by loloquwowndueo »

nevertoolate wrote: post #31
cocoa19 wrote: post #8

This echoes what I have thought about my career. What to work on. I've been blessed to have a good paying career in software engineering, but I've never really felt passionate about the products I work on. At the end of the day, my job is a paycheck. I do feel joy solving problems for others, improve society, be able to answer colleagues questions when they "come to my office". My family is happy that I can provide a…

I was surprised that after “closer to god” comes the “build the next kubernetes”. How do you connect these two things? E.g. I’ve found the “closer to god” in my yoga practice. And how I now realize that through words I can’t connect that much as through practice (e.g. just eating my lunch being fully present). I still think I can help through my software product building skills, but also know that if I can help peopl…

Kubernetes - only god knows how it works. There :)

Re: What Problems to Solve (1966)

#54

Post by 9dev »

amelius wrote: post #47

> I have worked on innumerable problems that you would call humble, but which I enjoyed and felt very good about because I sometimes could partially succeed. For example, ... [list of many problems] ... Plus all the “grander” problems of quantum theory. I'm having difficulty understanding what is meant here. Does he intend to say that his student thinks quantum theory is a humble problem?

Part of the point here, IMHO, was to show that Feynman himself worked on numerous problems, even small ones, not just those he is famous for, and sometimes even failing to solve them.

My interpretation is that he is both meaning to say that getting where he is took a lot of patience and hard work, and also that it is on yourself to determine which problems are worth your time. Which are both very important insights to have if you don't want to feel miserable.

Re: What Problems to Solve (1966)

#56

Post by hencq »

karussell wrote: post #14

Thanks a lot for posting this. I highly recommend having a look into the mentioned flexagons. This is a child toy where Feynman laid the mathematical background and it is very fascinating toy which you can easily build yourself. Try it out - it is really fun. No child required except yourself :)

I didn't realize it until I searched for it, but as a kid I did have one of those. An M.C. Escher one (a quick search found exactly the one [1]). My aunt got it for me when I was little and I was fascinated by it. Fond memories.

[1] https://www.jacobsurovsky.com/researchanddevelopment/2020/8/...

Re: What Problems to Solve (1966)

#58

Post by gjvc »

godelski wrote: post #41

> No problem is too small or too trivial if we can really do something about it. I think we often forget this. Especially in our fast paced world and career. But often it is the little things which are hard to get right and also the things that create the most problems. I think we try to think we can predict what are important problems and what are not. Sometimes this is easy and we're right, but often we aren't. Thi…

In CS we got here because we loved to play around and hack. I hope we never lose that.

get a job with a few managers and a jira installation and it will dry up pretty quick.

Re: What Problems to Solve (1966)

#59

Post by godelski »

gjvc wrote: post #58
godelski wrote: post #41

> No problem is too small or too trivial if we can really do something about it. I think we often forget this. Especially in our fast paced world and career. But often it is the little things which are hard to get right and also the things that create the most problems. I think we try to think we can predict what are important problems and what are not. Sometimes this is easy and we're right, but often we aren't. Thi…

In CS we got here because we loved to play around and hack. I hope we never lose that. get a job with a few managers and a jira installation and it will dry up pretty quick.

Well that's kinda my point. If you are losing it, push back. I'm betting there are others who feel the same but also feel alone.

Remember, they hire us for our skills. They hire us for our expertise. That means not always being a yes man. If you don't stand up for what you think is right, the product will become worse. The reason to question your boss is because you're on the same side: making the best product you can. It's okay to be wrong, it's okay to speak up, it is okay to ask questions. If anyone says anything different, they aren't interested in making the product, they are interested in their paycheck. Frankly, most of this loss we're talking about is because the business people took over and don't understand that an engineer saying "but what about " is not "no" it is "yes, but let's figure out how". This culture needs to be fixed, and it requires every day normal people to make that normal.

Re: What Problems to Solve (1966)

#60

Post by _9ptr »

meristohm wrote: post #13
cocoa19 wrote: post #8

This echoes what I have thought about my career. What to work on. I've been blessed to have a good paying career in software engineering, but I've never really felt passionate about the products I work on. At the end of the day, my job is a paycheck. I do feel joy solving problems for others, improve society, be able to answer colleagues questions when they "come to my office". My family is happy that I can provide a…

In keeping with the list preceding "climate change", consider changing it to: "...advance AI, change climate."

He obviously wants to advance climate change
Post reply on HN