TLDR: I'm going to learn React by writing a coin collecting app using CodeSandbox and will post an update on my progress each week.
Then, recently, whilst searching for an app which I could use to track my coin collection (yes, I collect coins!), I was struggling to find something which had all of the features I wanted; had good performance; and generally looked and felt good to use. This inspired me to finally set some time aside to start learning a framework by actually building something I (and hopefully others) would find useful — a basic, fast, coin collection tracking app which is easy to use and looks good!
My plan is to post an update on my progress each week, even if all I did that week was read some articles.
The first step is to choose a framework, this is fairly easy for me as there is one framework in particular which I have noticed has been driving some really great patterns and coding practices, offers a simple API with lots of flexibility in the ways you can build applications using it, as well as being very performant. That framework is React.
I'll be honest, I have used the framework before — mostly taking example code from blogs and playing around with it. A colleague and I also ran a few sessions of a React workshop where we walked a group of engineers through the basics of React, setting up coding exercises so that everyone got some hands-on experience using the framework. Planning those workshops involved reading a lot of blog posts and taking some online courses but a lot of that knowledge has since faded from memory.
So what I'm trying to say is that whilst I'm already familiar with the basic concepts of React, I've never put what I learned into practice. Running the workshop helped me to learn a lot, and teaching is a great way of learning, but I have a feeling that when it comes to writing some actual code I'll have that classic struggle where I realise that reading and watching videos is all good, but nothing compares to actually building something in order to really solidify that knowledge.
As I mentioned previously, I'm going to build a coin collecting app and to start with it's going to be dead simple.
That's about it. I have a few ideas of other features I'd like to add in the future but I don't want to overcomplicate things at the start and risk holding everything up, or worse; giving up because there is too much to do.
Before writing this post I read an article by Kent C. Dodds where he mentions that he used CodeSandbox to build an app for his wife. The thought of using an online editor to build an app sounded crazy to me but I tried it out for myself using their create-react-app sandbox and was really impressed! It's really fast, integrates with your GitHub account, has some great tooling added by default (prettier, ESLint), plus it will run your unit tests as you work.
Using CodeSandbox means that I can work on the project wherever I am, as long as I have an internet connection and a browser, and because of the GitHub integration there is also the option to clone the repo and develop on my laptop if I want to.
This section is here in case anyone other than myself ends up reading this!
My method of learning a new technical skill is typically not very structured, I don't tend to plan too far ahead so there will be no architecture diagrams or detailed descriptions of features I plan to implement in future posts.
My general approach is to find and read blog posts, watch training videos, and sometimes find a good book on the subject. I follow that up by writing some throwaway code which allows me to quickly try the codebase out to see if it works as I expect it to, and find out if there is any behaviour which is unexpected.
That's how I learn and it works for me — lots of failure driven development! I'm probably not really selling myself as a UI engineer very well in this section 🙈
One other thing to note is that I'll often spend a week or so either writing no code at all - perhaps reading or even spending time away from the project completely. I have a young family so it's important to me that I don't shut myself off from them, spending time with family is much more important to me than learning in my spare time.
I find that taking breaks like that allows everything I've learned so far to sink in. Often I find that if I become stuck on an issue which I can't figure out taking a step back allows my brain to recover and sometimes I'll subconsciously figure out a solution which takes minutes to implement.
So the plan for the first week looks like this:
Right, enough of my waffling, I'll post again in a week.