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?!
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.
Is it even worth becoming a “web professional” now and what does that even mean?
It can be strange how we categorize our positions and professions. For example, what one person would call a web developer, another would call a web designer. Then there are web programmers and specialties like “front end”, “full stack”, “back end” and “mid-thigh carver” ( I made that last one up, and yes, the last place I came from was the butcher’s…). So then what is a web professional?
And there are other questions, like is web development going to be obsolete with products like WEBFLOW and the like (products that will take away the need to code)?
With these titles and questions swirling around it can be very easy to throw up your hands and say what am I doing?! Is this even worth my time?!
The answer is: yes, yes it is and as far as ‘what is a web professional?’, well, that is a little more complicated…
First off, shameless plug: We offer kick-ass, detailed, and laboriously designed courses that will help to answer this question. So a web professional is kind of all these things combined in different ratios: designer, developer, front end, full stack, braised tenderloin ( I think I’m getting hungry…), etc, etc. Some devs may specialize in specific things (ex: back end or client side whatever), but it’s all in there. Hodge-podge is not necessarily the right word, but it’s the first word that comes to mind…
And how do you, as a web professional, ensure you know all these things or have a passable knowledge/experience with them? You learn. Either from having “been around the block” or by taking our course <another shameless plug, I know!>… But seriously, web development or whatever you want to call yourself is not going anywhere, in fact if the rate at which things are becoming more and more technological keeps growing, we’re going to need more and more devs at all kinds of different strengths and experiences.
Check out the vlog for a way more detailed and in depth explanation of this subject and quick side dig at RUBY… -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!
In a word …Nah… “I don’t think there’s ever going to be an official CSS4 specification…in terms of how CSS is developed…they now release CSS in terms of being module, so components of new CSS comes out…and are widely excepted by all the browser manufacturers.”
But before you go grabbing all the new and shiny things, we do have a warning for you as an active web professional/developer: just because you see a certain technology or feature is implemented in the specifications, it doesn’t mean that you can use it. “It takes awhile for browser manufacturers… to put into place these new capabilities according to the specification.”
And the kicker? Even if these browser manufacturers do streamline these capabilities into the newest versions of their product, not every person, business, or entity will not be using that browser, they’ll be suing an older browser and not even an the updated version of it. “A lot of people do not upgrade their browsers on a regular basis; some don’t upgrade them for years! So depending on your target market, …you may not be able to implement a particular feature that very modern browsers implement.” I know, it’s frustrating, right!?
So in conclusion, there’s not gonna be an official CSS4, there will be new CSS capabilities released into the ecosystem, but shinier is not always better.
Check out the video for a more robust explanation by a human (me) and <shameless plug>: we do offer a CSS course where we teach the foundations do you really get the sense of how it works. Also, for our followers out there or people interested, we go into how we chose which features to implement when we designed webstudio and the thinking that went behind it. Enjoy!
PS – We were just having a little bit of fun with words in the headline…we love you, CSS
HTML4 classic formatting tags, vs modern HTML5 interpretation of semantic tags.
HEADS UP: We’re answering what may be considered a beginner’s question so if you’re super busy and you already know the answer to this, feel free to move on. But there’s a little nerd history lesson in it…
So, “what is the difference between strong vs. bold tags, and between EM(emphasized) vs. italic tags? To me, they look the same on a web page. What is the purpose of distinguishing between the two?”
Great question. Simple answer: it’s semantics NOW… “You can use either/or today; it doesn’t make a difference.”
Historically: “when HTML was first invented there was no CSS, so they needed tags (a set of html tags), to allow web pages builders to add some styling to the page. ie: add italics, make certain texts bold, insert images, etc. So the early browser-makers … created a set of tags that were display tags: they allowed to change the look of things on the pages.”
As things evolved and HTML5 came along, the powers that be decided to give semantic meaning to the tags instead of having programmers go back and update/correct their previous work. Now, that being said there is absolute use in these semantic tags; for example those with accessibility issues like the seeing impaired will have a “reader” talk the page out and in that case, the reader will interpret paragraph tags, heading/footer tags,etc and it may become pretty useful.
Another use would be to target a very special audience or for very specific web application needs…but that’s another video…
Speaking of videos, please check this one out for a more in-depth history lesson with way more charisma than the typed word.
Also -shameless plug- Our web development course teaches you the infrastructure / history of these tags and how they operate. We like to go above and beyond -Check it out. Plus at the end of the video, some sweet summer heat and beach!! Enjoy!
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!
In the name of the JAVA; The RUN(time), And the HTML / PYTHON …DRUPAL.
THIS just in, from the Department of Urban Humanity or “DUH”: Programming Languages Are Not Religions! You’re all grown up professionals and we’re sure you have better things to do with your time than this, right?
Now if this doesn’t apply to you, please click on the video and enjoy the show…
But if you feel like “yeah but”-ing us about this, know that this isn’t a good look for you: both personally and professionally. Personally you come across as an arrogant jerk that has a “my way or the highway” approach (and not in a fun, sassy way), and professionally, well, you look like an amateur or a stunted, mid-level programmer that has no imagination or flexibility.
I know that seems harsh but it’s just such a waste of time when there’s amazing and inspired work to be done. Truly creative stuff that transcends the boundaries of algorithms and languages; and here we are chirping each other out cuz we don’t like the other person’s choice of programming language? C’mon!!
If you still feel the need to argue over this, might we suggest taking all that good energy and hitting the gym?Or maybe going to an actual church, breathing in some incense and chilling out in the back pew to some hymns? I mean, it should go without saying that even religions themselves shouldn’t be argued over like they’re religions, but here we are…
I don’r really know how to end this except by saying, be cool to each other guys. Life’s too short and you got better things to do with your time.
Unless you’re using RUBY, ya backwoods savages!! …just kidding!! …ish…