I think that intention in process is very important. I like to think that I’m stoic and agile in nature, but intention is that extra piece. Not just being methodical by nature, but rather, being methodical intentionally.
“If you do things shittly, you tend to get shit out. S, h, I, t, t, l, y, it’s an adverb.” - Jeff Casimer
Only about 10% of code is actually worth while because of the shit processes of developers who’ve aggregated lots of knowledge over the years. Our perspective, our processes, what truly informs us; that will be the key that sets us apart in the workplace, not the accumulated knowledge. Like a violinist, there is always time to do code right the first time. There is no point in doing it crazily in practice. If you practice good/bad processes, then you will reproduce good/bad product. If you’ve been working on a project for 3 month, it’s not agile. If your site does not solicit user feedback, it is not agile. Agile should be accessible, and responsive. Well planned, and tested, versus extremely overly produced with no user input, and no customer in mind.
Sprint: a time box that fits into …. -typical sprint is 2 weeks -starts with planning (aka requirements) -it always takes longer than planned -cut scope or extend time? -always cut scope (half, not half-assed) -Features are delivered in production -Solicit user feedback -Ends with review/retrospective
The story that the application tells the user is subsequently the story that your code tells.
How can you move the story when the user does something so that the user then receives something as a result of their action.
4-5 overlapping stories is better than 1 long story.
“When I check this box, this happens, but if I don’t have enough letters and I check the box and then hit submit.”
Using Projects manager in Github for my personal projects and workflow.
Implementation of management tools for pairing projects.
Project management, communication of expectation, and workflow were all dramatically improved in GameTime and allowed us to strategize moving forward from our DTR.
Strengthen communication skills and styles, as well as continue to exercise patience.
Description of the role you played in your pair/group projects this module -- what was your role as a teammate? How did you utilize your strengths and leadership skills?
I was adamant about sticking to DTR while also remaining flexible. In situations where I felt the least connected and communicative, these tools weren't used. I used by strengths to seek out information, and to understand the unique circumstances associated with each human's varyied personality traits and working styles.