What a joke. Eff complains that Musk threw out the previous censors. It's been well documented they were censoring in bad faith. Effectively the Eff wants the bad censors re-installed.
a project isn’t dying because of no commits. Rather it’s stable
I often feel I need to setup bots to make superfluous commits just to make it look like my useful and stable repos are “active”
One example (not mine) a a qr-code generator library. Hasn’t been updated in 10 years. It’s perfect as is. It just provides the size and the bits. You convert those bits to any representation you want. It has no need to be updated
It's rare, I think, for a project to have such a well defined and singular purpose that has not changed in 10 years nor have any bugs been discovered or its dependencies changed underneath it.
It's not impossible, of course, but if I saw even a qr library that hadn't changed in 10 years I would worry that it wouldn't build on current systems (due to dependencies) and that nobody was actually using it (due to lag of bug reports).
I have several of those projects. I avoid dependencies as much as possible, striving to only use things which I know ship with my target OS. I code for a level of correctness and longevity. That benefits everyone, including myself.
A QR (or barcode) library is exactly the type of thing I’d assume would still work fine, since there’s nothing new to do, the parsing rules don’t change, it’s a static, known, solved problem.
> A QR (or barcode) library is exactly the type of thing I’d assume would still work fine, since there’s nothing new to do, the parsing rules don’t change, it’s a static, known, solved problem.
I agree with you - and yet the barcode library I used recently for a variable-data-printing project was last updated 13 hours ago, despite having been around since 2008!
Well said. Even an awesome library with no bugs that has no external dependencies still depends on the stdlib. For a while, before we were using containers, we even had the issue on Mac dev machines especially, where a half dozen Rubygems would crash while building its C extensions if your Mac OS version wasn’t just what the author expected, due to changes in the compiler shipped by Apple. So a MacOS major update might on its own functionally break a gem, even if the gem itself was designed well and you were using the same Ruby version.
This might be true for libraries or utilities that have a well-defined scope and no dependencies, but that's not what the article is focused on. When considering a company's main product, it's usually never done and patterns of activity—and especially changes in those patterns—can give you insight into potential issues.
In a real company? A private codebase at a minimum should still be getting regular security patching and dependency updates. Always eventually one of those updates requires some level of refactor. If I see a project with no commits, I run away.
> a project isn’t dying because of no commits. Rather it’s stable
Agreed. Assuming there are no open issues and PRs. When I find a project, if the date of the last commit is old, I next look at the issues and PRs. If there are simple-to-deal-with issues (e.g. a short question or spam) and easy-to-merge PRs (e.g. fixing a typo in the README) which have been left lingering for years, it’s probably abandoned. Looking at the maintainer’s GitHub activity graph should provide more clues.
> I often feel I need to setup bots to make superfluous commits just to make it look like my useful and stable repos are “active”
I have never done it, but a few times thought about making a “maintenance” release to bump the version number and release date, especially since I often use a variant of calendar versioning.
Today: Ask AI to "do the thing", manual review because don't trust the AI
Tomorrow: Ask AI to "do the thing"
I'm just getting started on my AI journey. It didn't take long before I upgraded from the $17 a month claude plan to the $100 a month plan and I can see myself picking the $200 a month plan soon. This is for hobby projects.
At the moment I'm reviewing most of the code for what I'm working on, and I have tests and review those too. But, seeing how good it is (sometimes), I can imagine a future where the AI itself has both the tech chops and the taste and I can just say "Maybe me an app to edit photos" and it will spit out a user friendly clone of photoshop with good UX.
We already kind of see this with music - it's able to spit out "Bangers". How long until it can spit out hit rom-coms, crime shows, recipes, apps? I don't think the answer is "never". I think more likely the answer is in N years where N is probably a single digit.
No, I don't think it is temporary. As AI becomes more powerful, we'll simply ask it to do more difficult things. There's a level of complexity where "do the thing" is insufficient. We'll never be at a place where AI can infer vast amounts of nuance from simple human requests, which means that humans will always need to be able to describe precisely what they want. This has always been the core skill for software developers, and I just don't see that changing.
It's not a matter of whether it surpasses me. In some respects it already has - I watch Claude Code spitting out long terminal commands that I've never even seen in my 15 year career.
The question is whether AI will ever become good enough to magically infer information where none is provided.
For instance, I've had this startup idea for an itemized physical storage company. We'll never reach a point where I can simply say "Hey AI, create all the software necessary for an itemized physical storage company". It's not because AI won't continue to improve, it's because there's literally not enough detail in that statement to understand what I mean. It's too vague. I'm sure the AI of tomorrow could do a pretty good job in guessing what I mean by it, but the chance of it capturing my vision is literally 0%.
It might have a better vision than you and pursue that vision instead. Why should the AI wait for your impetus when countless founders and CEOs didn’t?
AI has no intrinsic way to align its efforts to solve human problems. In order to solve that problem, you'd need an enormous amount of nearly real-time data feeding into the model. Then the model would need to routinely look for patterns and identify ways to improve human life in some way. It would make today's models look tiny by comparison.
What we're building today isn't even remotely close to that.
I don't know anything about Oklahoma City but I'm pretty confident that SF is a shit hole having lived there up to 2024 and seeing it first hand every day. Any stats that claim otherwise are lying.
It's not designed for anyone to go though - Yesterday I setup an Nintendo Switch for my Uncle. There were so many steps it was ridiculous. Off the top of my head
1. enter your language
2. enter your region
3. enter your wifi and password
4. select your wifi (why 3 didn't do this I have no effing idea)
5. create a MII, you can't skip this step though you can pick a pre-created one
6. link your MII to an account - you can skip this but the device is useless without an account if you didn't buy games on physica media
7. Setting up an account shows a QR code so now you have to get our your phone
8. Enter your email and get send a verification email
9. switch to your email app and find the code
10. switch back to your browser and enter the code
11. Fill out your name/address/phone etc....
12. Now you want to download an app so you can use your switch so, pick e-store
13. Get QR code and scan
14. Get told you were sent another email verification
14. Go to email app and get code
15. Switch back to browser and enter code
16. Type in your CC Card info
17. Now pick a game to purchase
18. The purchase button is off screen after a bunch of legalize before it and no indication you need to scroll down
19. Choose purchase
20. Get told you need to verify again (in a tiny box you can check "remember me")
there were more steps. The whole process took about an hour, maybe longer
Even with all of that, there just a ton of stuff about a Switch that's taken for granted or poorly designed. As an example, he wanted to play Switch Sports Golf. The Switch home screen assumes you're using both controllers. At some point Switch Sports Golf switches to using just one controller. That's not clear at all. Another example, you pick Golf. It displays a screen showing you to hold the controller down and press the top button (X), but also on that screen is a generic, "press (A)" to continue this dialog. It's a very poorly designed screen giving to conflicting directions.
A business doesn't have to serve all customers. You can't walk into 99.99% of USA stores and pay in rupees or yen or yuan. This is no different. They can choose what they accept and what they don't. Just like not every store takes credit cards or doesn't take certain credit cards (discover, amex) or doesn't take bitcoin.
Unfortunately there is a ton of pressure not to review code. AI enthusiasts see themselves in a race against others and code review = going slower. I recently attended a company wide "let's all use AI" conference and several talks were about how they were not reviewing much code anymore because the PRs were coming in 10x to 50x more and they just couldn't keep up.
I’d be happy to use the app if they didn’t suck. The websites have more info and the browser is more capable by default. Like by default I can select any text I see, an address to copy into a calendar, a phone number to send to someone else, a name I want to paste into a search engine. an app is the opposite, by default nothing is selectable and I’m at the mercy of the nearly universally bad UX designer’s whims
reply