zlacker

I do think that's one of the reasons it's easier to do in physics. You're taught to see math as a language and therefore need to interpret it. With that in mind who cares if you memorize formulas and can churn out some algorithmic computation. You'll memorize formulas "accidentally" as you use them frequently. But if you don't know how to interpret the math you're completely fucked and frankly probably won't do well as a physicist. Much of the job is translating back and forth.

I actually loved my classical mechanics class. The professor was really good and in the homeworks he'd come up with creative problems. The hardest part was always starting. Once you could get the right setup then you could churn away like any other (maybe needing to know a few tricks here and there).

Coming over to CS I was a bit surprised how test based things were. I'm still surprised how everyone thinks you can test your program to prove its correctness. Or that people gravely misinterpret the previous sentence as "don't write tests" rather than "tests only say so much"

>>godels+(OP)
It's normal for young engineers to believe they can write code that cannot fail, design parts that cannot fail, design bridges that cannot fall down, etc. Fortunately, it was beaten into me in my first job that the idea is not to create designs that cannot fail, but to create designs that can tolerate failure. It's a very different mindset.

>>Walter+N4
Unfortunately I don't think this is being beaten out of people these days. I meet plenty of people that are seniors at quite reputable companies that believe that and it scares me...

>>godels+Xb
What I hear sometimes is along the lines of "I know my program has crashed, but I know it can continue to run safely."

>>Walter+N4
What was your first job?

>>throwa+Ai
Designing machinery parts for the 757 airplane.