I don't know C#
I decided to jump into a Twitter thread being a little facetious.
I 've been using C# for a number of years, within the very first year of my first contract. Initially, I used it sparingly for tasks that were outside of what I could do with C. C is the language I was actually hired for. It would have been between C and Java since those were the languages I had experience with from my courses at The University of the West Indies. Eventually, I started using C# more and more for internal tools and client tools written using Windows Forms, and supporting the company's client portal which was written using ASP.NET WebForms.
Subsequent jobs, beginning in December 2013 required C# as the primary programming language. The impetus which triggered that first job change brought on a spiral that impacted my performance and confidence in my skills in cycles.
One manager told me I was a journeyman, though he may have had a different opinion had he met me at a different time. It was meant as a compliment on my skills, but indicating that there were areas I needed to improve on. He recommended a few books, but the primary ones were Clean Code, Clean Coder, and Design Patterns. I started the first two but distractions got the best of me. The aforementioned cycles culminated with an extended break.
I decided to participate in Advent of Code 2019. This was after taking on the #100DaysOfCode challenge where I committed to writing at least 1 hour of code per day for 100 Days. I spent the first 26 days or so on freeCodeCamp, going through every single learning level. I skipped some of the Responsive Web Design projects to get through the JavaScript Algorithms and Data Structures Certification. I'll dedicate another post to my FCC progress.
For Advent of Code, I decided to use C# with Visual Studio Code. I'd also been using C# for leetcode puzzles. For previous competitions, I used Python, even though I've never really dived into learning the language properly. It was just easy to implement what I needed with the rich packages and simple integration with contest platforms. Fewer possibilities of "But it works on my machine".
Then came https://blog.dalevross.com/2019/12/advent-of-code-2017-day-7-yikes.html. I couldn't figure out how why my solution wasn't working so I first requested help on Reddit. That failed to bear fruit so a few days later Eric Wastl, the creator of Advent Of Code, shared my request on Twitter. I got a few offers to help, but this is what I desperately needed to hear.
After viewing their code, it was clear that I needed to improve.
So in essence, while I know SOME C#, enough to be paid handsomely, I don't know or practice enough to comfortably call myself a Senior C# developer, though I used it regularly spanning 11 years, prior to the break.
That's why I dedicated this morning to this blog post instead of diving right into Day 14 of Advent of Code. I intend to migrate to Visual Studio from VS Code, to get a richer and up to date development experience by default for C# development. VS Code will still be my go-to for scripting, and websites.
C#— Dale Vivian Ross (@dalevross) December 10, 2019
I 've been using C# for a number of years, within the very first year of my first contract. Initially, I used it sparingly for tasks that were outside of what I could do with C. C is the language I was actually hired for. It would have been between C and Java since those were the languages I had experience with from my courses at The University of the West Indies. Eventually, I started using C# more and more for internal tools and client tools written using Windows Forms, and supporting the company's client portal which was written using ASP.NET WebForms.
Subsequent jobs, beginning in December 2013 required C# as the primary programming language. The impetus which triggered that first job change brought on a spiral that impacted my performance and confidence in my skills in cycles.
One manager told me I was a journeyman, though he may have had a different opinion had he met me at a different time. It was meant as a compliment on my skills, but indicating that there were areas I needed to improve on. He recommended a few books, but the primary ones were Clean Code, Clean Coder, and Design Patterns. I started the first two but distractions got the best of me. The aforementioned cycles culminated with an extended break.
Work Experience
Work Experience
- Independent Software Contractor, Self EmployedDec 02, 2019 - PresentJoined an undisclosed company as an independent contractor for a payroll management product
- Time off, Took some time to healJanuary 07, 2017 - December 01, 2019
- Application Developer, Zero ChaosJan, 2016 - Jan, 201711 monthsStarted as a member of the Implementations Development team responsible for developing custom integrations for new clients being imported and eventually migrated to primary Integrations developer (internal)
For Advent of Code, I decided to use C# with Visual Studio Code. I'd also been using C# for leetcode puzzles. For previous competitions, I used Python, even though I've never really dived into learning the language properly. It was just easy to implement what I needed with the rich packages and simple integration with contest platforms. Fewer possibilities of "But it works on my machine".
Then came https://blog.dalevross.com/2019/12/advent-of-code-2017-day-7-yikes.html. I couldn't figure out how why my solution wasn't working so I first requested help on Reddit. That failed to bear fruit so a few days later Eric Wastl, the creator of Advent Of Code, shared my request on Twitter. I got a few offers to help, but this is what I desperately needed to hear.
Now, I'd known my code was far from clean (See Code Smells from Jeff Atwood), much farther than normal, but I initially hoped to struggle along by myself without anyone seeing the mess and worry about refactoring (if necessary), later. David shared a port of his TypeScript solution and another good samaritan shared his C# solution as well.Alright a few hints -— David Whitney (@david_whitney) December 12, 2019
- This is hard to debug as you've got everything in one big blob of static state - makes debugging the instructions tricky - try taking your processing logic and putting it in a class with it's own List of ints.
If it helps, I'm using C# and either tdd or just command line for #AdventOfCode. Code is here: https://t.co/qRIXX6iqa9— András Velvárt (@vbandi) December 12, 2019
After viewing their code, it was clear that I needed to improve.
- I know how to get things done, but if I planned to troubleshoot or share any code I should first make it easy to understand. The C# Language Specification provides many options to ensure your code is SOLID.
- Writing testable code should never be an afterthought and I have for far too long treated it as such.
So in essence, while I know SOME C#, enough to be paid handsomely, I don't know or practice enough to comfortably call myself a Senior C# developer, though I used it regularly spanning 11 years, prior to the break.
That's why I dedicated this morning to this blog post instead of diving right into Day 14 of Advent of Code. I intend to migrate to Visual Studio from VS Code, to get a richer and up to date development experience by default for C# development. VS Code will still be my go-to for scripting, and websites.
The blog title's inspiration came from You don't know JS. So, in the spirit of knowing C#, I'll be using this resource serendipitously shared by Scott Hanselman while I was crafting this post."Space Stoichiometry" - Day 14 - Advent of Code 2019 https://t.co/DaaTmYBoGN #AdventOfCode Putting down #VSCode, taking up Visual Studio, Writing a blog post about the why and will worry about the leaderboard in 2020 after a few @leetcode contests. #100DaysOfCode #Day40— Dale Vivian Ross (@dalevross) December 14, 2019
— Scott Hanselman (@shanselman) December 14, 2019This will be similar to my approach with freeCodeCamp where no stone will be left unturned this time around. I'll try to improve the readability score for the next draft, and subsequent posts.