Top all-time · #17571
B
bytebase.io
Company blog · bytebase.io/blogprogrammingproductivity
bytebase.io is the company blog at bytebase.io, writing about programming and productivity. Since 2020, 4 different Hacker News readers have linked it 18 times, most often “What I learned about using Slack statuses when working remotely”. No feed was found, so read it on the site itself.
No feed foundVisit the blog
18mentions?
4HN people?
2020–2022first – last linked?
Too few sampled comments (1) to say how often HN recommends it.?
Why HN links it
Only one comment, which identifies the linked article as being about bytebase.io. It says nothing about the writing itself.
Summarised by Claude from a sample of 1 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- What I learned about using Slack statuses when working remotely2 people · 2 mentions · first linked 2021-07-21
What Hacker News says?
> 1. If we have time to enter something into a knowledge base of any kind - then we have time to just jot it on a piece of paper. Great point. I often see people sharing strategies for organizing notes but I rarely see people discussing how they get stuff down in the first place. And there's a lot of improvement we can make here. I wanted to add more modularity to my jot-downs so that it would be easier to organize…
Comment linking /
on “Zettlr – FOSS markdown editor for personal knowledge management and publishing”Submitted You probably don't need a knowledge garden as a story · 17 points
HN discussionBytebase ( https://bytebase.io ) is re-inventing the engineer's notepad. We're engineers from Twilio and Nextdoor and are backed by Techstars, top-preseed firms, and engineers from companies like Github, Slack, Stripe, and more. We're hiring for founding software engineers in the US. Remote/Hybrid team with HQ in Durham, NC. Reach out at cara [at] bytebase [dot] io https://pragmatic-engineer.pallet.com/jobs/e05a60b4…
Comment linking /
on “Ask HN: Who is hiring? (March 2022)”Submitted What I learned about using Slack statuses when working remotely as a story · 12 points
HN discussionBytebase (I'm one of the creators) is built for keeping track of notes and snippets on your own or with your team. Everything you create is one short snippet or "byte" and these snippets can be grouped into different "collections" using tags. Would love any feedback. https://bytebase.io
Comment linking /
on “Ask HN: What do you use to keep track of bookmarks/notes/snippets?”Submitted Setting Slack Status for Remote Work as a story · 2 points
HN discussionTotally agree. As a software engineer, I was always excited to try new notes apps and to "really stay organized" this time. But I always ended up falling back on either Apple Notes or Sublime because everything else was too slow. Decided to build an app where it's fast to start writing but is also set up to keep your notes sane over time. The app has a built in scratchpad where you capture notes in small chunks, lik…
Comment linking /
on “Notion Timeline View”I’d recommend two phases when writing notes: 1) dump everything into your notes that might be useful 2) organize and highlight the most important stuff --- I’m one of the creators of https://bytebase.io and that’s where I take notes. We’ve designed Bytebase to decouple the capture and organize phases. - In my first pass when taking notes, I write down anything that might be helpful later. - Each note is captured as…
Comment linking /
on “Ask HN: How to Take Good Notes?”Great deep dive into core principles of a good note-taking system. There are a few things I'd add. Curious to hear your thoughts. > 1) Captured ideas are better than missed ones > 2) Adding new ideas is better than updating old ones. Updating notes in-place is inherently lossy, and I think it’s unnecessary. Yes. And, setting the intention to "add," not "update" reduces friction to capturing. When you write something…
Comment linking /
on “Incremental note-taking”> Getting people to contribute can be a problem This is so spot on. and I don't think it even has to be a problem. The way people actually work is they 1) write a ton of private notes 2) share a small amount of these notes ad-hoc 3) publish a tiny amount of this to a wiki To make knowledge more available, the key is to streamline these steps. Building an app that's grounded in this workflow. Would love to hear the c…
Comment linking /
on “Self Host a Wiki or Knowledge Base for Your Team”I surveyed 50 engineers a little while ago on how they take notes. This is what I learned. Most people's notes have two phases [0]: 1) Jot-down 2) Organize In the jot-down phase, you write down thoughts and gather any raw resources that are useful to you (code snippets, links, etc.). These notes are messy. In the organize phase, you pull notes from your jot-down that are worth keeping and refine/categorize them. The…
Comment linking /
on “Ask HN: How to take notes?”Effective remote work is about prioritizing. Work and Work/Life balance breaks down when you lose intention with how you spend your time. Work from home can be less structured and as a result requires more intention. This can involve communicating Deep Work and Deep Breaks (e.g. with Slack Status [1]) so that teammates know when you're unavailable. I've learned to set a clear intent each morning. I allocate and prot…
Comment linking /blog/slack-status-remote-work
on “5 Habits of Highly Ineffective Remote Workers”Thanks for sharing your guidelines. > Review and edit messages before sending Part of the joy of Slack is that sending messages to your team is super low-friction so more people are likely to contribute. The example use case is "I have this thought-through proposal I'd like to do. Is it okay with you." In this case it makes sense to review more thoroughly before sending in order to communicate the proposal more clea…
Comment linking /
on “Creating a Slack Writing Etiquette Guide for Your Workplace”The goal of product documentation is that new devs (and future you) are able to get the info they need. This doesn't mean that it needs to be entirely from a wiki. In my experience, wikis are rarely up-to-date because 1) shared ownership === no ownership 2) too high expectations --> people publish less I recently surveyed a bunch of devs on their knowledge sharing and learned that for most devs, private notes are ac…
Comment linking /
on “Ask HN: How do you document long term products”In my experience, code documentation is painful because people often try to maintain perfectly comprehensive formal docs and the expectation is too high. Aiming for perfection instead of iterative improvements can feel intimidating and painful. I recently wrote this blog post on how you can use lightweight daily habits in git and https://bytebase.io (I'm one of the creators) to avoid the dreaded "Docs Overhaul" that…
Comment linking /
on “Ask HN: Why is code documentation such a painful process?”For remote meetings, having a process for writing down and sharing meeting notes is especially important. As compared to in-person meetings, it's easier for someone to miss a key point and not be caught up on it. When considering tooling, I'd recommend looking at ways to: 1. Enable live access to the shared notes during the meeting. This gives teammates the chance to clarify things that may have been misunderstood r…
Comment linking /
on “Which tools are you using for effective remote meetings?”Awesome article, thanks for sharing. You make a great point that comments aren't trustworthy but can still provide a useful breadcrumb. My thoughts are that an overall documentation strategy can include several lines of defense based on how narrow or broad the context you need is. 1. write "self-documenting" code using good variable names, encapsulation, etc. 2. write comments to explain anything non-obvious in a sp…
Comment linking /
on “Comments Are Useful Lies”This is an article about https://bytebase.io/
Comment linking /
on “Catalog your thoughts like an engineer”