agilob

u/agilob@programming.dev
147 posts · 98 comments

Recent posts

Recent comments

Any reason to stick to large SD cards? I have a really good experience running a cluster of rpis on USB nvme disks. I got cheap USB 3 nvme pockets and post-market/post-lease nvme disks. 4 rpis have been running like that for more than 3 years now. They boot in about 1 second, don't have any spikes in energy usage and I don't worry about writing or reading too much from them. Average read/write time is under 2ms.

That's not at all what I meant. Coordination of people is value added too, that totally counts into working hours.

The other reason is, the more employees, the easier it is to get shitty unethical stuff done

That's the main spirit of what I tried to express. The more people to keep employed, the more ideas you need to justify your existence to the shareholders. The 300 devs aren't adding new features, aren't making your app faster, smaller, safer. The last 20 updates with "bugs fixed" in change logs? These bugs were bugs in A/B tests they are running on your device. They aren't adding any end-user facing value to the app or experience. They are adding new way of tracking, updating existing A/B tests for new remotely controlled flags, adding new A/B tests.

They are squeezing the profit margin from you. You're paying for it AND are the product.

Without it being said, we knew such things are happening. There are a few 100s of only mobile devs in Uber, while Uber app hasn't really changed in years, and these devs aren't creating any user-facing values. Running it must be difficult and a company need a lot of people for it, but there must be some point at which a company stops "disrupting" and just starts optimising and micro-optimising. This is what OP is talking about it, they are micro-optimising budget. There are 100s of them employed, so they must be doing something!

Consider that 300 mobile devs produce close to 1 year of man-hours every day. This is enough time to complete your TODO list of app you always wanted to do. They spend it producing values for shareholders, not you.

Now consider how many devs and experiments like these are done every day on facebook, instagram, X (formerly Twitter) and gmail.

Source: https://lwn.net/ml/all/CAHk-=whNGNVnYHHSXUAsWds_MoZ-iEgRMQMxZZ0z-jY4uHT+Gg@mail.gmail.com/

Ok, lots of Russian trolls out and about. It's entirely clear why the change was done, it's not getting reverted, and using multiple random anonymous accounts to try to "grass root" it by Russian troll factories isn't going to change anything. And FYI for the actual innocent bystanders who aren't troll farm accounts - the "various compliance requirements" are not just a US thing. If you haven't heard of Russian sanctions yet, you should try to read the news some day. And by "news", I don't mean Russian state-sponsored spam. As to sending me a revert patch - please use whatever mush you call brains. I'm Finnish. Did you think I'd be supporting Russian aggression? Apparently it's not just lack of real news, it's lack of history knowledge too. Linus

I have an apostrophe and it’s super annoying as some companies see it as a SQL injection hack and sanitize it.

My surname contains a character that's only present in the Polish alphabet. Writing my full name as is broke lots of systems, encoding, printed paperwork and even British naturalisation application on Home Office website. My surname was part of my username back at uni, and everytime I tried to login on Windows, it would crash underlying LDAP server, logging everyone in the classroom out and forcing ICT to restart the server.

on AI auto apply jobs · c/programming · -2 pts · 1y

I would like to confine it to firms using AI recruiting tools

and actively do damage to companies that don't.

The Linux kernel uses the CPU default scheduler, CFS,

Linux 6.6 (which recently landed on Debian) changed the scheduled to EEVDF, which is pretty widely criticized for poor tuning. 100% busy which means the scheduler is doing good job. If the CPU was idle and compilation was slow, than we would look into task scheduling and scheduling of blocking operations.

EDIT: Tried nice -n +19, still lags my other programs.

yea, this is wrong way of doing things. You should have better results with CPU-pinning. Increasing priority for YOUR threads that interact all the time with disk io, memory caches and display IO is the wrong end of the stick. You still need to display compilation progress, warnings, access IO.

There's no way of knowing why your system is so slow without profiling it first. Taking any advice from here or elsewhere without telling us first what your machine is doing is missing the point. You need to find out what the problem is and report it at the source.