• 0 Posts
  • 59 Comments
Joined 1 year ago
cake
Cake day: August 12th, 2023

help-circle

  • File tree not a file tree like in a file explorer, more like the output of find, but with filtering. The letters you type to restrict your search only need to present in that order in the file path, not as a string.

    So “abc” would match “./assets/others/abort/cancel.png”, not just “./assets/abc.png”

    Additionally, lower case letters match case insensitive, upper case letters match case sensitive. This is surprisingly helpful if you don’t use exclusively lowercase file names.


  • Not to talk down the suggestion, but with your experience in writing software I would not recommend adding JavaScript, HTML, CSS and whatever Llibrary you need for plotting to your tech stack.

    Distributing python applications can be a pain (no easy “here’s the .exe, just run it”), but it’s easy to write, you can use matplotlib, numpy, etc. And the graphics libraries are well established.

    I am currently writing an application with PyQT6. It works well. There is a graphical editor to design the layout if you don’t want to write everything in code by hand.


  • Space-f lets you open a file in the current workspace, and :open /path always let’s you open any file on the computer

    Plugin support not yet I think. Not gonna lie, I chose helix over nvim for it’s good out of the box experience, so I didn’t actually have a need for plugins yet.

    Fair enough. That would be a use case for a plugin (or simply a setting!)











  • So the core concept is that when you validate some property about input you should also transform the input into a new form that represents the new guarantee in the type system.

    This is very, closely related to the “make invalid states unrepresentable” concept. If we have validated our list to be non empty, we should return a non empty list - after all an empty list is now invalid and as such the type system should exclude that possibility.







  • If you’re cheap like me, just change the keyboard layout on the software side and instead of looking at the now incorrect key caps, look at the American keyboard layout image on Wikipedia instead. It doesn’t take long to relearn the few differences. And the parentheses are more ergonomic on the us keyboard layout IMO.

    Edit: compared to the German layout. Brazilian looks ergonomic enough for programming without having to switch.