Some of the examples listed when the author speaks about why they are such a good learner felt a bit forced to me. I understand that authority is being established here, but a good number of the early examples seem to be what I would expect from a successful college student who has done an internship or two (e.g. what is recursion, building reusable UI components for a large company).
I also clicked through to some of the projects to find that they were team efforts, not independent projects that the author miraculously completed due to their own precociousness alone. This felt a bit misrepresented to me, although I understand the intent was probably just to show the breadth of involvement.
All in all I was happy to read the author's advice about learning but something about the intro rubbed me the wrong way. The author clearly has had quite a good number of experiences and I'm glad they're publishing these thoughts on those experiences. I just wonder if the post could do without the early hints of (forgive me) vaingloriousness? It felt quite academic and intriguing past the intro for me.
As the author may see this: please don't take this as anything other than a single individual's thoughts. I mean in no way to discourage you.
OP here, great point civicsquid. I got that feedback a lot from people (i.e. spending too much time on the post trying to establish credentials) and that I overdid it.
The point of this post for me is start trying to write (I think I'm pretty bad at it) so I'm extremely thankful for the feedback and glad you found the content itself academic and intriguing. :)
If you are in industry and you've some experience, highly likely you are already doing what the author claims to be his fast learning secrets. There are actually no deep secrets I find in his post, all of those things atleast I instictively do. Even my friends use same approach, so I thought it's so common that I don't have to write a blog post about it.
Maybe the technique in this post is common, but I personally believe that putting yourself and your thoughts out there is a good thing for engineers and critical thinkers in general. It allows us to get feedback and involve others on a wider scale, even if that means writing about things that have been discussed or thought about a number of times before.
I also clicked through to some of the projects to find that they were team efforts, not independent projects that the author miraculously completed due to their own precociousness alone. This felt a bit misrepresented to me, although I understand the intent was probably just to show the breadth of involvement.
All in all I was happy to read the author's advice about learning but something about the intro rubbed me the wrong way. The author clearly has had quite a good number of experiences and I'm glad they're publishing these thoughts on those experiences. I just wonder if the post could do without the early hints of (forgive me) vaingloriousness? It felt quite academic and intriguing past the intro for me.
As the author may see this: please don't take this as anything other than a single individual's thoughts. I mean in no way to discourage you.