Telescope 1.8 is a significant mark for everyone active and working on the project; the microservices and the new UI are now on our production server. Which means the new Telescope is flying. And I’m so proud of every active member that contributed to the project since we started porting to NextJS.
The new UI is not 100% implemented, but it is working well.
I was reviewing a PR from Duke when I faced a JS shorthand pattern in his code that I had never seen before. I spoke with Josue, and he already knew the shorthand and pointed me…
The Telescope team has been working mainly on three points:
Telescope is going to be a totally new Telescope in the 2.0 release.
One of the features that I’ve been working on is the new design, which means that I send the drafts, and then listen to the feedback. The hardest part is when the feedback is a good one. Because knowing the project front-end code and what we would have to change in it and then looking at our schedule, sometimes it’s impossible to implement all of my colleagues' feedback.
At this point…
The new User Interface is coming.
After reading about Jaguars and architecture, I end up thinking about how the design of things that surround us affect us.
I was working on fixing a bug on Telescope’s front-end related to our component ‘ScrollToTop,’ and I thought it was a good time to improve the UI while facing the screen. We will be launching version 2.0 in a month, and I believe that is the perfect occasion to introduce our users to a new UI.
So I started digging the web for references and inspiration that could help me to start the…
Since the last time that I blogged, my mind has been in many different places and subjects.
I think I’m the kind of person who likes to talk and learn subjects not related to computer science, and that’s exactly where the journey begins.
I found an amazing project in Brazil wich the objective is to protect wildlife. https://www.jaguar.org.br/ and after watching some of their videos, I started to think more about our environment's relationship with our cities. For some reason, I start to look at the city with other eyes. …
Recap of what I’ve working on my release 0.4.
My goal is to create a slack integration app for the Telescope project.
Until now, I did not reach my goal, but I have been through all of the following:
I have been reading and coding, and my conclusion is: the more you understand something more you want to know about this…
Reflection on my NPM release and git tag.
In this lab, we should publish our URL checker on a package manager; as my program is written in NodeJs, I choose to publish on NPM. But I published it a long time ago, 21-Set-2020, when I wrote a briefly documentation about it here.
Today the project is totally different, with many new features that we have been working on in the course, and I have blogged about it.
So for this lab, I created a tag (0.9.0) using git and push it to the GitHub repository, but I decided to keep…
I’m working on the integration between Telescope and Telescope’s slack channel.
The goal is to monitor our servers, and if something is wrong with them, a message is sent to our slack channel. David Humphrey indicated to me the auto-deployment server to implement the bot.
Follow a picture to illustrate how one of the bot features should work:
So my first step was to jump into some research about how slack bots operate; it was a pretty good journey. YouTube tutorials, Slack documentation, node community articles; But Slack upgraded their bots, so what we use to call a bot now…
For Release#4, I will keep working on the Telescope project.
My idea is to contribute to the project with a slack integration. Keep our slack channel informed about the status of our servers and our GitHub repo.
I researched about slack bots and decided that it is the way to go.
So far, I have been working on the project’s front-end, and now I will give my first steps towards the backend.
I want to thank David Humphrey and Josue for all the support that makes the possibility of my release#4 on the Telescope project real.
But wait, I still will be there working on our frontend port to next.js and some issues on the front-end and reviewing PRs!
I decided that I will share what I was listening to writing each post.
Unit test, end to end test and CI.
This article uses Url Pilgrim as a case of study.
To add unit and end to end tests to a Node.js project, I choose Jest.js, a top-rated testing tool.
Before we start focusing on the tests, we must understand why we need to add tests to our program. Tests help us to keep our code maintainable and working. Because even small changes can bring giant bugs, so if we keep our tests up to date with our code, the chances of facing a bug in the future are minor than without tests.