Stories by Christian Marques on Medium

The ultimate hamster monitoring system

Optimal Route Crafting: Finding the shortest path on the surface of a mesh

<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tYBXmeUqmMbywv8Q"><figcaption>Fig.0 — The onboarding journey begins (Microsoft Bing Image Creator)</figcaption></figure>It’s now roughly six months since I joined Promaton as a front-end engineer working intimately with WebGL/three.js. Despite the course of time, I’m still feeling the excitement from my first weeks, which I’d love to share with you, as it has been one of the most interesting and thrilling onboarding experiences of my career.
New joiners at Promaton are usually invited to tackle an onboarding project, for about a month’s time, which is typically suggested by the team they will be working with. Generally, it is a relatively open-ended assignment.
The reasoning behind this is that new joiners can start their life at Promaton by getting familiar with the stack, technologies, processes, and team without the pressure of meddling in production code. This also provides them with more agency, ownership, and accountability for their project, on which they have to work by themselves.
My onboarding assignment was to build a prototype (or rather proof-of-concept) based on a series of hypotheses that had been determined by my team. The structure of the assignment presented the problems (mostly user experience pain points) and some of the hypotheses that had been brainstormed by the team in order to attempt and improve on these issues. From there, I was given total autonomy to consider how it would be approached. I approached it by researching the existing experience, outlining the user journeys and verifying the described pain points — which then led me to start writing detailed technical documentation, illustrating how the problem would be approached (Fig.1 &amp; 2). I was given the freedom to choose some parts of the stack and design the architecture I felt most comfortable with, and had some technical discussions with the team, helping to validate that the path forward would be a fruitful one.
<figure><img alt="" src="https://cdn-images-1.medium.com/max/775/0*qGQ4OgH8tDumlWI7"><figcaption>Fig.1 — Choosing the tech stack and solutions</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JG631u-SkI1C7jLN"><figcaption>Fig.2 — Drawing user journey diagrams</figcaption></figure>During the course of a month, I was given the opportunity, freedom and ownership to build a prototype tackling some high-impact user experience issues. This is because we believe that you need to empower people if you want them to reach high-impact goals. Without wanting to go too much into detail, we’re talking about a web application that leverages Promaton’s AI and 3D visualisations to greatly improve dental clinicians’ lives, by saving them time and effort by automating implant and restorative treatment planning and design. I also had a huge amount of support from the extended team, who very promptly were ready to brainstorm, answer questions, suggest solutions and help with various infrastructure-related hurdles.
During this time, I had the possibility and agency to build this piece of software and experiment with different technologies I had been curious about. I had the chance to decide on the technical options, and in that process also learned a lot about the business context of Promaton, but also about the products, not only the ones owned by my team but also the wider-range portfolio of products, some of which I had to integrate.
Roughly one month later, I was presenting the prototype (still quite incipient at this point, as you might imagine, Fig.4) to the broader Promaton team, who provided very constructive feedback and widely celebrated the efforts made in this journey. The first iteration was completed successfully and well received. In the middle of this journey, there was also a very fun week-long hackathon, where I completely changed the context for a full week and made a little interactive map for displaying the geolocation data of our API usage — (Fig.3)
<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hoQbzJQ1Xbp_fZtp"><figcaption>Fig.3 — Building cool stuff during hackathon amidst onboarding</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kQMjAAsXdqB8TidP"><figcaption>Fig.4 — First iteration of prototype</figcaption></figure>Little did I know that this onboarding project would turn out to be so relevant, that after this intense month, we’d continue to work on it.
We performed a series of user interviews with real clinicians, and based on that feedback, continued iterating on the prototype for the next couple of months.
At a point, it became ready (we could consider it a completed second iteration, Fig. 5) to be presented to the extended team and technology leadership of our parent company.
This led to a brief moment of nervousness for me: showcasing the prototype I had been working on in an all-hands meeting with nearly a hundred people watching.
However, this quickly dissipated as the team continued to be supportive and constantly reiterated the practical value and potential of the work that had been done.
It ended up being a successful presentation, the feedback was overwhelmingly positive.
We now continue to work on this project with greater support from our parent company and continuous positive reception, which is where we are at the moment: performing user interviews and working on a third iteration based on that feedback.
<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*a-SAwGighMvRoZbq"><figcaption>Fig.5 — Second iteration of prototype</figcaption></figure>This leads me to the end of the story per se, but I still want to reflect on this journey.
I believe it not only very well represents a lot of the Promaton values, but also constitutes an interesting onboarding experience that is rarely seen throughout our industry, as usually, engineers joining a new company are typically given menial and routine tasks to start with and get accustomed to the codebase, the processes and the team.
With this very particular format of onboarding, Promaton is successfully promoting key pillars of its (engineering) culture:
<ul>
<li>
ownership (as new joiners are expected to own their onboarding project from start to end and be accountable for it)</li>
<li>
trust (as the bulk of choices made during this time are the responsibility of the engineer)</li>
<li>
empowerment (as people are encouraged to present to leadership, discuss and challenge ideas, take the helm of the project)</li>
<li>
building things fast (prototyping and testing ideas is widely encouraged),</li>
<li>
agility (continuous iteration and rapid feedback are essential to drive the development further)</li>
<li>
involvement (as people are encouraged to participate in user interviews, be proactive with UX questions, etc)</li>
<li>
teamwork (as support and collaboration from peers and other actors within the company are encouraged and welcome)</li>
</ul>
Feeling the real impact of your work, being given the opportunity to demonstrate your value and getting overwhelming support from your peers to achieve great results: this is certainly one of the best and most exciting ways to start working in a new company.
<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SfUaiQ0Tdvw6COCa"><figcaption>Fig.6 — Reaching the onboarding summit (Microsoft Bing Image Creator)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=172df3b5b037" width="1" height="1" alt=""><hr>
<a href="https://blog.promaton.com/the-on-boarding-ascent-climbing-the-peaks-of-ownership-and-trust-172df3b5b037">The onboarding ascent: climbing the peaks of ownership and trust</a> was originally published in <a href="https://blog.promaton.com/">Promaton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

The onboarding ascent: climbing the peaks of ownership and trust

<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GuXYEW790g9EwSH04s-RJg.jpeg"><figcaption>Image from <a href="https://unsplash.com/@oriento">五玄土 ORIENTO</a></figcaption></figure>I’ve recently had a couple of experiences in the job market as a software engineer where after an entire recruitment process, the feedback just didn’t arrive, and emails weren’t replied to, which left me confused and struggling with unexpected feelings of frustration, rejection and self-worth.
In the world of job searching, it’s not uncommon for candidates to go through an entire recruitment process, only to receive no feedback and have their emails go unanswered. However, there are ways to deal with these situations and let go of negative feelings. Some have found that Eastern philosophies, particularly Zen Buddhism, offer useful philosophical lessons and approaches that can be applied to such situations, as well as many other complex, fast-moving and frustrating situations in life.
<h3>A brief context on Zen Buddhism</h3>
Zen Buddhism is a school of Buddhism that originated in China during the Tang dynasty, and later spread to other parts of East Asia, including Japan. It emphasizes the practice of meditation and mindfulness as a means of attaining enlightenment, or a state of deep awareness and understanding.
Zen Buddhism is often associated with simplicity, directness, and a focus on the present moment. Practitioners of Zen Buddhism seek to cultivate a sense of peace, clarity, and compassion in their lives, and often use meditation and other practices to help them achieve these goals.
In Zen Buddhism, there is also an emphasis on non-dualistic thinking, or the idea that there is no inherent separation between oneself and the world around them. This perspective encourages practitioners to see the interconnectedness of all things and to approach life with a sense of openness and curiosity.
Overall, Zen Buddhism is a philosophy and practice that emphasizes mindfulness, compassion, and non-attachment as a means of achieving inner peace and enlightenment. Its principles can be applied to many aspects of life, including dealing with difficult situations like being ghosted by a recruiter.
<h3>How Zen can help you deal with job market rejection</h3>
<h4>1. Practice non-attachment</h4>
Zen Buddhism emphasizes the importance of letting go of attachment to outcomes and accepting things as they are. Try to let go of any expectations you had about the recruiter getting back to you, and accept that they may not have been the right fit for you.
<h4>2. Practice mindfulness</h4>
Pay attention to your thoughts and emotions as they arise, without judgment or attachment. Observe any feelings of disappointment or frustration that come up and let them pass without clinging to them. Understand that these feelings are natural and part of being a human being, but practice and direct your non-attachment efforts towards them.
<h4>3. Focus on the present moment</h4>
Rather than dwelling on the past or worrying about the future, focus on the present moment. This can help you stay grounded and centered, and may also help you notice other opportunities that arise. Past and future are, in many cases, constructions our minds create. By immersing ourselves fully in the present moment, we cultivate a sense of awareness and clarity that transcends the limitations of time and learn to appreciate the beauty and richness of each passing moment, realizing that the present is the only moment that truly exists. Embracing the present moment allows us to live authentically and fully, unfettered by regrets or anxieties, and to discover the peace that lies within.
<h4>4. Cultivate compassion</h4>
Remember that the recruiter who ghosted you is also a human being, with their own struggles and challenges. Try to cultivate compassion for them, rather than anger or resentment. A good way to do so is to try and put yourself in their shoes and empathize with their experience. Recognize that they may be dealing with their own pressures, deadlines, or personal difficulties that led to their actions. By shifting our perspective from one of judgment to understanding, we open ourselves to a deeper sense of compassion.
<h4>5. Practice gratitude</h4>
Focus on the things in your life that you are grateful for, rather than dwelling on the disappointment of being ghosted by a recruiter. This can help you maintain a positive outlook and cultivate a sense of contentment and joy. Fortunately, the software industry is a thriving one and even if you didn’t land this particular job, there are still numerous opportunities awaiting you. Instead of fixating on the missed opportunity, redirect your attention towards gratitude for the skills and experiences you possess, as well as the potential for growth and new possibilities. By embracing gratitude, you open yourself up to a world of endless potential and cultivate a resilient spirit that can navigate through life’s challenges with grace and optimism, which definitely result in eventually landing the job you were looking forward to.
<h3>In conclusion</h3>
Being ghosted by a recruiter can be frustrating and disappointing, but it’s important to remember that it’s a common occurrence in the job search process. Essentially, being ghosted means that a recruiter you’ve been in contact with suddenly stops responding to your emails or calls, leaving you unsure about the status of your job application or the recruitment process. This can happen for a variety of reasons, such as the recruiter getting busy, the position being filled, or the company changing their hiring plans.
However, approaching the situation from a Zen Buddhism perspective can help you find peace and acceptance. Zen Buddhism emphasizes the importance of non-attachment to outcomes and accepting things as they are. To deal with being ghosted in a Zen way, you can practice non-attachment by letting go of any expectations you had about the recruiter getting back to you, and accepting that they may not have been the right fit for you. You can also practice mindfulness by paying attention to your thoughts and emotions as they arise, without judgment or attachment, and focus on the present moment rather than dwelling on the past or worrying about the future. Cultivating compassion for the recruiter who ghosted you can also help you move on in a positive way.
It’s important to remember that being ghosted by a recruiter is not a reflection of your worth or abilities. Instead, it’s a common occurrence that can happen to anyone during the job search process. While it’s understandable to feel frustrated and disappointed, taking advantage of Zen Buddhism techniques can help you find peace and acceptance, and move forward with a positive outlook, stronger than ever.
<img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=750a7465b888" width="1" height="1" alt="">

The ultimate hamster monitoring system

Optimal Route Crafting: Finding the shortest path on the surface of a mesh

The onboarding ascent: climbing the peaks of ownership and trust

Finding Peace in the Silence: A Zen Approach to Being Ghosted by a Recruiter