541–550 of 1001 posts
I'm building a new twin ad-hoc encoding format to replace JSON and friends [1]. It has native support for all commonly used data types, so you don't need to artificially specify custom encodings just to get your data across. It's a twin text / binary format, where the text format can be transparently converted to the binary format, and vice versa. This means that you can use the binary format for storage and communic…
The idea that we throw away a lot of the signal we generate while doing things online and this can be put to good use for ourselves.
As it is right now, Histre aids the casual online research we all do (ie the explore -> filter -> decide loop). For example, it removes friction in taking notes on links you're looking at, with free-form tags that you don't have to create first and other such niceties that add up. And it easy to group notes into notebooks and share with teams. In short, when you have to look at a bunch of links for something (decide on AirBnB, people to hire, material for your next blog post, etc) Histre makes your life easier. But this is just the starting point for what Histre intends to do.
IMHO the biggest problem with apps like Evernote, Notion, Pocket etc is that it becomes digital hoarding, and not a knowledge base. And the knowledge base focused apps out there involve a lot of manual upkeep, which almost never happens, especially at work. Things start out okay and quickly fall into disrepair. I'm differentiating from the other note taking apps by automatically putting together a knowledge base (grouped by topic etc). Automatic Upkeep (WIP): Histre detects links/notes related to your existing notebooks and offers to update those notebooks with the new links and notes. This is similar to how Google Photos suggests new photos for your existing albums. This solves the upkeep problem. Currently people create knowledge bases with good intentions and it becomes stale and useless quite fast.
Exports: I'm working on org-mode exports, as I'm an Emacs user myself. Other export formats coming soon.
There is Hacker News integration that you may want to try. It lets you import and optionally share the stories you upvote.
I’m working on a tool that allows developers to record and playback interactive, guided walkthroughs of a codebase, directly from their editor. It’s called CodeTour, and it’s currently available as a VS Code extension: https://aka.ms/codetour . I built it because I frequently find myself looking to onboard (or “reboard”) to a project, and not knowing exactly where to start. After speaking to a bunch of other develope…
I'm catching up on movie watching. For the last 10+ years, I've been collecting a list of any movie mentioned on reddit or HN as being good or excellent. I also will add the Netflix top 100 DVDs each month (yes, I'm still a DVD Netflix subscriber!). I'll also add all of the academy award nominated movies (although most of those already show up in the Netflix 100). That list has grown to about 650 movies now (fun fact…
I’m working on a tool that allows developers to record and playback interactive, guided walkthroughs of a codebase, directly from their editor. It’s called CodeTour, and it’s currently available as a VS Code extension: https://aka.ms/codetour . I built it because I frequently find myself looking to onboard (or “reboard”) to a project, and not knowing exactly where to start. After speaking to a bunch of other develope…
It takes time to derive the high-level from the codebase. I guess, your walk-throughs would be similar to how I'd explore it myself - without the mistakes.
EDIT it's documentation, so can get stale/out of sync as the codebase evolves (not a problem for PRs). Though high-level architecture/APIs rarely change.
BTW In github, I keep expecting the text next to files/dir to be a comment explaining the high-level (instead of the most recent commit message).
FOSS: https://github.com/zackb/forcecode
only TestFlight right now but AppStore soon under the name "Force Code"
It's a useful tool for DBA to identify issues in SQL queries automatically. Only 50 rules for now, but more than 1000 described in backlog :)
Funny, but initially this tool aimed at developers' needs.
I've made a lot of microservices, which only started the database queries. I came up with the idea of making a tool that would automatically generate all the microservices based on SQL queries. The MVP of such a tool was implemented, which reduced the developer workload by at least a quarter. In this tool, it was required to write queries in a certain way that did not make it universal and did not give a connection with the database structure.
The next step was to create a system that relies on the text description of the database schema in SQL format (DDL) and automatically understands the types that will return the SQL query. Such a tool can automatically inform the developer about possible errors on the interface between the application and database when changing the structure or the SQL queries themselves. It can also be built into the CI to provide the automatic code review at the version control system level and prevent the erroneous code from entering the repository.
But the developers did not appreciate all the advantages, as most projects are developed using ORM :(
But at the same time, DBAs expressed interest in implementing a system of the automatic search for bad requests already on the production database.
Any questions are welcome :)
Adding support for Mind Maps to https://diagram.codes .