The SARS-CoV-2 outbreak forces many companies to jump into the new reality when many (if not all) employees are working from home. The remote work movement was not invented just today. But this is the first time in the history of mankind, when such a new and radical concept would be adopted by thousands of companies around the globe in a matter of months, if not weeks. When everybody works from home and your office is empty, you have no other option, but to adapt quickly. Conventionally, software development companies are more agile than traditional ones. They can react faster in a constantly changing environment. But still, for many tech businesses that would be groundbreaking changes.
Everyone knows that storing and structuring documentation of any software project could be tedious. One should invest a lot of effort to keep a team’s knowledge-base in good shape. Having that in mind, Nots team analyzed our experience, and from the day one we made several handy ways to access the right doc: from code in a file through the directory structure; in a commit list for these types of docs; via “my notes” list, or with a help of bookmarks. But still, Nots lacked a high-level tool for shaping up documentation structure. And today, we’re excited to introduce an elegant instrument to solve this issue — Tags.
This year Lviv ITArena 2019 organizers kindly invited to participate in the startup competition. For us, this was challenging, jittery but also exciting and wising up. Here are some lessons we learned from visiting this awesome event and from taking part in ITArena pitch competition.
Oftentimes software development teams prefer to store their documentation in various online systems and knowledge bases. But this way lack of linking this information with the source code. To make more suitable for such use cases, we’re introducing our integration with Google Drive.
Now that you know how to add quick memos on, it’s time to get more from these notes you’re adding. We made them suitable for any kind of developers’ workflow: they could be just a short piece of text with a note to future self. Or an even bigger piece of well-formatted text for making specs and RFCs.
Once the project created, it’s now time to start adding documentation. As we mentioned in the previous posts, the major idea of Nots is to tie your docs to the source code. To make it easy to discover documentation from what every developer operate on an everyday basis — from the source code. Here’s how you can do it.
In terms of Nots, a single piece of knowledge, that added to the system, is represented as a note. A note could be a short text message, like a yellow sticky note on a whiteboard. Or a bigger article with rich-formatted text, links, attached images, and PDFs. Here’s a brief overview of the notion of notes.
Project is the central concept of Nots. This is the place where all the work happen. In this detailed guide we show you how to set up your first project, what options do you have and how to invite your teammates right away.
Some time ago our team quietly launched the beta of Here are a brief introduction and our motivation for doing this project.
The core of is built on top of Elixir Phoenix framework. It’s stable, well designed, modern, pretty extensible with lots of great libs for essential web development needs. The production version of it is all about handling HTTP/1.1 requests. But it turns out it’s surprisingly easy to add HTTP/2 support into existing Phoenix application. This is a post in “Less is more” series on little nifty tech things which pop up while we’re working on Nots.
Yeah, it’s been a while since last blog post. Building startup and a company take waaay more time than it was initially planned. This year and a half were full of wins and losses. In this blog, I’m gonna cover most interesting stuff happened to me and team during this period. But first, let me step back and look at a larger picture, and show what drove me to the idea of building Nots.
Hey everyone, welcome to My name is Point and I'm doing various software engineering stuff for more than a decade now. For a past few months, I had a free time to think about what is the most annoying thing that happens in my programmer's day-to-day life and what could make me be more productive. And my hunch is that I know the answer.
load more