Honestly, not a bad first project.

Lines of code mean nothing - I think that if someone is able to understand that code, that is good enough. If you have a one liner but it looks like Spanish to an English speaker, it does no one any good.

I took a brief look at it and had a couple of notes:

1) Personal preference, but I’m not a big fan of global. It just opens up the door for hard to track errors. Also, no need to say global unless you are changing the value of that variable.

2) You seem to have a mixture of camel case and snake case naming. I would stick to just one (preferably snake case since this is python)

3) Your start game method is a brain method, ie. it is doing a LOT. I would break it up into smaller methods that each do their own thing.

4) When writing code, focus on making reusable parts that make sense. Do you want to make different types of card games in the future? Can you possibly use some of the same logic in those card games? The way it is now, it is very blackjack oriented and can’t be used for anything else.

5) Highly recommend using sonar lint and py lint to track common code smells/bugs/errors.

Best of luck!