It feels like you think that the parent hasn't really considered their options and don't know what they really want.
> Not that big of on an issue in most home user cases as a home server
I don't know what "most home users" want, but I can understand wanting something more compact and efficient (also easier to keep cool in tighter or closed spaces), even at home.
> Cheaper if you ignore much lower performance and versatility vs a X86_X64 NUC as a home server.
Or maybe they noticed they don't need all the performance and versatility. Been there. It's plenty versatile and can run everything I need.
My APC UPS self-tested and monitored battery status automatically. Then started to endlessly beep when it noticed the battery needed replacing (could be muted though). Eventually, I stopped using UPS since I rarely needed it and it was just another thing to keep and maintain.
> What I really wanted is a web interface which will just show me EVERYTHING it knows about the system in a form of charts, graphs, so I can just skim through it and check if everything allright visually, without using the shell and each individual command.
For this reason, I've created Lightkeeper: https://github.com/kalaksi/lightkeeper to simplify repetitive tasks and provide an efficient view for monitoring. Also has graphs as a recent addition, but screenshots don't show it. You can also drop to a terminal with a hotkey any time.
Ironically, it works over SSH without any additional daemons.
> I routinely have several thousands of tabs opened on my devices, and I never considered myself a hoarder.
You seem serious, but it sounds a bit funny!
I also often open links in new tabs. It's also a bit faster than e.g. going back in history. But I do close tabs after I'm done browsing that site or otherwise don't need it. I'd start to feel lost with a lot of tabs open (say, hundreds), not knowing what is actually relevant, what kind of research is "in progress", how to keep track of them well etc.. I do use multiple browser windows and vertical tabs in Firefox.
> Browsers tend to take open tabs into account when I search for stuff, and it’s nice to be able to enter a few keywords and get redirected to an existing tab.
Similarly, I mostly receive suggestions from my browsing history and use that a lot. I've disabled any suggestions from search engines, since they are usually useless.
> I've worked on teams where multiple engineers argued about the "right" way to build something. I remember thinking that they had biases based on past experiences and assumptions about what mattered. It usually took an outsider to proactively remind them what actually mattered to the business case.
My first thought was that you probably also have different biases, priorities and/or taste. As always, this is probably very context-specific and requires judgement to know when something goes too far. It's difficult to know the "most correct" approach beforehand.
> Sometimes hacking something together messily to confirm it's the right thing to be building is the right way. Then making sure it's secure, then finally paying down some technical debt to make it more maintainable and extensible.
I agree that sometimes it is, but in other cases my experience has been that when something is done, works and is used by customers, it's very hard to argue about refactoring it. Management doesn't want to waste hours on it (who pays for it?) and doesn't want to risk breaking stuff (or changing APIs) when it works. It's all reasonable.
And when some time passes, the related intricacies, bigger picture and initially floated ideas fade from memory. Now other stuff may depend on the existing implementation. People get used to the way things are done. It gets harder and harder to refactor things.
Again, this probably depends a lot on a project and what kind of software we're talking about.
> There's always a balance/tension, but it's when things go too far one way or another that I see avoidable failures.
I think balance/tension describes it well and good results probably require input from different people and from different angles.
I think the QML linter detects that but may require maintaining some extra files that tell which methods and properties are available in C++ classes. Not sure if they can be auto-generated if using C++ and more native tools since I've been using QML with Rust. Better type integration would be nice though.
Whoa, I noticed something similar. I was updating my password or something a few years back and decided to test the backup codes too. They didn't work. I don't know what went wrong but that got me worried a bit.
> Not that big of on an issue in most home user cases as a home server
I don't know what "most home users" want, but I can understand wanting something more compact and efficient (also easier to keep cool in tighter or closed spaces), even at home.
> Cheaper if you ignore much lower performance and versatility vs a X86_X64 NUC as a home server.
Or maybe they noticed they don't need all the performance and versatility. Been there. It's plenty versatile and can run everything I need.
reply