The belief that the cutting edge tech must be the tech you use in your projects.
You may have heard your dad or your grandpa say something pretty close to this while grumbling about cars, phones or television sets; and that’s ‘shiny and new isn’t always better’. “As beginners you hear about this new technology is so great, that new technology is so great, etc, etc, and you can get overwhelmed and caught up with all this. …It’s chasing the illusion of perfection.”
And no demographic is more vulnerable to this illusion than young developers. For ease (and fun) let’s refer to this demographic as “noob” developers. “…[Noob] developers will chase perfection in their application development looking for ‘the better language’, or ‘the better framework’.” No only is this a waste of precious time but also a brisk jaunt into the realm of madness. “Don’t get me wrong, there are frameworks that are more ‘mature’ [or] ‘better’ than other frameworks given the application that you want to build. [For example]…If you’re building an AI based system, you’re not gonna wanna do that with PHP…you could…people have done machine learning with PHP – I wouldn’t do it – no, no you do PYTHON because that’s where all the action is, that’s where the market share is: that’s where it’s ‘mature’. …[But] you’ll find that any of the prominent frameworks and languages out there today…they’re going to produce good work…whether the app is good or not is up to you.”
Break your foot off on this VLOG for a very in-depth (and tangent-filled) dive into the “new tech trap” and remember, “in general all these frameworks and languages have pros and cons and everything looks greener on the other side of the fence until you get there.” -Enjoy.
Ever wondered how different apps or OS communicate with each other? For example, maybe your working on a JAVA app but it has to communicate with another app in California and they’re not the same app? Or you have an AI developed in PYTHON and it outputs a certain amount of data, how does it get that to a PHP web app (for arguments sake, I don’t make up your own scenario…)? How are the two going to communicate to sync or rectify data?
Well way back in the day there was RMI (Remote Method Invocation) and that was possible in JAVA world only. After that they used XML (eXtensible Markup Language), “XML code was so verbose, meaning there was so much XML code, …often times there was more XML code than data you were exchanging from system A to system B…”
These days the most commonly used method is something called JSON (JAVAscript Object Notation). “JSON is just basically a little bit of JAVAscript code wrapped around the information event you want to send from computer system/software A to software B. It’s pretty much the universal standard these days.” “It’s much more lightweight than the XML solutions…typically if something is easier and faster, it wins.”
If you enjoyed this soupcon into inter-operability, then check out the VLOG for a meaty main course and a little ‘digestif’ of advice on what to learn to be able to handle JSON effortlessly should the need arise. Keep on doing your good work and ponder the thought of two computers in a room trying to talk to each other in a human language…what would they even say? -Enjoy
What kind of highly complex and crazy work will you be doing? The answer may surprise you…
So what is the most common web developer job that is going to be out there in 2019? Are you gonna be building the next FACEBOOK from NODEjs or the next WordPress.com with PHP? The short answer is…maybe, but probably not…
“The most likely situation is you’re going to be working with small to medium sized businesses. Web developers will be building wordpress-based sites with custom mini apps, perhaps. You might be modifying shopify sites and deploying those for people.” Not as glamorous as you thought, is it? Well, it’s the truth…
Think of your standard web developer “…like a GP in the medical [professional]. You got medical doctors that are general practitioners, they don’t specialize in brain surgery, which would be kind of the equivalent of a NODEjs master or a PHP-Laravel master. The most common doctor out there is the GP (general practitioner): someone who takes care of most people’s medical needs. That is what a web professional is, you might do a Paypal integration, another day you might do a WordPress theme customizer…this is where a lot of the professional web-based jobs are gonna be.”
Don’t get us wrong, there’ going to be plenty of work building highly complex apps from scratch, “… but at the end of the day for every advanced app that’s built with NODEjs, there’s going to be five hundred, maybe thousands of jobs where you’re going to modify and build up a WordPress-based site, or work on a Shopify site for somebody.”
The VLOG really does this subject justice, including an answer to the common question of money. Specifically why does the NODEjs master make as much as the common web developer who’s just modifying Shopify or WordPress, etc. and it’s a good answer. -Enjoy!
People tend to fall into “camps” when it comes to programming languages, operating systems, etc. They swear by a certain operating system or only code with a certain programming language… Simply put, if this is you, you’re going to have a bad time…
To use an analogy, “If I was doing home repairs…[I see] we’ve got some nails to hammer, I’m not going to pull out my screwdriver…”. “When you become a professional developer, you’re going to be language neutral. You’re going to look at all these languages as tools to leverage depending on the circumstance.”
Broken record time: it’s all about fundamentals. Learn your fundamentals, “…because every language, every technology has it’s purpose or has it’s strong points and weak points…with some exceptions, some technologies are just dated…and they’re old school and you’re not gonna use them anymore.”
Generally speaking “noobish developers will say that this language is the best and everything else sucks, and if somebody tells you that on youtube or anywhere else, you know by definition they’re noobs (…except for us LOL).”
Check out the VLOG for some other really fun analogies and a sweet dig at RUBY. It wouldn’t be right if we didn’t dig at it every now and then… Go out there, try it all and save the camping for summer vacation or FPS games!
Come yung’uns, gather by the fire that I may tell you a story… well more of a walk-through really… The older kids have heard it before and have gone on their separate ways… Now, you’ll hear it and make your choices and go your separate way… I see you’re all fresh-faced and want to make a splash at being a developer but you feel inexperienced and unequal to some of the bigger boys and girls out there. You wonder, ‘what can I do to become a pro ASAP?’ Well huddle ’round the fire quickly and listen, before you start asking yourself why are a bunch of ‘young’ developers huddling around a fire to listen to an old man? Wait, what’s happening, where are we?!
1- Learn Your Foundations Well: Foundations being the languages; HTML5, CSS, JAVAscript, etc. Understand the client-server model, understanding the relationship between client computer, server computers, client apps, server apps, etc… <SHAMELESS PLUG1: Check out our links at the bottom to a bunch of awesome and beefy courses which will detail everything you will nedd to know>. 2- Frequency of Exposure: Simply put: the more you code, the better you get at it. You can read a book or watch a video but if you can’t put the theory into practice, how much have you retained? How much can you really use? <SHAMELESS PLUG2: Our courses have a wealth of questions, quizzes and exercises to make sure that you can put what you just learned into practice.> 3-Start Building Little Mini-Projects: You don’t have to build a “facebook” right outta the gate. Tiny, diverse projects will get you way more all around experience. Then you can start building small projects that actually do things for yourself or others. Ex: build a shopping cart that integrates with paypal, build a basic login system, etc… 4- You’re Always Learning New Things: Obviously, a developer of 10 years has a lot less to learn than a dev of 2 years that they’re STILL learning. It keeps you sharp and versatile. Which brings us back to point #1, if you’re well versed in your foundations, learning new stuff is pretty easy…
Well, that’s it yung’uns… Any questions or something you need more explanation on, check out this Vlog where we go into detail on all the points and of course, feel free to check out the links below to our courses, you won’t regret it <SHAMELESS PLUG3>. I’m going to go talk to our location director… -Enjoy.
Some criteria to consider when selecting a programming language to learn…
We get this question all the time in some form or another; “I really want to be a developer, but what language (programming) should I learn?” Well, let’s jump into it:
1- Consider the Job: The type of coding or kind of programming you want to do. For example do you need to do/want to build an iOS or android app? Web for small businesses? Etc… These decisions will play a role in what language you choose. 2- Consider the Ecosystem around the Language: You don’t necessarily want to jump into a technology that was not yet well enough established. Generally speaking if there’s no support/community for that framework/language, it might not progress or evolve with the “times”… 3- Consider the Job Opportunities Around the Language: Kinda relates to #2, if there’s not a lot of cross-platform support or community base, then generally speaking, you’re going to have a hard time finding a job with a more obscure language… Sometimes the “niche” market pays off but those opportunities are few and far between. 4- Consider the Market Forces: Competition can play a big role in choosing a language. How many other devs will you be competing against? What’s their experience? What is the Language that the majority of the market uses? All these things should at least be considered when you’re choosing a language.
Now that we’ve wound you up tight with anxiety and nervousness for choosing the right language (or failing miserably right out of the gate), let us offer you calming and relaxing idea to soothe you mind… It doesn’t really matter what language you pick… “Most of the modern languages share 80-90% (depending on language) of the same principles and constructs. The syntax or code that you write may be different, but at the end of the day…it’s the underlying architecture that makes the language…” so don’t worry about nailing your choice right outta the gate.
Check out the vlog for a more in depth explanation of how to go about choosing a language. And when in doubt, choose an open platform over a closed one; they tend to win out in the end. Enjoy.
First things first, a kick-ass opening for this vlog with a (literally, for those afraid of heights) breath-taking view of Montreal, and then back into the “studio” to check out my rig (drums), all to a slick tune in the background. Maybe we’ll call this segment, “Weeee, so fly.”
But let’s dive right into it… Should you use JAVA for back end web app development?
A very specific question deserves a very specific answer: “At the end of the day you have to always judge your technology stacks based on both technical implications of the choice and market implications.”
Technology implications: Do you have experience with the language you’re using? Are you comfortable as programmer? “It depends how nerdy you are, if you are very comfortable writing code, you’re very comfortable as a developer and you’ve done web apps before, yeah, JAVA, could be a good choice, but you gotta consider more than just the technical aspects of the language…”
In terms of market implications: “…are there jobs there? Is there a long road ahead for that particular technology stack?” Now, there are plenty of jobs in JAVA but they tend to be in or with larger businesses/ organizations. Even with smaller businesses or freelance work “JAVA would not be my first, second, or third choice…”.
Check out the video for a super detailed answer to this question and the more broad lesson that we’re trying to teach: What can you do Vs. what will the market pay you for. Also, did you find our RUBY diss(es)? Oh, yeah, there might be more than one! Enjoy!
Alright we’re going to lightly touch on this and if there’s enough of a public outcry, we’ll gladly do a deep dive but for now let’s skim over client side Vs. server side rendering. YAY!!
Now, full disclosure: It’s better to watch the video than to spend time reading what’s being written. The video is quick articulate and makes good and knowledgeable arguments for sides better than writing this out. But if you still feel like reading on, here’s the (very) skinny…
CLIENT SIDE RENDERING: So when you’re looking at the app/website, the views you render/send out (to the web browser) for the client to see. Generally you want to keep the views pretty simple when it comes to the processing power behind it.
The downside? Not everyone has the same hardware on their computers and may encounter trouble viewing the page (ex: web browsers not up to date, lag, slow load times, etc.)
SERVER SIDE: Does not rely on your viewers having the most up to date web-browser or fastest computer but it does require a lot of server side processing power…
So what’s a dev to do?
Check out our video for answers and opinions. Enjoy!
Hard to learn, easy to write … but slow to code with
Full disclosure: I love Java and in some ways, it can be easier to write than faster-to-write languages like JavaScript, Python and PHP. That being said, I wouldn’t use JAVA today in most situations… I know, I know, I can hear the rage-typing right now as the JAVA cavalry sweeps down the hill, charging towards me, but hear me out…
It’s hard to learn, even compared to other languages (like PYTHON, JAVAscript or PHP). It’s hard because “…you have to declare everything. …You have to explicitly write out everything your code is doing. …There’s a lot less things done automatically for you.” Which can be good: as a programmer that means there’s a lot less errors creeping in because there’s not really any “implied coding” (explanation in the video), BUT the coding you do write is super-detailed and verbose.
ALSO: It’s dog-slow at run time when writing desktop applications (never mind mobile apps).
-Totally dating myself here- JAVA was a great language for it’s time in the 90’s. “Because when you wrote JAVA it just worked…and it was very consistent. …JAVAscript: relative to JAVA was very inconsistent …it had some really weird, wonky behaviors and it could cause some really stupid little bugs that could cause you to pull your hair out trying to chase them down in JAVAscript, whereas you didn’t have that occur with JAVA.” I’m also not saying that JAVAscript is bad, in fact most companies toady are leaning towards lighter, faster languages and JAVAscript fits that build (especially when compared to JAVA).
So there you have it, from a guy that loves JAVA. It’s super verbose and heavily detailed in the writing (which also means less errors because you’re being explicit), and that writing code takes much more time, much more time means much more work and money/cost: “I wouldn’t do it.”
Check out the video for a more in-depth explanation PLUS what’s coming up with us with STUDIOWEB and other fundamental stuff we’re working on; super exciting stuff!
Which programming languages will be the most popular in 2-3 years from now? Should you even care?
Since the dawn of time, man has looked up to the sky and wondered what the future will bring…
Where will we live?
Will Pokemon revolt and catch US for their own twisted means?
…And what will the programming languages of the future be?
Well we’re not gonna sit here and cook something up, my crystal ball is gathering dust in the closet and I’m only going to bring it out when it attains “vintage” status, so I can sell it for a killing on craigslist…
But, by market share PHP is the biggest. It’s got to the point [where] “…none of these languages are going to go away any time soon, simply because they’ve reached that tipping point where they’re woven into the nerd language.”
It’s really the same thing with all the BIG languages. They’re part of the background and still very much a part of the forefront. They are relatively easy to use, convent and almost universally understood by virtually all of the developer community (even though opinions on them will differ wildly…)
Thinking about it from a practical standpoint, with the corporations you work(ed) for, let alone huge multi-nationals regarding the languages they use in their products: “…they’ve all gotten so good now that there’s no real major reason to want to change from one technology platform to another… for some company to want to move off PHP to PYTHON there has to be something really compelling about PYTHON or something really bad about PHP.”
Check out our video, where we explain our “theory” and drop some hints about what we think the future will ultimately bring…plus catch the (backhanded) nod to RUBY (we should be keeping track of these…). Enjoy!
