![[3/12] September](https://cdn.hashnode.com/res/hashnode/image/upload/v1731521471350/244bd3e2-e8d6-4d92-b5d1-05465b3151fd.jpeg?w=1600&h=840&fit=crop&crop=entropy&auto=compress,format&format=webp)
September continued to immerse me in the complexities of enterprise-scale software development and presented new challenges that stretched my technical and professional skills. This month's key takeaway was the sheer scale and intricacy of the ACC codebase. Despite having spent a considerable amount of time familiarizing myself with different areas of the app, each new component still feels novel and complex, as if I'm navigating an entirely different application. The vast nature of the codebase means every feature seems unique, revealing unfamiliar dependencies and connections. This ongoing exposure has given me a greater appreciation for how teams work across multiple domains, each contributing to a massive product that balances functionality and scalability.
Work Summary
More Complex Tickets
This month also involved tackling increasingly complex tickets, often requiring extensive troubleshooting and deeper analysis. With these more complex tickets, the gratification of quickly moving a task across the board is no longer the driving force; instead, the motivation must come from within. This shift has taught me to embrace the satisfaction that comes from sustained effort rather than immediate resolution. Working on these demanding tasks has encouraged me to be more self-driven, fostering patience and resilience as I work through intricate problems that require prolonged focus.
Asking for Help
As the tickets became more challenging, I encountered instances where I felt genuinely stuck. Overcoming this difficulty meant developing the humility to ask for help—something that may seem straightforward but is easier said than done. Admitting that I needed help, especially after being helped before on the same ticket, was an essential lesson in teamwork and personal growth. Reaching out to my more experienced colleagues and acknowledging my limitations has accelerated my learning and underscored the value of collaboration. This experience has been invaluable in resolving issues more efficiently and reinforcing the importance of building a supportive network within the team.
Technical Skills Developed
One of the most significant technical insights this month was the importance of code readability and maintainability. Working through the ACC codebase highlighted how past developers' decisions impact current processes, often dictating the complexity of even minor updates. Observing this firsthand underscored the critical need to write clean, maintainable code as these decisions ripple throughout the project.
Witnessing the effects of past choices firsthand has emphasized that efficient software development requires creating a sustainable infrastructure that can adapt over time without unnecessary obstacles. The technical debt within ACC serves as a constant reminder of the need for maintainable code and the challenges posed when development prioritizes immediate functionality over long-term adaptability.
In addition to working on code, this month provided an opportunity to present our Hackweek project. This presentation experience was rewarding and educational, allowing me to articulate our team's work to a broader audience of about fifty people across Autodesk's Construction Engineering division. Presenting our findings and discussing the project's suitability helped consolidate my understanding of the feature we built while reinforcing my ability to communicate technical information clearly and concisely. This experience was an excellent introduction to presenting technical work, and it encouraged me to develop my communication skills further for future collaborative projects and presentations.
Agile Development Is A Whole Thing
Another notable experience was participating in a B4C Agile Community of Practice session. This session focused on the intricacies of story-pointing and how it helps teams estimate work in agile settings. We discussed assigning story points to tasks in detail and balancing accuracy with efficiency to enhance sprint planning. The discussion highlighted the nuances of story-pointing, especially in large-scale projects like ACC, where complexity varies across sections. Learning how to gauge effort and difficulty in a more structured way has already proven beneficial, as it allows me to set more realistic expectations for task completion and time management. Applying these principles in our sprints has improved my approach to estimating tasks, making me more conscientious about planning and time allocation.
Internal Beta Testing
I also participated in a USEIT session, which involved beta testing new features developed by other teams within Autodesk. This hands-on experience allowed me to engage with fresh code, actively testing for unexpected behaviors and identifying potential issues in unfamiliar modules. This activity provided an enlightening perspective on quality assurance, as I could observe firsthand the unexpected ways code can interact within a complex system. Not only did I learn about different teams' development approaches, but I also appreciated the importance of rigorous testing and the need for meticulous attention to detail when integrating new features into an existing system before releasing them to a broader audience. This session was a reminder of the importance of a holistic approach to software development, ensuring that every new addition aligns seamlessly with the product.
Reflection and Growth
This month has been a period of intense growth, pushing me to adapt to technical and personal challenges. Working within such a large-scale application has tested my patience and resilience, especially with more difficult tickets where progress was slow. The shift from quick ticket resolution to sustained, in-depth problem-solving has encouraged me to find intrinsic motivation in my work, focusing on long-term development rather than immediate accomplishment. This mindset shift has been essential in balancing my expectations and maintaining motivation as I work through extended, complex tasks.
Even when it felt uncomfortable, the experience of asking for help has been transformative. The importance of admitting when I'm stuck and seeking assistance sooner rather than later is a valuable lesson I intend to carry forward. I've recognized that asking for help is not a sign of weakness but rather a strategic approach to learning, especially in a collaborative environment. This shift in perspective has positively impacted my interactions with colleagues, building stronger relationships and creating a more supportive and interconnected team culture.