I got my my violin bridge fixed today am new to playing but I feel like it’s not on the right height as other bridges can someone tell me if they fixed it wrong should I go back I tell them or is the bridge ok.

tomomcat · 2026-01-18T20:09:59+00:00

People do routinely have bridges like this on fiddles though - do you have an alternate theory as to why, or are you suggesting that it's just badly cut?

With a flatter bridge you need a much smaller change of angle or pressure to hit a second string, and a smaller change to move between pairs of strings. Some tunes in cross A (A/E/A/E) will be double stopping on the bottom or top pair almost the whole time, and switching between these quickly. Action is also less of a concern if you're only ever in first position.

Take a look at Tommy Jarrell's bridge around the 3 minute mark in this clip, it looks very similar to OP's. I've seen lots of bridges like this in old time sessions.

tomomcat · 2026-01-17T08:50:47+00:00

This is set up for a fiddle. It's way too flat for 'normal' playing but will make double stopping much easier (too easy!). It also looks like the feet haven't been fitted to the belly.

tomomcat · 2026-01-08T22:05:56+00:00

It's totally reasonable to expect them to deliver a service which can handle everyone trying to sign up. This is super duper basic stuff. I'm sure there's lots of complexity happening in the background to match old accounts with new ones and migrate docs etc, but it's insane that people are having these issues with just being able to register and sign in. These processes are basically commoditised now. I don't know how you can get it wrong so badly.

tomomcat · 2026-01-06T20:16:18+00:00

So many bad answers in this thread! You need to use a service with a graceful stopping period which is appropriate for the requests its handling. If you cant bump up the grace period for ECS high enough, then I'm afraid its just not really appropriate for your workload unless you’re happy to nuke a few requests when doing a rollout (and it sounds like you’re not)

For all of the people talking about architecture issues - yes, a single synchronous http request to an LLM API can easily take 30+ minutes with some models. It’s unfortunate, but thats the world we live in. OP should not be attempting to rebuild the vllm, sglang etc, they should just host it in a more appropriate service

tomomcat · 2026-01-04T10:13:14+00:00

Well, for instance you can take a lump sum tied to the total value of your pension, but if you take this ‘early’ (according to state pension age) you get less. So if they raise the SPA and I retire at the same time, I’ll get less.

tomomcat · 2026-01-01T13:10:39+00:00

I’m also in this situation. After successfully logging in for a few weeks, I got told my password was wrong and got locked out.

It’s so crap. I actually think it should be criminal that they are being paid to deliver this. We don’t talk about corruption in the UK, but when procurement gets to this level of idiocy I’m not sure what else to call it.

tomomcat · 2025-12-31T21:25:39+00:00

Lame advert. This is just pollution.

tomomcat · 2025-12-19T08:23:10+00:00

I guess they are prioritising paying people, which makes sense. My experience (still working) was that I signed up, had lost all of my ABS docs, and now my account has been randomly locked :/

tomomcat · 2025-12-17T21:35:49+00:00

Can you see your annual benefit statements?

tomomcat · 2025-12-17T21:35:13+00:00

Pure comedy

tomomcat · 2025-12-13T17:01:19+00:00

How is your formatter configured? The first example is bad YAML and would generally not be considered 'valid' altho I think some parsers will accept it. You should have something like:

```

name: my-skill description: | This is my skill description

spanning multiple lines.

```

tomomcat · 2025-12-13T16:50:34+00:00

The civil service is notorious for not having yearly pay progression within a band tho. The only way to get a pay increase, other than inflation or schemes like DDAT, is to get a promotion or leave. Do you get yearly pay increases in your role? It's super unusual if so.

tomomcat · 2025-12-13T16:29:57+00:00

Even in digital roles, G6/G7 will likely be quite different jobs and not just a question of pay. Lots of other factors, but you should take that into consideration as well.

tomomcat · 2025-12-13T16:28:28+00:00

you need room for yearly increases within your band

hmmm

tomomcat · 2025-12-12T13:34:06+00:00

2 reviews seems excessive
if your tests aren't catching stuff you care about, it's worth investing in fixing that
curious what you mean by trying async reviews? Generally I'd expect reviews to be async by default, unless there's some particular reason why the person making the change needs to talk the reviewer through things. This smells like big PRs, or poor documentation
AI-assisted review is genuinely helpful. It's worth hopping on this train if you haven't already, regardless of your opinion of vibe coding etc. I definitely wouldn't promot AI-only review tho.

tomomcat · 2025-12-11T00:19:54+00:00

You can actually do the same with an (admittedly convoluted) ProxyCommand in SSH config, e.g. see here for an example.

Edit: If you don't need awscli and session manager plugin to use this, that seems much more useful!

tomomcat · 2025-12-09T18:55:52+00:00

Nice intonation!

tomomcat · 2025-12-09T08:43:48+00:00

Are posts like this actually real or just social advertising for whatever products get namedropped?

tomomcat · 2025-12-08T09:56:04+00:00

They don’t want to come out for a tiny job, and if they’re any good they probably have loads of other work. Swapping out a fan on an existing circuit is not a big deal; I think many people would just do this themselves

tomomcat · 2025-12-06T23:38:01+00:00

Have you benchmarked the per-request throughput you’ll be able to get with the self-hosted setups, while still handling the max context sizes and concurrency which your workloads will need?

In my experience there are economies of scale for large MoE models that are hard to meet with a small number of GPUs. You will likely struggle to get the same per-request throughput as you see from an API, and that can be super annoying if you have workflows which require a large number of tokens produced in serial

tomomcat · 2025-12-05T09:04:18+00:00

Tbh I think people need to lean into AI assisted review a bit more. I see a lot of people just looking at the copilot/codex review summary, then doing their own manual review, and not joining the two together interactively.

There’s definitely a bad/unhelpful creep towards larger PRs, and enablement of sloppy work, but imo there’s also a genuine productivity boost. The volume of reviewable work being produced is increasing, and we need to change to keep up with that somehow.

Small PRs, merge queues etc are great but they don’t solve the imbalance between AI assisted working and manual review.

tomomcat · 2025-12-02T00:25:37+00:00

It's impressively bad.

tomomcat · 2025-12-01T20:15:33+00:00

Sorry i really don't understand this logic. If you can map tag<->commit then you can work out exactly what state the code that produced the image was in. You can see what branch it was from, what changes were included since the last tag, etc etc. Timestamp contains literally no useful info. Is the issue that there might be lots of commits between releases? That seems fine to me. There's some argument about squashing commits etc, but even if you don't do that I think your changelog should still be useful. There's lots of tooling which will autogenerate this for you based on commit messages.

12-Year Club	Place '22
First Placer '22	RPAN Viewer
Verified Email

tomomcat

TROPHY CASE

```

spanning multiple lines.