C# Part 2: Projected Fails As a List

A self-evaluation of C# Part 2 at NWTC Fall 2024 semester. I had dreaded this course and OOP Programming in general as an expertise or specialty (which I want to commit to, by the way) due to the learning phase of it. Learning phases of something you want are confusing - you don't dread it; you are in a foundational mentality that lively hosts for how much you lack in comparison.

C# Part 2: Projected Fails

• Teamwork tasks incomplete, incomprehensible, undirected
• Resource gathering speed was not fast enough
• Internal built-in feature list is null
• Prioritizing schedule and time management

Pros : Projected Fails (Yes.. like a class. We are defining the positive outcomes with the projected fails list to offset and include how I somehow made up for it!)

• I was able to follow a template of instructional documentation (which I also suffer with writing, instructionally, since my first class back into college from my Social Science degree in 2013. I just got done with an IT Documentation course and was following this structure. However, the details entailed within the actual programming of a game, was nothing like an agile framework. Agile framework is the coordination of team environments to collaborate effectively for that time management. The actual task you commit to is entirely different structuring in the program - paying attention to this part was being more involved. I understood what was happening up to a point and once you lose track of the even further details in those processes of planning the program, the more difficult it is to maintain your developer role. 
• Spend the extra time researching C# tools, built-in features, and other relevant articles outside of documentation to reveal new coding hacks, tricks, tips. It's worth taking a dabble in. I would often get distracted, interested, and that information was useless because I wasn't using it. Take the time to find where that will be useful and place it there for you to review and use at that time. 
• Developing the perfect questions. Before you can do this, you are resolving with solutions to put a tangible essence with the code for the program to operate as it should. This part, I shadowed my teammates as they talked through their processes. It helped me envision how they were solving a bug, logic, or invoke method crises. Don't be afraid to let the group know you are falling behind in making sense of what to do next. Don't worry too much about how to get your code to work from theirs, at this point. Do the code. Share. Then everyone can figure out how to instill your code into the project together. 

Team project #1 with 4 members was tough with GitHub as a first-time user of it. My files would be unfound, too many changes without maintaining a push/pull commit flow for only making minor changes or reading code or outlining something minimal as an undone forced commit. I did ruin the project towards the end but was able to fix it though! 

It was rough, I don't know how they did it. But it was a good learning experience for me. I truly enjoy learning in this program and want to continue to improve. Making notes of this now will help me recollect my future progress to recall how to help the next person in their beginning steps. 

Yaw^!

__Mischief

Just do it.

The only way to know, is to do it!

Going into my C# Part 2 course and IT Training this term, coming from A results in my first half with ASP.NET working with MVC techniques and IT Documentation. I will be in a team environment with my C# Part 2 doing a game project with specific tasks each week. In the other course I will be doing presentations and training engagements to critique our group assemblage events as a host/presenter. All of this is relevant for learning in the Software Developer Program at NWTC. 

I began reading more documentation and relying more of my comprehension and study "tone" to have the documentation perspective, rather another blog or social media article that is characterized for fun, sales pitch, or otherwise positivity in general. Another tip for what to do or what to think like when doing a study session - is important. It helps you absorb the content, remember it, and adjust to your space as that learning environment. Teaching yourself to iterate within your own context or guidelines helps bridge later updates in terminology, change in software documentation style/deliverance, or anything that you disagree with personally (you can correct this yourself to accept - bypassing the dissonance cognitive effects that may or may not happen).

Before you do it, talk to someone that has been through it (learning how to code, going into IT, building a career) and what advices they have or would change in their understanding of the material. At best, most guidance will suggest to just immerse yourself and adjust as you can. The majority of subjects that you can excel in academically is easy money but for how many others like you? Looking at the statistics, what will be needed, and the AI competitive edge for learning skills and who isn't needed in the company later provide us with what should be learned today. 

I write this blog for readers who are interested, brand new, or in any point in their career can remember that there are many underrepresented minorities out there trying to understand from an entirely different mindset. I want you to know the types of questions I have about what I am learning and to maintain transparency for the pioneerism involved where in comparison to other categories is about 1% representation. We are coming from a different value system (remarkably) and teaching methods (generational adjustments). One of the ethno-study objectives I have learned with my first associates degree in social science is that the cultural exchange is not done yet. Now that we have transitioned into an American culture of technology, the intake of world philosophies templates are available and we are just beginning to study and compare with our own perspectives. 

For all the Natives who ever wanted to bring purpose to cultural revitalization whom are interested in doing the interpretation in comparison, with our own scope, and without any other intention than each of their own re-learning a tone in their touch to the stars. We may not have it that way, so we have to converge as one without interfering with personal guidance in public parameters. The influence is plentiful and without the time or audacity to create the scope itself to measure up with. 

Don't be afraid to be who you are and what you believe in. 

Just do it. Probably the best quote for action impediment. 

__Mischief 

Writing with acrylic fingernail clicks on the keyboard...

 Technical Writing 101: A Real World Guide to Planning and Writing Technical Content

3rd Edition covers Web 2.0 and DITA

by Alan S. Pringle and Sarah S. O'Keefe

Copyright 2000-2009 Scriptorium Publishing Services, Inc.

I intend to reference this for technical writing later but found some of these snippets interesting, informative, or otherwise useful knowledge. These are snippets from the above mentioned reference and within the text, it provides obsolete information or writing processes that is explained on the website from the publisher. This is such a good read (so difficult to make relatable/daily conversational vocabulary work in a technological document), I highly recommend for the budding IT enthusiast!

What I found in the pdf:

This last tidbit of advice has me at an advantageous point if this practice isn't configured into a programming style of doing documentation now. With placeholders, HTML, ASP.NET, and other tools for web developers, why can't this be programmed? We have the same data but need to update/maintain its integrity... can this not be planned?

Or is this a new type of IT Documentation in the future?

Note: Hence the title, there was much cut and paste action in this post!

_Mischief

JavaScript Just Started....

 JavaScript has been feared up until this point. 

Now imagine, running into script jots of javaScript in other programming commodity bags of goodies to allow features to help you shine beyond others and not understand what this snippet of code is actually doing. 

Now, the web browser tools, development tools in Inspect totally make sense! I have been waiting for this moment to understand how to be effective with reviewing websites and maintaining the websites I do have under the rug - and enjoy the start of this course so far. 

I am in a client-side scripting course with NWTC. I have been struggling with so many medical issues as of recently that getting the mentality and volition to do the work has been the most difficult thing I have ever done! I have done some extreme tasks in good and bad opportunities by just wanting the experience of how to maintain my life that going through these last couple of weeks has brought me to a point that I know I have to not take any Summer courses that affect my cumulative GPA. 

Remember to only take courses that you know you can pass, are ready for, and can commit to. That Cumulative GPA is so important for funding and program requirements!!

So, JavaScript is essentially like other programming languages because they are intended to work together. However, using JavaScript you are able to overwrite with authority what is revealed or used in certain code blocks that help with update and maintaining the website (for example). A couple of things I enjoyed were the resources provided in class - using MDN (Mozilla Developer Network) documentation. I very much enjoyed this part because I wanted to get into a course with documentation writing, a technical writing for computer programs and software to post online for any body to peruse and use with example and user-friendly language. The professional point about it, is if I am going to be a software developer, I need to know how to write this and that includes goals in patent writing which includes over 50 pages of code, which I want to include documentation writing. 

Other things I enjoyed so far (only two weeks into this course so far), is the material for it has gotten much improved. Color coding and the thinking on paper has improved. Big text, little text separations help us visually separate the concepts, tools, code and remember it. I would listen to podcasts anticipating and dreading this course about how difficult and undesirable it was - but how many people use it on the web! I timidly opened my book and so much relief brushed over me to see that it is a modern, hipster, book that I can carry in my purse and easily navigate the chapters. 

                                                                                                            Co-Pilot Generated Image. 2024.

JavaScript & JQuery

interactive front-end web development

by Jon Duckett

__Mischief