Just finished setting up the blog. Doesn't look terrible at all; what more could I ask for? I wonder if attachments show up properly. Hopefully, it's not terribly cropped.
The pattern I chose to explore is called "Your First Language" from Chapter 2, which focuses on the importance of choosing a primary programming language and developing proficiency in it. The pattern addresses a common concern for many aspiring software developers: the fear that job opportunities and success are contingent upon mastery of multiple programming languages. However, the pattern provides reassurance by emphasizing the significance of selecting a language and becoming fluent in it. This chosen language will serve as the foundation of your early career, and investing time and effort into mastering it will yield fruitful results. I found this pattern particularly relevant to my own journey as a computer science student. Like many others, I have dabbled in multiple programming languages during my studies. However, this pattern reminded me of the importance of honing my skills in one specific language, rather than spreading myself too thin across various languages. By ...
Technical debt is a programming theory that refers to the necessary work that gets delayed during the development of a software project to meet a deadline or deliverable. It is an idea that shortcuts are taken to quickly deliver a product, but this decision incurs a "debt" that must be paid in the future when the work is eventually completed. Technical debt is often the result of a tradeoff between perfect products and the short timelines often required for product delivery. Developers may choose the easier route with messier code or design to deliver a product faster, but this can lead to technical debt that must be addressed later. Technical debt can accumulate "interest" over time, increasing the difficulty of implementing changes and leading to software entropy. It is important to manage technical debt to avoid these negative consequences. This involves identifying technical debt, accounting for nonfunctional requirements, and implementing best practices and...
I read Apprenticeship Patterns as per the syllabus and I found a lot of things that resonated deeply with me. Dave talks about giving up on learning to code, or rather to program after being unable to do anything compelling or significant, and only having had mastered Perl on his third attempt. I myself have on multiple occasions traded a language for another when I stop making progress. My thinking was – “Maybe, this isn’t the one for me”. So, I hopped from Python to JS to Scala to Java to C learning only the basics and just enough to satisfy any classes that might’ve required it. I was a jack of all trade, and master of none! Only upon revisiting Python again for a summer fellowship with a professor, and working on learning more than just the syntaxes, idiosyncrasies, and fun facts about the language, was I able to move on to being somewhat competent. Dave’s story tells us how he sought out mentors, took on challenging projects, and continuously challenged himself to improve and grow...
Comments
Post a Comment