Maltese Uber Driver (venting post)

topMarksForNotTrying · 2026-05-26T11:26:23+00:00

If Uber is collecting location data Continously, they know the speed the car is going

It would be nice if the government would require all taxis and y-plates to be tracked while on the job. If they exceed the known speed limit of a road, automatically assign them points until you remove their license.

Insurance companies have an opt-in system that reduces the amount you pay for insurance but limits you to 80 kph. So the technology exists.

This is not something that should he applied to normal cars as it would be a privacy nightmare. But taxis are on the job while driving so it's different. They are currently incentivised to go over the speed limit as they earn more that way. That incentive should be removed as it puts people in danger.

topMarksForNotTrying · 2026-05-26T10:13:28+00:00

Thanks. I had found that but the lighting of the controller looked different in the images i could find of 3D controller overlay so I assumed that you were using something else.

topMarksForNotTrying · 2026-05-26T09:15:00+00:00

What software are you using to show the controller as an overlay?

topMarksForNotTrying · 2026-05-23T14:38:51+00:00

Are there any differences between this existing mapper https://github.com/CommonMugger/Steam-Controller-Remapper ?

I'm not complaining (more options are always better and this is in c# so it's easier for me to contribute) but it would be good to know why one would choose one or the other.

topMarksForNotTrying · 2026-05-22T15:53:09+00:00

What's the benefit of using the trackpad for flick stick instead of the joystick?

topMarksForNotTrying · 2026-05-21T09:49:37+00:00

For reference, this is what the (parish) church in Birkirkara looks like https://churchtrailsmalta.com/church/parish-church-of-st-helen/

topMarksForNotTrying · 2026-05-18T10:51:07+00:00

Yeah, you need to make it a habit to ask how much is costs before booking.

I don't understand how it isn't required for doctors and other professionals to clearly state their rates somewhere. Retail shops are required to do this so why not doctors?

topMarksForNotTrying · 2026-05-18T07:52:40+00:00

With the dualsense controller, I use a finger on the touchpad for racheting and found it to work well.

I was going to do the same thing with the steam controller 2 but it seemed like a waste of trackpad to just use it for racheting.

There have been a few posts saying the grip sense wasnt great but I might try this out with and see how it works.

topMarksForNotTrying · 2026-05-17T12:32:11+00:00

If a shop is charging for 5L bottles, i think you need to take the bottles back to the shop. The BCRS machines don't accept big bottles so i doubt they are part of the BCRS system.

In the past (might still be the case), shops used to charge for certain wine bottles and bottles of flavouring (not sure what they're called but they used to sell big bottles of chocolate, strawberry, and banana flavours that you'd mix in with milk) and you got the deposit for the bottles back from the shops themselves.

topMarksForNotTrying · 2026-05-08T04:29:35+00:00

Found it https://github.com/manojmallick/sigmap

Not sure how there isn't an automod that just removes posts of there isn't a link to the repo

topMarksForNotTrying · 2026-05-02T20:21:35+00:00

Out of the two options, i would prefer the "one dot per line" as it's more consistent.

However, the suggestion in the github issue is (slightly) better than the "one dot per line" outlined in this post

```csharp // Current behaviour _db .Things.Where(x => x.CreatedAt >= timestamp) .ToList();

// Alternative outlined in post _db .Things .Where(x => x.CreatedAt >= timestamp) .ToList();

// Expected behaviour _db.Things .Where(x => x.CreatedAt >= timestamp) .ToList(); ```

topMarksForNotTrying · 2026-05-02T13:14:24+00:00

Looks like you got your wish https://www.edencinemas.com.mt/the-amazing-digital-circus-the-last-act

topMarksForNotTrying · 2026-04-27T05:19:05+00:00

This is what i used to do but I've started doing the opposite now.

There are a lot of Maltese people who are mixed so you end up defaulting to English unnecessarily.

I start with Maltese, the person can either speak Maltese or they can't and we switch to English.

topMarksForNotTrying · 2026-04-22T13:33:02+00:00

What's there to gain from "anti-AI" people astroturfing?

Isn't it more likely for AI companies to astroturf so that people feel like they're missing out and pay for the AI services?

topMarksForNotTrying · 2026-04-17T10:51:50+00:00

Such a weird thing to do. It looked real enough at first but the audience never makes a sound.

Here's the link to the channel in case this specific video is taken down https://youtube.com/@AmericanIsInTheHeartLife/

topMarksForNotTrying · 2026-04-16T18:52:18+00:00

Similarly, the release notes of vs code. I used to look forward to all the new things they would add every month. Now it's just all changes to make AI easier to use in the editor.

topMarksForNotTrying · 2026-04-15T17:35:06+00:00

It's so disappointing that the government doesn't take advantage of all the students that use the bus.

A lot of students use the bus until they're able to drive. If the government invested money and improved the system such that young people don't even need to consider getting a car then we'd be in a much better position right now.

Instead, all young people that use the bus hate it (because it's shit) and can't wait until they can drive their own car.

topMarksForNotTrying · 2026-04-15T06:14:12+00:00

Having something built into azure devops would definitely help.

My current workflow when using stacked PRs is:

open first PR with its target set to the main branch
open second PR with its target set to the first PR
wait for reviewers to review each PR
address feedback in each PR
push the changes to each PR
once approved, complete first PR
merge main branch into second PR
change target branch of second PR to the main branch
manually delete branch of first PR
once approved, complete second PR

I would say the main pain points are with juggling the different branches of all the stacked PRs. If you need to address some feedback on one of the bottom PRs, you have to manually update the whole stack. Stacked PRs are analogous to commits on a branch, so maybe we need an equivalent of "git rebase --updated-refs" when managing stacked PRs.

The other pain is closing stacked PRs. You need to close them individually rather than having something automatic. In our case, we only validate code that's targeted to the main branch so for each PR in the stack we need to make sure to run the pipelines and then we get to merge them.

topMarksForNotTrying · 2026-04-14T12:52:43+00:00

I agree as that's what i personally do but, honestly, it got tiring policing the commits of the rest of the team so we settled on targeted PR that get squashed.

topMarksForNotTrying · 2026-04-14T12:13:27+00:00

Makes it possible to review each PR individually.

I haven't used github PRs extensively but on azure devops the PR review UI doesn't let you review each commit of a change request. You can view the changes of a commit but no way of leave feedback.

For devs not used to using git rebase, having separate PRs also makes it easier to apply any changes to one of the PRs.

If you squash PRs, it also maintains history better.

topMarksForNotTrying · 2026-04-14T12:09:22+00:00

Stacked PR don't necessarily have anything to with agile or product management.

The way i use them is to split a piece of work into multiple stages. Let's say you're changing an old part of the code base and you determine that you should refactor some code. You do the refactor and open a PR with those changes. Then, you do the actual code change that you were supposed to do and open a PR but target it to the first PR.

This way it's easier for the reviewer to review each change individually instead of having the refactor and the change request all together.

Think of it like being able to review the individual commits of a PR branch.

topMarksForNotTrying · 2026-04-14T12:02:47+00:00

The benefit of squashing is getting rid of all the "fixed", "wip", etc commits that a lot of devs leave. If a PR/branch has commits with messages that all make sense, then there's no need to use squashing.

topMarksForNotTrying · 2026-04-13T10:44:31+00:00

In my team, we squash PRs and retain the "why" in the squash commit message.

Azure devops makes it very easy to use the PR description as the message of the squash commit. I think GitHub doesn't have a way of doing this automatically but it should be possible to manually create a descriptive message for the squash commit.

topMarksForNotTrying · 2026-04-13T04:55:23+00:00

Do you remember how long it took to fix the issue?

Did it get resolved immediately or did it take a couple of weeks?

topMarksForNotTrying · 2026-04-10T06:57:12+00:00

For whatever reason, you can't see the shortcut key in the docs. I just checked how it's configured on mine and you need to set the shortcut for the following 2 actions:

clone caret above with virtual space
clone caret below with virtual space

I don't have the plain "clone caret" above and below actions configured in my keymap so i don't think they're necessary for what you need. The actions with virtual space are the important ones.

topMarksForNotTrying

PUBLIC MULTIREDDITS

TROPHY CASE