Thanks for checking out my first blog post on my journey into tech! I'm aiming to do one of these each week as a retrospective, to see how far I've come! 🏃🏻♂️
Consider following me on GitHub and Twitter.
I went to University and did my degree in Design Engineering, which is just Industrial/Product Design with a different name slapped on it. For just over a year I worked as a Technical Designer for a prop and set design company.
A little bit of Python
A little HTML and CSS from a while back
That I enjoyed learning about what makes the tech I use work, and honestly I think this is the most important pre-requisite rather than any knowledge/experience.
Here's a list of some of the things I've learnt and links to resources I've found useful!
On freeCodeCamp I've gone through everything from comments and variables through to loops and recursion.
LOTS of ES6 content, from let and const variables through to Promises.
Manipulating Arrays and Objects! Great fun 🥳
console.log() is now my most typed phrase — and I love it — it's such a valuable tool for understanding what is happening at any point in my code.
The best advice from this course is to stop using Finder for searching through your docs, use your Terminal! I now use mine for as much as possible, and it's taken a lot of the fear out of the mysterious black box.
Very daft video series and really enjoyable, if you have a GitHub and haven't got a clue where to start, why not with a rainbow poems 😂
Here's a couple of extensions and themes that I've been enjoying so far, if you know some good extensions let me know!
Such a great way to warm up in a morning or to try out some theory work that I just covered. Highly recommend for anyone starting out, it's a great way to put your skills to work!
Grasping processes that happen in the background, especially the processes that compound and have no observable steps.
As an example, mapping over an array rather than creating a for loop.
The reason why length() doesn't work. (MDN says it best)
If after trying and trying again to get a solution to work I start to feel like there's a better way. And there usually is.
The path of least resistance isn't about cutting corners but is about working smart not hard.
This means thinking about the problem logically rather than rationally, i.e. not always needing to split a string down to an array, or not always needing to create a for loop.
Got stuck in Vim?
Not defining where I am in my tech journey based on where others are. 💜
Learning, it's great fun to grasp something new and there's so much more to come!
Ternary operators and syntactic sugar in ES6
Template literals chef's kiss