Should you continue to learn Python, even if Python jobs in the area are more or less in data sciences or other areas you’re not interested in?
So, what if you’re learning a language; Python in this case and you start looking around at possible jobs and realize that all or most of the jobs for Python are ones that you have no particular interest in? Do you stop learning and move onto something else?
“I think it’s a good idea to learn multiple languages, …every time I learned a new language my skills as a developer went <sound of a rocket taking off>, rocket[ed] right up. All these modern languages…they all share so many of the same qualities, but they look at things from a different point of view.” Think of it in terms of hanging out with different friends, even though hanging out with different friends has a lot of similarities: having a drink, talking, laughing, etc, the experience will always be different, ya know?
We’ve said it here before but there is no such thing as a wasted language, because each language learned is like a tool in your tool box, there will be an occasion to use it. Now that being said there are some obscure tools out there and if you’re getting into this business to make money, you’re probably better off learning to use the most popular tools. But, hey, you’re an adult and as you become more experienced in this field, you’ll figure out what’s worth your time…
Check out the VLOG, there’s a lot of great info, including some commentary on Swift and JavaScript. -Enjoy!
New freelance web designers and developers have a choice between freelance sites where you have to compete globally, versus securing web development contracts from local business. But what are the Pros and Cons?
The Job market can be kind of tough, especially when you’re new and don’t have much experience or reputation to bank on. But thanks to technology and the internet, freelancers can work on jobs all over the world and in many different markets. We’re talking about freelance sites like Upwork, Guru, and Freelancer, etc, etc. where you can bid on contracts against people all over the world and how some freelancers have chosen to work in the global market over local businesses.
Pros & Cons: One big con would be that, “if you’re not in India or Bangladesh or if you’re in a richer country where your cost of living is much higher, so you have to charge more…if you’re in the West and you got to compete against people in India and Africa or wherever else on the contracts, it could be daunting. But even on those sites, if you position yourself properly -you develop a reputation, etc, you learn the pricing models <shameless promo>, I talk about this in my freelance course- you can compete, even in New York city with people in Bangladesh.” Btw, another advantage to the freelancer sites is when you bid on jobs, you can offer to do them for free, just to get your experience and start building that reputation.
Local jobs, on the other hand offer much less competition. “Because it’s a local business: likely a small business, <they> are less likely to deal with people overseas because they don’t trust it, they don’t know, they don’t know how to deal with them, they don’t know how to assess anything…they’d rather deal with local talent because they can actually communicate with them, in their language and there is a cultural alignment as well, but you have to go out there and put yourself out there.
I don’t know if you’ve been keeping score or not but unless you’re leaning really hard to one side, they both seem to have their faults and potential upsides, so we’ve come up with a strategy, “first do your foundations, one or two projects, then do a couple of freebie contracts whether it be local or use one of those online sites <Upwork, Freelancer, etc.>,then I would start cultivating both: online and if you can cultivate local business, do that as well.”
The VLOG goes into heavy detail about this subject and is definitely worth you time to check out. No matter which side you pick or even if you decide to do both, just get out there and get what’s yours. -Enjoy!
Complex development can linger in production, as you work on the last 5% of the job.
So you’ve got your project, your app – mobile or web, etc. ready to go and you’re almost done, “You’ve got the end and use case defined, meaning people can run through your system, you’ve got the UX defined, you got your UI in place…now at this point you’ve got just 5% left -so you figure, ‘we’re going to crack this thing out in a month…or a week depending on the scope of the thing over all- but what you’re going to find is that last 5% lingers…” Oh yes, ladies and gentleman, like a fart left in the back of an airplane bathroom…it lingers.
Light at the End of the Tunnel To get that crucial 5% working from end to end takes longer than you think and that is just par for the course. “[You’ll] find all these little things: this has to be fixed here, that has to be fixed here…this is normal. Keep that in mind when you’re first getting into the game, especially when you’re dealing with clients, and you’re building their system; you’ve got to account for that last bit of back and forth.”
So there it is my weary devs… Check out the VLOG for the some more insight into ‘the forced march of the last 5%’ and just know that it’s normal and to always account for the back and forth between you and the client when you hit that last 5%… -Enjoy!
Heads up! This is going to be geared to our courses (specifically our web development course), but you can definitely take advantage of the information we’ll be providing…but it works best with our courses 🙂
So, when should you start freelancing after taking our developer course? “This is what I’d do: you finished my full stack course, you do all the foundations training, you do the first few projects that I suggest on the project section, and then the thing which you should do at this point is if you got my freelance course, you should read the first few chapters of the freelance course which gives you the framework to setup your freelance business. Then you have to complete your web design training as a padawan web designer or web developer-junior: what you do is you go out there and you do one or two small…SMALL projects as a freelancer for some independent company/third party.” Consider this your final exam cuz you’re going to be out there doing work AND communicating with clients! “…And if you have our freelance course, you’re going to get all the templates, the contracts, the initial proposal templates, etc…”
So there you have it. The VLOG goes into even more detail and you can even hear about how Stef got started out as a freelancer, having no idea how to build a CRUD based application and what he did. Thanks for listening to our shameless promos and if you’ve had your interest peaked by what it is we offer, check out our courses, it’s definitely worth your time. -Enjoy!
Spending all your time doing code tutorials, is not going to get you to developer-land quickly. You need to get on with it, and start building real projects!
In life there are two different approaches to situations that people generally take. There are ‘preppers’ and there are ‘doers’…and no doubt you’ve come across this in many parts of your life and you’ve chosen to be one or the other, to varying degrees of success, I’m sure, but let’s talk about prepping vs. doing in the context being a coder, programmer, dev, etc, etc.
Be warned there are shameless promos ahead… Now we want to be clear that there is nothing wrong with a certain amount of prep; no one is saying that you should charge head first into the mouth of the beast(as bad-ass as something like that would figuratively be), without knowing what kind of a beast it is, do I have an appropriate weapon? Is there a healer present if things go bad? Prep like that is perfect for most situations (and a good indicator that I’m playing too much DnD), but too much prep: i.e. – what is the optimal whether pattern to attack the beast? Is it best to attack on an empty stomach? Only serves to bog you down and ensure that you never get out of the gate to slay that beast…
“They get caught up in tutorials…the perpetual tutorial doer rather than the project builder… What you’re going to learn…they only real way that you’re going to get good at software development is to actually build projects.” For example in the courses we offer (there it is), we teach the foundations first and foremost, some ‘projects’ afterwards: one or two or even three and then we teach you to get out there and get some work done because there is no better teacher than cold and indifferent ‘experience’.
“It’s all about the basics, if you have your basics, then everything else becomes ‘easy’; your level of production just shoots up. …If you really want to learn, don’t spend nearly as much time as the preppers spend prepping: just do it.”
Check out the VLOG for a way more detailed talk about prepping vs. doing and if you’re on the fence about it, please check out our foundations course, it’s worth the look, we promise you. -Enjoy!
Whether you’re learning CSS or anything in general: give your mind time to assimilate the lessons.
Learning anything can be hard, but learning CSS (which is not a particularly intuitive system) can be just plain daunting. What do you do when you feel like your brain is getting ‘fried’? Take a break, man!
“Learning something new is very much like exercising: lifting weights/working out. Anybody who does regular exercise knows that the rest period in exercising is just as important as the exercising itself.” For example, let’s say you do some heavy weight-lifting and the next day you’re sore…should you go on that same day and lift some more? Contrary to popular ‘bro’ opinion…NO, you should take that day for your body to rest and relax, so that when you go back to lifting, you’re refreshed and ready.
“The exact same thing applies when you’re learning CSS, …etc. You are literally tasking your brain in a physical way to learn, to acquire, to assimilate new knowledge. And because of that it’s going to reach a certain point where it needs a time to process this and assimilate it properly, so that means that you need to rest; so when you come to a point when you just can’t, it can’t sink in anymore: where the information is just becoming more difficult -your brain seems to be resisting the acquisition of new information (it’s becoming strained!) – at that moment, it’s your brain saying, ‘okay, we’ve trained enough, it’s time to take a break to assimilate.”
Check out the VLOG for a very understanding and meaningful deep dive into this subject. Don’t beat yourself up over how long it’s taking to learn either. That will not matter once you’ve attained your goal, and no one out there in the real world cares how long it took for you to learn something – they just want to take advantage of your knowledge. <Shameless Promo> Our courses, whether it’s the freelancing course or the web stack, or any of them are designed in a way that takes advantage of the fact that you’re learning at your own pace. So no worries, take your time, do it right and be good to yourself. -Enjoy!
…Or you can spend 25 years writing code to figure these rules out for yourself. Your choice… 😉
We use the ‘royal we‘ a lot here, but the man in charge and captain at the helm is Stef. He’s the guy whose over 25 years of experience as an entrepreneur, freelancer, and programmer, etc. is presented on a shiny platter of VLOG-ness every week, not to mention the courses offered (links below).
But when we <Stef> release a top 10 programming rules for you to take advantage of, well ya gotta give the devil <also Stef> his due and drop the pretense. And when we say 25 years of experience we don’t just mean showing up, doing your job, drinking coffee and then calling it a day… It’s also hard-knocks, disappointments, and life lessons. Stef doesn’t want a medal or anything, he just wants to save you a little heartache by listening to what he has to say. That way you have more time (and heart) left to do the things you enjoy.
I’m not gonna tell you what the programming rules are, you should watch the VLOG for that, but I’ll give you a hint: if you’ve been watching these VLOGs, even casually or out of sequence, you’ve come across all or most of them. This is just a condensed version of everything: the ‘from concentrate’ orange juice that has not yet been watered down at that small diner that you get breakfast sometimes, you know the one, their home fries are soooo good, but why do they ‘cheap out’ on the OJ?!
Check out the VLOG, it’s worth it. Or, like the subtitle says, spend 25 years figuring it out for yourself. Thanks, Stef (can I have a raise?). -Enjoy!
What are the top 10 programming (and coding) languages do employers want?
According to job listings on indeed.com as of may 16, 2019, we have the top 10 programming and coding languages that will get you hired. That’s right, sometimes the languages you enjoy and frequently use or swear by may not necessarily get you hired, but if you have experience with any of these top ten, you’ll have a job…at least until the end of 2019.
So what are the top ten, you ask? Well, if you’ve been following the VLOG, it’s not really a surprise… 1. Java 2. SQL 3. JavaScript 4. Python 5. HTML 6. CSS 7. C# 8. C++ 9. Ruby 10. PHP Bonus tip: While Java is at the top and you’ll have work for decades with it, Google has announced that they will be using Kotlin (while still offering support for Java) going forward. So, if app development for Android is your thing, ya might wanna look into that.
The VLOG goes into way better detail regarding the rankings, and of course, what would a VLOG be without some nice shots at Ruby for the #9 ranking! -Enjoy!
In safety news today, we regret to inform you that our ‘code on the go’ segment: where we drive around and talk about coding/tech and give our opinion will no longer be done in the car. I know, I know, but driving requires attention and concentration coupled with the ability to react to danger in a split second, and I just don’t think I can do that while delivering a deep dive into coding and insulting ‘Ruby’ at the same time…
Going forward there will still be a ‘travel’ component, where I show you parts of the city or nice scenic views but that will either be at the beginning of the VLOG and then we’ll go into deep dives, or maybe it’ll be more of a ‘walk n’ talk’, I haven’t decided yet… Which brings me to my next point; multitasking is a lie. There I said it. Think about it. When have you ever been able to do two things at once and finish both of them quickly and efficiently? Or to put it another way, “…our brains cannot multitask: they can focus on one thing, and then they focus on something else… that’s why if you want to be maximum productive in what you do, do one thing and finish it and then you move on to the other thing.” Studies have shown that taking on two tasks or projects at the same time has been shown to actually reduce your output and efficiency. “There’s not such thing as multitasking with human brains. …Our brains cannot multitask: they focus on one thing, then they focus on something else. That’s why if you want to be maximum productive, …you do one thing and then you finish it and then you move onto the other thing. If you’re trying to do two projects at the same time you’re actually reducing your output by quite a bit. …There’s a start-up time, there’s a spin-up time; let’s say you’re focused on talking about subject A and then you want to go to coding for an hour and you’re going to go back to talking about something else…the time it takes you to spin-up into coding mode…typically it’s ten/fifteen minutes, especially if you’re dealing with complex application development. …When you’re switching from one area to the next, there’s a loss of productivity with every switch, so multitasking doesn’t actually happen”.
There you have it. Now, obviously the VLOG will go into better detail about multitasking and you can hear the channel news straight from the source, so check it out. -Enjoy!
We get comparison questions a lot: Is it better to learn x or y? Is this language even worth learning over that language? The most recent example: Is Java and Kotlin development dead for Android development? When compared to progressive web apps (PWAs), which while more ‘generalized’, can be faster, and can cross-platform(Android & iOS) so you only have to write the app once, it’s easy to see why native tech would not be long for this world.
Our answer is, “I think native dev is going to be important for awhile…[but] there’s nothing to be lost by learning any language, as I said you can’t lose when you learn – even if you don’t end up using the technology.” “…Because what you’re going to see as you advance as a developer…is that all these frameworks, all these languages share many, many, many, many things in common and in fact when you learn your second framework, when you learn your second and third and fourth language (which will eventually happen), learning the new languages and frameworks are going to make you more knowledgeable of all the frameworks and languages you learn.” So, if you learn Java and then you go into PHP, you’re going to find the PHP is “…pretty much like Java. Yeah there’s some differences here and there but whatever; a function’s a function, a method is a method, and arrays are arrays…”.
Check out the VLOG for a more eloquent explanation of this thinking, but essentially, learn as much as you can because most languages have more in common than different, and you can’t lose from learning. -Enjoy!
