My ship was Carnival Inspiration! :) I absolutely agree, it's a great life lesson especially in your twenties. The drills, the discipline, the lifestyle, and the adventures. For me it was a bit more dire though. I started as an assistant waiter - just one step above the galley stewards. It was army :D

Yes, some things I do!

1. The madness: Standing behind a bar on a party, having like 50 people around, back-to-back with your bartenders, shaking 16 espresso martinis or 20 jager bombs at times, loud music, loud people, managers are looking away when you drink a few shots on duty because they see that you must work super hard to stay above the water and they are grateful. Oddly I miss those things. No bullshit, just "right now" solutions and improvisation. It was hard to come back to corporate software dev. - where we have meetings for two weeks to decide something. :)
2. Brotherhood: There is this tendency in hospitality, that the businesses are constantly testing how much they can decrease their used resources, without losing the quality of service or revenue. This often means that the crew has to work harder and harder to get through the night because they haven't got the manpower, or there is some other logistical problem that the business 'saved on'. But the thing is: the harder the work gets, the closer and more intimate you get with your colleagues. You get a kind of "soldiers together in the trenches" feeling, and it's very satisfying. You know that all of you have to work hard to keep the operation under control, and you must support each other. You never get that intimate with people in an office.
3. The small wonders: Making fresh coffee by the Thames, keeping the bar clean and tidy, managing ales, teaching kids to do cocktails and latte art, explaining wines. I liked those things too.

+1: confession. I must admit I never really liked to serve people. Inside I'm more of an introvert. It was always a bit hard to play the nice talkative guy.

Geat question! And the answer:
Managing operations between departments in a hotel.

A lot of times I had situations when I was organizing functions or daily service and information was scarce. Just some examples:

• Finding out in the last minute that the couple changed the wedding welcome drinks three days ago, but the concierge forgot to hand you the sticky note he wrote it on.
• Asking the kitchen that is a 5-minute walk away if they finished the cakes for the 16 people afternoon tea session - when you can't make the walk as you're alone in the bar and there are guests pouring in.
• Checking the cellar stock if there are enough beer kegs for the festival days without going down to physically count them.
• Running all the way to reception -leaving the bar unmanned again- to ask them to call housekeeping to check if a given room is ready for a guest who keeps asking you in the bar if her/his room is ready yet.

It would be nice to fix this somehow. Actually, maybe even a proper slack group could solve these things with proper notifications. :D

The first thing that hit me was the revelation that no one knows the solution to problems right away. In hospitality it's usually quite simple how to connect the dots, and I thought development is the same. It took some time for me to realize that I shouldn't hide any uncertainty to look more competent, because it actually just slows my learning process if I don't ask questions. The thing what I had to understand is that we never know how to solve the problems right away. Because the job itself IS actually about figuring out the solutions. Not just executing them. Executing them is easy, everyone can type. :D

Good question. It was tricky. Actually I first applied again to the university and after I was re-accepted I applied for internships. There are two reasons for why I went this way:

1. In Hungary you have a certain amount of free semesters payed by the government. I still had 2 back then.
2. It's much easier to get a developer intern position, than getting a junior developer job, if you don't have experience. Because every damn job requires experience! I only had some portfolio and a bootcamp qualification. For some reason companies don't want coder wannabe adults, but they want to pick up ambitious students (which is just elitism really. Sometimes a fast learner ex carpenter is much better than a disinterested 19 year old kid who only works for some extra money to spend on weed. I'm exaggerating but you got the idea.) So if you are a student companies are more willing to train you, and you are also cheaper for them as student workers have tax benefits.

I got an intern position at a big telecommunication company, where I started working in a DevOps team. This was really beneficial, as I was quickly exposed to many toolchains and practices. Git, bash, python, groovy, java, perl, C++, Ant, Make, also a lot of development practice stuff like source code management, building applications, CI, build automation, etc. I was learning a lot and working a lot. I was watching tutorial videos even after work. My team really supported me, so the stressful part was only my own fear of failure. I was really afraid that I can't learn fast enough. The first year was hard but I really wanted to make it, and I also enjoyed this new lifestyle. Later I was offered a full time position, so I dropped university and I've never looked back since.

Good question!

fav: Old Fashioned.

Beautiful drink, beautiful ritual. Classic cocktails need the most creativity. Choosing the right bourbon (or even rye), executing the cooling nicely, experimenting with the amounts of acids and sugar, playing with it's garnish. Needs competence to figure out how a certain guest likes it.

least fav: Espresso Martini

Has to be individually shaked, and usually 10 is ordered. Coffe is needed in it which is sometimes hard in a bar that has a separate cafeteria. Makes such a mess.

Find a way to get a programmer job. Doesn't matter how simple or bad. Find the easiest route. Then start learning and get some experience.

Hi. So my path was tricky in a way that I actually went back to university a bit, and from there I used my student status to get an intern job. And then I worked my way up as an intern.
But for you my suggestion is to just get a good basic knowledge of your field (whether it's frontend/backend/or other) and do shitloads of applications and interviews. Do interviews as you would do a job, don't worry if you fail them. Interviews are a very good way to practice and to learn what companies are usually asking. It may take 5-10-20-30 interviews, but you'll eventually get that first job. Be resilient! That's one of the most important things in this field!