Ask HN: What tools are you spending your money on?
For additional context, I'm relatively new to homeownership and enjoy building/making things!
[ my public key: https://keybase.io/niche; my proof: https://keybase.io/niche/sigs/PYgSdidGqbmdbDCb6PTwzqRyJ3beim1pxn9r4xmnZ5o ]
For additional context, I'm relatively new to homeownership and enjoy building/making things!
USB-C Smartphone <- [ USB Hub ] ...
[ USB Hub ] USB-A -> USB-C Storage medium (2x)
I need the (android) phone to be able to mount these two USB-C devices (which, unfortunately, require USB-A -> USB-C connections) at the same time. The current solution is _slow_ to mount and sometimes fails completely.
I can't control the USB hardware of the phone and the connected devices, but I can control the hub selection. I'm looking for tips re: USB hardware/software testing procedures.
In the short term, I need to choose a commercial hub, but in the long term, will design and build a custom hub. Recommended resources + techniques in the vast world of USB would be greatly appreciated!
So. How do you manage to fall (back) asleep?
Any suggestions will be greatly appreciated :)
I'm currently trying to work on my network administration skills at my full-time job.
Looking to purchase a Synology NAS or something similar to start creating a repository for all of my personal projects/data.
Thoughts on where to start? Considerations for organizing files and documenting what I have?
Curious to see how others have handled archiving years of data. Thanks HN!
Recent grad working full-time for an engineering firm that tackles just about any project related to electrical/systems engineering in the industrial world.
Problem: we still use time tracking/invoicing software from the mid-90s.
Attempted solution: develop an in-house replacement.
They've been working on and off for over a year now, I was asked to contribute when I joined due to my (limited) background in software development.
After a few months I realized that I don't think it's worth the time or energy to make an in-house solution that will need to be maintained forever.
How do I discuss this with my coworkers - particularly the one who has dedicated a great deal of time to developing this project? Especially as the newest and most inexperienced employee.