91–100 of 108 posts
That's the good part of AI. Lowers effort and knowledge barrier and makes things possible.
systemctl status 1
sudo lsof +c 0 -i:22> witr is successful if users trust it during incidents. > This project was developed with assistance from AI/LLMs [...] supervised by a human who occasionally knew what he was doing. This seems contradictory to me.
I'd not trust any app that parses /proc to obtain process information (for reasons [0]), specially if the machine has been compromised (unless by "incident", the author means another thing): https://github.com/pranshuparmar/witr/tree/main/internal/lin... It should be the last option. [0] https://news.ycombinator.com/item?id=46364057
While that’s theoretically true in a security context, it feels like a 'perfect is the enemy of the good' situation. Unless the author is discussing high-stakes incident response on a compromised system, discarding /proc-based tools for debugging and troubleshooting seems like throwing the baby out with the bathwater. If your environment is so compromised that /proc is lying to you, you've likely moved past standard tooling anyway.
A quick note on scope: this is not meant to replace existing monitoring or observability tools. It’s designed for those moments when you SSH into a box and need to quickly understand “why is this running” without digging through configs, cron jobs, or service trees manually. Happy to answer questions or adjust direction based on feedback.
I left a different comment, but I think this is good. You're example is 3306 and has a useful breakdown. Not everyone has that port memorized by trauma, and not every mysql instance uses that port. New tools are always welcome, and having a purpose to explain a purpose seems like a good pitch.
This is amazing. Thank you for sharing this. Do you have any qualms about me making an entry in the AUR for this?
I‘m SO going to steal your AI Assistance Disclaimer.
This is amazing. Thank you for sharing this. Do you have any qualms about me making an entry in the AUR for this?
Not sure if you're the one who created it but the AUR for this is present and needs update for the latest version - https://aur.archlinux.org/packages/witr-bin
Earlier quoted context omitted.
Neither do you need and IDE, syntax highlighting or third party libraries, yet you use all of them. There's nothing wrong for a software engineer about using LLMs as an additional tool in his toolbox. The problem arises when people stops doing software engineering because they believe the LLM is doing the engineering for them.
I don't use IDEs that require more time and effort investment than they save. You mileage may vary, though. Lots of software engineers love those time and effort tarpits.
Every IDE I've used just worked out of the box, be it Visual Studio, Eclipse, or anything using the language server protocol.
Having the ability to have things like method auto-completion, go-to-definition and symbol renaming is a net productivity gain from the minute you start using it and I couldn't imagine this being a controversial take in 2025…