MoreQARespect

11 ms·

1.
by MoreQARespect 1mo ago
I had a similar experience when I tried to search through reviews on amazon on the mobile website. The search box is gone and you're supposed to ask Rufus now.
2.
by MoreQARespect 1mo ago
There are plenty of alternatives for git hosting. The last thing which needs to be migrated before we get an exodus off this vibe coded monstrosity is reputation (i.e. github stars) which are inherently sticky.
3.
by MoreQARespect 1mo ago
I guess that was google wave and yea it was a horrorshow. I had hoped that something useful would come out of blockchain technology that would allow for a better messaging protocol that was spam resistant, e2e encrypted and decentralized by
4.
by MoreQARespect 1mo ago
Email can't really change much. The protocol is too old. It would be better if we came up with new protocols that solve the email messaging problems and then gradually wean ourselves off email rather than trying to "fix" emai
5.
by MoreQARespect 1mo ago
I don't think so. Natural language is vague and repetitive. I used hitchstory (YAML based stories) for doing this coz it's terse and typed. I've tried using cucumber before and it reminds me of COBOL - which also had the same
6.
by MoreQARespect 3mo ago
>This is the problem: your judgement is biased. You think it was a good idea, but in reality, you have no real idea if it was or not. My judgement is based upon my experience trying it both ways many times over the course of decades. &
7.
by MoreQARespect 3mo ago
It's predicting that you will predict wrong frequently enough to make it not worthwhile predicting at all. I apply the same logic at slots: the way to win is not to play. >Creating abstraction for a code that was designed without be
8.
by MoreQARespect 3mo ago
>Building speculative structure can be a forcing function to establish requirements Sure, if you're doing it as a spike but if you're not throwing the code away then it functions as a forcing function for creating slop.
9.
by MoreQARespect 3mo ago
YAGNI is simply a tacit recognition that you can't predict the future with any reasonable level of certainty. The reason it is controversial is that some devs truly believe that they can predict the future with all the self assurance
10.
by MoreQARespect 3mo ago
This study seems to be mainly about the value of vibe coded tests and not at all about TDD. Perhaps unsurprisingly it found that vibe coded tests suck. As a card carrying member of the "church of TDD" (I do think it is practical),
11.
by MoreQARespect 3mo ago
yes, there is some yak shaving necessary to make writing tests possible. There is often a tension between delivering fast and high quality/bug free and what is necessary for medical software or financial calculations might not be neces
12.
by MoreQARespect 3mo ago
Iterate on the design til the snapshots look the way the design team wants. That's just an extended red where you get feedback from elsewhere.
13.
by MoreQARespect 3mo ago
Um, show the snapshot to a designer? When it feels right, lock in the snapshot ("green") and then move on to refactor. Or, probably more likely a group of snapshots.
14.
by MoreQARespect 3mo ago
snapshot test driven development again. i already wrote a similar answer in response to your other comment. it follows the definition of TDD and it works really well (with some caveats) but again some people get hung up on what their imp
15.
by MoreQARespect 3mo ago
https://hitchdev.com/hitchstory/approach/snapshot-test-drive... set up a rendering profile and preconditions that generates a minimal snippet of images/video using a predefined GPU profile. then test for eith
16.
by MoreQARespect 3mo ago
That is a flaw with unit tests written at far too low a level, not with TDD. You would have the same problem if you wrote tests like that after the code. TDD has no opinion about the level at which you wrote your test, it just assumes it&#x
17.
by MoreQARespect 5mo ago
The problem with gherkin is that it was a badly designed language. The general idea of "readable specification language" was an inspired one but it failed on execution - it has gnarly syntax, no typing and bad abstractions. This r
18.
by MoreQARespect 5mo ago
Yes, except a test can be turing complete - i.e. code. An executable spec like gherkin or hitchstory is config - it has no loops or conditionals. There are a number of rarely recognized benefits to this.
19.
by MoreQARespect 6mo ago
Ive almost never worked on a project where there was the right number of QAs who were doing the right thing. Usually there either arent any in which case bugs get missed or there are 5 very cheap ones running mindless scripts who are standi
20.
by MoreQARespect 6mo ago
Really? The best people I worked with were never QA. Moreover, the best QAs would almost always try to be not QA - to shift into a better respected and better paid field. I wish it werent so (hence my username) but there is a definite class
21.
by MoreQARespect 6mo ago
I never said he was "truly independent" nor meant to imply it. Nonetheless it looks like he was both willing and able to push back on a good deal of the AI stupidity raining down from above and then he was removed and then, well,
22.
by MoreQARespect 6mo ago
It operated with an independent CEO for a long while. When I saw his interview: https://thenewstack.io/github-ceo-on-why-well-still-need-hum... i thought "oh, there is some semblance of sanity at Microsoft". This
23.
by MoreQARespect 6mo ago
This makes much more sense as an zoom-buys-keybase style acquihire. I bet within a month the astral devs will be on new projects. Bundling codex with uv isnt going to meaningfully affect the number of people using it. It doesnt increase the
24.
by MoreQARespect 6mo ago
any of them.
25.
by MoreQARespect 6mo ago
Putting LLMs on a pedestal is very much in vogue these days.
26.
by MoreQARespect 6mo ago
Humans have the ability to retrospect, push back on a faulty spec, push back on an unclarified spec, do experiments, make judgement calls and build tools and processes to account for their own foibles.
27.
by MoreQARespect 6mo ago
I've been trying to push people to use hitchstory or similar to generate docs from specification tests precisely to avoid that redundancy but most people just look blankly at it and go "why don't you just do that with AI?&quo
28.
by MoreQARespect 7mo ago
Youve been able to hire a dirt cheap Indian or fillipino living on poverty wages in those countries to knock out cheap crap for a long time.
29.
by MoreQARespect 7mo ago
This is all good advice.
30.
by MoreQARespect 8mo ago
I find that 80% of the time the assumptions i made doing detailed planning are invalidated when doing the actual work. Usually whole subtasks need to be junked and others created.

More ›