• 1 Post
  • 31 Comments
Joined 2 months ago
cake
Cake day: November 12th, 2024

help-circle



  • I came back to playing a few weeks ago and absolutely stopped working on the 3rd party tool for X4 that I was making.

    Now, to get back to making programs, I am going to completely stop playing for a while. Because when I start dong something, I feel like doing another thing and then another and it goes on and the day is over.

    I also tend to be stuck thinking sometimes, whether to make the program I want, to put on my CV or to complete my resume website and spend a few minutes of staring at the screen, until I just go make some food.









  • Did you not know?
    You can simply select all files you want to commit, in the File Manager, Ctrl+C, then paste in the terminal and it will automatically add all those file names (full paths) separated with spaces at the cursor. At least in KDE: Dolphin -> zsh + Konsole it does.

    And sure, it might look like 2 extra steps, but you will still be clicking around a lot in case of a GUI anyway.

    I tend to just type partial filenames and use tab completions, which are also pretty configurable. And the only dissatisfaction I have rn, is that I don’t have zsh module for completions with pascal case and snake case.


  • That’s definitely how it is seen.
    If I were to see “Discard Changes” anywhere in a dialogue, I would assume it will discard whatever changes I made in that dialogue. In this case, probably some source control related changes. If it were to say “Warning: This will Discard ALL changes!!!”, I might do a double take, but had I never used git CLI before, I would still assume that at most it would discard “ALL” changes made in the current session.

    For me personally, I would consider it more useful for it to say:

    This action will delete the following files:
    - followed
    - by
    - a
    - list
    - of
    - files
    - that
    - would
    - be
    - deleted
    Continue?
    

    Which neither has to look like a warning, acting like you might be doing something you don’t want to and also is much more useful for someone like me who wants to double check what exactly I am deleting.


    Also, I have used git CLI before and apart from being able to see blame in the editor itself and maybe a better representation of tree, I don’t feel the need to use any git GUI tool. Even when I tried, I realised it was slower and more finicky to use. So, it would stand to reason that it should be targetted towards people who don’t use CLI (and might have never used git CLI).





  • Lower end is more complex and critical

    In that case, I suggest:

    1. Taking into consideration, the US Govt. mandates and learning Rust.
    • This would only work out in the long term though, as in most places, there is not a demand for it yet
    • I feel like it will catch on, considering they do have some points and a lot of power.
    1. If you are going with the short term one, getting familiar with C, C++ and being able to visualise memory.
    • The visualise memory is required anyway. Alright, maybe not strictly required (I worked in a Govt. workplace and a lot of them could not) but it is important to excel.