Getting the paper that says you have a degree in something (software engineering in my case) is what really matters.
If two candidates apply for a job, and one has a degree while the other doesn’t, the one with the degree will most likely get the job.
Don’t go to college purely to learn something and especially not CS, since everything in CS can be learned at home. Go to college to make it easier to get a job. It just makes you more future-proof.
That’s my opinion, but I also learn much better by just jumping in myself and trying hard, rather than listening to someone explain how it’s done.
View quoted note →
Frederik Handberg
npub1nj0c...2gqz
23 🇩🇰 Studying for a degree in Software Engineering while building fun projects and working freelance as a News Photographer 📷
I share my software projects, photos and videos from my work as a news photographer, and progress updates as I learn to sew garments.
Basically, I just write about my hobbies.
frederikhandberg.com
The new #Canon C50 is pretty crazy! 📷
I could really use a second camera with my long zoom lens attached all the time, so that I don't need to switch between my two primary lenses all the time. It's pretty annoying... And, I don't have the time to change lenses, so I'm often missing out on good pictures and videos.
But it would be stupid of me to buy a Canon, as both my primary lenses (Sony 200-600mm and Tamron 35-150mm) are for Sony FE-mount. Also, the Canon RF lenses I would be interested in are so crazy expensive... 😳 They are basically the same price as the camera itself.
Hopefully #Sony is working on a second generation of the FX3 🤞
I think I'll get the new AirPods Pro 3, but not tempted by the 17 Pro Max... Already have a 15 Pro Max and I just don't see any reason to upgrade. Was really hoping they would finally get rid of the camera/face ID cutout, but nope, that didn't happen.
Performance is pretty bad in my notes app and it makes sense why. And when I say bad, I really mean it 😂 It jumps to 100% CPU usage when writing super fast in a document with lots of #Markdown styling.
I am currently rerendering the entire Markdown file every time the user types a single character - this is obviously not ideal...
The plan is to only rerender the Markdown in the visible area.
Also, I should track the text that was last processed to avoid re-parsing it.
I don't really use #Bluesky, but I found this and thought it looked interesting.
It’s a way to build custom feeds (aka little recommendation algorithms), and then the feed can be shared with others.
https://www.graze.social/
It’s technically a folder, but on macOS it appears as a single file because it uses a package extension (`.textbundle`).
**Then it’s all bundled and easily shareable:**
My Note.textbundle/
├── text.md
├── info.json
└── assets/
├── some-image.png
├── screenshot.webp
└── video.mp4
View quoted note →
Just found out about `TextBundle`. Could be interesting for my notes app.
I need a way to bundle all assets referenced in a note so it’s easily portable. Users should be able to just share a folder and all assets should be included. TextBundle could potentially be a solution.
Welcome to TextBundle.org!
A community site for the development of the TextBundle standard
The bug is fixed, so now Markdown renders immediately when opening a note.
However, there's a new bug now... 😫
**The bug:** Clicking below the text in the Markdown editor to focus the text field works correctly on the first click, but on the second click, it no longer focuses. The caret should jump to the end of the text.
**Scenario:** Text in `NSTextView` spans only three lines, leaving plenty of whitespace between the text and the bottom of the window. When the user clicks on the text or below it, the text view becomes focused as expected. However, after this, clicking in the whitespace below the text no longer focuses the text view.
View quoted note →
A small fire broke out in a shed after a weed burner caused it.
One person has been charged by the police. #press


September 💚
I love this month. I guess mostly because it’s my birthday month…


I think I finally figured out a solution to this annoying problem! 😅 🎉
I created a new separate project with a simplified version of the code only for debugging.
**The solution:**
It turns out that it's possible to wrap the `ScrollView` in a `GeometryReader` which calculates the total window space.
Then I am using the value from the `GeometryReader` to calculate the total height without the header. The header is the blue box that contains the document name and information like word counter.
The calculation is simply `geometry.size.height - headerHeight` and now I have the minHeight value for the `NSTextView`.
It's even a dynamic value that updates when the user resizes the window.
From web development, I'm used to just being able to say `width: 100%` and then it works, but with native development, it's not as easy 😂 #dev #Swift #AppKit
View quoted note →
View quoted note →Will look at it again today. Hopefully I can find a solution.
It can’t be this difficult just to get a `NSTextView` to stretch full height inside a `ScrollView`…
View quoted note →
This is driving me crazy!
I can't figure out how to make the green box fill all the available height...
The green box is a `NSTextView`. I can obviously give it a fixed height, but I want it to be dynamic so it fills all the available height even when resizing the window.
I'm wrapping it all inside a `VStack` which is inside a `ScrollView`.


Something that bothers me about #Obsidian is that (to my knowledge) it’s not possible to open a #Markdown document outside the vault. You must import the document into your vault before being able to edit it.
I find that annoying. It should definitely be possible to open a document outside the vault/workspace to view and edit it. It will be a feature I will add to my notes app.
I think, when opening a document outside the workspace, it should open in a separate window that doesn’t include the sidebar but only shows the document by itself.
Otherwise I need to figure out a way to make it clear for the user which files are part of the workspace and which are external.
View quoted note →
**Workspaces in notes app**
In my notes app, I need to decide how to represent **workspaces**. It’s the top-level context where a user’s notes, images, and mood boards are stored.
#Obsidian uses _vaults_, but it's really just a normal folder. I think that’s the way to go for my notes app as well. It’s really important that it’s portable and open, and because it’s just a normal folder, you can copy it anywhere.
The idea is when the user opens a directory, the app treats it as a workspace and loads all notes, images, and mood boards from inside it.
When a user pastes or drags an image into a note, the app will copy that image into the workspace directory instead of keeping a reference to its original location on disk.
This is important because the image path would break if moving the workspace folder to a different location while the image isn’t saved in the folder itself. By keeping images inside the workspace directory, all paths remain relative and the workspace folder can be moved around freely without worrying about breaking paths.
**Multiple windows in notes app**
It's currently possible to open multiple windows in the notes app that I'm working on, but each window is a mirror (it shows exactly the same), and this is obviously not the behaviour I want.
Each open window should be completely independent from each other, allowing the user to have completely different directories/workspaces open.
I got infinite scrolling working on my Nostr blog. Now whenever reaching near the bottom of the page, new posts will be fetched.
Now it’s past midnight and I’m tired.
GN #Nostr 😴
I made a UI design of the search functionality I want to implement in my notes app. I think it looks pretty nice. I need to figure out how I can add some filters. For instance, if the user only wants to search in a specific folder.
I have actually already implemented a search function in the sidebar of the app. It might be a bit redundant to have two search functions, but I think they still can complement each other. I'll keep it for now and figure out later if it still makes sense to keep it... #dev #Swift #Markdown
View quoted note →
View quoted note →Ngl making a lightweight replacement for MS #Word would be awesome. It feels so clunky and slow to use…
#OPD format is probably the way to go for this, but I believe it’s pretty complicated, so not something I’ll be working on any time soon. First, I need to get my notes app fully working with features like #Markdown support, the visual canvas for brainstorming, and a search function similar to #Raycast.
I have already implemented a basic search function in the sidebar which works nicely. Nothing special about it. But I do want something similar to Raycast, Arc Browser, and Spotlight on Mac. A search function that opens through a shortcut, perhaps CMD + SHIFT + F. It shows a search input in the center of the window with a beautiful blurry background. Then search results will show in a grid of three columns with previews for each search result. So for example, searching for a document, would show a preview of the text, image, or whatever content is inside the document (basically the first 5-10 lines). #dev
View quoted note →
Markdown is great for simple notes, journaling, and such, but if you need _advanced_ formatting then Markdown quickly starts to become too basic and limiting. Even something as simple as text alignment, you just can’t do in Markdown, unless you break the simplicity of Markdown and start introducing CSS.
This is why I think, besides supporting Markdown in my notes app, having another format would be a good idea. Something more advanced.
It needs to be non-proprietary, so it must be an open standard like #Markdown - perhaps #Asciidoc or #Pandoc Markdown.
There are mainly two downsides to having support for multiple different formats in the app. Firstly, it takes longer to develop, and secondly, it makes it more confusing to non-technical people.
The first downside is not so much of a problem imo. I’ll start with Markdown (which I’m already working on and have most of the essential formatting working), and then later, I can start implementing support for another format.
I see the second downside as more of a problem. If users need to choose between two formats such as Markdown or Asciidoc, they are going to be like _“wtf is this?!”_
I probably need a little helper explaining the two formats…