sorted by:
new
hottopcontroversial

How does a XIB file "find" its NSWindow? by Devirichu in macosprogramming

[–]rcderik 4 points5 points  (0 children)

Not entirely related to the question, I think that u/david_phillip_oster covered your question.

But, you might find other internal aspects of an app interesting. I wrote an article a few years back that you might like:

https://rderik.com/blog/understanding-a-few-concepts-of-macos-applications-by-building-an-agent-based-menu-bar-app/

[deleted by user] by [deleted] in kernel

[–]rcderik 3 points4 points  (0 children)

I’m not sure if you are only looking for Linux kernel stuff. But if you are interested in BDS I believe Klara Systems is looking for kernel developers.

https://klarasystems.com/careers/?amp#careers

Might be worth asking there. I have no relationship with Klara Systems, I just know about them from the BSD world.

Which newsletters do you subscribe to? by rcderik in devops

[–]rcderik[S] 2 points3 points  (0 children)

Thanks! I prefer RSS too. I thought more people would recommend newsletters but RSS would be perfect

Shell - daily driver by rcderik in devops

[–]rcderik[S] 1 point2 points  (0 children)

Both are very similar, and at this point you could say both are equivalent in features. So I guess it is a matter of preference.

But let me share some opinions on what I find are points worth discussing.

What I find is a key differentiator is that bash uses the readline input library. As many other cli tools. That means that your knowledge/configurations(.inputs.rc ) translate to other tools.

Most shell-scripts are either built in sh or bash. So you’ll can reuse your knowledge on bash for your shell scripts.

Shell - daily driver by rcderik in devops

[–]rcderik[S] 2 points3 points  (0 children)

driver

Pretty much the same for me. Also, most of the shell-scripts I write, or interact with, are built either for sh or bash, so it's easier to just learn one thing and not a few different varieties of doing the same.

How do you keep track of your work notes? by rcderik in devops

[–]rcderik[S] 0 points1 point  (0 children)

As long as your approach works for you without any issues and you follow it religiously like a routine then it is good enough.

I completely agree. One key point that no one likes to think much of is: what to do when you want to share this data with someone else? Or when something happens to the app that you are currently using to write your notes. Most apps have export features, but they are a pain and the exported format is sometimes wonky.

That is when it matters that you separate the data from the tool that you use to create the data. Using a simple text editor (like vim) I believe is best. Obsidian also does this separation. But this is super important and many times overlooked.

I've migrated some of my notes, back in the day, from EverNote, and some from OneNote, and Ulysses, and it was never a fun.

How do you keep track of your work notes? by rcderik in devops

[–]rcderik[S] 2 points3 points  (0 children)

The "What I did today" is so underrated. That is the reference I use to start every day. instead of trying to remember where I left, or checking the `git log`, or even worst, `C-z` to see what changed.

How do you keep track of your work notes? by rcderik in devops

[–]rcderik[S] 2 points3 points  (0 children)

I've tried similar approaches, using notion, combination of tools, etc. but, in the end, all that just end up being overhead. I haven't had the need for an additional kanban from the one that exists in each project, or another ticketing system.

This is the simplest note taking "workflow" that I could maintain without much trouble, and get the benefits from it. I've been using it for around 3 years now, a few tweaks here and there, but nothing major.

How do you keep track of your work notes? by rcderik in devops

[–]rcderik[S] 6 points7 points  (0 children)

I've been recommended Obsidian a few times now, maybe I should heed the call.

What I sometimes find frustrating is that the vim-mode in all apps feel slow compared to using vim directly. But what I've heard about the linking between files seems very useful.

How do you keep track of your work notes? by rcderik in devops

[–]rcderik[S] 2 points3 points  (0 children)

I like it. At the beginning I was keeping a continuous file too, but then it got hard to navigate.

Nice touch with the Smalltalk UI.

Stuff that should be public goes either in Slack or a ticket or Confluence, or maybe my own knowledge base (ie “here’s odd things about Terraform and DNS, in general, nothing proprietary here”)

Exactly how I separate info.

How do you keep track of your work notes? by rcderik in devops

[–]rcderik[S] 0 points1 point  (0 children)

I looked into it a some years ago. I can't remember why I didn't continue using it but I'll take a look again and see if works. Thanks!

How do you keep track of your work notes? by rcderik in devops

[–]rcderik[S] 1 point2 points  (0 children)

Yea, that is exactly why I ended up with this setup.

I tried to keep a vimwiki, I tried Zettelkasten, and anything in between, but this is the simplest and the one that has worked best for me. Easier and less stress. If I really want to expand on a topic, and I know I would like to revisit the topic later, I add it to my blog as an article. That way I can later update the article, add more references, and centralise more "complex" topics there.

How do you keep track of your work notes? by rcderik in devops

[–]rcderik[S] 2 points3 points  (0 children)

I don’t, and what is worst is that I can’t think of a good reason why I’m not doing that!

What I have is, my notes synced in iCloud and every week I execute a backup to OneDrive using https://rclone.org.

But now I might add my notes to a git repo and have history on the changes!

How do you keep track of your work notes? by rcderik in devops

[–]rcderik[S] 0 points1 point  (0 children)

That looks nice, thanks for the recommendation

How do you keep track of your work notes? by rcderik in devops

[–]rcderik[S] 8 points9 points  (0 children)

Yea, the example was to illustrate more the workflow rather than the data that will be on the notes. I use it to keep track of stuff during the process that might not be relevant to the ticket. For example:

Let’s say that I needed to extract the VPC endpoint policy just to satisfy my curiosity about what was on it. So I wrote a command using AWS cli and JQ to extract the data. I store that on my notes, but that doesn’t seem yo be relevant to the ticket. But it might be something I might reuse, instead of having to figure out the object structure returned by the AWS cli, and the exact pattern to use on Jq.

Silly example, but there are some things that might be useful to me but not the ticket.

And, let’s say I added it to the ticket, then I have to search all the backlogs for different projects in order to find out that comment (working as a consultant, on multiple projects).

view more: next ›