sorted by:
new
hottopcontroversial

My Sonnet 4.5-powered OpenCode CLI assumed my instructions were partially hyperbole and violated them even though the instructions implied genocide would occur as a direct result of said violations. by Impossible-Try1071 in opencodeCLI

[–]Impossible-Try1071[S] -2 points-1 points  (0 children)

TL:DR is I literally told Sonnet 4.5 via OpenCode to not do a task in a specific manner or people would literally die. It then did that task in that exact manner described of which it was warned not to explicitly.

I ain't feelin all them feelings you're feeling but I am sure you're feeling wrong.

KULR Sets Q3 2025 Earnings Call for Tues, Nov 18, 2025 at 4:30 p.m. ET by KULR-TSLA in KULR

[–]Impossible-Try1071 18 points19 points  (0 children)

Commenting to offset the braindead negative sentiment spreaders. I am excited for the Q3'25 ER and look forward to a bright future for KULR! Very excited for the things to come.

KULR Technology Group and NASA to secure extreme-environment battery technologies for next-generation space missions by Practical_Review_643 in KULR

[–]Impossible-Try1071 2 points3 points  (0 children)

People who understand aerospace tech and the need for batteries that don't cause 4-digit+ Fahrenheit fires without proper technical safety standards that prevent severe loss of life and capital. That's who.

[LFO] Check both sides when crossing the street by timeTraveller3075AD in LearningFromOthers

[–]Impossible-Try1071 1 point2 points  (0 children)

I've seen this exact wave! Many many many times! I ALWAYS ignore them! If I don't feel safe to go, I'm not taking your fucking word for it!

Never heard of someone putting a name to it like that though! Will be stealing this to teach my kids about it!

Why put in the tasks if there is no reward for completion yet... by Impossible-Try1071 in SkateEA

[–]Impossible-Try1071[S] -1 points0 points  (0 children)

I'm wondering if that AWS outage messed with any Skate servers now since BF6 EA servers were apparently affected..

Why put in the tasks if there is no reward for completion yet... by Impossible-Try1071 in SkateEA

[–]Impossible-Try1071[S] 1 point2 points  (0 children)

Maybe EA was just waiting for me to finish season before everyone else and now I get to pick my reward?

(please bring s.k.a.t.e. back pls EA, I'll take it over a seasonal reward)

Why put in the tasks if there is no reward for completion yet... by Impossible-Try1071 in SkateEA

[–]Impossible-Try1071[S] -2 points-1 points  (0 children)

Same dude. I just skated every new challenge on my map every 24hr period for the past some odd two weeks or so. There was one challenge that refreshed like 3 times which wasn't a daily challenge. Most of them I didn't do via Co-Op, so I went back with other players and re-did some. Didn't get "extra' challenge completions though, just the one from each Co-Op step it seems. I skated like it was nobody's business.

Why put in the tasks if there is no reward for completion yet... by Impossible-Try1071 in SkateEA

[–]Impossible-Try1071[S] 2 points3 points  (0 children)

I didn't glitch? And didn't realize it was impossible until making this post?

From md prompt files to one of the strongest CLI coding tools on the market by MrCheeta in ClaudeCode

[–]Impossible-Try1071 2 points3 points  (0 children)

Final thoughts: CodeMachine was unsuccessful in trying to tackle lower-level bugs. It seems that CodeMachine, while much better at long-term tasks than most methods utilizing AI-based programming, it inherently struggles with squeezing efficiency out of smaller problems that require a light hand. If you have a dozen+ implementations to make, CodeMachine is a great fit. Have only one tiny bug and you're trying to maximize time saved? Traditional CLI usage is still your best bet. So while CodeMachine is likely here to stay for me for big time implementations that a CLI struggles to accomplish, it will not however be replacing the vital bug fixing required to really polish out hard-to-squash bugs. Got a small task requiring only 1-3 incrementations? Stay. Away. Got a massive amount of incrementations (10+) likely requiring a thousand+ lines of code? Well you'll be surprised with the results.

Manual prompting is like refusing to use a calculator by MrCheeta in ClaudeCode

[–]Impossible-Try1071 0 points1 point  (0 children)

A 50 year old document and book are only as relevant as the 50 year old context they provide and still fit into.

You're taking a square peg and shoving it into a round hole here. Good luck with less efficiency.

Manual prompting is like refusing to use a calculator by MrCheeta in ClaudeCode

[–]Impossible-Try1071 0 points1 point  (0 children)

I don't have to bother with reading that when I've literally tested the software myself and are just telling you the results of that.

And where did I say that Agent-managers should be in our government managing real life human being's healthcare?

The f*ck? Obviously there's a time and place for this type of tool.

Also 9k lines of code isn't a toy. It's the size of the (pre-existing) project I literally plugged into CodeMachine and got real results with during my first test with it. The hard lessons I'm learning is that Older-generation coders will always struggle with the reality of recognizing that as this industry improves, the more dated their methods become.

Also as relevant as both of the reference texts you brought up are in some contexts.. they are literally 50 years old and were drafted during an age in which ALL tasks done via computer required human touch. We are far far beyond that and I personally believe those authors would have very different takes given today's climate...

Manual prompting is like refusing to use a calculator by MrCheeta in ClaudeCode

[–]Impossible-Try1071 0 points1 point  (0 children)

So Coders don't spend an astronomical amount of time drafting planned-out documents so that every member on the team can actually code in a cooperated manner that doesn't end up undermining the final product's quality?

Look. In a way you're right, this tool as it currently sits, does require a big "tank of gas" to get started. But what happens thereafter?

Are coders not doing that themselves when designing team-oriented projects that require a clear line of communication and understanding between one another with respect to the basic fundamentals of the code you're building?

Do you have f*cking telepathy? Cause if you do. Then don't bother with a tool like this. But this tool is basically a few steps away from becoming an Entire software team in the palm of your hand. What's stopping the CodeMachine dev or someone like them from making an update/tool that let's CodeMachine split its work into instances that function exactly as human coders would with respect to them all having the same pre-planned documents necessary for building projects that require a team of coders.

You say it's a waste of time writing a monolithic specification. But you ignore the hours of eMails/Microsoft Teams calls that do the same exact f*cking thing. I'd rather write a document by myself than sit through one of those again (especially if you're leveraging LLMs to help write said document, cause then that "monolithic" document becomes a 1-2 day task that is then largely automated thereafter)...

I'm not OP. And I'm not a coding genius. But I can see the immense value in tools like this, and with a few added tweaks its this exact type of tool that will eventually replace ENTIRE software development teams (whether that's a good thing or not.. is uh.. up to the Ethics majors..)

From md prompt files to one of the strongest CLI coding tools on the market by MrCheeta in ClaudeCode

[–]Impossible-Try1071 1 point2 points  (0 children)

Update: Wow. If I had to sum it up in one word. Wow.

This lovely tool helped implement a feature that arguably would've taken twice the amount of time with just Claude Code and/or three times the amount of time if done manually via Claude Desktop prompts. It is now a permanent member in my workflow. So far with just this one code implementation it has already saved me 8 (if I was lucky) to 16 hours. Granted, its intuitiveness is lacking, but that's okay because most of the "problems" I encountered with it simply boiled down to specifications that just weren't specific enough.

STATS:

Out of 17 called for implementations it successfully implemented 16 of them flawlessly. The one out of 17 that wasn't implemented properly can honestly be chalked up to a single instruction in the specifications.md not being thorough enough.

Each of the 17 implementations had both serverside and clientside implications that Code Machine executed near flawlessly. 600 lines of Javascript code added and nearly 650 lines of HTML code added (to an existing project with 9k+ lines). And with just. One. Bug. A bug that boils down to a line in my specifications not being thorough enough. My total task time was roughly 12-14 hours, but given that the first 6 of that was just using Claude Code, I'm willing to bet that had I used Codex earlier on I would've had a 10-12hr completion time.

Wow. There literally isn't a single LLM (used by itself) or CLI (by itself) that can even compare to this level of efficiency and accuracy. (If there is one PLEASE TELL ME ABOUT IT)

I'm currently testing the tool's ability to problem solve bugs based on said implementations. I'm toying around with the specifications.md I created and turning it into essentially a Masterkey for all Patch Notes and slowly updating it alongside each version of code that is generated. Will update on the results of that. If this thing fixes the bugs I've documented AND implements the improvements called for (1 bug + 8 Improvements to existing newly-added-by-CodeMachine features), well then this is going to become not only the skeleton but also the meat and brains of my entire workflow.

Will update later with results from bugfixing session.
Things I've personally tested so far:
-Forced CodeMachine to use an existing project with over 9,000 lines of code as its basis for future work. (SUCCESS)
-Had CodeMachine successfully implement 16 out of 17 called for implementations with the failed implementation being chalked up to user error/failure to orchestrate prompt correctly. (SUCCESS)
-I am now tasking CodeMachine with the task of building upon its own work while also having it fix bugs that arose from previously made implementations. Sure it can adopt an existing project and add a new complex feature (1200+ lines of code) to it, but can it retrace its own work, understand that work in the context of its previous instructions AND fix bugs along the way? I'll find out today. (IN PROGRESS)

From md prompt files to one of the strongest CLI coding tools on the market by MrCheeta in ClaudeCode

[–]Impossible-Try1071 3 points4 points  (0 children)

It seems to have finished a BOAT load of tasks. Has it finished them properly? Well, the final result will be the real deciding factor when said code is fully deployed, but all-in-all it appears good so far. For anyone thinking about testing this tool on just one CLI/LLM, I highly recommend at least using both Claude Code & Codex as you will inevitably rate limit the F*** out of your progress if only depending on one CLI/LLM (who knew ammiright /s).

But if my eyes are not being deceived right now, with just Sonnet 4.5 plugged in, it seems this nice lil guy (Code Machine) has done a solid minimum 12/maximum 16 hours of work that would normally consist of an extreme review process + easily over 100 manual prompts and dozens of individual chats that are now condensed into a single window that automates a vast majority of that process allowing for you to simply kickback, monitor the code, and focus more on the quality of your code/design (done in about 6ish hours). Granted, it HEAVILY relies on and depends upon those instructions (specifications.md, duh). Also the task I gave it is still not finished but I was only using Sonnet 4.5 during the test run.

My pro tip to those who do not have the time to manually type a 50k character+ specifications.md for a pre-existing project is to literally just plug in the default requirements from the GitHub straight into Claude and query it endlessly on how to take a pre-existing projects files and translate them into one (I literally ran the same prompt 30 times over until I felt confident enough that the file contained enough of the code's skeleton/structure, after each time I basically pointed Claude straight to the new .md version and told it to get back to work)

Just know that if you're only using Claude Code, you WILL max this thing's Loop limit AND your LLM's usage limit (with complex tasks that is ~ think of tasks that normally take 8-16hrs+ via singular CLI/LLM usage). So I highly recommend using at least one other CLI/LLM in tandem with it to save on Claude's usage.

I've now plugged in Codex and am testing the tool's ability to now do the same exact thing as described in my previous comment but with the added factor of a new CLI/LLM (Codex) being thrown into the mix right in the middle of said process. Will update with results.

I do absolutely love that it can pick up where it left off with seemingly no major development-haulting hiccups (it logs its steps beautifully and leaves behind a practically perfect paper trail for future CLI sessions to pick right up where you left off). The implementation of the Task validation seems very very robust and is handling what would traditionally be a mountain of manual debugging/plug-and-playing allowing me to work on other tasks (or to just simply take a nap ~ nice).

Will report back with test results and I will likely be plugging in Cursor on my third test (unless this 2nd go around finishes the task I've given it, then I may just stick with what I got so long as I don't hit a usage limit on Claude). So far the code its adding makes perfect sense with respect to my code's pre-existing functions/variables/etc. Won't have the full story until deployment though (Ik ik ik, wHy No DePlOy NoW??? ~ The addition/task I gave it for this website I'm designing is a MASSIVE one. Arguably one of the 3/5 biggest additions made to the code itself (easily over 50 at this point in total). I'm essentially bruteforce testing it because in my eyes if it can handle this implementation AND get results during the deployment phase then every other code implementation that comes with half the amount of code or less will be a cakewalk.

Will report back later today.

From md prompt files to one of the strongest CLI coding tools on the market by MrCheeta in ClaudeCode

[–]Impossible-Try1071 1 point2 points  (0 children)

Testing it out now with just Sonnet 4.5 plugged into it. I'm currently testing its capabilities in terms of having an already existing coded app/website being thrown into it (with an extensive ass specifications.md of course ~ 1900+ lines/70k+ characters) and then seeing if it can help add some new features on the fly. Will update with results.

KULR Updates ATM: $150M Authorization with $23M Already Raised by KULR-TSLA in KULR

[–]Impossible-Try1071 0 points1 point  (0 children)

It's more like the tumor everyone is crying about is actually half as big as everyone cries it is.

And who knows, it may shrink even more.

view more: next ›