Skip to content

LogBook

whatevercamps edited this page Feb 23, 2021 · 8 revisions

LogBook 📓

Here I will write down every thought, every idea, every doubt that arises during the process. So... let's get started! 🤓

[60h left] Getting to know the API endpoints

I am reviewing the https://torre.bio/api/bios/$username path and find the part about your skills interesting.

First, I think this information could be displayed in a more interactive way, using D3 or something like that. I also think that, by creating an additional database (probably relational or graph-based), it would be possible to visualize the relationships between users based on this field; however, most likely this Torre already does better than I could, so I will guide my value proposition elsewhere.

I also noticed that this API returns the psychological test information in a field called professionalCultureGenomeResults, it occurs to me from this to investigate a bit about how people complement each other in a team, and thus create a system to connect (recommend) people who complement each other according to their profile both in skills -which is already obvious- and professional-cultural characteristics.

In the other route https://torre.co/api/opportunities/$id I can't find anything interesting for now. I think I'll focus on working with the first GET route of the API... we'll see if something comes to my mind in the process.

Now, in the POST routes, or at least in the first one (https://search.torre.co/opportunities/_search/), I found some very, very, interesting things. First, if I set the aggregate option to true, it returns "a summary" of the jobs -or the aggregation, to mention it would be redundant-. This would allow me to do things like "state of the art", or how is the user's work environment, in a visual and interactive way. I don't have much time, but I'm already beginning to suspect that what I'll do will be a Torre section that assists you, like a virtual Coach!

The same thing happens with the POST https://search.torre.co/people/_search/ route, I am very interested in the option to see the aggregated data, or classified, as this allows me to do many interesting things. For example, it occurs to me to make a graph -or bubble chart-, where the work environment is shown with the path /opportunities, and where the professional environment of people is also shown with the path /people.

[59.5h left] What will I do then?

I have several ideas still about what to do, so to clear my mind a bit and stay with just a couple of these ideas, I will start by trying to define in words why to do them. So, who do I want to do this for? Clearly, because I don't know roles other than my own very well, I will be doing this service for users like me: people who are looking to constantly know their status in the work environment. However, I also want to make this service meet my consultation needs in a slightly more informal way, since it is information of eventual, rapid, and constant consumption -few things are going to change in two small time spans-. And the latter is where the key lies, I think: What things have changed in my work environment for today? Uhm... Hey Siri, how's my work environment today? Okey Google... What's new to tell me?

Got it... A chatbot! I could make a smart chatbot, maybe consuming an external service because I don't have much time to build one of my own, but one that connects to services like Messenger, Whatsapp or Telegram. But, a chatbot alone is not enough, although it is a good idea. Maybe I should add something else, but I'm not sure yet. For now, I'll start defining the idea well.

[59.4h left] Design

For this particular case, being an atomic service -that only depends on itself and the third party services it consumes-, I think I'll use a classic architecture... maybe MVC, I'm not sure yet. As an interface, I think I'll use React, or Vue, to manage the state of everything in an easier way.

Regarding the design pattern, I think I'll use Material Design, although in this case I don't want to give myself too much freedom, as I'll try to be as faithful to Torre's UI as possible. We'll see.

[59.3h left] Let's get started!

As I said, the best for this service is to use a simple, but effective architecture, which can even work later in a Serverless way. I will start by building all the initial back-end, at least the base. Then I think I will have more clarity on what routes I need to create and I can move forward. I'm going to use Node, it connects very well with React or Vue, so... NodeJs it is!

[56h left] Project created, now... planing

I already have a clearer idea of what I want to do. However, I first had to organize the activities I need to do - at least the ones I have in sight. I made this little Gantt chart to have clear timelines. I must admit that everything points to the fact that time is not in my favor right now.

Activities planning
Uploaded with Imgur

[53h left] Let me sketch my ideas on paper 🥺

I had to take this one-hour break to really understand the user and what I can offer him. I made a diagram trying to empathize with the user and find the questions I want to solve.

Sketch from user empathy mapping
Uploaded with Imgur

This image allowed me to find the purpose of Torre Control: to accompany the Torre user towards his professional growth. That is to say:

  • what skills should he/she obtain?
  • what strengths should he/she improve?
  • what skills do companies need that he/she can gain?

[38h left] Arch design!

I think I finally have a clear idea of the architecture I want to use, I don't know if I will be able to finish it due to time constraints, but this is my proposal.

Sketch for Architecture
Uploaded with Imgur

[35h left] Sketch of Data...

I still don't fully understand the structure of the information obtained by the Torre API, however I made a small draft of the data aggregation to understand it better.

Sketch for data
Uploaded with Imgur

[30h left] MVC Patter!

I have already started to build my Back End service. I decided to use Node Js MVC pattern, because if I stay long enough I want to migrate the modules to a microservices architecture.

[25h left] A little pause 🤯

Alaska came to replace me while I am taking a break. I hope that while I'm gone she will find a solution to the bug.
My dog
Uploaded with Imgur

[15h left] Lets get started with interface

Well, actually I'm lying a little bit... I had already started. Here's what I'm wearing.

Interface
Uploaded with Imgur

PS: Ignore my girlfriend on the screen. We were giving each other support (it's remote work, isn't it?).

Soon I'll need some sleep 🥱

[1h left] This is the end...

Okey, sorry for not updating, but I overslept and had to run at the end. This is the final result, there is one hour left and I'm afraid to make more changes and damage something at the last moment.

[1 day after] This is not the end...

Last night, after submitting the form, I found many new emotions in me. On the one hand, I found hundreds and hundreds of things I could have improved: a navbar was missing, this color contrasts poorly, many things like that. I wanted to cry. But today, seeing the result, I felt happy, although I know that there is still a long way to go to leave things at their best. I was happy because I found a new project to do, Torre Control ❤️🛫 Some pics of work
Uploaded with Imgur

Clone this wiki locally