What is the best developer computer/laptop in 2019? Should you go with MacOSX, Windows 10 …. or perhaps Linux?
It’s 2019 and you’re just getting started as a developer and you want the best gear that will help you get this job done quickly and effectively, so you look into it and maybe you should get a laptop for on the go work? Mac? PC? Or maybe you’ll just decide to get a ‘tower’ setup and just stay home? But what kind of specs do I need? Where am I? Who’s that guy and why’s he smiling? What’s going on, why is the room spinning?
Easy, young warrior, you don’t have to go pedal to the metal when it comes to getting a computer because, “it really doesn’t make a difference anymore in terms of which laptop you get or which type of computer operating system(OS) you get for software development (I wouldn’t use iOS yet for software development or Android…although I imagine that is going to be coming pretty soon…), …all these computers are pretty good: all very powerful, all very capable”.
Not only that but in terms of how much power you need, “You could use a six year old laptop and be able to do most coding with no problem. Where power comes into play…is compiling, if you have to compile…having a faster computer will allow you to compile much more quickly…”.
So there it is, the VLOG will go into a much more deep dive into what Windows 10 is doing vs. Linux vs. iOS, but it’s all pretty much the same. The only real thing you have to consider when possibly buying a new machine is “… think about your broader use case…if you’re a gamer, you’re probably going to want to be on Windows, as an example”. -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!
Is Microsoft starting to embrace ‘openess’ in it’s push towards the web platform?
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.
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
We’ve touched on this before in past VLOGS but maybe you haven’t seen that one or you want a more up-to-date take on this subject.
So, short answer: Java is really best for web application development, and Android client development. It never took off for desktop applications (we go into more detail in the VLOG).
If you don’t believe us, check out the job market. We would venture to guess that very little to zero jobs are going to have you building desktops apps with JAVA; “JAVA is not client-side, …it is server-side programming”.
The VLOG comes equipped with not only my lovable mug crooning to you about all the finer points about this, but I also offer solutions to in forms of other languages and options that will optimize your time and output for creating desktop apps. You should check it out, it’s less than 4 minutes!
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.
Another breaking discovery from the Department of Urban Humanity or ‘DUH’: “You are a flesh and blood human being and the software “tools” you choose do not define you. Whatever programs, hardware, etc. other people use is their own business and has nothing to do with you. Go live your life!”
The main reason for this VLOG is because we had the audacity to mention that some lifelong MAC users were switching to WINDOWS for a bunch of reasons, hardware inconsistencies, etc… And some people (and one in particular) practically pooped a kitten!
Now, trolls and general sh*t disturbers aside, we know that most people either have too much common sense or not enough time to care about this statement. But for those of you who genuinely have your back up: “it’s just an opinion, man. Who cares!”
Check out the VLOG below or if you feel like you’re on the outside looking in, checkout the links to some great courses that we offer, that way you can learn coding and then spew your opinion all over the internet…or take those amazing skills and become a highly paid and respected DEVELOPER SUPREME!!
The face of native mobile development is changing indeed … and fast!
Okay, so a couple of months ago we talked about SWIFT and how we felt it was going to “lose market share” because frameworks like FLUTTER, React, etc. were going to put more pressure on native development (like SWIFT) with their sheer versatility… it did not go over well with the SWIFT OG’s… but if we could just have a moment of your time, I’m sure we can make things worse… 🙂
“Flutter allows you to write cross-platform mobile applications (iOS & Android) using one language: DART, one framework: FLUTTER framework, and it’s created by google; and what interesting about FLUTTER -it compiles down to native so you don’t have a ‘performance hit'”.
Now, traditionally when you use frameworks, you don’t have access to certain things that you would with native but the major concern when creating FLUTTER was to give developers the ability to customize and have access to everything…in other words: flexibility. Writing and maintaining one code base which is responsive, compiles down to native is gives you a lot of control over UX and UI is pretty attractive and while no framework is perfect, it’s pretty close…
In the video we go into more detail and hit on a few interesting points. Check it out, it’s worth a look. Enjoy!
Widely used by some big name organizations like Nasa and Harvard, is a job working with DRUPAL outdated in 2019?
We’ve been asked if DRUPAL is a dinosaur, an aging language that won’t matter in the years to come and if anyone who works in it will be working towards obsolescence (whoa…heavy, huh?).
Well the short answer is “…no…”
The long answer is (thankfully) a little more detailed and availablehere in what I’d like to be the first to describe as a “Sausage” explanation. In that it is both meaty (detailed) and has a hint of spiciness (fun nerd ranting) mixed in…yeah, ya know what never mind, I’m regretting this metaphor already…apologies…
Suffice it to say that it’s better to experience this explanation in it’s entirety, with the relevant senses than to write it out. Plus, there a bonus RUBY dig (mwahaha…). Long story short if this is a first job for you, we all have to start somewhere and work looks good on a resume no matter what (not to mention experience) and you’d be surprised how many languages are still being used today…
But when it comes to the development of high demand (in terms of performance) mobile apps, using native languages like Swift for iOS and Java for Android is still the way to go. This might change with Googles Flutter framework.