observability
obsidian-wielder
observability | obsidian-wielder | |
---|---|---|
2 | 4 | |
- | 92 | |
- | - | |
- | 0.0 | |
- | 4 months ago | |
TypeScript | ||
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
observability
-
Take Advantage of Git Rebase
GitLab team member here, putting my personal hat on - from my experience in using different Git workflows since 2009, a smaller clean unit of work can with debugging and troubleshooting. It also provides a way to new team members and contributors to understand the thought process and ideation to implement a new architecture, apply performance fixes, add documentation, work with tests, additional fixes, until its final release. Most of this can be tracked within a MR/PR and the history of code reviews, etc. - even after the merge and squash and Git branch delete, not trying to argue with this functionality. :)
From the Git CLI, without any reference to Git* platforms, it is not so obvious when searching for a commit that introduced a bug, e.g. using "git bisect" for binary search. Reading a 10,000 lines git diff can be harder than a smaller commit that also explains the reasoning in the commit message. Speaking from own experience and programming mistakes in a small team, focussing on clean commits and a good history tremendously helped in stressful debug situations. Until you hit a compiler regression bug, but that's a different story then ;)
I'm personally still very fast on the Git CLI, but I also know that there are a variety of CLI and UI tools out there that can help with analysing large Git commits. Potentially in the future also AI assisted that tell us which change a diff caused a performance regression in a release 5 months later. Or we don't need it at all because Observability driven development enabled to see these problems before merging and code reviews, e.g. the memory leak but only when DNS fails. True story from ~2016, more in my KubeCon EU talk at https://www.youtube.com/watch?v=BkREMg8adaI and project at https://gitlab.com/everyonecancontribute/observability/cpp-d...
-
Show HN: My new free note taking tool
GitLab team member here, thanks for sharing!
I'm using the Web IDE to take notes in most of my projects, work and personal, and publish the notes with MkDocs and GitLab Pages to a searchable frontend/domain when needed. Editing also happens in Gitpod with live preview in the browser.
You can find all resources for o11y.love [0] and opsindev.news [1] in the GitLab projects, including .gitpod.yml configuration, mkdocs.yml setup, .gitlab-ci.yml deployments.
I have been writing lots of documentation in my past OSS projects, so I am used to Markdown as markup language, taking notes very fast. Learning Markdown requires some practice, and can be helped within Gitpod and the VS Code extensions, if the default preview is not sufficient. [2] [3] You can also sync the notes repository offline into VS Code as desktop IDE for example.
Using Obsidian.md to take notes and publish with GitLab pages [4] looks promising too; I have not tried it yet.
[0] https://gitlab.com/everyonecancontribute/observability/o11y....
[1] https://gitlab.com/dnsmichi/opsindev.news
[2] https://www.gitpod.io/docs/ides-and-editors/vscode-extension...
[3] https://code.visualstudio.com/docs/languages/markdown
[4] https://about.gitlab.com/blog/2022/03/15/publishing-obsidian...
obsidian-wielder
- Show HN: Obsidian 1.0
-
Show HN: My new free note taking tool
Depending on which particular subject you are interested in:
- The plugin:
https://wielder.victor.earth/Welcome shows the sort of things you can build with Wielder. The github repository for the library is here https://github.com/victorb/obsidian-wielder
- How To Solve it
The key ideas behind How To Solve It are that for a lot of our challenges there are strategies we can use to tackle them effectively. How To Solve It expounds on how to go about understanding a problem, understanding the connection of the data you have with what you don't know, how to make problems more tractable, carrying out a plan, and evaluating the results.
- Untools
A site dedicated to listing various strategies for thinking, communicating and prioritization; they sell templates similar in nature to what I'm building, but I depart sharply from them in my desired document representation choice for templates - Zettlekastian graph continuations for me versus linear documents for them.
- My own tool
This is currently private and not yet ready for public consumption. I have a whole lot of philosophical backing for what I'm trying to build but it is still very far from generating utility at the level I want it too. Later today I'll see about moving some private notes into a blog post going into more depth about what I'm building and why.
- Show HN: Wielder – Write and evaluate Clojure code in your Obsidian documents
What are some alternatives?
Perlite - A web-based markdown viewer optimized for Obsidian
voiceliner - Braindump better.
vscode-todo-md - VSCode extension for Todo tracking based on "todo.txt" format.
dev - Development repository for the CodeMirror editor project
excalidraw - Virtual whiteboard for sketching hand-drawn like diagrams
PineDocs - A fast and lightweight site for viewing files
api-playground
til - :memo: Today I Learned
www-gitlab-com
dev - Press the . key on any repo