Shinji_Ikari [he/him]

  • 0 Posts
  • 25 Comments
Joined 4 years ago
cake
Cake day: July 29th, 2020

help-circle


  • Yeah I actually just prefer the command line, I’ve never had to force myself to use it. I even tried using VSC for a bit recently but i couldn’t get myself to like it. I just use nvim with some plugins in a tmux session now and its productive as hell.

    Of course I don’t browse the web with the command line. For merging branches, I always merge main into the working branch first, check conflict files, and go through the file finding the diffs and resolving them. I’ve used merge tools before that were sorta nice but I had my own issues with them.

    Maybe it’s the type of programming I do. I don’t do any web stuff, so file count is down. For larger code bases I keep a non editor terminal up and will grep -re for word/phrase searching, find to look for specific files, etc. I’ll occasionally use an IDE, typically eclipse based because embedded, but I don’t find myself missing the features they add.




  • I really never understood why one would need a GUI for git except for visualizing branches.

    I feel like I’m crazy seeing so many people using clicky buttons for tracking files. I need like 4 commands for 95% of what I do and the rest you look up.

    You’re already programming! Just learn the tool!

    And now there’s a github CLI tool? I hate to beat a dead horse but Microsoft pushing their extended version of an open source tool/protocol is literally the second step of their mantra.





  • Its not dead simple but its also not extremely complex.

    I’m currently working with some interns and there’s just concepts they were never exposed to. Without decent mentoring, git can be difficult because a lot of the workflow does come with experience.

    That being said everyone needs to stop acting like its an impossible task to properly do source control. There is some truth that if you don’t care enough to do your source control, you don’t care enough to write decent code. Its not a moral failing, just take some pride in your craft.

    Show the newbies how to care and they’ll care enough to want to do it right. Measure twice, cut once and all that.



  • I bought a super cheap classic and did a flash mod, battery upgrade, and bluetooth mod.

    The bt mod only came after I went back to wired headphones and experienced the rage of having earbuds ripped out when the wire hooks onto things. I was a bt earbud hater for a bit but the freedom is somethin else.

    It does suck a lot to load music onto it, I’ve tried foobar2000 and a linux option. the former is better but windows, if you switch around you need to re-sync the entire ipod, which over slow USB2 is a many hour endeavor.

    The simplicity of not being distracted by a notification when you go to change a song is undefeated.




  • I watched a lot of youtube before I dove in. There’s a LOT more content on watch repair now after covid so it should be easy. Pay specific attention to how the seasoned watchmakers use their tools. You should never have to force anything in a watch. Go as slow as possible and really savor each movement.

    If you don’t have a camera with good macro abilities, grab some of those cheap clip on macro lenses for your phone.

    Take a pictures at every step until you don’t need them anymore. I specifically was interested in 2-3 movements but you start to see the commonality between them if you’re just working on a simple hour/minute/second/calendar watch without extra complications.

    I really suggest buying one of those little plastic trays with a clear dome on top that have dividers. With that, I divide the parts and screws by the aspect of the movement. ie I’ll use one compartment for the automatic winder components, a compartment for the stem and winding mechanism, one for the main drive, and another for the date complication. I repair a lot of misc things so I have a decent memory for where parts/screws go. If you dont, take pictures of the screw next to the hole you took it from so you can compare scale. Screws inside watches are usually at most 2-3 sizes, if not all the same but its good practice to ensure you put the right screw in the right hole.

    Also check out the forum watchrepairtalk. Its an international group of old men who love to help out. It has a completely different atmosphere to watchuseek and is an endless fountain of knowledge.



  • I struggle with frontend too, it was a super basic jinja templates with html and a plotly js applet that I just fed data to. Its ugly but functional.

    I Started to re-write the server in Go, I have like 90% feature parity with postgres instead of mongo, but I need to figure out vue when I have a chance to make something a little nicer. I have an old obsolete ipad with a bunch of touch deadzones I’d like to load up in kiosk mode for a nicer data display.

    I really liked the ESP32 ecosystem. I figured out the ESP-idf and really liked the build system and freeRTOS. The examples given are really exhaustive and super useful. I basically did format strings into static HTML headers to send the data to the server since it only has like 3-4 readings.

    Interfacing with any common hobbyist sensor is mostly a matter of finding a basic C driver and adapting it for the ESP build system.