• 0 Posts
  • 6 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle




  • Create a folder, put markdown files in it, sync* and backup* the folder however you like and edit the files with whatever you like*.

    Within my folder I have a daily journal - start each day with a list of what I hope to achieve today and make notes throughout the day as I progress on those tasks. The next day that journal becomes something I’lll refer back to in the morning to decide what to do next. Depending on the project - weekly or monthly might be more suitable than daily. Or maybe something else entirely.

    I also have folders an files for longer term tasks.

    If you want to collaborate, make a second folder and choose a sync platform you can all agree on.

    (* I use GitHub for Sync, Backblaze B2 for backup, and Visual Studio Code for editing, with extensions for markdown and making GitHub a little easier… specifically GitDoc for auto-commit/push/pull and Markdown All in One for formatting/etc. Also Copilot is handy for some note taking tasks. The “foam” extension mentioned here looks like it might be great too)


  • I use various extensions for Visual Studio Code. They add a million features, but these are the ones I find most useful:

    I prefer to view the current status of my checkout in the sidebar of my code editor than on the command line.

    It’s easier to view a diff of a file and decide whether to stage or rollback changes in a GUI. With most GUIs you can even select individual lines of code and revert or stage them.

    I like how Commit and Push and Pull are a single “Commit & Sync” button in Visual Studio code. Similarly there’s a simple “Sync” button in the status bar.

    Speaking of the status bar - it also has a counter for commits that need to be pushed or pulled. And it tells you what branch you’re currently on. And whether you have uncommitted changes. Handy.

    I find the GUI equivalent of git log --graph is significantly easier to understand when the graph is drawn with nice vector lines instead of ASCII art.

    Finally - I don’t just use raw git, I also use extensions like pull requests, and I create branches for issue numbers. I have an extension that shows pull requests in Visual Studio Code and also shows issues assigned to me, with a one click “Start Working” button to create a branch named after the issue and change the issue status to In Progress. And when I’m finished working on it, there’s a button for that too.