“Development Hell”: It’s right behind me, isn’t it?
Dun! Dun! Dun! ☀️
Welcome back. It’s summer time, and things are starting to heat up!
Specifically with this Final Major Project’s submission date coming in hot with the longer path I’ve decided to take with developing Patch Odyssey (just a vertical slice, really).
Nah!
Ideally, it’s more a hard lesson learned now than a painful setback in the future.
“Oh? What’s that? Deadline’s even closer?”, “Wow, future’s even closer than I thought!”
Alright. Let’s go to it then! We can at least go out fighting for a passing grade if it comes down to it?
Hmm…
Seems this format won’t do. It’s more technical jargon that would require multi-structured paragraphs and great technical communication to explain simply.
At this point, you might even be asking: “are these mini tasks all he has to show for his effort?”
Well, they are still part of the work that went into designing Patch Odyssey and they deserve their place somewhere. Each task especially tells its own story of planning and consistent re-iteration, but this isn’t just a story of hard work, it’s a story of results.
So let’s switch things up a bit, shall we?
Each new post on this blog would cover a series of incremental updates formatted as a list, and instead of going through each one-by-one, we’ll just explore the general feelings of the “what”’s and “why”’s that were happening at the time 👍🏾
Sounds good? Great!