I’d love to give NixOS a try on an old ThinkPad. I’m pretty comfortable with Claude; is it as simple as ask and go, or do you have any suggestions for getting started?
Is this HN user runako’s comment[1] from 2 days ago turned into an article?
I guess it’s very possible multiple people are coming up with the same idea at the same time but given this was submitted by the author it seems kinda rude not to mention it.
Request: “manual step X should not be part of the automated build script”
Fulfilled as: build script is now split in two. X is still done as a manual step in between. Rather than prompting and waiting for it to be done, the documentation and scripts no longer mention X.
Part poorly written requirements, part implementing under pressure, and part lack of engineering discipline.
The main issue is catching stuff like this early enough to course-correct. Differences in time zone, language and cultural norms can make that a challenge, all of which LLMs have the advantage in.
Not the op, but it’s fairly easy to hit if you automate a kanban and have some stuff you want to get done. All those little “wouldn’t it be great if” tasks that show up after doing a big task become very doable, it just soaks your tokens.
Yes, but at this point I'd almost rather have my CC info exposed than my personal info. There is law and consequence for fraudulent charges that protects me from loss (if not inconvenience) but there is basically no protection for playing fast and loose with my PII--in fact, it's the opposite! They sell it!
There was a time when I built games entirely using Visual Studio 6 Edit and Continue. These were the days when debuggers were reliable. Nowadays, I treat the debugger’s output like a best guess: it’s probably right about local variable values and the call stack, but it sometimes has nothing useful to say, and very occasionally is actively misleading.
Thanks for this -- have been using Cody a lot and just tried Windsurf on my hobby project. So far it seems immediately like a step up. Has anyone paid for it? The free version is doing good work.
If a company provides a service for free to enable selling something else, and that something else becomes illegal to sell, then it’s up to the company whether they want to keep offering the free service. They can’t continue doing things that are now illegal just because that’s how they made money in the past. No decision-making power has been taken away.
Google Apps Script can do all of this. Take the email body and put it into a Google doc, then export the doc as a pdf to drive and attach it from there to send.
This is a more interesting take to me than others since it seems you’ve actually learned it?
I see the response later that you’d rather use whatever the team already uses, but could you explain this very strong opinion?
I maintained a 200,000 loc TCL codebase running the front end for millions of lines of industrial C spread over hundreds of machines. It was glorious. After moving on, I’m still struggling to figure out why TCL is so unpopular outside that domain. Other comments seem to boil down to not understanding the language or how to apply it. So what’s your take?