Himself

https://www.theguardian.com/us-news/article/2024/aug/08/rfk-jr-roadkill-freezer

Eating roadkill on the reg

Daily reminder that the fact RFK has a platform for the health policy of the US and not a grave after having his brain literally eaten by worms entirely due to his own risky behaviour, is fucking ｃｏｍｉｃａｌｌｙ　ａｂｓｕｒｄ

I did yes, it almost felt like it could be structured slightly differently into a poem

I felt it had that sort of cadence to it when I read it

Cheers for the content

It’s GAFAM now?

Well done to Microsoft for knocking Netflix down a peg then I guess

Edit: sorry just realised I engaged with the image and not the content to which the image isn’t really related

I think there’s an alpine build too if your system has low oxygen levels

In the magpie nests

(Sorry, you made me think of this article)

Ew, imagine spending money to wear the privacy invasion of everyone around you on your face

Didn’t end well for the people a decade ago with Google glass

Why not just IPFS? Have I missed something?

For a good while, Plex was the only game in town that did the job well, and they put the transcoding feature behind the paywall.

Given it wasn’t that expensive for a lifetime pass a number of years ago (I remember it was cheaper than a game anyway) and they still seemed relatively user-centric at the time, many people like me felt like they were supporting developers building something that was useful to us.

I still run my Plex server since it’s not really costing me not to, but I’ve been running Jellyfin too for a little while and it more or less can do the same job these days

This comment fascinates me

California is apparently about 12% of the total tax revenue of the US, and New York is about 8%. If every other state was equal after that, they are about 1.5 each.

That’s quite a lot of leverage

Can’t send people to El Salvador if you can’t pay for planes

Most Java engineers I’ve ever met have Stockholm syndrome with the framework du jour.

Flashbacks to one of my early freelance PHP gigs I did about 2 decades ago where I opened up the existing backend source code to find a load of unsanitised user input directly from the query string getting interpolated into the various SQL queries the application made. Part of me also feels like the “bobby tables” xkcd already existed by this point, so I’ve got no idea how that website managed to not get nuked before I refactored it.

To top it all off, of course the application authenticated with the database using the root user…

Thankfully I think that was the worst I ever discovered in the wild

“gotta see shit to know shit” someone once said to me

It pops into my head semi-regularly

This comment has graduated to becoming my head canon for this scene

It makes everything make sense

I wonder if the website did the thing where it lists their big customers like a trophy cabinet on the main landing page.

It would probably make a good list of places to sell snake oil

Also love that this is all evidence to back up the premise that building the happy path of an application is generally easy, one of the main skills in software engineering is ensuring the unhappy paths are covered sufficiently. I can say I’ve started a bank and keep people’s money in my wardrobe, I’ll be providing the service of holding their money—I’ll also probably get robbed sharpish because I’m not skilled in the kind of security needed to avoid that.

Yes, silly engineers that don’t like being held to unrealistic estimates and deadlines; typically the ones that arise at the start of a project where there are still who-knows-how-many unknowns to find.

Waterfall is the most effective tool for software engineering in a world where the whole world stops once you’ve planned and only starts again once the project has finished—i.e. a fictional world that doesn’t exist. Literally every waterfall project I worked on back in the old days was derailed because something happened that wasn’t planned for—because planning for everything up front is impossible and planning for anything more than a handful of eventualities is impractical.

Agile and subsequent methodology comes from realising that requirements will change and that you are better off accepting that fact at the time than having to face it once you’re at the end of the current road.

Agile does not mean engineers talking continuously to the users, engineers are hired to do what they’re good at: engineering. Understanding user requirements and turning that into a plan has always been product’s job regardless of methodology, in agile and similar it’s just spread out over the duration of the project, not front loaded. Agile isn’t “make the engineers do every proficiency”.

A software engineer was not involved in this if waterfall is painted positively.

I think the last time I heard an engineer unironically advocating for a waterfall IRL was about a decade ago and they were the one of the crab-in-a-bucket, I-refuse-to-learn-anything-new types—with that being the very obvious motivation for their push-back.

You get used to it, I don’t even see the code—I just see: group… pattern… read-ahead…

Probably true, worth pointing out I browse with the “old.” theme when I’m at my computer which doesn’t come out bad at all given it’s pretty basic HTML (just tried it on my phone too, which is something I wasn’t sure would give a good result)

You’re right though, it would be a good pull request to the Lemmy UI to add a print stylesheet