All jokes of ominous soothsaying and portents aside, Oracle has released Java 13 with a promise of updates every six months. This is kind of a big deal because they are famous for releasing updates every 3 years, up until about 2017…
This article goes into more detail and provides a little historical content too, but let’s focus on a few things; mainly two new features:
Text Block: “The Text Blocks feature is designed to simplify writing Java programs by easily expressing strings that span several lines of source code without escape sequences.”*
There is the caveat that these are ‘preview features’, which means they may be removed in the future at some point or not, but this coupled with other improvements has given Oracle the image of coming out of the gate swinging.
Which brings us to the big question, should you learn Java in 2019? “Why not, you can’t lose. If you want to get jobs in the enterprise/android development, Java is going to be good for a long time. …And if for some reason an asteroid hits the earth and Java starts tanking in terms of popularity, you will have the [nerd] background to be able to move to any language you want.” This of course referring to the fact that Java is one of those big languages that has inspired so many other languages after it, and as such has many roots (for lack of a better term), in so many other languages that learning those other languages when you have a competent understanding of Java makes it so much easier. “…Java teaches you all these different concepts, best coding practices and so forth, which carries over 102% into any other language.”
The Vlog goes into some more detail and is worth a look. Plus, we’ve teamed up with InMotion hosting for a really amazing offer where they pay for you to take our courses and learn how to become a web developer. Links to all these offers are below. -Enjoy!
*: To quote Liam Tung’s ZDnet article (link above).
There is no better teacher of software development than the long term experience of building and refining a commercial app used by countless users.
As we get older we have friends who get married and have children. Sometimes while hanging out, maybe while having drinks or dinner, you might ask them how parenthood is going or (heavens forbid), you let it slip that you can’t wait to have children yourself, that it would be ‘fun’… Then you get to watch their brows furrow and the mood get very somber (did the lights suddenly dim in here? Did it get colder?!), and with a gaze that seems to penetrate your very soul they say in a foreboding voice, ‘YOU.HAVE.NO.IDEA.’. That somehow the scope and challenge of raising children is completely out your experience and in the abstract and ethereal, and one can never hope to grasp it until they are waist deep in it… Wow, that got ranty real fast…
Well, we’re going to make a statement that might put us in the same category as those pretentious parents but unlike those parents, we do it with love and encouragement…but we will dim the lights for dramatic effect… “You don’t really know app development until you’ve developed an app, taken it to market, gotten feedback, refactored/refined, and then made money with that app, or at least been part of a team that’s gone through that process where you’ve seen the app go from inception to actual functional use with the end user.” I know, for some of you ‘thems fightin’ words‘, but what we mean is that version 1 of your app, is not going to be the end – far from it in fact. A lot of (young) developers [devs] coming up are under the assumption that if they write the ‘perfect’ code, that the app will be perfect and there will be no need for a version 2, 3 or even 4. “…You have to expect that when you become a professional developer, that you’re going to go through many iterations…”. There is a purely academic idea that has been making the rounds lately in articles and even some YouTube videos about the “purity of code” or “purity of implementation”, and when you’re making commercial software, it’s just not the case.
The VLOG goes into waaaaayyyyy more robust detail, stemming from over 3 decades of experience in the business (which is like 269 years in young dev time), but what we really want you to know is, with regards to your app: (A) – Don’t worry about making mistakes (B) – Don’t expect that your first iteration of your code and your software is going to be perfect –it will never be perfect. so “…get your app out quickly (within reason, of course), don’t waste your time with perfect implementation.” Also, bonus material: We make fun of RUBY a lot. But at the end of the Vlog is a sort of postmortem theorizing -from a reliable source- why RUBY lost out on a huge share of the market. Plus, some sweet aerial scenery of MTL. -Enjoy!
We make fun of Ruby a lot here: 1. because it’s fun and 2. … …okay, it’s just fun really, but a question did come up recently from an individual who was offered a job working with Ruby on Rails. They come from a PHP – Laravel background and while they don’t know how to use Ruby, per se, their potential employer also offered to pay them while they learn it. So the question was do they take the job knowing that the use of Ruby on Rails has diminished or should they look for something else?
Now Ruby aside, we’d like to answer this question in general terms if you ever find yourself in a situation like this and you’re on the fence… “If you don’t have other work and the job is high paying, why not? …A language or framework does not define you as a programmer… you [just] happen to be using those tools at that particular time”. Now, specifically regarding Ruby jobs: “…it’s not gonna disappear over night and in fact we’ll probably see Ruby development for the next five years, at least, so …you do that for one year, two years, 3 years; what have you…”
Another question we’ve been getting recently is if Java is dead? With Google making the switch to Kotlin for app development and Oracle charging for Java licensing, what will be happening to Java jobs? “Does that mean the whole Java-Android development is going to collapse overnight? Probably not: it won’t, it’ll probably take a couple of years.” That being said, “if you’re writing code for your android app using Java, you’ll be able to transition into Kotlin very, very quickly.”
Check out the VLOG for a more sensible and detailed answers to these questions, and remember, “you cannot lose learning any programming language.” -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!
Google announced it would comply with U.S. government restrictions meant to punish the Chinese tech powerhouse.
Google suspended some of its business with Huawei by restricting access to Android updates. Huawei could lose its grip on the No. 2 ranking in worldwide cellphone sales but amidst espionage and technology theft accusations, that would be the least of their worries. This article from the verge and this CBCarticle pretty much sum it up, as will any other online news article you search for (depending on your news outlet).
But what does this mean for developers in the field looking for work? Will this affect the number of jobs out there?
Nah. “I don’t think there’s much implications. That’s it, if you work in China, and then maybe work for Huawei or for the Chinese it’s not so good for you…”. In fact, “if you’re in North America or Europe it’s going to be good for you because they’re going to start moving things back here…” What will this mean for China, whose chief economic advantage was “cheap” labor? Well, it’s hard to say as the North America is also in massive debt to China and other countries but as with most things, only time will tell.
The VLOG offers more insight into the subject and some sweet drive-by scenery of Montreal towards the end. -Enjoy!
The tech giant will still support Java but Kotlin is king for Android development.
A quick snippet to be sure, but Google has announced that when it comes to Android development, going forward it will use Kotlin. There will still be support for Java, “…but in terms of documentation, new libraries and so fourth…they said, ‘that’s it! Kotlin is our beast’.”
Without sounding like a broken record (probably a dated reference…), this does go back to what we were saying about a language that is easy to write in, generally gets more use/support and ends up winning out over more verbose/heavy languages. “Kotlin is an easier language to write in, it’s far more productive so…if you are looking for native Android development (and that I think is going to diminish over time…), …then I would lean towards Kotlin.”
The VLOG goes onto mention other casualties in the “simplicity wars” of languages and frameworks, like Apple’s ‘objective C’ being replaced by Swift. It’s worth a look just for the nostalgia factor alone. -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!
Is Microsoft starting to embrace ‘openess’ in it’s push towards the web platform?
A couple of months back Microsoft announced their new ‘Fluid’ framework and we read off the intro from an article at the beginning of the VLOG at the bottom of this page, so we’ll spare you that here… But what makes this announcement interesting is that Microsoft seems to be moving away from native apps, systems, etc and embracing a more ‘open’ operation. It’s even “…going towards the web platform, …it’s embracing web technologies: think html5, css3, javascript versus native development…”.
This is something we’ve touched on in past articles and even dedicated a whole VLOG to here, and Microsoft is just another great example: “…when you’re not sure which way to go, always go for the open technologies, …because open technology typically wins out over closed technology”.
We even went so far in a past article to say the native development languages like ‘swift’ for iOS or ‘kotlin java’ for android were going to go down to the open web technology solutions. Now we’re not saying that we know it all or that maybe we have the gift of premonition or anything like that, but it looks like Microsoft seems to be having a ‘premonition’ of their own…
The VLOG, of course, goes into more detail and is worth checking out but we want to let you know about a really cool offer by clicking here. We’ve teamed up with InMotion hosting for a really amazing offer where they essentially pay for you to take my course and learn how to become a web developer. Links to the offer below as well. -Enjoy!
…That’s ‘Positive Mental Attitude’ for ‘Progressive Web Apps’…
We keep on getting requests to cover PWA/RWD’s and because we’re not DJs or that small band at the back of the bar that’s playing ‘only originals’, we’re taking those requests…and 5-6-7-8…
So a PWA is a progressive web app and an RWD is a responsive web design. How are the two related? Well first off, “RWD is basically writing your HTML5 and your CSS code so that the layout of the site will flex and change depending on the size of the screen of the web browser that is visiting your site. So if you have a smartphone or a 75 inch flat panel TV, a properly coded responsive website or web app will look just fine.” So the idea being that fonts, images, layout, etc. will change size depending on the size of the screen you’re viewing them on. As you can imagine, with the way consume data and media, it was a pretty big deal.
Okay, but where does the PWA come in? “…A PWA is basically taking RWD to its ultimate highest level. Essentially…you can think of it as RWD on steroids, because it brings in all the power that comes with native HTML5 and CSS (and you throw in some JavaScript to add some extra capabilities, of course…).” “The big advantage of using a PWA over native is you have one code base, so instead of having to write one app in iOS with SWIFT, and then having to write the whole app again from scratch for android in JAVA or KOTLIN. PWA is a lot cheaper to get your app out there, and [while] you don’t get the full benefit with a PWA that you get with native, you get a lot of the benefits.”
Now the VLOG will go into really good detail weighing the pros and cons of PWA or native (and believe me there are way more pros), but as a dev or a freelancer you should always be thinking about where businesses are coming from. Most of the time they’re not interested in the “nerd” implications of the languages, frameworks, etc. that you use, they just want to get up and running fast and get the product or service out there and PWA is your best bet. -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!
