SimonPStevens

Yeah, I suspected this could be related. Additionally frustrating as I'd honestly not a massive fan of printer dot codes either.

Unfortunately it's not one of the transparent window ones. Nice when it used to work though.

I've said this before, and I stand by it. I think AI does pose a threat, but not the existential one that leads popular discussion.

Over the next few decades AI is going to take huge numbers of jobs away from humans.

It doesn't need to fully automate a particular role to take jobs away, it just needs to make a human significantly more productive to the point that one human+AI can replace n>1 humans. This is already happening. 20 years ago a supermarket needed 20 cashiers to run 20 tills. Now it needs 2 to oversee 20 self checkouts and maybe 1 or 2 extra for a few regular lanes.

This extra productivity of a single human is not translating to higher wages or more time off, it's translating to more profits for the companies augmenting humans with AI.

We need to start transitioning to an economic model where humans can work less (because AI supplements their productivity) and the individual humans reap the benefits of all this increased AI capability or were going to end up sleepwalking into a world where the majority have been replaced and have no function in society, and the minority of capital owners control the AI, the money and the power.

I wish we could focus on these nearer term problems that have already started instead of the far more distant existential threat of a human/AI war.

Take a look Parkitect. It's very much a modern RCT, complete with grid layout. As a fan of RCT1/2, I found it very enjoyable.

I mostly agree this way of looking at it, but find 2 things distort this nice clear explanation.

1. Lack of clarity. I've no problems paying a fee I want and use. But when the fees are hidden at point of sale, and then added later it makes comparisons hard or fees I don't want getting added because I didn't know about them in advance so couldn't change behaviour to avoid them.

2. Fees that don't accurately capture the benefit Vs the cost, and are gamed. Things like "2 peices of hand luggage" with no weight specified. I once had an attendant tell my wife her hat she was carrying counted as one peice, so she had to put in her bag to walk past the check-in desk to avoid being charged a fee for extra hand luggage. And then you get the opposite with schemes like wearing vests to carry extra items without it counting in your hand luggage allowance. I once had to move ~2kg from my hold luggage to my hand luggage because one was over and the other under. Why not literally charge a per kg fee regardless where you store it that way everyone pays for exactly what they use, no gaming. The current fee structure tends to incentivise maxing out on hand luggage to avoid hold fees, which means overhead storage gets crammed full. Charging per kg would shift a portion of this to the hold and make the cabin less cramped and better for everyone.

Oh the irony of examples of bad UI being posted on twitter where I just get half a UI loading with spinners and can't see anything.

> Where are the docker/redis/next.js/linux kernel/qt/roller-coaster tycoon creators?

They create their own thing from scratch, and turn it into a job.

The first 5 from that list were open source creations that became big because they met a need at the time and lots of people adopted them. Which is one route into creating your own thing.

I've seen senior engineers who have leveraged lots of domain knowledge to build a prototype of something super useful internally within a company that then grows in adoption and size as people recognise it's value. Projects then start to organically cluster around the core that was built solo.

Kind of disappointed. What would have been amazing is if the code it gave you did what you requested but also contained a breakout attempt to take over your computer and copy itself.

I'm imagining a future where AIs try social engineering on humans to convince us to give them root access to our devices.

Not sure it matters that much.

Most non-technical people I know wouldn't have a clue what a .zip was. Windows has hidden file extensions by default now for decades. And having a phishing link in an email that says something.zip but links to somethingelse.com is a basic scammer 101 level technique. Why would it matter if the .zip was a real part of the URL or not.

Don't get me wrong, I dislike all of the generic TLDs, and the registration process behind them. But of all the points to argue on them, this seems like the weakest and least relevant.

I think for many gig type work out would be hard to hit 50 hours. There are only so many peak hours for these jobs in a week.

If tried to work more you'd find yourself just waiting for jobs a lot of the time and your average hourly rate would drop even lower.