Valodim
Valodim on Hacker News
Like those people who can't drive stick shift. What do they even do if they need to operate a real car?
> I really wish we could leave these types of decisions up to parents and parents only. Leave the companies and governments out of it.
If you'd like to advocate for this position for a living, the tobacco, alcohol, and gambling industries will all be happy to pay you.
It changes the cost of living context of the salary. So, a lot.
*learning opportunity. Damn autotype
Doesn't sound like AI is necessarily the root the problem. If he's not the person to test, iterate, and deliver quality with AI, he probably wouldn't be without it. You just figured it out sooner.
Or, if you have reason to believe he's got what it takes - treat it like an leaving opportunity, give him room to make mistakes. This is, ime, what a rookie AI user mistake looks like.
It is easy to get carried away by the momentum. Many have fallen into that trap, not all are irredeemably bad software engineers.
At Valve's scale, it becomes the publisher's problem. Which is, in this particular case, a good thing imo. I certainly don't mind the pressure on publishers to ensure basic compatibility with Linux
Good article, enjoyed it. I might give this idea a shot!
> Comments: these contain high level descriptions (faster than reading the code) and external context (the “why” that reading code can’t answer). This is the most scannable thing in any big code file.
Not sure about that one, depending on comment culture. Comments are prose and not structured, so to understand their meaning is a lot more cognitive load for me than (most) code. I certainly wouldn't have thought to call them "scannable".
Almost seems like they can do anything at monzo.com
Speak for yourself. It certainly isn't for me.
What are your even talking about, the case here is an internal api change with no change in behavior. It's called maintenance.
Yes, and at that time the answer was "move over where?" now it's 2026 and x-wing is a draft still
There is a whole section in the article about that
You still get snapshots of the working tree every time an agent calls a jj command, including reading ones. This is regular for me that I'm not worried to lose any intermediate state.
It's easy to agree to that, but you're disregarding that the resources you spend on the stronger model could be allocated elsewhere. Conversely, you're assuming that spending more on AI will always yield better results and be worth it, compared to spending the money on other things.
This might actually still hold true now, or or at least many actors in the market behave that way. But I'm not so sure there isn't a cliff to that effect. At some point, if SOTA models remain expensive, it'll turn into a market advantage to figure out how to get things done without depending on the most expensive tooling available.
Similar scenario, different phrasing: if your company relies on overqualified workers to deliver 100% quality, the market may still decide that it's fine to go with 90% quality for 50% the price.
The readme starts by saying how the author used to use atuin, and why they wrote stinkpot as a less featureful alternative.
Genuine question, why? It seems like a reasonable knowledge check that can be answered in a few sentences.
This tends to be necessary as soon as you move any non trivial amount of money around. You can't get a bank account without some bureaucratic overhead
You say that as if it wasn't true for anything human programmers ever produced
Simple to do when you don't care about e2e and clients can just show data they receive to the user with little logic of their own. It is a world of difference in complexity.
Those nice things are what you get when you're fine having all your data (messages, images, files) forever in plaintext on servers owned by some Russian rich guy.
Pray there will never be a telegram.zip torrent.
I'm curious, do you do version control, sync, or work with AI agents? If so, how does that work (for you)?
Even if it was something people wanted, and it wasn't clear that it was even before the advent of CC, abandoning the mainline product for years was a terrible move.
Hopefully they at least got something out of it for themselves from that VC money.
It pains me to say, but it's probably too little, too late. Logseq remained a buggy mess, is now on an unmaintained (thus insecure) version of electron.
And now after several years of complete stagnation, the supposed improvement is a database format to fix their technical issues, so I can no longer keep all my data as markdown files? At a time when half the edits are done by Claude and tracked with jujustu, this is just not useful for me.
All I wanted was the original vision, but with less bugs and more quality of life features.
Did you just paste your marketing copy into a hn comment?
I kind of understand for i18n, but not for most other things
Please buy a license if you are happy with the project :) it's free, but you can still buy a license for a small amount of what you saved
Their business model is basically donations, it's not a for-profit operation. Maybe if you consider yourself less of a customer and more the beneficiary of a community effort, it'll be easier to "get"