This is the introductory post for the CS-448 course of Spring 2018.
From the blog CS@Worcester – Fun in Function by funinfunction and used with permission of the author. All other rights reserved by the author.
CS-448 Capstone Blog Intro
First Blog post for the capstone!
From the blog CS@Worcester – Rookey Mistake by Shane Rookey and used with permission of the author. All other rights reserved by the author.
Apprenticeship Patterns – Chapter 1
My thoughts on the first chapter
The opening chapter of the book Apprenticeship Patterns serves as a brief introduction for what to expect throughout the rest of the book. There were a number of concepts that I am unfamiliar with and am looking forward to learning more about. I had previously heard of the terms apprentice; journeyman; and craftsman; but never I had not thought of them in the context of software development.
Once we wrap up all of these new concept applications, we arrive at the idea of the Software Craftsman. Within this moniker are suggestions on applicable mindsets that encourage pragmatism, information sharing, and surrounding oneself with those with better skills. Each of these taken individually seem obvious. But once you line then up under a single purpose, they highlight an approach to becoming an accomplished developer through community and experimentation.
Breaking down the titles
The opening chapter offers us a loose definition of the hierarchies we can expect to encounter in this book: Craftsmen (or Master), journeymen, and apprentices. But beyond these archaic titles is a value system that should be imbued on the reader. This system lays the foundation for becoming a better software developer.
The apprentice is probably what most of us in this class would classify themselves, yet this assumes a journeymen/master who is teaching us. The classroom model is our current vehicle, but soon it will branch out as we become journeymen and expand on our skill set.
The master or craftsman designation seems to be reserved for those that can and are willing to further the zeitgeist of his or her craft. These are those who reach a point that they re-examine the methods and rules of his or her craft and attempt to better the tools and means of it.
My takeaways
I am learning that there are pattern languages for just about any discipline one could imagine. I am not confident enough in mu understanding to say whether I agree or disagree with the material but am intrigued by the prospect of bettering my skill set and understanding of the development world. I am eager to dig into the material and begin to apply it to my career.
From the blog Rick W Phillips - CS@Worcester by rickwphillips and used with permission of the author. All other rights reserved by the author.
CS-448 Introductory Blog Post
Hello! This is my first blog post for CS-448. I hope everyone has an exciting and educational semester!
From the blog CS@Worcester – BenLag's Blog by benlagblog and used with permission of the author. All other rights reserved by the author.
CS-448 Introductory Blog Post
Greetings CS-448!
I am looking forward to having a wonderful experience with all of you!
From the blog CS@Worcester – Ricky Phan by Ricky Phan CS Worcester and used with permission of the author. All other rights reserved by the author.
Software Apprenticeship: Becoming More Than Proficient
Reading the first chapter of Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman by Dave Hoover and Adewale Oshineye made me feel both anxious and optimistic about entering the software development field upon graduating this spring. As the authors very clearly point out, there is now an overabundance of developers but a scarcity of good developers in the workforce. In an effort to become one of the good developers, I have in the past kept up with many of the so-called masters referenced in Apprenticeship Patterns including Uncle Bob and Martin Fowler. I hope that by following the advice of Hoover and Oshineye I am able to make begin a career where I will make a difference as a software developer, and that someday I am able to pass along my experiences to future generations in an effort to continue the advancement of the industry.
What I found perhaps most interesting and important about the first chapter were the disclaimers that the authors gave. Statements like, “These tools are not algorithms that guarantee the same results on every execution,” really helped to reinforce the idea that there is no magic recipe for success. The truth that Hoover and Oshineye are trying to convey to new developers is that being successful is not easy. The path to becoming a great developer has many hurdles, it takes more than simply following an apprenticeship pattern or any other set of instructions. What the apprenticeship patterns hope to offer, rather, is assistance in beginning a software development career and advice on how to become outstanding rather than simply proficient.
As a new developer trying to make it, motivation and drive are key. Perhaps most important, however, is a willingness to learn. Not being afraid to make mistakes, and being able to turn mistakes into learning experiences is crucial to personal and professional growth. It is also important to share your experiences with others, rather than hoarding them. Just as apprentices learn from journeymen, so too can one apprentice learn from another. This collaborative scheme was especially interesting to me. Far too often, especially as a student, I feel that individuals are selfish about sharing information with one another. While this is certainly understandable in situations where only one party benefits, collaboration can be an extremely powerful tool. I feel lucky to be entering a field that places such a high value on teamwork and collaborative success. Working together is what most often leads to the most profound or impactful discoveries and advancements.
Although the first chapter of Apprenticeship Patterns did not go into much detail on any particular subject, I am looking forward to discovering how to improve my chances of a beginning a successful and rewarding career as a software developer.
From the blog CS@Worcester – ~/GeorgeMatthew/etc by gmatthew and used with permission of the author. All other rights reserved by the author.
Intro Post for CS-448
My name is Timothy Kmiec, I am a senior at Worcester State University and this will be my blog site during Spring 2018 semester for CS-448.
From the blog CS@Worcester – Tim's Blog by nbhc24 and used with permission of the author. All other rights reserved by the author.
CS448 Test Post
CS448-02 Spring 2018 semester test blog post.
From the blog CS@Worcester – README by Matthew Foley and used with permission of the author. All other rights reserved by the author.
Introduction for CS 448
This is the blog I will be using for this course.
From the blog CS@Worcester – orscsblog by orscsblog and used with permission of the author. All other rights reserved by the author.
CS-448 Software Development Capstone
Hello everyone; this is my first blog post for the CS-448 Software Development Capstone course.
From the blog CS@Worcester – Jason Knowles by Jason Knowles and used with permission of the author. All other rights reserved by the author.