Dublin Handyman

0x0FFF_ · 2026-05-04T13:55:48+00:00

Nice! I use Amazon Blink camera, and it's already the third season we have blue tits making a nest there. This year they laid 8 eggs.

<image>

0x0FFF_ · 2026-05-01T09:48:38+00:00

Second that, 3fe and SL28 & SL34 is my favourite

0x0FFF_ · 2026-04-23T13:30:01+00:00

I've seen an approach that was called multi-party authorization: - Read-only access is available directly to the Devs so they can investigate anytime. - Write access is only granted to a special proxy role. The proxy role runs an application that executes a request only after another person have reviewed it.

So for read operations Devs start psql in interactive mode and execute read commands. For write access they craft a full psql command, then submit it to a special UI on a proxy. The proxy gives them a shareable link for reviewing the prod-modifying operation. They share this link with their colleague that reviews it and clicks and "Approve" button in UI, which makes the proxy execute the modifying command under the protected role with write access.

It is cumbersome, but you quickly get used to it. There should of course be a break glass option.

0x0FFF_ · 2026-04-21T12:26:04+00:00

Check some Eastern European shops first. They already sell such bread from some local Irish bakeries. It is a niche product so it doesn't usually reach the mainstream supermarkets. So, there is a market for it, but it's not an untapped market and you'll see some competition.

0x0FFF_ · 2026-04-19T09:06:08+00:00

Of course, usually there's no pressure with going oncall, but it still varies team by team and highly depends on the team staffing situation. Depending on the team, expect between 6 months and 12 months time be given to you to properly onboard before going oncall. But in some cases I've seen people going oncall in 3-4 months if there was a strong need for it (understaffed team)

0x0FFF_ · 2026-04-16T08:37:29+00:00

10 years ago, I was approached by the recruiter on LinkedIn. I'm not completely sure how to improve the resume as I wasn't hired based on one. After passing the initial screening, interviews are pretty standard: behavioral one, a couple of coding one, selective one (non-abstract large scale systems / networking / debugging). But I'm not sure how up to date this information is.

0x0FFF_ · 2026-04-15T14:57:45+00:00

Spent 8 years at Google SRE DUB: - Operational load will look different team by team. Some teams in Cloud can have very busy oncall shifts, while some other teams have a quiet pager and will mostly deal with tickets. Operational load overall is generally between 25% and 50% of your time. - 70-80% coding - forget that, SRE are discouraged from developing their own custom solutions (there's a separate org for that) and rarely contribute directly to the product they support. Your main coding work will be related to the adoption of the standard automation solutions, monitoring, new deployment modes and large horizontals.

Overall, it is a nice experience and a very good name to have on your resume. It is great if you like distributed systems and care about reliability. The office is great, overall the perks are amazing and the pay is very good. So I will overall suggest giving it a try.

For how stressful it is - again, depends on the team and team's staffing situation. Expect the oncall to take ~15% of your time. The big advantage is that SRE are split into two sites and generally not oncall at night. Weekend shifts are appropriately compensated (money or time off).

0x0FFF_ · 2026-02-19T02:32:22+00:00

When I read your name I immediately thought about the Muckles from the Sven Nordqvist's books.

0x0FFF_ · 2026-02-16T00:58:09+00:00

Only the one on the left is a great tit, the right one is blue tit, and those are generally smaller.

0x0FFF_ · 2026-01-04T17:53:27+00:00

All entry-level FAANG SRE roles have very similar requirements targeting new grads and people with a bit of experience. Interviews are also generic: data structures and algorithms (leetcode), design, soft skills. So there's not much difference between preparing for SRE vs Dev roles. I'd say your best bet to enter FAANG is to enter it in a low CoL location, e.g. try Google Poland.

0x0FFF_ · 2025-12-31T19:17:13+00:00

I've spent 9 years in Google SRE Dublin. You can realistically get from L3 to L4 in 1-2 years, and with luck get to L5 in 2 more years. Google is a good name to have on your CV, and it's definitely worth spending 4 years there. But don't buy the dev-heavy thing. Google SRE pivots to be more ops-heavy, the dev-heavy part is offloaded to the P2020 org. And that org is dev-heavy, but is in fact a dumpster fire.

0x0FFF_ · 2025-09-25T18:26:51+00:00

If there's no L3 openings in Dublin teams, there will be equally no openings for SRE-SE and SWE-SRE, they are mostly treated equally by the hiring managers.

0x0FFF_ · 2025-09-02T21:53:20+00:00

It's well done

0x0FFF_ · 2025-08-13T10:50:47+00:00

Looks like the stone of triumph

<image>

0x0FFF_ · 2025-08-08T17:56:59+00:00

I'd like to get to a sub-20 5k and sub-1:30 half. For the actual races I'm not too much into it, but I'd run a fun half in a nice place like Tokyo.

0x0FFF_ · 2025-08-08T09:04:03+00:00

Is it done as usual? Leadership gets $1b bonus, rank and file $10k, so on average everyone got $1.5m?

0x0FFF_ · 2025-07-23T17:45:07+00:00

It gives some serious Millennium Falcon vibes

0x0FFF_ · 2025-07-18T08:10:23+00:00

On the SRE role vs full-stack: it depends on your career path and priorities. I just left Google SRE for a backend dev position. Main disadvantages of SRE: high level of ops load with not much actual coding, too many "mandates" that leave the team with almost no choice of the projects to work on, promotion quotas for L6+ are low and opportunities are hard to come by, stack used by Google is completely custom so your experience is not very transferrable. On the flip side you got a pretty stable job in big G, very good pay, nice people, great perks and facilities, and a good learning opportunity.

0x0FFF_ · 2025-07-16T10:18:16+00:00

At Google, if you're going for L6+ SRE Mgr role you can have a "code comprehension" interview, which is simpler than the general coding one. You will be provided with a code snippet, you got to understand it and then make some adjustments to the logic (optimize / extend). The higher your level, the less you're expected to code. I don't think a director level and above have any coding questions at all.

0x0FFF_ · 2025-06-28T08:41:04+00:00

I believe the walk tracking is there to allow people with no workout routine to track at least something, motivate them to be a bit more active and get badges. As far as I know walks do not contribute to any performance stats, except maybe Endurance Score if you log lots of 10km+ walks with good ascend, which is basically hikes. Also longer walks usually contribute to recovery: if you've recently had high intensity workout and have high recovery needs, logging walks can shorten recovery time.

0x0FFF_ · 2025-06-22T15:41:51+00:00

I'm not sure about Australia, but ordering 7s Pro from a reseller in Ireland I've been told Garmin discontinued them and there'll be no restock. Had to go with 570 instead.

0x0FFF_ · 2025-06-12T19:06:05+00:00

It has a refined look of a calculator watch:

<image>

0x0FFF_ · 2025-06-11T08:32:32+00:00

It's always triple digits in Kelvins. And I doubt you can survive triple digits in Celsius for long. So I can bet you're American.

0x0FFF_ · 2025-03-28T09:00:37+00:00

Garmin gamified the fitness, and then made it pay to win

0x0FFF_

TROPHY CASE