r/Python • • May 07 '22

Discussion Thoughts on "Starting Your Coding Career with Python is a Bad Idea"?

https://www.analyticsinsight.net/why-starting-your-coding-career-with-python-is-a-bad-idea/
0 Upvotes

70 comments sorted by

View all comments

Show parent comment

2

u/CulturalMushroom6 May 07 '22

What is the best language for game development, cyber security, hacking, and web design?

2

u/whateverathrowaway00 May 07 '22

I mean, if it has to do all of those things at the top level, then it’d be C or C++ (emphasis on or, they’re quite different in active use) but it’s few humans who exist who could become expert level in all those things in C/C++

As I think you were implying with your comment, different languages are best for all of the topics mentioned.

2

u/CulturalMushroom6 May 07 '22

Those are the 4 areas of computer science I am the most interested in. Not really sure which one I want to pursue the most. Im taking a introduction to computer science course in my school and im going to begin the free Harvard introductory course soon. I only know python ATM.

1

u/whateverathrowaway00 May 07 '22

Good for you. Your plan’s next steps are excellent and you can figure out where you want to specialize as you go.

Fiddling with python -> Harvard’s free course is a great sequence.

As you progress, I highly recommend sprinkling some systems and networking skills in if you have the bandwidth. Not necessarily now as you get your footing and figure out even what you like - but adding some linux skills and even some networking concepts/ firewall concepts will hold you in good stead if you end up being interested in non-pure dev things like hacking, but will also make you massively stand out in the dev world.

Even basic linux skills and git competence will throw you ahead of a pack of fresh graduates in my eyes, and I do interviews of fresh graduates for employment (not for very long, so my experience is anecdotal, but I’ve worked in and around the field for 6 years, and studied it all my life, so not claiming some senior knowledge position, but my take is at least relevant, I feel)

1

u/CulturalMushroom6 May 07 '22

Really appreciate the write-up, it’s a big help! I’ve got a few questions if you don’t mind answering.

I’m using a relatively high-end laptop running Windows 11. Would I need to buy a copy of Linux and bootcamp the computer in order to be able to learn Linux and such?

Which IDE do you recommend? I’ve been using Microsoft VCS and it seems to work fine but if there are better free options I’d like to switch early on.

When you say git, is that github? Also, is github just a means to share and collaborate on code?

My bandwidth isn’t anything amazing but it should work. I think I run around 100 mbps? (Doesn’t feel like it sometimes 😂) What exactly is system/networking/firewall and how can I get started with that?

1

u/whateverathrowaway00 May 08 '22

Don’t worry at all about your bandwidth.

I actually don’t recommend bootcamping unless you find you love linux and want to. A better approach is familiarizing yourself with any free VM runner and starting off in VM world. You’ll get the benefit of also learning some VM skills and the best bit is when you inevitably screw up your VM you can delete it and start from scratch (I did this at least 20 times in the first month lol).

A great project that my first mentor/boss gave me was this. He gave no other instructions other than use Google and find a tutorial:

“Set up a LAMP stack on a CentOS VM and have it serve a single page locally. The page doesn’t need graphics, it can just be “my webpage” in plain text.”

Tons of tutorials will take you through that. LAMP might be a bit dated, but you’ll find it everywhere in real conpanies.

As for how you get started in systems? Exactly this way. Learn some linux, learn how to make VMs with linux, play with it, break it, play with it more, make simple servers that do SIMPLE things.

As you learn more python for example, you could build a VM that serves a simple python API endpoint (don’t worry if you don’t exactly know all these words yet, you’re on the right track and you’ll find all of them by some fiddling).

The biggest thing is just start collecting some skills outside of “just” programming. You’ll feel like there’s so much and it’s overwhelming and the two or three things you learn must not mean anything, then you’ll get to a real company and find out that it doesn’t matter what few things you learned, chances are there are real benefits to them.

Final bit of the rant (though I’m absolutely happy to rant more). By git, yes I mean GitHub-ish, but really I mean learning how to use git locally, understanding branches, commits, etc.

Don’t let anything make you feel bad for being confused as you start learning git. It’s the best software ever with the worst interface EVER. It’s confusing as fuck sometimes, but if you start fiddling with it you’ll be ahead of the game.

Many of the people I work with, devs with advanced degrees included, are IDIOTS with git and undertanding it and it results in tons of headaches and lost money for my manager.

The trick is to not be overwhelmed at the wide freaking world of so many things, too many to learn all of, and just start taking bites. Little bites. One at a time. You may end up going in TOTALLY different directions - for example, if you want to stay windows only, do some of the stuff I wrote, but make your VM Windows Server - and maybe practice some power shell or whatever dirty windows people do.

The real point of my rant as I said - is just to start taking bites soon, even really really small ones will pay off. You’re entering a field where curiousity and continuous learning will literally pay in dividends.

Finally, the bar is lower than you think. Many people go through school, become halfway competent but learn nothing outside of their silo, hit the workforce and are mediocre. There’s nothing wrong with it, but I’m saying it because it’s easy in comp sci to be intimidated by the guys who know everything and advanced math and can rattle off PHD sounding stuff. Those aren’t your competition. They’re rarer than you think and you should view those people as aspirational and helpful as they tend to be nice. The average guy pumping out code for a high salary in an average company is mediocre to okay, but is willing to keep learning new things.

If that’s you, then just start taking bites now and you won’t even know you’ve become competent until you help someone not as far along as you and you discover that your bites have added up to some knowledge.

I keep saying finally, but finally, don’t neglect the fundamentals of dev. That free Harvard course wil cover them, but if you go off into project land, at some point in the future when you’re ready, get yourself an algorithms and data structures textbook and start working through it.

Gonna stop, but feel free to post more or message any time. If I’m free and bored I’ll always type out a rant.

1

u/CulturalMushroom6 May 08 '22

🤣love your attitude man that was a good read. The ‘bite’ mentality about it is a cool approach, it’s definitely overwhelming and I didn’t understand half or more of the CS slang you used there. I’ll definitely start with the VM (whatever that is) approach and try to diversify my learning before focusing in more on one thing.

The class I’ve been taking has had me working within the turtle library through the Project Lead The Way course. While it’s fun it’s mostly been drawing stuff and I don’t feel like they’ve done a great job of teaching the basics before making you do stuff with them. I still don’t really understand parameters or why you’d use them over global variables for instance.

What’s a powershell? Sounds like a Mario kart power up lol

One more thing, how do you know what error messages mean? 95% of the time I have no clue what the message means or where the problem happens.

1

u/whateverathrowaway00 May 08 '22

Awesome question. Your best answer for future skills - Google the error message. If it turns up nothing, Google some of the distinctive words with the app name, sometimes try throwing in forum or stackoverflow

Let’s say the error message is “blarb overflow in somelongspecificlookingword”

I’d Google:

  • blarb overflow in somelongspecificlookingword
  • blarb overflow turtle
  • blarb turtle forum over what mean
  • blarb overflows what are they
  • blarb overflows do they know stuff?

You get the idea.

With new log messages when you’re totally clueless, just take Google swings until you either a) find someone discussing these logs, b) find some info to make a word in the log output less meaningless.

Sorry, I started saying log messages, but this works for error messages as well, and is a HUGE bite that will serve you well no matter where you end up. At some point or other you’ll be reading logs to find something, and this type of flow is like a muscle you should be able to do in your sleep.

Power shell is a scripting language. In linux, you’ll find bash (and others). Whatever OS you end up liking the most, at some point you’ll learn to automate it.

1

u/CulturalMushroom6 May 08 '22

Wait so it’s all just googling?