u/NickoGermish

watched 2 days ago how 340 bucks sat in processing on a cross‑chain swap that was supposed to land in 20 minutes. nothing changed in 4 hours, the support bot kept sending the same line, so “best route” stopped meaning anything for me and i went to try a few services. for me letsexchange is the option i open when i want something familiar with a normal set of pairs. changenow is more about a slick ui and quick quotes when i do not feel like digging into details. fixedfloat is the one i use when i actually want to tweak fees and pairs myself. bridge aggregators are what i reach for when i need to move funds across some odd chain combo and see the route. but i didn’t get from all of them in one place the mix i wanted: a cross‑chain swap that starts in my own wallet, ends in my own wallet, does not bother me with an account and does not make me watch every step. so for my last swap I used  simpleswap and so far it’s the most acceptable option for me, the swap landed within their quoted window while i just watched it go through from my wallet to the destination address. still not sure if that is the perfect setup, so i am curious what else matters to others in these services, maybe i’m missing smth

So last Tuesday I almost signed a permit2 approval that would have drained a bit I have been LPing out of for two years. The screen just showed a hash and a “Data Present” line. My brain went "Yeah, seen this before" and my thumb was already on the button.

Barely caught it. The thing people underrate with blind signing is that the muscle memory IS the attack surface. You stop reading because you cannot read it anyway. Ledger has been pushing the Clear Signing thing and the ERC-7730 stuff helps, but the parser still depends on metadata existing for that contract somewhere, so a lot of stuff falls back to generic screens. A lot of the random LP contracts I touch still fall back to hex. I keep the hot DeFi stack on an ERA wallet sitting next to the Ledger, mostly because the hex‑to‑readable translation runs on the device itself and the QR signing means my laptop never touches the key. It did not click for everyone in my group chat though, some people hate the two‑device dance.

So I am curious, for the people here actually farming, what do you do when the contract is too new for any readable parser? Tenderly sim every tx or just YOLO?

Saw another “best ADHD apps for kids” list today. It bugged me. Same stuff again: chore apps, reward charts, stars, little games, points for doing whatever. Fine. I get why people use them. We’re getting our son assessed after school brought up some concerns, so maybe I’m noticing this more than I normally would, but it feels like every app assumes the kid is the one who needs another system. That’s not really where I’m stuck. I’m stuck on the parent side. The part where something is already not working and I’m standing there trying to figure out whether I should push, back off, explain, ignore it, start over, whatever. Most app lists don’t touch that. They just give the kid another thing to complete. Savvy Kid came up somewhere while I was looking around, and I didn’t close it right away. Small thing. But lately that’s kind of the bar. It seemed less like another thing for him to keep up with.

our L&D team in Columbus got the old vendor tool pulled mid-cycle. compliance flagged it, IT blocked access, and we had a backlog of placements sitting there with no way to process them.
started googling at like 11pm, trying to find anything that wouldn't require a new vendor contract and a six-week procurement cycle. ended up comparing whatever came up for spoken English assessment that wasn't the usual suspects.

i looked at a few options:

Testlify, decent for general skills screening, but the English component isn't built around spoken fluency. and that's exactly what academic and corporate programs are testing for.
our old tool, I don't write specifically the brand, so as not to ruin their reputation, perhaps it didn't suit us, inflated scores badly. candidates who tested at C1 struggled in live conversations. placement decisions were wrong roughly a third of the time our academic partners needed CEFR mapping or they wouldn't touch the results. that narrowed it down fast. ended up on smalltalk2me - it's built for spoken English placement, 15 minutes, scores come back the same session. no waiting two weeks for a human rater to get around to it. honestly kind of annoyed it took a compliance fire for me to find it.

still testing whether it holds at our placement volume.

i get paid in usdt from freelance work, so i dont like sending money to bank just for betting, dont want to mix it with regular transactions. tried few offshore sites with crypto. some take only btc or eth, which is not for me bc i mostly use usdt. also had a couple moments where deposit flow felt a bit sketchy, rechecked everything twice before sending. now mostly using 1win indias bc it supports more coins in one wallet and i can switch between inr and usdt inside. i just move from binance and  play small without overthinking it. but i dont keep much there, just what i plan to use. dont really want keeping bigger balance on betting sites, so i prefer moving in and out even if its a bit annoying

do you keep balance on exchange or on sit  or move in and out for every session?

Tried to swap a low-liquidity alt into USDT last night with a floating rate and got a worse fill by the time my deposit confirmed. Not a huge amount but enough to remind me why I hate using floating quotes on weird pairs. I might be misunderstanding how these services handle execution but it feels like if the first liquidity source moves or dries up you either get a worse rate wait forever while it reroutes or end up talking to support while your funds are just sitting there.

I tested simpleswap after that mostly because they claim to use multiple liquidity sources and I used fixed rate the next time. It did what I expected but Im assuming the fixed quote probably has some buffer baked in so maybe Im just paying for certainty instead of getting a “better” deal.

Mustafa Suleyman said it out loud at Build, which, honestly, i wasnt expecting: "true self-sufficiency in AI." Not a partnerships update. Not a roadmap slide. A pretty direct admission that Microsoft is trying to cut the cord from OpenAI.

Seven new in-house models dropped at once.

So yeah. The plan, as far as I can tell: build enough in-house models to stop depending on OpenAI, wrap everything in an agent layer (Microsoft Scout is literally OpenClaw's open-source tech but baked into Windows at the OS level), and push inference down onto local hardware via the RTX Spark chip. That's the through-line connecting all of it - self-sufficiency at the model layer, the agent layer, and the compute layer.

Like I said, the self-sufficiency framing is the part worth watching. Whether the models can actually reach frontier quality is a different question, and Suleyman kind of dodged it - MAI's flagship reasoning model was benchmarked against Sonnet 4.6, not Opus 4.8. Maybe I'm missing something, but that's a weird comparison to lead with if you're claiming the absolute frontier.

i think experienced users sometimes become more vulnerable. beginners are cautious because everything feels unfamiliar.

veterans start speed-running approvals because they’ve interacted with thousands of contracts without issues before.

then one day muscle memory catches up to them.

feels like a lot of recent drains happened because people became too comfortable operating in environments they never fully verified in the first place.

tl;dr: Matt Pocock, a TypeScript educator, open-sourced his personal .claude/skills/ directory and it crossed 80,000 GitHub stars in weeks. The repo is explicitly labeled "not for vibe coders" - which is exactly why people who are almost-but-not-quite engineers should pay close attention to it.

the README says "skills for real engineers" in the first line, which either intimidates you or makes you want to prove something.

the thing most people get wrong is treating the "engineer-only" label as a gate rather than a diagnostic.

the most common failure mode in software development is misalignment - you think the agent knows what you want, you see what it built, and it didn't understand you at all. same problem, AI age or not.

that failure isn't reserved for beginners. it's structural. and the five skills here don't require a CS degree, they require you to care about precision.

improve-codebase-architecture finds "deepening opportunities" in your codebase, informed by the domain language in CONTEXT md and the decisions in your ADRs.

concretely, it dispatches an exploration agent through your project looking for architectural friction, surfaces the top five issues in priority order, and tells you which files are involved, what the fundamental problem is, and what a concrete fix looks like. if you've ever had a project where six months of "ship it" sessions turned the codebase into load-bearing spaghetti, this is the command that diagnoses it without you having to already know what's wrong. the catch: it gives you the list, not the fix. your judgment still does the triage.

grill-me tells the agent to ask one question at a time until a plan has been tested against each branch of the decision tree.

the fix for misalignment is a grilling session - getting the agent to ask you detailed questions about what you're building.

after maybe seven or eight questions and ten minutes of back and forth, you go from "here's a vague thing I want to change" to an actual design with every downstream decision already resolved. other tools ask five high-level questions and then wing the rest at implementation time. grill-me keeps pulling the thread until the whole decision tree bottoms out. WAY more thorough, and yes, it costs tokens.

which brings you to caveman.

the ultra-compressed "caveman" mode claims to cut token usage 75% by dropping fillers, articles, and pleasantries while keeping full technical accuracy.

in practice, one test run comparing the same response with and without it came in at 768 tokens versus 502 - roughly a 30% reduction on that specific output, which compounds hard across a long session.

at $3 per million input tokens on the current API, that's a real cost difference that stacks across hundreds of daily interactions.

the sharp design choice is that caveman mode auto-exits for security warnings, irreversible operations, or any multi-step sequence where terse output could get you in trouble. it knows when clarity costs less than brevity.

zoom-out is the one that catches you before you make a confident wrong decision. you run it when the architecture review or grill-me session produces a recommendation that lands above your current understanding of the system. it starts from domain vocabulary, traces which modules interact, maps where files are read and written, and then places the specific claim you're evaluating into that full context. in one example, it revealed that an architectural "problem" flagged by the codebase review was actually unfounded, the ranker and the logging stage were doing different things entirely. catching a ghost before you spend two days refactoring it is NOT a trivial outcome.

the fifth skill in the active manifest is handoff

, and it solves a grittier problem: you've accumulated valuable context in a session but you need a fresh context window, or you want to pass a completed planning session to a different tool for implementation. handoff distills everything into a markdown brief, with whatever framing you specify, problem statement, key decisions, resolved specifics, and hands it cleanly to the next session.

skills teach Claude procedural knowledge - how to follow your deployment process, when to write tests, how to structure issues. MCP servers give Claude new capabilities - query Postgres, call Slack APIs, access file systems.

handoff sits at the seam between those two worlds, letting you carry the procedural output of a skills-heavy session into a spec-driven implementation tool without polluting either context.

the open question: improve-codebase-architecture and grill-me together can generate a very complete design brief, but I'm genuinely not sure whether the quality of that brief degrades significantly on larger, messier codebases versus the small, well-scoped projects they seem to be demo'd on. the token cost of running both back-to-back on a 50k-line repo could get uncomfortable fast, and I'd want to see more evidence before treating that workflow as reliable at that scale.

so, the takeaway is this: the five skills - improve-codebase-architecture, grill-me, caveman, zoom-out, and handoff - are worth using whether or not you consider yourself an engineer, because they address problems that have nothing to do with skill level and everything to do with process.

the repo was MIT licensed and had about 79,500 stars and 6,900 forks as of mid-May 2026

, all installable with a single npx command. the "not for vibe coders" label is doing marketing work, mostly. what these skills actually enforce is precision before implementation, context continuity across sessions, and cost discipline inside long agentic workflows - none of which require a decade of software experience, just the willingness to slow down before you ship.

curious if others have hit the limits of these on larger codebases and what the degradation actually looks like.

swapped $2.5k worth of ETH into a mid-cap token recently. the preview showed 3% slippage, I set my tolerance to 4% and went ahead. came out $183 below the quoted amount. the pool showed roughly $800k in 24h volume so I assumed it was fine. I

s this expected at this size or did I mess something up?

been going back and forth on this for longer than i'd like to admit. just registered a ltd, first proper company, and the number of accounts out there made the decision harder than it should be. so here's what i actually looked at, in case it helps anyone else in the same spot.

the criteria that ended up mattering to me: payment reliability (can i access my money when i need it), tax compliance overhead (how much admin do i have to do myself), support responsiveness, and whether the account would still make sense as HMRC's rules change this year. that last one caught me off guard.

i'd written off ANNA money early on, assumed it was more of an invoicing tool than a real business account. ended up being what i actually went with. the reason is practical: it combines a business account, bookkeeping, and MTD compliance in one platform, automatically categorising transactions and preparing records for HMRC submissions, which means the tax side isn't a separate task i have to remember.

where it gets the most praise in reviews is customer support, with many users reporting replies within minutes and real people rather than bots.

only things is: it works as a current account supporting domestic GBP payments but doesn't hold foreign currency balances, so if you invoice internationally in EUR or USD and want to hold those currencies, you'd need a separate tool for that piece.

Tide was the first name i seriously looked at. setup is fast and the invoicing tools are decent. but the pattern that kept coming up across multiple review sources was account freezes with no clear timeline.

accounts frozen for "security reasons" with the entire balance blocked, not just the transaction under review, on paydays when businesses needed to move money. one business reported being put on hold at a critical time when they needed to pay salaries and receive payments, with no response from support over three days despite urgent attempts.

when the hold was eventually explained, it turned out to be a routine check to confirm the nature of the business and legitimacy of payments, information that had already been provided at setup. for a new company with thin cash buffers, that kind of disruption isn't a minor inconvenience.

Revolut Business came next on my list, mainly because the multi-currency functionality is genuinely strong for anyone dealing with overseas clients. the app is polished, FX rates are competitive, and the Xero integration works well.

but one of the most severe complaints involves accounts being restricted or funds frozen without prior warning or clear explanation during compliance reviews. the customer service model relies heavily on automation, which appears to leave little room for personalised support when users face complex issues like frozen funds. there's also no FSCS deposit protection on Revolut Business accounts, which is worth factoring in if you're planning to hold any meaningful balance there.

one thing that shifted my thinking on all of this: from 6 April 2026, the first wave of 860,000 sole traders and landlords must use digital software to manage their tax affairs, marking the most significant shift in self-employment taxation in a generation, starting with those earning over £50,000 a year.

from April 2027 that threshold drops to £30,000, and from April 2028 it's expected to fall further to £20,000. most comparison posts i found were written before this was confirmed and don't account for it. picking an account that's already HMRC-recognised for MTD removes a whole category of future admin.

so, when it comes to choosing a business account for a new company, what i'd actually weigh is: payment access reliability first (a frozen account on a supplier deadline is worse than paying slightly higher fees), then built-in tax compliance, then support that reaches a human without a two-day wait. multi-currency depth matters only if you genuinely invoice in foreign currencies and need to hold them. for a UK-only ltd with HMRC obligations and no dedicated accountant, the account that handles the most admin automatically wins, not the one with the longest feature list. FSCS protection is worth checking on any account where you plan to hold more than a month's operating cash.

what does your setup look like - are you running through Xero or handling tax yourself, and do you have international clients?

posting this because i've spent the last three months switching accounts after our previous setup caused us to miss a VAT payment date, not because of the tax itself but because our business account froze mid-month and we couldn't move money when we needed to. if you're self-employed or running a small ltd and you care about keeping HMRC happy, the account underneath your business matters more than most people give it credit for.

i went into this assuming ANNA money wasn't really for me - looked like an invoicing tool dressed up as a bank. ended up being what i actually went with. the reason is practical: it calculates your running tax liability in real time as transactions come in, so you always know what you owe HMRC before the deadline surprises you. the one limitation worth naming is that it doesn't integrate with Sage, so if your accountant works in Sage, you'd need to export manually or use a different account for that part of the workflow.

Tide was the first place i looked seriously. the invoicing tools are decent and setup is fast for most registered businesses. the problem that kept coming up in nearly every account freeze story i read - and there were a lot of them - is payments going onto pending for days with no clear explanation, support taking hours or sometimes days to respond via chat, and in some cases entire account balances locked while a "review" runs in the background. one review described needing to pay employees on the exact day the account was frozen. that's not a compliance issue with HMRC, but it becomes one fast if you can't move money to meet obligations.

Revolut Business was next on my list because the multi-currency functionality is genuinely useful if you invoice internationally. the app is polished, the FX rates are competitive for what you pay. but the account freeze issue runs just as deep there. compliance reviews that lock access to funds for weeks, sometimes longer, with no timeline given and no human to escalate to - this came up repeatedly. there's also no FSCS deposit protection, which matters less day-to-day but changes the risk calculation if you're holding significant balances.

one thing worth knowing: Making Tax Digital for Income Tax is expanding in 2026, and HMRC-recognised tools that automate quarterly submissions are becoming a practical necessity rather than a nice-to-have. most older comparisons online don't factor that in at all.

two questions that might help you decide: do you manage your own tax filing, or does an accountant handle everything through Sage or another platform? and how much does same-day access to your funds matter to your cash flow - would a 48-hour freeze genuinely put you in a difficult position with suppliers or HMRC?

if daily payment access and built-in tax tracking are both on your list, that combination narrows the options pretty quickly.