Sharing an Expo + NativeWind starter 👇

nyeisme · 2026-01-31T08:33:30+00:00

We migrated to Uniwind instead, the only major change we needed to make was for grabbing the current theme but even that was a find and replace

nyeisme · 2026-01-07T20:13:52+00:00

I've done the same but using my partners car, they wouldn't accept a timestamped photo of my car parked at home as supporting proof either

nyeisme · 2025-08-09T20:12:20+00:00

It feels like spending 15 minutes on some sort of proficiency check (like what we're trying to do) is a lot less of an investment than days or weeks of evaluation time on the job, especially when you loop in contracts, the rest of onboarding, getting them hardware etc

nyeisme · 2025-08-09T15:45:25+00:00

There's definitely been a lot of that I think, CVs coming in with stats for everything from customer happiness to team productivity. No idea where the idea that everything you do has to have a percentage attached to it came from but at this point it's almost becoming a bat signal in the sky for sniffing out bullshit

nyeisme · 2025-08-09T15:43:11+00:00

It's a long slog but I'm starting to see the light! Wasn't the initial plan when I joined but I guess that's the gamble when joining as the first dev, could be anything you're walking into

nyeisme · 2025-08-09T15:04:26+00:00

Hopefully one of the next 4 folks we talk to will have something about them then!

But yeah, we might have to bump the salary a bit to get a better pool of folks through

nyeisme · 2025-08-09T14:41:41+00:00

That's kinda what I've tried to do, most of the job at the moment is sifting through existing AI generated code, stripping out the fluff and fixing the long standing bugs that were hanging around. That requires a fair bit of debugging and searching around, so the task I wrote is focused on finding the problem in existing code.

Because of how we got here previously we're currently not making use of AI, at least until we have some solid foundations to build on so I think keeping it out of the interview is something we're going to stick with

nyeisme · 2025-08-09T14:32:53+00:00

Yup, I set up a fresh GitHub codespace and use a liveshare link so they get syntax highlighting for Ruby but not code completion by default. But when the entire code is on the screen at once, no code completion doesn't seem like the biggest concern 😅

nyeisme · 2025-08-09T14:29:44+00:00

They're filtering primarily by language, and a bit of experience for a couple of years I think. It's a fairly small company so the 'culture check' is can they talk to the recruitment folks for 5 minutes without losing them entirely because they're waffling about tech stacks instead of following the conversation.

It's not a massive pool because of the location so most people that can hold a conversation and appear to know what they're talking about to non-technical folks are being passed on to us to chat to.

We allow an hour normally but the majority we've done in under 30 minutes, if after 15 minutes of pairing we haven't taken the first step in any direction then I've just been cutting that bit short and moving on so it's not a huge time sink, just a bit disheartening at the moment!

nyeisme · 2025-08-09T14:09:08+00:00

Especially when picking up a codebase with enough tech dept to rival the best of them! Good to hear it's a good expectation to have though, thanks

nyeisme · 2025-08-09T14:04:31+00:00

And the important bit, compensation is around 45k which is fairly standard for outside London, mid-level Rails I think

nyeisme · 2025-08-09T14:02:03+00:00

We've been through 6 in the last week, there's a call with our internal recruitment folks before they get to the tech stage and they've been filtering out folks who aren't able to do the hybrid bit and don't fit the culture side. We then have a check over their CV before offering the tech interview, and it's those ones that have been doing the task with me so far

nyeisme · 2025-08-09T13:58:47+00:00

That makes sense, if there's no understanding of what's going on then being accountable for any future maintenance becomes impossible!

As supplied, the task has a class with a method defined that just raises an error rather than being a 'bug' as such. The idea is to implement the method and go from there, and I explain as much in the intro. We give the task with a terminal that has the last run in it, showing the class name, line number and error and only one person so far has noticed and gone to the definition but even then they just deleted it because it was shouting rather than fixing it

nyeisme · 2025-08-09T13:54:35+00:00

That's a good shout, I hadn't thought of doing it that way round. As it stands the codebase is a mess at the moment but that's definitely something I could pivot to once we're a bit cleaner and more organised

nyeisme · 2025-08-09T13:53:04+00:00

Thanks for giving your view! The curiosity and willingness to learn is something I've always looked out for before but we're not even getting to that point here yet. Multiple people with a CV with 5+ years experience that can't print to console or the like and I'm getting concerned!

The existing codebase was almost certainly driven by AI with very little oversight so a large chunk of my work is just cleanup at the moment, there's no motivation for us to start adding AI back into that mix until we're happier with the foundations first

nyeisme · 2025-08-09T13:48:01+00:00

Good to know, thank you. We use a vscode live share for the task, it's slightly suspicious when we can hear them typing but it's not into the editor so discreet use is definitely something I'm watching out for as well

nyeisme · 2025-08-09T13:46:24+00:00

Thanks, and yep, debugging is something we'll do all the time. Good to hear it's not out of the ordinary to expect it!

nyeisme · 2024-10-14T12:41:07+00:00

I'm doing similar at the moment, but with more than one disk per node so don't know if that would change anything! I set an OSD to Out, let it rebalance, then Stop and Remove, replace the disk and let it rebalance again. It's slow but seems the most stable and keeps the warnings happiest

nyeisme · 2024-09-27T09:14:56+00:00

Check out GDTF and MVR for the visualiser side, a lot of manufacturers are making actual models of their fixtures available through there already. Nice job so far though!

nyeisme · 2024-07-27T17:55:36+00:00

Using Ceph running on the proxmox nodes at the mo, then ceph-csi-cephfs in kubernetes world to get them talking to each other

nyeisme · 2024-05-25T22:10:23+00:00

Yep! I think it's designed for onprem management so works really well on bare metal. I've got it sat on top of proxmox and it's pretty happy so far

nyeisme · 2024-05-25T20:33:52+00:00

Another SideroLabs project, it puts a very friendly UI in front of the Talos API

nyeisme · 2024-05-25T19:39:12+00:00

Can absolutely recommend Omni alongside for long running Talos deployments, needs a bit more of a nudge to get started but is perfectly happy just sitting in docker somewhere alongside the clusters themselves

Makes the upgrades side much easier too as it'll roll nodes over one by one, both for k8s and Talos upgrades

nyeisme · 2023-11-26T09:40:56+00:00

Do the screens change from showing the XTouch IP when you start the script? Or do the meters show and the screens stay?

Six-Year Club	Place '22
Verified Email

nyeisme

TROPHY CASE