Format – 2 Live shows per week:
1. Live Q&A (Sunday 10:00AM UTC -7):
Live Q&A is directed towards beginner and intermediate Android/Java/Kotlin Developers with questions regarding said topics. As a self-taught developer, I never wanted anyone to do my work for me, but I could have benefited greatly by someone explain fundamentals and pointing me to resources. General/Principles based questions are easier for me to answer, but sometimes I can help you with API specific questions.
2. Let’s Build an App Live (Monday 10:00AM UTC-7):
This show is still under beta, but my goal is to demonstrate what it is actually like to build good quality software, to an architecture. I’ll still try to address comments in the chat, and take breaks to answer short questions, but this is not meant to be a Q&A primarily.
Current Project: Catalyft Workout Log
Looking for bite-sized content on Android and Programming? Check out my WTF playlists:
Android specific videos (Android WTF):
General programming tips and knowledge (Programming WTF):
If you like what I do, and want to see me do it better, please consider supporting me via Paypal or Patreon:
Check out these options to support me over Social Media:
Introduction to Kotlin (Google I/O ’17)
Kotlin is now an officially supported language for Android. This session provides an introduction to the language, covering basic concepts and tips for developers to get started with it.
Subscribe to the Android channel: http://goo.gl/GEh1ds
#io17 #GoogleIO #GoogleIO2017
Channel: Android Developers
Published: 2017-05-19 19:17:47
Programming WTF – How to learn code faster and get hired sooner | Top 2 Tips
Warning: I swear some times.
In this video, I summarize my thoughts on some of the most important things a beginner developer needs to know. Primarily, it contains tips and knowledge regarding the best way to learn new concepts and tools quickly. I also discuss what I believe to be the most important factor in getting hired as a junior developer; having work samples on a revision control system.
Kotlin Clean MVP Calculator on Android:
Published: 2018-09-08 02:08:47
Industry tips for transitioning into software architecture – Interview with Mark Richards
Software Architect Mark Richards discusses the attributes that a developer needs in order to transition into architecture. Richards also outlines the common mistakes that new software architects tend to make, as well as how established software architects can stay current.
Mark Richards interviewed by Mac Slocum at Software Architecture NY 2016.
Published: 2016-04-13 16:01:26
Reflections on Willpower (Motivation), Goals, and Hard Work
A friend of mine asked if I could talk about willpower, which I define as the ability to put forth effort towards a particular goal, regardless of of how difficult it may be to do so.
If you’re expecting me to be concise, you’ll want to skip this one.
Much of this discussion is based on my understanding of Stoic and Buddhist philosophy, which has supported me immensely in my development as a human being.
Ajahn Jayasaro – “What is the greatest problem in maintaining effort?”
Published: 2018-09-18 19:17:35
Git Branching and Merging Strategies
PLEASE READ: This video demonstrates an EXAMPLE of git branching and merging strategies. It’s a decent template to get you started in different situations. It’s not a “THIS IS HOW YOU SHOULD DO IT” video. These are ideas based upon my experience. Hopefully they will increase your understanding of git. In the end, you should UNDERSTAND your own process, how git works, and then create a branching and merging strategy that works for YOU and your situation.
Three similar branching and merging strategies in Git, with a common goal of keeping development history linear.
NOTE 1: This example branching and merging strategy is intended for larger development teams that manage a formalized development cycle with distinct development, testing, and release phases, and require production maintenance of more than just the latest version of the product. I don’t recommend these thoughts for small teams and simple development processes.
NOTE 2: One thing to remember is that my advice is simply an example put together from my experiences. If you don’t know where to start, the specific processes I’ve laid out are a good starting point, but be sure as you get more comfortable with things to adapt them to your specific needs or preferences.
NOTE 3: Note 2 implies that you take the time to understand what I’ve laid out and not just emulate it and also to be in touch with what your development process needs are.
Channel: Mike Jansen
Published: 2012-09-07 20:59:57