cborenstein

13 ms·

91.
by cborenstein 6y ago
Great to hear! Currently Bytebase is free to use. When we move out of Beta, we'll have both free and paid tiers.
92.
by cborenstein 6y ago
My goals for my personal knowledge base are that it's comprehensive (i.e., it has a lot of stuff) and it's accessible. To achieve this, I need a way to support these two different phases of notes: * The first phase is "get-it
93.
by cborenstein 6y ago
Awesome piece, thanks for sharing. I agree that the key to effective communication is to lower the barrier to writing things down. In that vein, this piece is missing one thing. It is inherently easier to write something private than to wri
94.
by cborenstein 6y ago
This project looks awesome. I created bytebase.io, a notes app that shares much of the same philosophy - flexible hierarchy, simplicity, user control. We'll definitely consider supporting import/export to Margin.
95.
by cborenstein 7y ago
Bytebase (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 "co
96.
Django Real Time Chat Tutorial (WebSockets)(github.com)
3 points by cborenstein 7y ago|0 comments
97.
by cborenstein 7y ago
It sounds like you do a great job communicating regularly in your typical in-person environment. I previously worked at an "old-school" company where everyone on the team would work remote 2-3 times a week. We'd also collabor
98.
by cborenstein 7y ago
I like https://coolors.co/ for color palette generation. Not sure what their algorithm is.
99.
by cborenstein 7y ago
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 tooli
100.
by cborenstein 7y ago
+1 that Why matters most. My teammate recently wrote a blog post on how we document Why in git commits and PR descriptions. https://medium.com/better-programming/daily-habits-to-turn-y... Would also recommend checking
101.
by cborenstein 7y ago
Thanks for your thoughtful reply. What do you to accommodate people who aren't natural writers?
102.
by cborenstein 7y ago
Really interesting idea, thanks for sharing.
103.
by cborenstein 7y ago
I think encouraging people to ask for clarification is super important. One thing that's helped me receive more clarifying questions is adding pauses while talking. This gives an opportunity for someone to ask questions without interru
104.
Ask HN: How do you encourage a culture of written communication on your team?
7 points by cborenstein 7y ago|5 comments
105.
by cborenstein 7y ago
I think good tech talks (especially ones that are highly technical), are ones that make the high-level context for why we should care about the technology we're learning very clear. I'd recommend checking out https://fe
106.
by cborenstein 7y ago
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
107.
Daily Habits for Docs(medium.com)
3 points by cborenstein 7y ago|0 comments
108.
by cborenstein 7y ago
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 o
109.
by cborenstein 7y ago
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 pain
110.
by cborenstein 7y ago
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 n
111.
by cborenstein 7y ago
Another resource that might be useful is video recordings from the DjangoCon conferences. Here's the youtube channel for DjangoCon US: https://www.youtube.com/channel/UC0yY6a79pPY9J0ShIHRf6yw
112.
by cborenstein 7y ago
In my experience, remote engineers are often some of the most productive engineers at an organization. When any engineer can demonstrate a strong track record of shipping, any idea of "laziness" goes away pretty quickly. I think o
113.
by cborenstein 7y ago
Break things down. I'd start by getting an overview of the problem - in this case it's probably chapter names in a book. Then for each module, break down what you'd like to learn further into sections that take < 2 hours t
114.
by cborenstein 7y ago
Thanks for your question! We don't support integrations other than Slack yet but plan to add more soon as well as an API. Mind shooting me an email so I can learn more about what your team needs?
115.
by cborenstein 7y ago
Disclosure: I am a founder at bytebase.io, currently in closed beta. We're building Bytebase with this kind of use case in mind. Wikis - we found wikis are too heavyweight and formal to be used consistently for recording learnings. Sla
116.
Actionable engineering docs(medium.com)
2 points by cborenstein 7y ago|0 comments
117.
Show HN: Pull Request Checklist for Startups(medium.com)
2 points by cborenstein 7y ago|0 comments
118.
How we built a real-time web app with Django Channels(medium.com)
2 points by cborenstein 7y ago|0 comments
119.
Show HN: Notes app that combines folders and tags so you can write faster(medium.com)
3 points by cborenstein 7y ago|0 comments
120.
by cborenstein 7y ago
Disclosure: I am a founder at bytebase.io, currently in closed beta. My former team used Confluence and Google Docs for knowledge sharing and found that it worked great for planning projects, but fell short for things that change quickly or

More ›