-
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Write a blog post about lazy learning
- Loading branch information
Showing
1 changed file
with
36 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
title: "Lazy-learning" | ||
description: "Learning for the sake of learning might not be the most effective way to learn. I'm trying a new approach: lazy-learning." | ||
tags: ["Reflections", "Learning"] | ||
--- | ||
|
||
I've been thinking lately about my approach to learning. | ||
When I become interested in a technical subject (e.g., Rust), | ||
I tend to throw myself into learning it, | ||
even if I don't have a specific problem to solve with it. | ||
I'm driven by curiosity and the desire to understand how things work. | ||
Which is excellent from the standpoint of cross-pollinating ideas. | ||
However, | ||
since I don't use them, | ||
I end up forgetting them, leading to a feeling of having wasted my time. | ||
|
||
With many developers on Mastodon and X talking about [WWDC](https://developer.apple.com/wwdc24/), | ||
I can't avoid but think: *Should I watch some of the talks?* | ||
Part of me thinks that I should because I might get ideas for problems to solve with [Tuist](https://tuist.io). | ||
But the other part of me thinks that the ideas presented in it, | ||
and which I've seen people talking about on various social networks, | ||
are enough for me to envision the problems that I could solve with Tuist. | ||
When the time to work with them comes, | ||
for example enabling complete[ strict Swift concurrency](https://www.swift.org/documentation/concurrency/) in Tuist, | ||
I can simply look up the documentation and learn what I need to know. | ||
I feel it's a more effective way of learning because it's goal-oriented. | ||
I decided to call it **lazy-learning.** | ||
|
||
So I'll try to apply this approach going forward. | ||
I'm currently diving into [Apple's Virtualization Framework](https://developer.apple.com/documentation/virtualization), | ||
[Swift Testing](https://github.com/apple/swift-testing), | ||
and [how to flip a German company to the US](https://www.orrick.com/en/Insights/2024/06/Orrick-Legal-Ninja-Series-OLNS-7-Flip-it-Right), | ||
because these are the problems I'm facing right now. | ||
|
||
And you? What's your approach to learning? | ||
|