While I was studying physics I made an internship at a research institute. I was surrounded by world class physicist (noble price winnerS next building) and mat

While I was studying physics I made an internship at a research institute. I was surrounded by world class physicist (noble price winnerS next building) and mathematics in the theoretical department feeding one of the #10 supercomputer with simulations. You can imagine how hyped I was starting there as someone knowing shit about shit Reality hit fast since people spent like 80% of their time fixing other peoples code and spending all free time complaining about the same. Well, no wonder since the code was a pile of randomly attached PhD/master/whaterver-theses of people building software for one purpose and one purpose only to make their stuff run. All mixed with the attitude "I'm a scientist how hard can some programming be...". This was the time I realized the difference between programming and software engineering with project management and architecture (plus I'm not good at physics). In fear to go down a similar road I started listening to CS architecture/engineering courses at my university to make sure what I'm doing not just feels right but actually is. >10y fast forward I would say, maybe it was not the smoothest transition into CS (in a broader way) and I would challenge the one ore the other argument from back then but I never regret by career decision :)