> We have a blip in March / April every year; these cyclical patterns aren’t relevant to explain here.
The 'blip' post-AI is up ~30% for the months in question. There simply isn't enough data here to prove or disprove the thesis that "customer issues remain broadly stable" - you could equally argue something more along the lines of "AI engineering does not increase issues under ideal conditions but amplifies issues under external pressure."
"Not relevant to explain this stat" in an article entirely about using those stats to justify their AI policy is brazen, I have to give credit.
One other point of note is that the chart only goes back to January 2025, and only dilineates "majority AI" from "not majority". If the usage rate in January 2025 was at 45%, "issue rate remained roughly stable (with a giant asterisk) when moving from 45% to 51%" is not exactly a compelling story. There's no narrative I trust less than one created by cherrypicking data to lend itself an aura of faux objectivity.
Author here. This is valid feedback, thank you. This post was originally an internal post. Internally, I have credibility as "the guy that does his homework". That doesn't carry over to the broader internet!
I think you're right that the data presented doesn't prove or disprove the thesis that "customer issues remain broadly stable". I think it lends credibility to the idea that "AI didn't lead to an obvious and immediate slopfest of bugs".
As for the bumps, we've noticed them annually and we haven't yet found a solid reason why. There’s no correlation with customer growth, PRs shipped, or features shipped. It's likely a combination of various seasonal effects in our own hiring and customer onboarding. What isn't in this article: we've more than doubled our customer base in this time period, our customers are more mature and raise bugs more readily, we've got ~60% more engineers, and our product surface area has grown a lot too. I'm yet to land on a satisfying metric that normalizes bug rates in a changing environment.
This is a compelling idea, but it doesn't seem to work. Running it on a yml I'm working on currently, it skipped all my setup actions and then failed because the dependencies it needed weren't set up (why did you think I wrote them?) There doesn't seem to be a way to force-run a skipped step.
Thank you so much! Huge bug. Action steps (uses:) were silently skipped, which meant any workflow relying on setup actions would just fail.
This should be fixed in v0.1.3. Action steps now pause instead of auto-skipping, and PipeStep offers to run a local equivalent when one exists. It also parses with: inputs, so setup-node with node-version: 18 actually installs Node 18 in the container. Currently supported: checkout, setup-node, setup-python, setup-go, setup-java, cache, upload/download-artifact. Anything unrecognized gives you a clear pause to run commands manually.
Would genuinely appreciate it if you gave it another shot (pip install --upgrade pipestep) and if you hit anything else, issues on GitHub would be incredibly helpful. The "why did you think I wrote them?" line was exactly the kind of thing I want more of.
Friend. You gotta write your own comments. It feels so gross to get a response that’s so obviously from an llm, I would rather you not have replied to me at all. I will not be using your app.
Fully understandable, it's an AI minefield out there! I wrote everything except the technical summary of what I'd updated, just so you know...Claude only helped me there to explain what had changed.
No, no one has ever known anything, and every day people are born knowing even less. This is a strangely aggressive way to share this interesting information, especially for MacOS programming, a platform requiring such byzantine arcane knowledge I'm amazed people write anything for it at all. At least for Win32 people wrote books you could buy and not blog posts.
Anyway, thank you for the introduction to the very cool SwiftScripting project [0], extracting programmable interfaces directly from app bundles. It's just like COM, right? nice to see MacOS catching up (/ragebait)
Also, FYI the interesting part about the post is getting the extracted code in type-safe Swift code. Getting the extracted code for ObjC is trivial and any seasoned macOS developer should already know how to do it.
sure but they have a blog and a webserver that's serving html. just put the .html version there so i dont have to download anything or mess about too much. just want to click and see it
Standard always struck me as kind of scummy - it tries to present itself as something bigger than what it really is, which is a tiny CLI wrapper around one guy’s ESLint config. You have to scroll way down the FAQ section before ESLint even gets mentioned. The author is just squatting on the “standard” namespace and using it to blag his way into relevance. Think how much more good it would do if the sponsors of this project were actually supporting ESLint directly instead of this useless middleware.
This is normal, most people are like this. The idea that there’s something out there that you’re just amazing at without even trying very hard is a trap and believing it will destroy your life. You just have to pick something you want to be good at and do it until you are.
I think the specific trap the author is arguing against is where you try to make your classes model 1-1 some external domain model without tailoring them only to the functionally that your specific application needs. If you’re writing a FooClass, it’s easy to get caught up in giving it everything a Foo would have, even if you won’t actually use it.
If you’re not familiar with the experience of browsing the internet and then suddenly having deeply-held parts of your identity deemed undeserving of respect, it’s the kind of thing that the mind naturally develops habits to avoid, in much the same way that you might start to walk differently through a city after getting mugged. It is indeed tiring for everyone, but the solution is not to blame people for doing what they feel like they need to do to protect themselves.
That’s the whole point. If you know we are talking about a project name (for instance by using the word in a sentence) then it makes perfect sense, but with no context one is left to try to use etymology like one might do with any unknown word.
I did not, for a second, think, that an unknown word was intended to be racist, ableist, etc.
Why would you?
Also parent's reply:
> If you’re not familiar with the experience of browsing the internet and then suddenly having deeply-held parts of your identity deemed undeserving of respect [...] the solution is not to blame people for doing what they feel like they need to do to protect themselves.
It was a comment under a submission, FWIW.
Seriously though, just stop assuming everything is about race and friends. It is what is tiring. Ask first before making assumptions if it really is not a slur you know of, but an UNKNOWN WORD. If he were to say n***e* then yeah, have at it. That cannot be misunderstood.
And by my reply "That is on you" is down-voted for fuck-all, because people does not realize that the people preoccupied with racism are the ones first to believe it was a racist slur. I did not think it was a racist slur, because 1) it was an unknown word, 2) I am not preoccupied with such stuff, my mind is not filled with racism and such. Thus, the people who say "racist!" usually turn out to be the racists. I have seen it everywhere. Now I saw it on HN, too, which is just splendid. A single search would have sufficed. I do not deny that the person saying the word could have clarified what it is, but defaulting to believing it has to do with racism is one of the reasons for why we have racism. It did not cross my mind. Why did it cross yours, especially if you knew nothing but the unknown word?
I do not see race. Am I the racist one or the people thinking everything is about racism? Do not worry, I see race when it comes to a groups of people, except in that case it does not matter much, a group of people may always be trouble, regardless of race, so no, I did not abandon my self-preservation.
Note that GP didn’t say Meta, the trillion-dollar company, they said Facebook, the social platform that won its generation of social platforms. One of those platforms was bound to win, just by the interconnected nature of social networks, and I think reasonable people can disagree on whether that success sets you up inevitably to make a trillion dollars or not.
The 'blip' post-AI is up ~30% for the months in question. There simply isn't enough data here to prove or disprove the thesis that "customer issues remain broadly stable" - you could equally argue something more along the lines of "AI engineering does not increase issues under ideal conditions but amplifies issues under external pressure."
reply