I suppose that I mainly see this blog as somewhere I can go to quickly get some github contribution points. But I should also really be documenting what I’ve been doing and problems I’ve run into that are worth writing down how I’ve solved.

For example, I went to an RCOS workshop about work ethic, namely about being in an AGILE based workplace. My uncle has already taught me the basics of it, but I thought I’d write it down here in my own words since breaking it down would do me a lot of good compared to just trying to remember what I’ve heard.

For one, an AGILE working strategy centers around the idea of each and every person’s ability to be flexible in the face of challenges, and a big part of that is not spending too long on any one thing. Get help, change your approach, or just do something else even. It’s better than being stuck and not communicating that you’re struggling.

Another big aspect is that since everything moves quicker under an AGILE strategy, making sure anything that you’re shipping to the dev and especially main branch works and has as little of a chance as possible to mess with what other people are doing. That means do tests, don’t change too many files at a time, and focus on what your “ticket” is.

The last big topic I want to talk about is communication. I mentioned this in the first point but it’s too important to make it a sub point so I’m also giving it its own spot. AGILE usually happens under large workforces so making sure everyone’s doing their part is crucial to getting things done as quickly as expected. Stand ups as often as once per day was a big example of this, but so is effective ticket and message writing.