January 27, 2020
Developers have to choose in-demand languages and leave the nerd-affections for tech behind. Also, learning about Amazon Web Services.
For those of you that thought we were going to talk about the possible alcohol problems you’ll face as a freelancer, and having to stop carrying around a flask of ‘liquid inspiration’ with you at all times… Sorry, that’s not this article (I keep mine loaded with bourbon -it’s a sweet treat with a kick!). No, we’re talking about Python Flask, which is <generally> a web framework that few people use, so ironically, if you decided to base your whole career around Python Flask, you might be hitting the bottle pretty hard…
We’re responding to an email we received about a gentleman (cuz he’s in the UK, I guess…) who’s about to finish school, wants to become a freelancer, and is wondering what he should “pick up” as his back-end language. He’s currently using Python Flask and doesn’t think he’ll stick with it as job opportunities in his area are not great. So let’s get down to it:
AWS and the NTNB (Need to Nerd Basis): No doubt time is precious and, “…hosting is becoming more and more sophisticated, and there are now third-party hosting solutions that you can use that will be able to deliver not just disk space on their servers but all kinds of utilities and capabilities, and processes that you can leverage in your apps.” Amazon Web Services (AWS) is one of them, so is Microsoft Azure, and even DigitalOcean (full transperancy: We use them), to name a few. And while we’re not going to go into a huge description of the services offered or how to strategically use them (Check out the VLOG, link below), we will say that there are some robust and sophisticated solutions on offer. Do you need to drop everything you’re doing and learn AWS or any of these? The answer is: NO…maybe.
“Do you jump into AWS now? No, the first thing you have to do is your foundations, you [gotta] understand basic web app development, and so forth, and then you can look at the solutions.” Also, depending on the client, “AWS: I think those are for larger projects, larger community, or larger organizations because they require more money and are more sophisticated: they may require more setup…”. There are of course, more middle of the road solutions, but this would be a good time to introduce our founding core concept: NEED TO NERD (NTN). At its heart is the idea that you “…learn what you need to learn on a ‘need to nerd basis’ “, which is a play on the ‘need to know’ concept. “People think oh my god, I gotta learn this and I gotta learn that, before I even get a job, and I say no, no, no: you learn what you need to learn on a need to nerd basis: when a project comes up, when you have to implement a certain type of functionality that requires a certain type of technology, then you learn it.” NTN will also be a newsletter that will be going out to you guys with links to videos and we’re thinking that we may even do an accompanying podcast as well (more on that as it unfolds).
In the meantime check out the VLOG, (it’s packed with all the explanations and clarifications that this BLOG will surely be lacking, lol). Remember that you are a developer first and not to bog yourself down learning archaic/draconian languages before you even need to. Just take a look out there and go with the flow.
My popular courses:
Interactive full stack web developer course: https://school.studioweb.com/
Learn Python 3 fast: https://school.studioweb.com/store/co…
My business courses:
Complete Freelancer: https://school.studioweb.com/store/co…
Complete Entrepreneur: https://school.studioweb.com/store/co…
My social links: