With Bytebase, you can jump into a meeting note in one keystroke and set yourself up for success later.
It’s been a lot of zoom meetings this past year and the way teams have adapted and thrived has been inspiring. But there’s a piece of the puzzle that just isn’t working that well. Zoom meeting notes.
When a zoom meeting starts, you need to start writing immediately. You grab whatever is most handy — a paper notebook, Apple Notes, a plain text file on your computer — and just start writing.
Three months ago, we decided to pivot.
We had set out to build a modern version of a wiki to help engineers share knowledge better. But after some time, we realized that we weren’t serving our users’ real workflows. We were building for an idyllic version of knowledge sharing that no one really followed.
So we decided to do some more user research. We discovered something fascinating. While engineers didn’t post to wikis as often as we wanted to believe, they write tons of private notes.
Engineers start by jotting things down in Apple Notes (or similar). Then they often…
According to legend, Thomas Holley invented the first legal pad in 1888.
At the time, he was working at a paper mill in Massachusetts. He had the idea to stitch together the leftover paper and sell it as a cheaper notepad.
Holley then went off to start a business making these substandard pads. And the legal pad was born. The first pads Holley sold were actually white. And no one is sure why it became yellow. One theory is that it was difficult to bleach the substandard paper. And it was easier to make the pads darker instead. …
We started Bytebase with the belief that the note-taking systems we rely on are too formal. When it comes to writing notes, the first order of business is to just get it down.
Too often, friction gets in the way of jotting notes down. Obstacles might come from the shortcomings of our note-taking tool, or from the rules of the note-taking methodology we’re trying to adhere to. Each obstacle makes it a little less likely that we write something down that we’ll wish we had later.
It is tempting to imagine what an optimal practice might look like, whether it’s…
When we look to people we admire, we can recognize that they probably didn’t start this way. They had a base skillset and way of being, bu then they worked hard and adopted a can-do attitude to become who they are today.
The new Michael Jordan documentary is a great reminder of this.
Michael Jordan is widely thought to be the greatest basketball player of all time. Watching the documentary, you can see that he became great because he believed in himself. He dedicated himself to improving his game, on and off the court. …
As engineers, we write and commit code every day. Each line of code we introduce is just one small piece of a software system that’s likely to outlast the specific code we’re committing. Our goal isn’t only to ship the code today but to prepare the team to successfully add to and maintain the software system in the future.
Preparing the team for the future means making our code easy to understand by following best practices like descriptive variable names and encapsulating complexity. …
Many of us have, at one time or another, blindly followed a pattern we noticed, thinking that must be the way to do it. We do so without questioning if that pattern is the best fit for our particular situation or if that pattern was ever a good idea to begin with.
In doing this, we rob ourselves of the opportunity to learn and deepen our understanding, to be intentional with our work, and, ultimately, to get better at our craft. …
A common frustration with software engineering docs is that they feel like a waste of time because they often go unused.
But there are certain pieces of knowledge that are useful and actionable to your teammates and to your future self.
Actionable docs include:
- Code commands
- Post Mortems
After talking to dozens of engineering teams, we’ve found these four strategies help engineers write actionable docs that people actually use.
Standardized templates make it easy for engineers on one team to dive into the work of engineers on another team. Without a standardized template, each…
Startups that have an effective Pull Request (PR) process can ship features faster and with higher-quality code.
The key to an effective PR process for startups is to keep items small and decide on a lightweight guideline for describing what the PR introduces.
Here we’ll go over what we’ve found works best at Bytebase.
Short PRs lead to higher quality code because short PRs are easier to review. Instead of skimming through endless diffs, a reviewer is able to more thoroughly review a small change, making it more likely that any potential issues are identified.
Short PRs also lead to…
Part One covered why we chose WebSockets and how they work.
This post will cover:
If you don’t know us, Bytebase is the byte-size knowledge base for engineering teams. Bytebase supports collaborating on a module in real-time.
In this post, we share how we used Django…