Orestico

role

Web development

client

Orestico

recognition

year

2021-2022

Objective

Introduction:

Embarking on the dynamic journey of the Orestico project, a venture into reshaping the landscape of brand and retailer collaborations, was realized using the powerful No-Code tool (you can learn more about Nocode by reading this complete blog post written by Alegria), Bubble one of the most renowned platforms in the No-Code development realm. Stepping into this initiative, I assumed a pivotal role, joining the project as a replacement for a team member on vacation, entering the scene five months after its inception. The project team, led by a project manager, comprised three developers working collectively to bring the vision to life. At its core, the mission was to craft a sophisticated web application, facilitating seamless connections between brands and retailers. This platform empowered both parties to orchestrate impactful advertising campaigns, not only fostering partnerships but also revolutionizing the way businesses engage in promotional activities.

Creative Process

1. Revolutionizing Communication: Crafting a Feature-Rich Chat System:

In the realm of the Orestico project, my focus shifted towards the development of a messaging system akin to Slack, a feature aimed at enhancing communication between brands, retailers, and the Orestico admin through chat. This messaging functionality included the ability to selectively add members to a chat group based on their permissions. A noteworthy aspect of this endeavor was its introduction in the project's final stages, stemming from a client request amidst an already tight deadline. Originally allocated a week for this task in the rush of project completion, I took on the challenge and successfully delivered the functionality within a remarkable 48-hour timeframe, inclusive of bug corrections. This episode showcased not only my technical prowess but also my capacity to thrive under time constraints while meeting client expectations.

2.Untangling the Kanban Web: Unraveling Bugs and Finding Solutions

The Orestico project encountered a significant hurdle when a critical bug surfaced in the application's dashboard, the central hub displaying deals categorized by their status—ranging from deal drafts to setups. Some deals were not appearing in the correct status, while others seemed entirely absent. While my primary focus was on the deal setup aspect, the issue emerged in the deal-making section. Initially, the two other developers on the team attempted to address the problem collaboratively. However, after 48 hours with no resolution, I briefly examined the issue. Initially hesitant due to my perceived lack of expertise and unfamiliarity with that part of the project, I was eager to complete my own tasks. The project manager suggested a no-code review meeting, gathering all developers in the company. Unfortunately, the lack of context hindered problem identification. To gain clarity, we started building a data model, a task that proved time-consuming and impractical. In a time crunch, I proposed a 30-minute solo reflection for each team member. Armed with pen and paper, I translated the problem into an algorithmic challenge and, within 10 minutes, uncovered the solution, effectively unblocking the project. This episode underscored the value of a fresh perspective and the power of algorithmic thinking in overcoming complex challenges.

3.Navigating the Campaign Setup: Innovating Deal Management in the Kanban System

My role in the Orestico project primarily centered around the "deal setup" segment of the Kanban system—a crucial section empowering brands, retailers, and their Creative Partners to initiate and manage advertising campaigns collaboratively. In this section, a seamless workflow was established, allowing Creative Partners to share campaign posters for validation among stakeholders. For instance, a Creative Partner for a retailer might share a poster with others, triggering notifications for each recipient to validate or add comments. The validation order dynamically shifted based on the poster's originator, and validations occurred one by one, looping back to the next in line for approval. The complexity arose from this dynamic process, where the order of validation changed concerning the poster's creator, making thorough testing and assurance of flawless functionality a meticulous and time-consuming task. This intricate functionality aimed at fostering collaboration posed a unique set of challenges, demanding precision and careful validation to ensure its seamless integration into the broader Orestico project.

Conclusion

In conclusion, my journey with the Orestico project has been a testament to my capacity to thrive in challenging environments and deliver impactful results. Despite being the most recent addition to the project and having spent less than three months on the team, both the outgoing and incoming project managers entrusted me with the solo completion of the application development—a significant vote of confidence. My participation in this IT project provided invaluable insights into my technical capabilities and problem-solving acumen. Joining mid-project allowed me to tackle substantial technical challenges, implementing innovative solutions that propelled the project forward.

Recognition from my peers underscored the effectiveness of my contributions in achieving our set objectives. This experience not only deepened my technical knowledge but also fortified my software development skills, marking a significant milestone in my professional growth.