iOS Debugging Fundamentals
Learning Platform: Kodeko Course: iOS Debugging Fundamentals
Learning Platform: Kodeko Course: iOS Debugging Fundamentals
Learning Platform: Kodeko Course: Programming in Swift: Functions & Types
Learning Platform: Kodeko Course: SwiftUI: Layout & Interfaces
Learning Platform: Kodeko Course: SwiftUI Fundamentals
Learning Platform: Kodeko Course: Programming in Swift: Fundamentals
Learning Platform: Kodeko Course: Your First iOS & SwiftUI App: Polishing the App
Learning Platform: Kodeko Course: Your First iOS & SwiftUI App: An App from Scratch
I took a quiz offered by aperian.com to build my, what they call, GlobeSmart profile.
The result is interesting to share and compare. Here is mine.
You enjoy working as part of a group. You're flexible about roles and titles, and willing to challenge your superiors if you feel it is necessary. You tend to be decisive and like to demonstrate quick results. You generally say what you mean, but you can also be subtle when needed. You value relationships and will not sacrifice them for a deadline.
Almost everyone knows GTD. It is the acronym of "Getting Things Done" which is a productivity framework introduced by David Allen in his book "Getting Things Done (2002) - The Art of Stress-Free Productivity".
The key reason to have a such framework is that our mind is great at creating stuff, but it's terrible at tracking it. And yet there's a good chance you're tracking tons of stuff in your head right now. Stuff that drains your energy and clogs your creativity.
I became a GTD user during a period in which I was so full of things to do that I couldn't work well. Just keeping the task list in mind completely occupied my brain and I could no longer concentrate on the task in progress.
I GTD love it since it keeps track of my tasks and allows me to focus on each one of them individually. Also, it allows me to work on several workstreams (or projects) during the same period (e.g. a quarter).
As a software engineer, if you're reading this, for sure you already know that the error budget is defined when we select a Service Level Indicator (SLI) and for it set a target Service Level Objective (SLO) over a specific time period. If you don't, head to the "references" section below which suggests introductory resources.
How fast can we consume the error budget? This question was not easy to answer for me. That's why I'd like to share my notes.