761–770 of 787 posts
I got inspired so I created this: https://nomeatproxy.com/.
I have ofc linked to your post there as the inspiration :) If you do want to change how you're credited then feel free to contact me (link to my stuff is at the bottom).
Earlier quoted context omitted.
+1 on this being a great idea. I also need to learn how to write in German (I can speak at B2 and read C1, but I find writing difficult as I've never bothered tbh). The added benefit of avoiding Claudisms is interesting. I think I'll join you on this.
FWIW I did a day of German-language software design with Claude and it was great, a bit strenuous of course but I also wonder if it might have found some bugs it would have overlooked in English. If you're doing it for writing practice, one of the good/bad things is that it's quite typo-tolerant (in any language). So you can have the chat with less effort, at the risk of practicing bad habits.
I was asking it to correct my wording as we went along, and despite some weird stuff now and then, e.g. "Abfrage" for query, it was quite good.
I think benchmarking some tasks in both languages would be quite cool. I remember about a year or two ago benchmarking tasks in different languages was quite popular.
Earlier quoted context omitted.
Any non trivial coding task requires a conversation between human and ai. Just have devs commit (or provide however you like) their ai coding sessions. It then becomes obvious if someone has, or has not, reviewed the code, because then they discussed it. Bonus points: on very complex tasks, you can more or less resume the conversation, via session files. Same for schoolwork, research papers, and a lot more. The conve…
I want to suggest you read https://www.amazon.com/Advantage-Disadvantage-History-Hacket... You can't just remember every conversation and ... something useful. Indiscriminate memory buries you. What you need is "monumental" memories, which is also known as documentation. AI can be very effective in helping you manage that. That should be kept tight, just like code. You want to keep enough of a record of how you got t…
I was not really thinking in terms of reusing all knowledge at once.
It is useful to be able to see what was the reasoning behind a single PR to discriminate for effort. The difference between copy+paste+yes+yes+yes+open-pr and asking n relevant questions about the code is what tends to matter.
Also, suppose after a few months you need to look at that code again. Having the possibility to go back and look at what was the human/agent conversation about it helps clarifying which tradeoffs where being considered.
Sticking to PRs (and meat proxy), a discussion over which reasoning led to that code should help a team pick and choose reliable collaborative patterns.
Overall, I don’t think this is a panacea, simply that not storing it feels wrong, to me.
Earlier quoted context omitted.
While I generally agree for general human living, I've seen impressive "digital hoarder" success using AI because it changes the dimensions of reasonableness. Imagine your hoarder scenario except that the hoarder has unlimited storage space and a team of librarian/warehouse workers to go find and fetch the items needed for the wall hanging task.
AI does not have unlimited storage space and digging through tens of thousands of keyword hits will cost you an unlimited amount of money as your history grows and grows.
Pre AI, the equivalent would have been to got blame code you are going to touch to understand in which context it entered the codebase.
Earlier quoted context omitted.
People who uses the word "obnoxious" are also obnoxious. There are many unpleasant words, you have to use some of them and people don't like any of them.
The word “obnoxious” does not carry the connotation of smug superiority that “midwit” does.
Earlier quoted context omitted.
Would you refer to someone as a midwit in a typical office environment and expect your professional reputation to remain intact? If you were to do this on an ongoing basis for whatever reason, how long before you're asked to have a little chat with the folks in HR? Would you then attempt to explain it away as one of those unpleasant words that you just had to use? I want to be there for that conversation.
Different context, different politeness rules. I bet you're fun at parties. An online forum is a relaxed space, like a town pub. HR isn't breathing down our necks here. Personal attacks are a different sort of thing. Using a word to describe in a comment some abstract situations and kinds of characters you see at the office is not a personal attack. There is not one single discourse norm to rule them all and calling…
Earlier quoted context omitted.
The last straw (of many last straws) was over the weekend a co-worker sent me a chat "hey can you click approve on this PR real quick?". This only makes me click "Apply" (jobs) instead of "Approve".
I've been clicking apply myself, but only have had a few interviews. It's bad out there. I've been working since the late 90's and this is the worst job market I've seen in decades.
Earlier quoted context omitted.
I do. I'm pretty sure that at least some humans will shove any Claude answer at you. And some won't. You are assuming that I am making an assumption. Your assumption is wrong. I am recognizing that some humans are lazy and will do the minimum, and the minimum is to type in some query and copy-paste the results. If you like, yes, I am prejudiced - prejudiced against that behavior. (I mean, I still trust a human who kn…
But then we agree. Some humans will behave that way. Then direct your anger against those who do so, instead of against those (the majority) who ask the questions, read and evaluate the answers, and forward them to you only if they think they might be correct and helpful.
Earlier quoted context omitted.
Some skills are easy re-pick-uppable, like bicycling. Mathematics is probably more challenging. Not sure about programming, especially "borint" business-like programming.
Nah. After you have those skills, they don’t go away. Math: the most important stuff is the biggest picture. If you learned it properly (not just memorizing), that’s the last to fade. With programming, the details change but the fundamental skill doesn’t. Or hadn’t as of a few years ago.
Earlier quoted context omitted.
AI does not have unlimited storage space and digging through tens of thousands of keyword hits will cost you an unlimited amount of money as your history grows and grows.
You are assuming a naive approach, always pass everything. Pre AI, the equivalent would have been to got blame code you are going to touch to understand in which context it entered the codebase.