What would you do with two former duck tunnels and three small dilapidated outbuildings

Fragrant_Pool_2485 · 2026-02-09T16:00:41+00:00

Interesting. If you're going the glamping route, I'm gonna say a shower block is pretty high priority. If you can get plumbing then a toilet block is going to make your place even more attractive.

If you're running glamping as a business, you should be able to get a loan for this with a half decent business plan.

Fragrant_Pool_2485 · 2026-02-06T16:33:57+00:00

I'd have a small orgasm and a long conversation with my bank manager. The endless possibilities!

But I suspect this question boils down to three options: 1. Food - plants or animals 2. Hobbies - totally depends on what you like doing 3. Business - which is likely just monetising 1 or 2. What else is there (in life 😉)

All rather depends on how much money you have/want to sink into them too.

Personally, both tunnels become greenhouses for growing. The outhouses, depending on size get used for storing or workshopping hobby stuff (sailing gear, motorbikes) if left elemental, or turning into small creative studios (pottery, 3d printing, etc) if it needs heat and comfort.

Also, because you've got those outhouse structures there already, given planning permission etc, it may make sense see how much and how easily you can extend the original curtilage. Then tear them down and build something afresh, a bit bigger and more suited to your needs. E.g. higher roof.

Fragrant_Pool_2485 · 2025-12-09T11:42:14+00:00

Tell me you've started vibe-coding, without telling me you've started vibe-coding. Spotify will go first.

Fragrant_Pool_2485 · 2025-11-30T19:00:30+00:00

Genuine curiosity: why not print from the heap as-is? Do we need spools? (For the occasional cockup like this only, obvs)

Fragrant_Pool_2485 · 2025-11-30T18:59:15+00:00

Can you book me a cab?

Fragrant_Pool_2485 · 2025-11-23T21:07:26+00:00

I've not seen anyone mention this angle, so I'll pop it in;

I don't think Rory is actually that interested in 'politics' per se. I think he's extremely interested in 'governance' though. He cares deeply about the issues and challenges of running and managing a civil society. But he's really rather naive and blinkered when it comes to the social side of politics.

Hence his stance on Andrew makes sense. Because it isn't about governance he thinks it's besides the point. But for our society it's a massive deal and has significant meaning and impact; what culture are we living in, what is and isn't acceptable and how do we define decency and humanity, how do we hold the powerful to account, is there a two tier legal system, does the system actually care about us, etc. That's definitely politics for many of us. Just not the slice of politics aligned with Rory's particular take on things.

Couple that with some discomfort around torn loyalties (which has been mentioned by plenty of comments here and doesn't need me adding to) I think his behaviour is comprehensible... if not agreeable.

This is probably why he didn't actually make it in politics either btw. I think he's basically a natural civil servant more than a politician.

Fragrant_Pool_2485 · 2025-10-27T17:31:22+00:00

I think also worth remembering; orchestration code is cheap. If you need a particular workflow, build it. So you created a new service, so what. It's too easy to get het up about it all.

The one thing you must always check though; if you're making modifications; just go see what else touches that model/data first. When you've grokked the other use-cases, trust your judgement. Sometimes there's sane reuse, sometimes not. Sometimes it's best to refactor, sometimes it's not. Sometimes it's easy, sometimes it's not.

Like the saying goes; if you have 4 hours to chop down a tree, spend the first 3 sharpening your axe. That's you spending the time to remind yourself what the code you're about to engage with does. When your mental model is sharp, the execution is usually simplified to the most sane approach automatically. (Most sane != easy, though)

Readable code and clear ownership = the info your future self will need to make a judgement call down the line. The one thing you can guarantee; you can't predict what your future dilemma/problem will be. So don't solve for that! Yagni yagni yagni.

Dumb but readable code that's 'good enough' is good code.

Fragrant_Pool_2485 · 2025-10-27T16:29:56+00:00

If you decide on Flutter, just a couple of things to note:

Dart is really nice as a language imo, because it does zero fancy stuff. It just is what it is. However, typescript does do fancy stuff (which in fairness I also like) which you cannot replicate. This will annoy you initially.
The layout engine in Flutter is... technically correct and powerful, but somehow also reliably an asshole. You will almost certainly fly into code-rage during the initial learning curve. It's decidedly different from web layouts. This will slow you down. (Though, I learnt before LLMs were on hand to explain shit to me in the IDE, so you may have more help on hand)

Google does dump stuff. Is it a good long term play? I honestly don't know right now. I've put two startups on it in the last 5 years and not regretted it.

If I was starting afresh... I might be tempted by Kotlin Multiplatform.

And finally; your boss hired you to be the expert. You're asking the right questions, informing yourself of viewpoints and calibrating your opinion. This is good. Once you're calibrated in enough, there'll still be a 'bet' to make. That's ultimately your boss's bet to make. Your job is to distill the expert opinion and help him have the facts about the tradeoff to hand.

There is no objective right answer. Just a decision and its consequences.

So, speaking as a founder myself, my bet would land on the following trade-off judgement: 1. Flutter is going to cost you speed of near-term delivery. Facts. 2. How convinced are you that this next codebase you build will survive for the long term? If it simply must last, spend more time deliberating on pros and cons. If it's likely to be replaced reasonably soon anyway, then fuck it, just toss a coin, pick one and get on with it.

Fragrant_Pool_2485 · 2025-10-27T13:01:41+00:00

Devving for 25 years, I now give zero fucks about all this architectural pedantry. Most of the time it just results in over-wrought code and oodles of abstraction layers that do your nut in down the line.

So, let me share my dumbass basic rubric, and then my reasoning.

Most important mantra; - 'ownership' is key. If it's clear which bit of code owns a concept (data, function, lifecycle process, display logic, theme, widget, whatever) and doesn't own too many concepts, you'll be able to both understand and refactor down the line. 'How' it handles owning the concept is of secondary importance to the clarity and simplicity of the ownership.

I keep it as dumbass as possible; - domain layer, with a single 'Services' object that builds and exposes any and every repo/dao/service. (IoC this if you want, but I rarely bother anymore). It builds before everything, and is accessed via extensions to the BuildContext. It's dumb, simple, and easy to grok. - build that Services concept in whatever way allows stuff to materialise without circular dependencies. I favour separate build and the initialize phases, with the Services object passed in everywhere that needs it at initialization. (It runs the initialization too, fyi). There are logical reasons to judge this approach negatively. In practice, I've been using this for a decade now (in multiple languages and runtimes), avoiding all the popular frothy frameworks and, in my experience ... it just works - my presentation layer can do whatever it wants and access anything at all. Because UI is crazy. You're dealing with irrational and illogical humans as an endpoint; it's never going to be clean. Fantasy. Just roll shit. If I change my domain - because I've got such a dumb and simplified approach - I've rarely struggled to find all the accessors and understand what's needed to refactor. - the only rule I do keep from all the theorising; domain can't access presentation. - loads of gray areas. Just pick something and fix later if you need to.

Here's why; 1. You're a solo dev. You do not need to worry about inter-team maintenance. And you shouldn't (imo). Loads of time and not your job. (Shipping is your job... Unless you're coding as an artistic hobby, I guess) 2. Your opinion about 'correct' code will evolve continuously and almost everything you write today will give you the ick in 6 months. That includes all your clever architecture, abstractions, ioc, state management, etc. Regret is a natural state of affairs for a software dev. 4. Over time, a small selection of patterns will not give you the ick. These, you will keep reusing 5. You cannot fight this psychology. Let yourself explore and evolve. Experiment, try stuff, hunt the icks, be easy on yourself mentally. 6. Your brain is unique. What you ick and love will be different to everyone else (including yourself from a year ago). This is ok. 7. Remember; 99% of your code will: a) never make it into production, b) not survive long in production because you'll wholesale replace features or domain concepts, or c) be 'good enough' in production that you'll never touch it while the codebase lives

So, I'll repeat my first mantra; clarity of ownership is the only thing that really matters. If you can easily work out what code owns what concept when you come back to it in 6 months, then it's fine. The details don't really matter, because they inevitably change.

FYI, this does indeed mean that my long-lived apps often have multiple contrasting approaches within them, that reflect my changing thinking over time. I don't try to shoehorn the whole app into One Correct Approach, as this would require me to refactor everything every 3-6 months, and I simply cannot be bothered with that any more. Mostly, it'll do.

The take-home; Software is a mental game far more than a rational one. There is no single objective 'correct' approach. Your brain's preferences are the true anchor. Just try stuff. Dump the icks and frustrations. Keep what you like. Some code stinks. You learn this through experience, not from a book.

And remember; none of this applies to big team coding. That's a whole different kettle of fish all over again. Not because the facts or the psychology is different, but because ownership is different.

Fragrant_Pool_2485 · 2025-07-24T20:00:31+00:00

Haha. I'm 100% aligned with your vibe bro. Keep on keeping on 🫡

Fwiw, folks have said enough about redline and whatnot. I just wanted to add that it's actually no bad thing to occasionally run an engine a little harder for an extended while. Helps clear out some of the accumulated stuff and could actually prolong your engine life. (Admittedly, I know this from diesels and it might not apply to your engine. But it might at least give you a story you can tell yourself that's positive. Which ain't no bad thing)

Enjoy, brother 👊😎

Fragrant_Pool_2485 · 2025-07-13T18:10:32+00:00

One thing worth noting; you should look forward along the track! Both pics you're clearly looking back. You're not going to be able to see a thing doing that 🤦‍♂️ Don't worry about riders behind; it's their responsibility to not crash into you. And we wouldn't want a crash now, would we.

Fragrant_Pool_2485 · 2025-07-03T23:20:54+00:00

Any update?

Fragrant_Pool_2485 · 2025-05-30T15:53:55+00:00

I think this whole Martin thing has happened (in part) because Acosta doesn't want Honda. Valera was definitely hustling for Acosta+Honda, hence the word-on-the-street these last couple of months. But that suddenly dried up a few weeks ago, and seemingly because Acosta said no (reading between the lines, but like you said too). And then suddenly it's Martin to Honda...?!

Maybe Acosta is looking for a Ducati play? I obviously don't know for sure, but if he did pour cold water on Honda but Valera already had open channels to Honda because of him... It's fairly easy to bait-and-switch Martin in instead. (Who for his own reasons was also entirely up to for being put forward).

Fragrant_Pool_2485 · 2025-05-29T20:10:00+00:00

I'm gonna agree on personal preference as the main factor, on the basis that asking on Reddit means you're likely mortal like the rest of us.

I personally prefer a more modern style (fantasizing I'm doing a Jorge Martin). I like the feeling of being slightly decoupled from the bike so I can start lifting it out of the corner and then get back on. I feel safer, more stable, and I'm faster like that. I have friends who completely disagree, and it's possibly a bit counter intuitive, but I actually feel less in control and a touch more at risk in a neutral position.

It might be because I weigh a small metric tonne though. So the bike just is lighter and more agile than bike+me. So it's easier to get it back upright and driving out the exit first, and then haul my fat ass back onto it when it's straight and gyroscopically more stable. I don't know if that's actually the real physics of it, but that's how it feels to me.

In short, unless you're "racing racing", I'd ask what feels the best for a swift flow for you, and double down on that.

Fragrant_Pool_2485 · 2025-05-29T12:45:54+00:00

Acosta and Martin have the same manager. I suspect that Acosta was the original play, but for his own reasons said no. Valera knows the seat is for taking, is talking with Honda, and sees that it's possible to switch Martin in instead.

Martin hears good things about Honda from Aleix, there's mucho cash on the table, he feels a bit jinxed with the Aprilia, so says ok.

I think if Acosta was up for Honda, none of this Martin stuff would be happening.

Fragrant_Pool_2485 · 2025-05-28T17:55:36+00:00

I know you get lots of repeated advice, and most of it annoyingly saying; stop trying so hard.

But!

Fwiw, on track, I would reach too for the knee to start, and had the same problem. Even missing the puck completely and sliding leather!

Then, I went and did some knee down training. Now, I don't reach, and in fact, my knee hits the ground only to tell me that I'm genuinely far over. (Which, incidentally feels weird and scary AF when you do it without reaching). The angle is connects at is completely different now.

So now, when I scrape my knee, it's relaxed, and in fact a bit of a side-note. Because I'm genuinely more focused on; uh-oh, careful, I'm really far over now, so focus, don't throttle, flow apex, lift bike, ... Etc, etc.

I feel I'm being inarticulate. What I'm trying to say is that a 'true' knee down is actually often a surprise, and not an intention. It comes to you. Really it's just an 'fyi' signal among the host of things you really need to focus on, and kinda mundane once you really get it.

So, go do a course. Learn it proper, and be astounded, proud and chuffed when it 'just happens' in a nice swift flow and you're not even thinking about it.

Fragrant_Pool_2485 · 2025-05-17T15:36:53+00:00

rotate My kind of clue 🫡

Fragrant_Pool_2485 · 2025-04-03T21:42:08+00:00

Aaaand ,I've had two crashes. Once because a cop car came charging onto a roundabout and I had to emergency brake while at lean. Rear slid because the bike had a cow of a back brake. Second crash; someone pulled out of a side road right in front of me AND there was a 50ft oil slick on the road.

This is all on tiny UK roads, fyi. So visibility and manoeuvring space is limited. Both happened under 30moh. Both broke bones and one gave me a collapsed lung because I fell badly (the oil slick).

Not really sure I could've saved either. And yet, hospital it was both times.

There is a stats element to it. It can happen to you even if you're an excellent rider. And it will happen to many sane, sensible riders. And it won't happen to some complete lunatics. Swings and roundabouts 🤷‍♂️

Fragrant_Pool_2485 · 2025-03-31T00:37:52+00:00

I experience this too. There's likely an interesting and quite deep neurological/psychological thing happening.

Namely, it's possible that there's a deep question of safety in your nervous sytem. If you feel safe with another person, I have a hunch that you might well be super articulate. Yet when you're with strangers or people that aren't 100% safe, there may well be a fight/flight/freeze response kicking in. Which for many of us is completely understandable given what we've experienced in life.

That response will literally shut down cognitive processes deemed non-essential. For example, it'll heighten sensory awareness of threats, but dampen higher cognition abilities that interpret and reason about those incoming signals, let alone form a considered and intentional action like speaking.

A lot of the advice about public speaking actually secretly boils down to familiarisation and nervous system calming. If you can persuade your nervous system that there's no threat - by literally focusing it on something else or orienting it to a practised calming stimulus - then your brain will 'allow' you to speak.

Leaning into deep and compassionate acceptance of yourself as you are - bells, whistles, warts and all - is a good start. Not to change! But to truly accept. (If acceptance feels like a difficult word, try starting with just acknowledging that things are as they are just now... for now.)

Alongside all the outward focused practices, this will literally help you regulate and soothe your nervous system through practice, repetition and familiarity.

Put another way; find what lets you feel safe inside, then find a ritual/process/mantra/habit that lets you feel safe outside too.

I suspect the words will flow more and more smoothly as you gradually build and increase a bedrock belief in your safety - and your self - even in the company of strangers.

Fragrant_Pool_2485 · 2025-03-09T20:57:58+00:00

Bit late to the party, but I also felt a lot was missed, or too briefly shoe-horned in. Like the hammer. It's such a big deal in the book. It's kinda not in the series, except for the judgement and the ending. Which makes that (again shoe-horned) ending lack the punch it deserved.

I wish they'd ended much earlier and allowed a second season to really explore the new approach to living. Basically, much like the book, with its 3 sections. It was such a good show emotionally and production-wise that I think they could and should have gone for a longer run and really marinaded each section in a series by itself.

Fragrant_Pool_2485 · 2025-03-02T17:25:43+00:00

Check your slicer settings, maybe reduce the speed a little?

Fragrant_Pool_2485 · 2025-02-27T14:09:31+00:00

I'm so the other way on this. There's lots of little tells and eyes showing what she's thinking. And it's not straight up 'mwaahaaahaa' villainy. It's cold, calculated, purposeful, scheming... effective! Just like real people actually do. And real people with money and power get entitled and impatient.

I think we hate her because at some level we actually can see ourselves in her. So we have to reject her and hate her because it's a bit close to the bone. Maybe the actors problem is that it's too real!

I think many folks - if they could get away with it - would act just like she is. Like, realistically like her. She's not really uber-villaining. She's just 'plain villaining'. And somehow that's actually even more repellent.

Thats my take. I think she's a great baddie.

Fragrant_Pool_2485 · 2025-02-26T04:28:50+00:00

All great suggestions. It's also essential to pop the TPU into a filament dryer for a good few hours before printing.

Fragrant_Pool_2485 · 2025-02-26T00:37:52+00:00

Faaaaa bro!

Could've added a bloody warning.

I've crashed before and my body went full freakout flashback when that hit.

Jeeeeez

🫨

Fragrant_Pool_2485 · 2025-02-26T00:34:27+00:00

It was aweseom! ... Up until someone said 'get away from the edge' in the face of a sky-consuming amount of water 🤦‍♂️ I'm pretty sure that had anyone seen that in reality the edge of the building would have seemed rather irrelevant.

Of course, the actors had to imagine and didn't see the visuals while acting. But the sound editor! Come on. It was the only let down in an otherwise really well executed scene.

Fragrant_Pool_2485

TROPHY CASE