Sachot

Creative Process

‍

1. Mastering the No-Code Landscape with UDO:

In the dynamic realm of Sachot, UDo emerged as a pivotal force, a no-code tool designed by French innovators. Beyond the traditional coding complexities, UDo's unique workflows, represented as puzzle-like structures, empowered our team to navigate both front-end and back-end intricacies with ease. UDo proved to be more than just a no-code tool; it became a database dynamo, offering an intuitive interface to craft SQL queries.

Yet, even with its advantages, UDo posed a unique challenge in the realm of maintenance. With a small team of four, addressing bug fixes and improvement requests proved time-consuming, introducing an element of instability to the tool.

‍

2. Front-end and Back-end Integration:

In the front-end aspect of the Sachot project, my role involved the integration of designs created with InVision. The ERP comprised numerous tables within each module, streamlining the integration process as I could leverage and modify existing implementations, saving time and avoiding starting from scratch. Utilizing the UDo tool, I employed drag-and-drop functionalities for graphical elements like text, blocks, and buttons. On the back-end, UDo allowed the creation of interconnected blocks using arrows. Backend workflows could be triggered by various events, such as button clicks or page loading, providing flexibility in crafting responsive and dynamic functionalities according to our project requirements.

‍

3. Taming the Data Behemoth: SQL Query Challenges:

In handling SQL queries for the Sachot project, my entry into the initiative, approximately six months after its initiation, involved dealing with pre-existing extensive SQL queries that often required modifications. The primary challenge was deciphering these queries and pinpointing the exact locations for necessary adjustments, compounded by the absence of comprehensive technical documentation. Despite these hurdles, creating new queries became a smoother task, and to enhance future collaboration, I made a conscious effort to include ample comments within the queries. This practice aimed at easing the understanding of the queries for potential team members who might follow in my footsteps.

‍

4. Navigating Complexity: Designing Advanced Filtering and Sorting Systems:

In tackling one of the most formidable technical challenges of the Sachot project, I delved into the implementation of a filtering system. As previously mentioned, the project consisted primarily of tables, with each module featuring at least two. The objective was to empower ERP users to apply diverse filters to these tables, enhancing the search functionality. While the initial filtering system had been set up by one of the creators of the UDo tool, its complexity was a barrier for the Sachot project team. Despite being the most recent addition to the project at that time (having only spent a month on it), I took on the responsibility. In a brief 10-minute call with one of the UDo founders, I gathered essential information. Despite the time constraint, I managed to grasp the intricacies of the system within 24 hours. This effort led me to assume the role of tech lead on the project. In instances of challenges or roadblocks faced by team members, I became the go-to person, offering support and even facilitating onboarding for new members joining the project.

‍

5. Temporal Evolution: Overcoming Time Management Challenges:

The journey was marked by a dynamic interplay of three different project managers and a development team undergoing frequent changes. This flux was attributed to the fact that Sachot was the inaugural project for Alegria. The absence of established processes and the inherent complexity of the project necessitated a learning curve for both the team and the evolving project managers. After eight months, a semblance of stability emerged with a more consistent team structure. However, the project already faced a two-month delay, prompting us to accelerate efforts to deliver a stable V1 to the client. This narrative encapsulates the challenges and adaptations inherent in steering a complex project toward stability amid organizational learning and evolving team dynamics.

‍

‍

Conclusion

The Sachot project stands as a testament to my unwavering commitment to my craft and my fervor for software development. As a junior member on this groundbreaking venture, I approached each challenge with a positive mindset and an unyielding determination to succeed.

Navigating through crises during the project became pivotal tests of my skills. Confronted with intricate technical issues and tight deadlines, I maintained composure and devised effective solutions. My ability to swiftly and efficiently address these challenges became a valuable asset for the team.

Beyond problem-solving, I showcased my capacity for collaborative teamwork. Working closely with my colleagues, I openly shared ideas and knowledge to collectively achieve our shared objectives. This open and collaborative approach not only strengthened working relationships but also fostered an environment conducive to innovation and creativity. The Sachot project was not merely a technological endeavor; it was a journey that revealed my resilience, problem-solving prowess, and collaborative spirit in the dynamic world of software development.