Simon Flack 💙💛

"I thought I had 30-40 subscriptions costing €500/month..." I did not. I share my journey from discovery to shock to solution: youtu.be/tgdxbwq4xWA

💳 Yesterday, I found 78 subscriptions totalling €1,000/month. Today? 11 more... now over €1,200. And I’m still not done. Subscriptions are out of control—and I’m building SubScout to fix it. Join the waitlist 👉 subscout.app #BuildInPublic

@AlbaniaMykonos @gvravel @LLColorMeBlue @atrupar Sounds more Geordie to me

@gvravel @LLColorMeBlue @atrupar That’s a Scottish accent

I'm going to put together a thread on Trump's rally in Wildwood, New Jersey. Follow along for clips and commentary.

@aidThompsin It’s more like $450m if you include the back-dated pre-judgement interest. And to appeal he’ll need to put up an additional 20% to account for accruing interest

@MikeBseen @getifyX I believe the concern is about unintentional impact on screen readers if you use these elements purely for presentational purposes.

@getifyX same here, I don't see the problem with br or hr. 🤷🏼‍♂️

I unapologetically use <br> and <hr> in my markup.

@ecyrbedev I did `read only {}[]` TIL `readonly string[]` is allowed, but `readonly Array<string>` is not. Perhaps tomorrow I will learn why…

📢 Typescript tip Day 5: we saw Tuple concatenation 1⃣ Tuples are a powerfull way to ensure typesafety access in typescript 2⃣ If you know an array has a fixed number of items at compile time, prefer using Tuples to describe them It's safer and garanty no out of bound access

@Amy_Hupe This is beautiful. I'm grieving the recent loss of my partner, and I just wanted to say these words moved me. thanks for sharing 💜

It’s Sunday and I should be cleaning so I wrote about loss. amyhupe.co.uk/articles/2023-…

@FrontendMasters @EmmaBostian I think that's a common misconception about `visibility: hidden` -- It doesn't just hide things visually - it's also removed from the accessibility tree: #accessibility_concerns" target="_blank" rel="nofollow noopener">developer.mozilla.org/en-US/docs/Web… To achieve that, it's recommended to add a `sr-only` or `visually-hidden` class to your CSS

"Accessibility and CSS go hand in hand, significantly impacting user experience." @EmmaBostian delves into the vital connection between web development and accessibility. Get the foundations of CSS in Emma's course: frontendmasters.com/courses/css-fo…

@HicksTirra @KateEvert @KMA_Jackson @atrupar It’s so funny we need to decode these “truths” Imagine reading this and believing every word…

@KateEvert @KMA_Jackson @simonflack @atrupar Hahaha he said Cohen broke down?? Of course

it's a day that ends in y which means Trump is hurling abuse at judges and prosecutors

@housecor withX

Poll: Which boolean variable name do you prefer? showX isXVisible The former is shorter, but sounds like a function. The latter is clearly a bool, but a bit clunkier to read.

@DavidKPiano This is great. V5 upgrade is on my todo list. I’m also a few months behind on Stately office hours. You folks sure keep busy! Lots of good stuff to catch up on it seems.

Yes, that is correct. We recently introduced the ability to have dynamic parameters for action and guard objects, which further reduces the need for accessing context or events directly: entry: { type: 'greet', params: ({ context }) => ({ name: context.user.name }) }

Thinking about a potential XState v5 API that greatly improves inferred types and reduces boilerplate. You can provide actors, actions, guards, etc. What do you think? Bikeshed: setup() or provide() or similar 🤔

@DavidKPiano Love it. Do I understand correctly that this is only for services, actions, guards etc that don’t need access to context or event?

Btw, they're referenced by name instead of being used directly so that: - We can visualize it ✨ - You can provide different implementations (flexibility++) Also, you can still createMachine(...) as normal. setup() would be an optional API.

@mattpocockuk @TkDodo Can’t speak for other people, but I’m much more likely to read a thread of normal size tweets than 1 single long post. So many times I click “see more” then back straight out when I see how long it is.

I'm not sure that links are actually punishable, I think that's an over-simplification. I've had posts with links do well. The most important thing is if people interact with your post. On a thread, this means clicking on the post. On a long post, this means clicking 'see more'. Either works.

So with this pro subscription - do we still do threads or is it just one big post now? What's the etiquette ?

@UstaNajjar @turnrighthere @fesshole "Must've" and "would've" sound like "must of" and "would of," but hey, we usually get the meaning! It's like the classic "their/they're/there" mix-up. Language is quirky, so let's focus on understanding each other rather than nitpicking.

I've been struggling with my bowels for years now, can't have a decent poo without a million wipes after. I squatted in the bath to wash my arse with a high powered shower head for about 15 mins. I must of released 30 years of debris, going to go again next week.

@LauraKalbag @statelyai Oops, classic time zone hiccup! Shouldn't it be EDT until November? Had a fleeting moment of stress considering the calendar gymnastics I do twice a year with my team stateside. 😅

@statelyai Sorry everyone, this is my fault! I got confused because 2PM EST is 7PM in my Irish time zone🤦 Timezones are hard 😭

🚨 Correction The webinar will take place at 2PM EST

@TkDodo @he_zhenghao If a change in fooData requires a refetch of bar then I would put that data in the queryKey

@he_zhenghao Yes, this is the way.

@threepointone youtube.com/clip/Ugkx7mTJK…

@SimeonC_ @TkDodo @acemarke @tannerlinsley @diegodsdead It sounds like you’re looking for the `select` option const booksGraph = useQuery({ queryKey: [‘books’], queryFn: getBooks, select: books => transformToGraph(books) })

@tannerlinsley have you considered adding a “storeAs” option to “useQuery” to customize how query data gets stored in cache? I’d be sooo useful to me right now

@n___vc @DavidKPiano Good catch! That’s the only thing wrong with this. The real power move is to slap a `@.ts-ignore` on there

@simonflack @DavidKPiano that‘s technically not working properly & a bad type. type is saying it‘s YES or NO, but you are assigning an array

React state hooks don't scale Use something that truly scales, like mutating a global object on window