@ActuallyATleilaxuGhola's banner p

ActuallyATleilaxuGhola

Axolotl Tank Class of '24

1 follower   follows 0 users  
joined 2022 September 08 09:59:22 UTC

				

User ID: 1012

ActuallyATleilaxuGhola

Axolotl Tank Class of '24

1 follower   follows 0 users   joined 2022 September 08 09:59:22 UTC

					

No bio...


					

User ID: 1012

These aren't innate properties of the left and right, but rather the difference between the internal power dynamics of an ascendant movement with entrenched cultural and bureaucratic power and fragile that has claimed the mantle of Orthodoxy, and the internal power dynamics of a fragile, cobbled-together movement of people with little in common other than having been branded Heretics by that Orthodoxy.

The Orthodoxy can survive internal power struggles and status jockeying because the movement's survival hinges on institutional and cultural control. If one president is replaced with another, it doesn't really matter. The media and institutions will run cover for him regardless of whether he's a charismatic black(-ish) Harvard law professor or a senile, creepy, vaguely racist old white swamp creature.

The Heretics are still shocked to find that they have somehow collectively grabbed hold of a small sliver of power. Many of them recognize that the only reason there's a Heretic coalition at all is that the current Heretic-in-Chief is a rallying point for all groups. The Landian tech bros and the evangelicals might hate each other and want their own guy in charge, but they both realize that replacing the current Chief Heretic would mean that they go from having a sliver of a sliver of power back to having no power at all.

"E-prole" is a great coinage. It captures the alt-slop normie aesthetic while avoiding all three of those now very tired words.

This is interesting and timely for me. We have a legendarily dysfunctional QA team at my company, and as the DevSecSREInfraPlatformOps manager, my biggest beef with them is that they have been killing our Lead Time to Release (time between dev having an idea and that idea getting released as a feature for customers). They manually test almost everything, do nonsensical "verifications" (mocking responses from external APIs when they could just... use the APIs), and don't know how to code at all. Dev and automated testing might finish in a few days, but QA takes 2-3 weeks(!) and they batch multiple changes together which confounds results. They have been given a half dozen opportunities to change and learn but they have always made excuses or refused. At one point they even had convinced a (former) director that they needed outsourced QA members to help with the workload -- and then promptly shifted 95% of their work to the outsourced QA!

Just this past week, I asked for a Claude Code account and started trying to vibe code a replacement for our QA team, partly out of curiosity, partly out of necessity (we have an OKR to reduce lead time), and just a little bit out of spite. I was not optimistic because this is a very poorly documented 10+ year old codebase cobbled together by devs who have all since resigned to escape the mess they've created.

First, I told Claude to pull down all the test suites described in Qase and cache them locally. Then I told it all of the paths to local copies of our frontend, backend, mobile, and infra repos. I asked it to analyze each one. Then, I asked it to begin writing tests for each Qase suite, starting with the simplest ones like "login." Sometimes it would get confused (it shows you its thinking) and I would interject a message (you can send messages while it's thinking, unlike other LLMs) to explain some important bit of knowledge. Eventually, after repeating the same info several times which had apparently gotten lost in the context window compaction process, I told it to create a file called TRIBAL.md to record all of these contextual bits I was telling it that were not evident from simply reading the code. I also had it write a CLAUDE.md that points to all the repos, instructs it to read and update TRIBAL.md, BUGS.md and TODO.md, and contains descriptions of other tools it has created for itself (helper functions, data seeding scripts, env vars and credentials, etc).

So far I don't think I've written a single line of code and it has automated 85% of web QA tests. I have had the test vetted by code rabbit and I plan to check them manually before release. I am quite impressed, though I'm still curious to see how it will try to handle mobile testing. Claude Code really is next level compared to Gemini, Copilot, or Grok.

All that said, I am very aware that this project is probably riddled with false assumptions and nonsense code. I am still not optimistic about the final result, although given how dire QA is, our director might try it out anyway just to see if we can reduce our dependence on them. Either way, it's been a good way to get familiar with a SOTA coding LLM.