You just landed your first job as a programmer or a dev… Congratulations! Now how do you keep that job? We gotcha. First, read this. That’s a lot to remember, are you freaking out? No problem. All you really need to do is remember step 1 or (for those of you that didn’t read it):
Communication. “Communicate; listen, that’s a big part of it. …Being somebody they can count on, somebody that gets along, somebody that they can speak to is a huge part of the job. …Just work with people, listen, and that is like 90% of it.” -also- Don’t ask Google-able questions. “…If you find that you’re having difficulty, don’t be afraid to ask questions …short, concise questions -don’t ask super long-winded questions- keep it pithy/to the point… …[And] don’t ask too many questions -especially questions that you could research on Google (ultimately they’re hiring you to get the job done).” But stuff happens, for example, “…there could be some design issues, there could be some specifics with regards to their particular software…hopefully they’ll be able to provide that [answers] for you…” -and- The ‘Ramp-up’. It doesn’t matter if you’re a fresh-faced noob or a grizzled old veteran programmer, no one with brain in their skull expects you to get things right outta the gate. There’s a ‘ramp-up’: “When they first bring you in there’s going to be some expectation of a ‘ramp-up’ time. You’re not going to know everything …if they have an advanced piece of software, …you’re going to have to get to know the code base, and that could take time depending on the complexity of the software. It’s not your code, you’re going to have to learn it. And in your first little while go out of your way to make sure you try as quickly as possible to learn the code -don’t kill yourself; don’t get all sweaty and nervous about it- …but ask your coworker, your lead. ‘what do I need to do first so I can get up to speed and help you guys?’ “.
After that, it’s like any other job, “…be sure to double-check your work: make sure you don’t make any silly mistakes, …if you’re assigned to a task, make sure you get things done on time, …and hopefully you didn’t lie on your resume and say you were a ‘master nerd’, cuz they’re going to figure you out pretty quickly…”.
Check out the VLOG for some really good advice and <Shameless Promo> generally speaking, if you’ve taken the web stack course, you might find yourself ahead of the game as many people found out once they got the job… -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!
