Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)B
Posts
17
Comments
502
Joined
3 yr. ago

  • I recently read this blog post and gave it a try. After a little bit of tweaking, I found that it became a useful tool for me while still letting me enjoy coding. It doesn’t fix everything that is wrong with AI development but it does help a lot in my day to day.

    TLDR: Add this to your copilot_instructions.md or whatever you use.

     
        
    When the user gives you a task specification:
    
    1. Explore the codebase to find relevant files and patterns
    2. Break the task into a small number of steps. Each step should include:
        a. a brief, high-level summary of the step
        b. a list of specific, relevant files
        c. quotes from the specification to be specific about what each step is for
    3. Present the steps and get out of the way.
    
    When the user says "done", "how's this", etc.:
    
    1. Run git status and git diff to see what they changed
    2. Review the changes and identify any potential problems
    3. Compare changes against the steps and identify which steps are complete
    4. Present a revised set of steps and get out of the user's way.
    
    Important:
    - Be concise and direct, don't give the user a lot to read
    - Allow the user to make all technical, architectural and engineering decisions
    - Present possible solutions but don't make any assumptions
    - Don't write code - just guide
    - Be specific about files and line numbers
    - Trust them to figure it out
    - Do not offer to write code unless the user specifically requests it. You are a teacher and reviewer, not a developer 
    - Include checks for idiomatic use of language features when reviewing 
    - The user has a strong background in C, C++, and Python. Make analogies to those languages when reviewing code in other languages
    
      

    The last three points are my addition as I am currently do a lot of development in Rust which I have no experience with.

  • Uh, I’m pretty sure that is a jacemat.

  • Huh, what? I’m out of the loop. What did Jack Black do?

  • Mostly book, but also some plants since this room has amazing light. Also, the bottom left is my networking closet which will have a door on it. The bottom right will have a door for symmetry and probably hold games. The not yet installed top level will have some art and things.

  • Thanks! I'm really pleased with it so far. I know there is a lot of work still, particularly the finishing touches, but it makes the room already feel so much better.

  • Damnit, now I have another toy to add to my “need” list.

  • I’ve never used IntelliJ, or Java for that matter. I’m primarily an embedded robotics developer, so most of the time I’m writing C or a subset of C++ for uC/DSP target, or using SciPy for data analysis and algorithm development. I recognize that probably puts me way outside of the norm for most people and software engineers in terms of process preferences.

  • I’m a “serious professional” who has been developing for over 20 years and I’ve generally prefer a text editor the IDEs that I’ve had to use at work. I find that most IDEs are slow resource hogs that don’t give me features that I actually care about over a fast text editor.

    The singular exception was Cider when I was at Google. It was fantastic at wrangling their massive monorepo, and integration with their code review and ticket system was nice. Somehow it was snappy and reliable even though it ran in Chrome.

    Nowadays I’ve switched to Helix and use LSPs for the languages I use most. For what it’s worth, those are C, C++, Rust and Python. Mostly Rust and Python now.

  • I spent years using Notepad++ as my professional editor. We were a Windows shop and all of the IDEs available were much slower and buggier. It’s a surprisingly decent introduction to the idea of what a good text editor can be.

  • gdb works great without an IDE, and many text editors have autocomplete.

  • There are dozens of us!

  • May I recommend Helix? It’s a modal editor like vim, but has a better out of the box experience, better discoverability for commands, and uses an easier to understand select->command syntax.

  • How do you not? A text editor and a browser are the two programs that I use the most, both for work and at home. And while most browsers have pretty similar UXs nowadays, the different editors are vastly different. Helix, EMacs, vim, StyledEdit, Notepad++, Kate, etc all have radically different approaches to basically everything.

  • I would also add that the presidents party almost always loses votes in the midterms. This is particularly true for republicans since 2016 because a lot of trump’s supporters only care about him and won’t bother to fill out a ballot without him on it.

  • I can’t get the Windows based firmware updaters for my motorcycle helmet Bluetooth headset and joystick fully running under Wine/Lutris/Whatever. They both use USB and just will not connect.

    Also, once a quarter I have to use an archaic Excel sheet that is heavily dependent on some VB Script. This file absolutely will not open correctly in anything other than a locally installed version of Excel because the script needs a real local printer and Open/Libre/Whatever cannot handle the insanity of the VB Script. I have a Windows VM just for this one thing.

  • The other thing to do would be to see what is using so much memory. You can use

     
        
    htop 
    
    
      

    And sort by memory use.

  • Have you ran a memory check? Linux and Windows use memory layouts pretty differently so you may have avoided the bad bits before that are now an issue. https://memtest.org/

  • When I was a kid I bought an Atari with the cartridge holder stand for it and a ton of games for $5. ET was fucking awful, but there were a few gems in the collection.

  • I think that really depends on your perspective. I’ve spent most of my career in C or a minimal subset of C++ for embedded systems. For me, even no_std rust has a rather rich set of features.