353 karma · joined November 5, 2024
However, the whole "Spotify is terrible for artists" argument seems ill considered. Terrible compared to what? I lot of what I buy is relatively niche artists on relatively niche labels, who would never have been signed to a major and would never had had international distribution. These artists can't make a living through streaming, sure, but I don't think they could have made a living in the old world, either.
I still have a Spotify subscription - mostly for the family - but I use it to listen to albums before deciding to buy them. I'd buy a lot less if I couldn't vet it on Spotify first.
A lot of artists seem to think that they're entitled to make a living off their art, which seems to me to completely misunderstand the history of the music industry.
I'm mostly photo editing (Exposure, XnView, Nitro) or doing small dev projects (VSCode, Rider). On a my old Dell laptop with 16GB RAM, I'd have to actively monitor RAM usage if I wanted Exposure to run well, shut down most other apps etc. On my MBP with 16GB, it has never been an issue.
Right now I have: Mail, LibreWolf, Signal, Jellyfin, Bitwarden, LibreOffice, XnView, Nitro, Terminal, Safari, Calibre, Remote Desktop, WIIM Home, Notes and Rider open, along with a host of background things like VPN, Syncthing etc. Activity Monitor says 14.2GB used. But I'm not sure if that number matters, because I've never noticed running out of RAM.
It pretty much is that simple. The problem is that simple is not easy.
What makes software hard to estimate is not so much the work, but how much requirements, priorities and resourcing change on the fly. I've worked in places that did quite strict scrum: once the sprint was planned and agreed to, we pushed back hard on our business area if they wanted to change anything. For practical reasons we didn't outright ban it, but for example, if they wanted something new done "right now" they had to choose something of roughly the same scope to be removed. If they couldn't do that, we'd cancel and re-plan the sprint. They hated having to make that choice, so most things just ended up at the top of the backlog for the next sprint.
The other part was our own management wanting to take people out of the team mid-sprint to work on something else. We never said no, but did say "this means we have to cancel and re-plan the sprint (and tell our business area)".
Basically, we made the people making the changes take responsibility for the impact on deadlines. Our estimates in that scenario were quite good (within the bounds of the sprint, at least).
Of course, the longer the estimation window the less well this works. The only way to estimate accurately is to constrain scope and resources, which is not actually what management/business want.
This assumes that people are employed only because of their productivity, and that productivity can be replaced with AI.
You can't AI-away bureaucracy, because a bureaucracy's incentives are not efficiency or productivity, but the perpetuation of bureaucracy. Sure, in the future a lot of the "actual" work might be done by AI - but right now a lot of that "actual" work is done by a relatively small number of employees.
SELECT employee.Name
FROM employee
WHERE employee.Role = 'developer'
reads much better to me than SELECT employees.Name
FROM employees
WHERE employees.Role = 'developer'I also think the advice around join table naming is a bit silly. Calling a join table between `cars` and `mechanics` `services` (rather than `cars_mechanics`) does not make the relationship clearer, and only works when the relationships maps to a the real world where the relationship has a commonly used name.
The more I read of this guide, the uglier the SQL is.
The only time I sit these days is if I'm extremely tired for some reason. I have been doing this for more than 10 years now though, and it took a while until it became easy.