I have been really enjoying completing these tutorials and projects, I have written about over these 8 posts. The posts have also acted as a way for me to look back and reflect over what I have done and been learning. Even if I don’t get to use all of what I have learned at work or in a project. I would also like to take this time to thank everyone that has stopped by to read these posts and who have took the time to like, share and comment.
An extra thing I learnt this week from a co-worker, that I wanted to mention. Was that you can add code inside of breakpoints in the Google developer console. Simply place your breakpoints and then click edit to bring up a window that lets you add your code. It’s helpful when you want to only debug a line if it matches a certain name or ID for instance (this was my exact use case).
For C# this week I decided to have a look at my list of tutorials and go over somethings I have used in the past but don’t necessarily have a lot of experience with. The tutorial I started with covered basic exception handling using try catch blocks. I have used try catch blocks before but as much as it may hurt some people to hear, I never use error handling in my code. It is something I know that is really import and something I want to do, hence why I complete this tutorial.
Next I worked through a tutorial covering how to use dictionaries in C#. I have worked with dictionaries before, but they have always been added in by someone else or a library I am using. This was why I wanted to get some practice in with them and I am guessing with my new job they could come in handy. Finishing up this weeks C#, I worked through a tutorial showing how to use LINQ to select distinct objects. Just like dictionaries, I have used LINQ before but have never dived into it in much detail. The tutorial is short and straight to the point which I liked but if you are like me and have not had much experience with LINQ. You may be better of looking for a different/easier tutorial to practice with.
As I mentioned last week, my goal for this week would be to create a calculator using React. As you might have guessed from the GIF below, I manged to create it. Following on from what I made last week and the tutorials I did, it was a very straight forward thing to make. I definitely agree that using components in React does help speed up the development process.
The calculator itself is built up of just three components, the display, the number and operator buttons and the clear button. Then I used some div’s to help format and style the overall layout of the calculator. One thing I did do was use CSS a lot more compared to my other projects, as I haven’t used it much with React and wanted the experience before taking on other projects.
If you are wondering where I am getting the inspiration for the React projects, I would suggest you check out Dave Ceddia‘s, Learn the Basics of React in 5 Days newsletter. He will send you React tutorials for 5 days via email and at the end of it, you will receive resources to help you get started and creating things with React.
This week with our CoreWiki project, Jeff invited developer Jon Skeet on to help with handling date times in the project. Some of you may know Jon as the author of C# in Depth. The stream lasted for nearly 2 hours and was full of coding and explanations of date times in programming, which was very appreciated. I also experienced using NodaTime, which is an API Jon created to help make working with date times. The API wasn’t used much but from Jon’s description of the API and its website I can see why using it would be useful.