deergomoo
What's worse is that, while I can find other reports online, it doesn't seem to be a particularly widespread bug (my work Mac doesn't exhibit it at all), which means I'm probably gonna have to wait for it to be fixed incidentally when some Apple engineer makes an unrelated change to the Dock codebase in about four years time.
Of course, these days a three or four or more year old phone is often still perfectly usable even for a tech enthusiast.
I may be swayed by a second gen Air in the spring, as I would like a lighter phone that feels less of an imposition in my pocket and my life in general. But it almost certainly won’t have the zoom camera, which has unexpectedly become one of my favourite and most used features of the 17 Pro. Why the two-camera phones all come with the ultrawide instead of the telephoto is baffling to me. Perhaps I’m an anomaly, but I never use the ultrawide lens.
The areas where the iPad beats the MacBook are still (imo) the same as the day it launched: web browsing, watching video, and reading. Workloads that are heavy on the Apple Pencil too, but that’s a fairly narrow slice compared to anything else you might do on a computer.
> Never write READMEs, docstrings, or comments. I will write those myself later. And yes, I really mean this.
This is quite validating as I came to the exact same conclusion myself. We’re required to use an LLM for every task at work that touches code†, and I was really struggling to get Claude to stop with the long waffly comments that reiterate the next few lines of code in 3x as many characters, making contextless references to subtasks in whatever harness du jour we’re using this week.
No amount of examples or explanation of what I wanted would make it stop. And then I realised of course, I’m asking something which has no concept of meaning (or, indeed, anything) to only add meaningful comments. More fool me I guess.
Of course, it’s ultimately pointless given all of my colleagues are regularly opening PRs with more comments than code anyway. 80% of my code review responses these days are just increasingly exasperated “pointless comment, please remove”.
† This is just as infantilising as it sounds, by the way
Before I turned it off, my car would regularly beep frantically and try to steer me into the parked cars. Thankfully it’s a 2022 model so now I’ve turned it off, it stays off.
For who? Regular people are quite famously not clamouring for more AI features in software. A Siri that is not so stupendously dumb would be nice, but I doubt it would even be a consideration for the vast majority of people choosing a phone.
I would also call designing a system to be fed into an LLM designing. But I wouldn’t call it programming.
If people are more into the design and system architecture side of development, I of course have no problem with that.
What I do find baffling, as per my original comment, is all the people saying basically “programming is way more fun now I don’t have to do it”. Did you even actually like programming to begin with then?
But saying that AI development is more fun because you don’t have to “wrestle the computer” is, to me, the same as saying you’re really into painting but you’re not really into the brush aspect so you pay someone to paint what you describe. That’s not doing, it’s commissioning.
Software development was already one of the most democratised professions on earth. With any old dirt cheap used computer, an internet connection, and enough drive and curiosity you could self-train yourself into a role that could quickly become a high paying job. While they certainly helped, you never needed any formal education or expensive qualifications to excel in this field. How is this better?
It may be more extreme than what you are suggesting here, but there are definitely people out there who think that code quality no longer matters. I find that viewpoint maddening. I was already of the opinion that the average quality of software is appalling, even before we start talking about generated code. Probably 99% of all CPU cycles today are wasted relative to how fast software could be.
Of course there are trade-offs: we can’t and shouldn’t all be shipping only hand-optimised machine code. But the degree to which we waste these incredible resources is slightly nauseating.
Just because something doesn’t have to be better, it doesn’t mean we shouldn’t strive to make it so.
Uhhh no? I’m good thanks
I very much disagree here. To make any sort of progress in AoC, in my experience, you need at least:
- awareness of graphs and how to traverse them
- some knowledge of a pathfinding algorithm
- an understanding of memoisation and how it can be applied to make deeply recursive computations feasible
Those types of puzzle come up a lot, and it’s not anything close to what I’d expect someone with “just a little programming knowledge” to have.
Someone with just a little programming knowledge is probably good with branches and loops, some rudimentary OOP, and maybe knows when to use a list vs a map. They’re not gonna know much about other data structures or algorithms.
They could learn them on the go of course, but then that’s why I don’t think basic coding knowledge is enough.
Every time I see this I wonder how many amateur/hobbyist programmers it sets up for disappointment. Unless your definition of “pretty far” is “a small number of the part ones”, it’s simply not true.
Also, "democratizing"? Please. We're just entrenching more power into the small handful of companies who have been able to raise and set fire to unfathomable amounts of capital. Many of these tools may be free or cheap to use today, but there is nothing for the commons here.
Yes, obviously yes. In the same way we teach people to operate cars safely and expect them to carry and utilise that knowledge. Does it work perfectly? Of course not, but at least we entertain the idea that if you crash your car into a wall because you’re not paying attention it might actually be your fault.
Computers are a critical aspect of work and life. While I’m a big proponent of making technology less of a requirement in day to day life—you shouldn’t need to own a smartphone and download an app to pay for parking or charge your car—but in cases where it is reasonable to expect someone to use a computer, it’s also reasonable to expect a baseline competency from the operator. To support that, we clearly need better computer education at all ages.
By all means, design with the user’s interests at front of mind and make doing the right thing easiest, but at some point you have to meet in the middle. We can’t reorient entire industry practices because some people refuse to read the words in front of them.
I should be able to create a Jira ticket in however long it takes me to type the acceptance criteria plus a second or two. Instead I’ve got slow loading pages, I’ve got spinners, I’ve got dropdowns populating asynchronously that steal focus from what I’m typing, I’ve got whatever I was typing then triggering god knows what shortcuts causing untold chaos.
For a system that is—at least how we use it at my job—a glorified todo list, it is infuriating. If I’m even remotely busy lately I just add “raise a ticket for x” to my actual todo list and do it some other time instead.
Modern Apple presentations are just like being read some marketing materials. It's very disingenuous.
This has been Alan Dye's modus operandi since he took the helm on software design and the problem is it does not scale to larger devices. On a phone and mostly on an iPad, where you're far more likely to be consuming content anyway, it's not the worst thing to shoot for.
On a Mac it's infuriating. I'm working on anywhere from a 14" to a 27" display, both have a wealth of pixels to work with: why are you hiding controls? You're not making anything simpler, I need those buttons to perform the tasks I'm trying to do. All you've done is make it less intuitive, less discoverable, and added extra clicks.
To be honest it has some problems even on the smaller devices too, mainly in the form of lack of visual affordances. So much functionality you would never discover unless you'd seen someone else do it or triggered it by accident (and even then might not realise what you've done—just yesterday I had to help my mother get out of private browsing in Safari because she'd swiped across to it and didn't know how to get back).