Загрузка видео...

Не удалось загрузить видео

На главную

15 genius DIY fixes that actually work ‼️ Rope pulley from an old wheel, bottle hose holder, perfect screw trick, rebar tie, car snow shield, and a dozen more clever hacks that save time and money. Which one are you trying first?" #DIYHacks #LifeHacks #HandyTips

48,258 просмотров • 2 месяцев назад •via X (Twitter)

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Loops vs. Graphs, clearly explained! loops are great, but they have a ceiling: a loop makes one unit of work better. it cannot decide which units exist. so you end up with a very good agent running the wrong three steps, in the wrong order, one at a time. Graph engineering fixes this by moving the decision up a layer: what runs, what runs at the same time, and what never runs at all. you need both. here's how it works: a graph splits your system into two kinds of decision. ↳ inside a unit: the loop. produce, check, correct, repeat until green ↳ between units: the graph. split, fan out, merge, gate, send back Prompts → Context → Harness → Loops → Graphs you get parallel work, isolated contexts, and steps that stop running when nothing needs them. the trick is being selective about what becomes a node. only spend a model where judgment lives. merging, ranking, deduping and schema checks are edges, and edges are code. free, instant, and they cannot be argued out of a verdict. a graph where every edge is an agent pays rent on its own wiring. one thing to know before you scale it. a graph has two return paths, and almost everyone builds one. ↳ the correction edge is short. a gate rejects one unit back to the step that produced it, and it fixes the run you are in ↳ the learning edge is long. an accepted result goes back to the splitter as a constraint, and it fixes every run after skip the second and you get a graph that is fast and never gets smarter. next week it starts from the same place with the same blind spots. and a smaller one that eats whole nights: when a unit fails, return that unit, not the batch. send back four slices because one failed and you have just rewritten three correct ones. do it twice in a run and the run never converges. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

73,867 просмотров • 1 месяц назад

Orchestrators vs. Graphs, clearly explained! orchestrators are great, and everyone builds one first. here is the ceiling: an orchestrator sits above the work and routes every message. five agents report to it. it reads all five. it decides what each one does next, and reads all five replies. that is ten trips through one context, and by the fifth agent that context has read four reports, five instructions and its own reasoning about all of them. Graph engineering fixes this by removing the seat: not a better router, but no router at all. you need both, and here is the sentence that resolves the whole confusion: an orchestrator sits above the work and holds all of it. a graph is the shape of the work, and holds none of it. ↳ above the work: one context that has to see everything before anything ships ↳ inside the work: a splitter that hands out and lets go, and a merge that reads nothing Prompts → Context → Harness → Loops → Graphs the coordination did not disappear. it moved into the edges, where it costs nothing and cannot get tired. the trick is noticing what you actually built. if one node has to see every result before the run can finish, you did not remove the bottleneck. you hired it, gave it the longest context in the system, and made it the thing you were counting on to stay sharp. one thing to know before you scale it. an orchestrator degrades in the one way nothing catches. ↳ it does not crash, time out or return an error. it stays up and keeps routing ↳ it just starts routing worse, somewhere around the fifth report, and every downstream agent does exactly what it was told that last one catches careful people. you can have perfect isolation on every worker and still have one window quietly drifting at the top, and the traces will all look clean because each worker did its job. and the one that eats whole nights: the merge is where this shows up first. ranking five findings is not judgment, it is a sort. if a model is doing it, you are paying a model to read five reports so it can put them in an order that three lines of code would have got right, and now that model has read everything too. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

43,781 просмотров • 8 дней назад

🚨CHINESE CARS ARE EATING THE SOUTH AFRICAN MARKET AND THE BILL COMES LATER‼️ South Africa is being flooded with cheap Chinese metal🔥 Showrooms full of Haval, Chery, GWM, BYD, Changan, Omoda and the next badge that arrived last month. Big screens, fake-SUV stance, lights that dance and soft leatherette. A price that looks like a bargain next to a Volkswagen, a Toyota, a Suzuki, a BMW or a Mercedes. That is the con‼️ Youth is buying the advert, not the car, not the service book and not the trade-in🔥They see gadgets and think they stole a German interior at half the money. They did not, they bought a pretty box from a market that is being force-fed volume by a country that treats exports like a weapon‼️ Established cars earn their residuals. Toyota and Suzuki start, service and sell again. VW has parts on a shelf in this country. BMW and Mercedes cost more because the used market still respects the badge when you walk into a dealership three years later. That is not snobbery, that is a number on a valuation sheet🔥 Chinese volume brands do the opposite. Day one they look loaded. Day 800 the screen is still shiny and the offer on trade-in is "kak". Buyers discover the hard way that a car is not what it costs new🔥It is what a dealer will pay when you are done with it. That gap is where these brands live. Parts is where the romance dies. Break something on a well-known Japanese or German car and the country already has the pipeline. Break something on one of these new imports and you sit, week or sometimes months‼️ Finance does not pause while a control arm or a screen module sits on a boat. You are the one without a car. That is not “growing pains.” That is the product. This is market manipulation with a smile, flood the segment, undercut the monthly and stuff the cabin with toys. Long warranty on the brochure. Photograph it like an SUV even when the tyres and the drivetrain say city car. Take the young buyer who would have walked into Toyota, Suzuki or VW. Take the family that would have stretched for a used German‼️ Push them into something that looks expensive and depreciates like a phone. South Africa loses twice. First the customer leaves a proven brand. Then the same customer comes back poorer, waiting on parts, staring at a trade-in that does not cover the hole. The “cheap” car was never cheap. The marketing was‼️ Give it two years. That is when the first wave of owners hit real mileage, first serious failures, first refinance, first trade. Then the clever campaign from Beijing stops looking clever. It looks like a dump of disposable product into a market that cannot afford to learn the lesson twice🔥 If you want a toy with a tablet on the dash, buy the toy and admit it. If you want a car that still has a spine when you sell it, buy what this country already knows how to fix: Volkswagen, Toyota, Suzuki, BMW, Mercedes🔥 The rest is a costume. Beautiful in the parking lot but ugly on the valuation and when it breaks, you are not a customer, you are a waiting list‼️

RaiZel

153,083 просмотров • 19 дней назад