Full transparency: We have a book and we do videos, so we know what we’re talking about having been on both sides of the fence… And of course, our answer is (unsurprisingly) both-ish; kinda like a two pronged attack…
Books are great for referencing material, for example, you need to look something up, you find the page and boom: there it is! As opposed to sometimes having to watch a 15-20 minute video that has great material but it’s buried deep in the vid. You might have to start jumping around on the time bar to find it or it won’t be covered til minute 8 or the 15 minutes, which can be pretty frustrating when time is a factor.
Video on the other hand is great for “…engaging with the material you just learned.” If you’ve been following us for awhile, you know we have online courses that are tailor-made to helping you learn and then put to practice (through questions, exercises, etc.) the things you just learned. While with a book the learning tends to be more passive and in the case of retention, it’s hard to put it down sometimes and start practicing what you just read…
Now we’re not knocking anyone’s learning style, if you can retain and use information you’ve just read in a book, that’s great! We’re just trying to lay out what we think is the best of both worlds and will yield the best results vs. effort. Check out the vid where we go into MAJOR detail. And check out our links at the bottom to our kickass courses: it’s super effective! 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!
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!
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!
C# is probably Microsoft’s flagship language … is it worth learning 2019?
Well, is it worth learning? “If you want to interact with the Microsoft(MS) stack: …building web-based apps that are going to be interfacing with back-end MS technologies…AND you learn C# if you want to get into game programming with UNITY as an example”
Based around JAVA, this modern language was built by MS to function like JAVA but with some “robust” differences… But enough about that, let’s talk jobs!
There are lot of job opportunities working on .Net architecture (ie: web apps), mostly with big corporations…however most of them will require certification in C#. The good news, if you try it out and decide that C# is not for you, you haven’t wasted your time at all, because “all these modern languages(C#, JAVA, Dart, ,etc.) are based on the same principles [more or less]”. If you’ve learned C#, it’s like 80% transferable, “…you cannot lose when you learn a programming language…”
Check out the VLOG for a more in depth explanation, some wisdom about the game developer experience and a little heart2heart…awww. Enjoy!
Is Python really that much better than C#, Java or JavaScript, when it comes to jobs and what you can create as a python developer?
I think you really need to watch the vlog to put this into proper context…
We received an email that pointed out an interesting idiosyncrasy when it comes to learning programming languages. Long story short, it was pointed out that while python was a great language to learn, there are not many jobs (outside of AI) that actually use python today, thus making it harder to enter the job market. With so many other languages being used for other purposes, for example, games: C++/C# for games, and for native app development there’s swift/java/kotlin, to name a few, it doesn’t seem to be worthwhile to learn python if you want to get right into work…
Okay, now before we go any further, I strongly urge you to watch the video for context, I don’t want to start a nerd war; there are far better uses of our time…
That being said, for the most part, “there’s a lot of truth to that. Python is the go-to language in AI/machine learning and it’s the second [or] tertiary language…in many other areas.” The email goes on to conclude that “learning webstack is the best way to getting employed quickly.” I can’t argue with that, but where does that leave us with python?
“Python is a great language, it’s a language that glues everything together. If you’re working in large organizations, you might find the need for python. …A lot of schools teach with python now…because it is an easier language to teach people how to program with. …It’s accessible…Productivity of the language, in terms of how long it takes you to write things is a huge factor today, when you’re looking at programming languages…” But if you’re out to get employed right away then maybe webstack is the best thing for you. However, if you find yourself struggling and maybe you’ve had problems with other languages, python could be a great way to connect the missing pieces and streamline it all. The job opportunities will be less, not zero but less, unless you have a relevant university degree. Full transparency, yes, I do offer Python course but they teach foundations, modules, programming, etc. “…it’s just a vehicle to teach certain programming concepts and mechanisms.” I feel like the best way explain this is to watch the vlog, it really puts the things I’m saying here into perspective. Plus, at the end of the vlog, I look outside only to find February hasn’t left yet…jeez, get a clue, man! Enjoy!
Hello, Salute and Hola! Let’s talk about languages, specifically programming languages…
I often get a lot of emails and messages (Yeah, I’m kind of a big deal…lol.), and one of the main questions is what is the best programming language for me to start out with, or what would the perfect programming language be?
Short Answer: There’s no such thing. Pick a language and let’s rock n’ roll. If you’ve seen any of my videos, I’ve broached this subject before and I think, “there’s really no number one language. This is a fantasy, an illusion (WILL saves – BOOM; old school DnD reference.) that beginners would be interested in because at the end of the day, the language that’s going to be number one depends on the type of work you’re going to do, depends on where you live, depends on the type of programming you want to do…”.
Long Answer: “The first step is to learn the fundamentals – Pick a language; pick python, pick JavaScript, pick Java PHP, …pick that language and learn your fundamentals. Once you have your fundamentals, you’re going to have your nerd eyes – you’re going to be able to interpret and see and understand what you’re seeing out there.”
“First rule of programming: You don’t lose if you learn a language…All the modern languages share a lot of the same fundamentals, qualities and characteristics…”. Think of it like this: you’re 10 yrs. old in your parents basement playing super mario bros. on your nintendo ( please don’t sue, nintendo.). Then your older brother or sister enters and pops in super mario 2! At first, you’re a little trepidatious – different levels, different enemies – but after 3o seconds you’re back in saddle as you realize it’s still the same game – jump, jump, beat the boss, / next level: jump, jump, warpzone, / jump, jump, beat the final boss, finish the game, grab a pizza pocket and a soda, go to your room and air guitar to the RUSH album you stole from your brother’s room <the 80’s were a simpler time, yung’unns>.
Of course we’re going to go into more depth in the video <plus another RUBY zing :)>. But know that’s there’s really no one perfect programming language. Get out there, learn your craft, and you’ll always have the tools you need!
Documentation is super important in development. How important, you ask..?
…Very.
[Throw head back and laugh charmingly & disarmingly – then suddenly and intensely] …But seriously it is.
While it’s not the norm, it is becoming more common that programmers don’t leave proper documentation, be it self describing code, comments (little notes that you leave to yourself in your code) or more formal documentation (ex: what type of database structure did you choose and why?).
Granted, sometimes you’re doing something fairly straightforward, like a simple authentication object; it’s not really necessary. But for other projects, you’re only really hurting yourself. When you come back in 3 months or 6 months and you don’t recognize the thought process behind the choices you made, you’re going to double or triple your workload.
Also, it’s just a good professional courtesy from one coder to another. “The worst thing for coders is to have to go into a code base where there’s no documentation, you have no idea what the developers were thinking at the time, and it’s very hard to patch, expand, bug repair; extend a code base where you don’t know the reasoning behind the basic architectural decisions.” Take the time and make everyone’s job much easier and enjoyable…especially yours.
A Code of Conduct about Coding and a play on words for sure!
It seems every profession, association or club has their own “code” of operation. A set of rules or procedures that govern how members dress, interact and methodically complete a project or task. Well guess what? We have one too. And ours is Waaayyy better because it’s a code…about coding (if you can’t do anything with that, maybe you’re just dead inside…).
Presenting…
The Master Developer’s Code
A set of 5 lessons that have been amassed over 20+ years as a programmer. Granted some of the lessons here can sound pretty obvious if you think about it, we rarely do in fact. Sometimes we get so caught up in wanting to be the best, wanting to WOW, that we can end up making a mountain out of a molehill or worse; not listening to client needs. After this video, I recommend checking out our “Keeping it Simple” article if you haven’t already. It’s worth it.
These days we have many options when it comes to building websites, but which is the best way to build in 2018?
Let’s talk websites and the building thereof… So, you’re a small business owner or an aspiring website creator? Maybe you’re just interested in what goes into building a website. Well, there are many options and each has their PROs & CONs:
HTML & CSS The traditional way to do web design coding, these would be the two “languages” you’d have to learn and they can (theoretically) build any type of website. “There is literally no limitations, in terms of what you could build if you got into the nuts & bolts: the basics of building a website.” However, the downside is that you’re going to have to learn it; that is to say time investment, theory, practice; all the stuff that goes into learning a skill. But that being said, you know how to program!
Web Design Programs These can range from programs where you have to know a little bit of code (Dreamweaver, Brackets, etc.) to content management systems (CMS) like WordPress, down to easy site builders like WIX, for example. All are very different approaches (which we will touch on in the video) and vary in the amount of control you will likely have…
The key word here is control. As we go from straight up coding down the line, we lose flexibility and versatility; it goes from creating the very thing you see in your mind’s eye, to “what you see is what you get” on the building sites. And of course, that’s fine too. There’s nothing wrong or lazy with building a “wham-bam” website if that’s what fills your needs, but check out our video and you might get an idea of how to better fill those needs. And check out the links at the bottom if you’re curious about the aforementioned web design languages. Mastering the code of website creation does have it’s perks…
