How to learn hard things in tech
technicallychallenged.substack.com
How to learn hard things in tech
1–10 of 39 posts
Re: How to learn hard things in tech
#2No post body was provided.
Re: How to learn hard things in tech
#3>Start with the smallest working example —it doesn’t matter where this comes from, it could be a website, blog, the documentation for the technology, a friend or coworker, it could be from anywhere. This is your basic working example. It’s the baseline for building further knowledge.
This is the main idea behind over 400+ micro samples I created for ASP.NET Core https://github.com/dodyg/practical-aspnetcore
Re: How to learn hard things in tech
#4IME the hard thing is not something that there's accessible examples for. If there's a tutorial or an example project, you'll figure it out eventually.
The thing that's hard is something like how to make a project maintainable. You have to have the experience of screwing it up over a long period of time, feeling the pain each time there's a bug to find or a new feature to implement. You won't find a tutorial in how to do this, because the pain is a necessity to learning.
Re: How to learn hard things in tech
#5IME the hard thing is not something that there's accessible examples for. If there's a tutorial or an example project, you'll figure it out eventually. The thing that's hard is something like how to make a project maintainable. You have to have the experience of screwing it up over a long period of time, feeling the pain each time there's a bug to find or a new feature to implement. You won't find a tutorial in how t…
Can’t agree more! It was until I started my first full time job when I realized how ugly and disorganized my code was… I stopped maintaining one app of mine which I really like and still take pride in only because the codebase was a disaster…
Re: How to learn hard things in tech
#6I can only second learning from documentation rather than using (video) tutorials or blog posts.
If you're strong in reading and gaining knowledge from documentation, you will generally be able to decrease your time to create working solutions. The reason is that you get faster in finding the information you need and become independent of the availability of explanations by other developers.
I'd only consult other explanations if the documentation is poorly written or my way of using the software is uncommon and I'm looking for opinions or alternative solutions.
Re: How to learn hard things in tech
#7[deleted]
Re: How to learn hard things in tech
#8Love the link to https://slowlearnerclub.com/. I'm definitely in the club.
Re: How to learn hard things in tech
#9IME the hard thing is not something that there's accessible examples for. If there's a tutorial or an example project, you'll figure it out eventually. The thing that's hard is something like how to make a project maintainable. You have to have the experience of screwing it up over a long period of time, feeling the pain each time there's a bug to find or a new feature to implement. You won't find a tutorial in how t…
Yes, learning what syntax you need to write to make something execute is knowledge. When to use that approach is wisdom.
My biggest challenge is recognising that, having learned a particular approach, it doesn't need applying everywhere. For example, just because I know how to configure Kubernetes, it doesn't mean I need to host every application with Kubernetes.
Re: How to learn hard things in tech
#10Is anyone learning by not doing a variation of this?