I think this question is difficult to answer. What are your goals? What are you trying to achieve? Learn a novel skill - because of curiosity or to primarily ac

I think this question is difficult to answer. What are your goals? What are you trying to achieve? Learn a novel skill - because of curiosity or to primarily acquire a job? I can speak to my brief, very limited experience in the space. My first internship in college was working with COBOL programmers and migrating some legacy software to a modern, object oriented stack. I wrote COBOL, moved some things to a new stack, and write some documentation. Standard stuff. It was a very different job (than my later roles in big tech). The culture was old timers, very laid back, but some of the most genuinely kind and helpful people I ever worked with. My coworkers were at least a couple decades older than me, but I received some of the best feedback and mentoring on not just work but life lessons from their years of wisdom. Attire was business formal. The environment was less, “think big innovation, reduce complexity and cost at mass scale, think about long term support and evolution”. It was more, “Ozzythecat, you do A. Carl is going to work on B. For questions, go to Bill. Let’s check in tomorrow. Also we’re going to this diner for lunch if you want to join. The pancakes are great.” I was also just an intern, so maybe that stuff wasn’t as visible to me. I was paid $12/hr. Not sure how the COBOL market pays these days, but that’s obviously another consideration.