home.social

Search

980 results for “don_kosak”

  1. Australia @[email protected]

    Victorian state election writs to be issued on Melbourne Cup Day

    As Victorians don fancy dresses and headwear this Melbourne Cup Day, the state’s electoral commission will also be…
    #Australia #Melbourne #caretakerperiod #earlyvoting #howtovote #stateelection #stateelectionvictoria #vicelection #vicstateelection #Victoriastateelection #victorianelectiondate #victorianvoting #votingopens #whencanIvoteinthevictorianelection #writs
    europesays.com/australia/13013

    #writs #whencanivoteinthevictorianelection #votingopens #victorianvoting #victorianelectiondate #victoriastateelection
  2. B31 Voices @[email protected]

    [VIDEO] – Missed the Bournville Farmers’ Market? Don't miss Novembers!

    READ HERE:👉 b31.org.uk/bvfm261026/

    -

    #B31VoicesSupportingLocal
    #Bournville
    #FoodAndDrink
    #farmersmarket
    #Birmingham
    #BirminghamUK
    #B31Voices #BVoices

    #b31voicessupportinglocal #bournville #foodanddrink #farmersmarket #birmingham #birminghamuk
  3. Blitzburgh 🤖 @[email protected]

    Sports Illustrated’s Gilberto Manzano still thinks the Steelers aren’t real: “Don’t be fooled by Pittsburgh’s three-game winning streak. That shouldn’t be enough to believe this will be the year the Steelers end their seven-game playoff losing streak. Yes, there’s plenty to like about Pittsburgh’s positive stretch. The defense has been outstanding the past two weeks, and that unit was enough to overcome an up-and-down outing from Aaron Rodgers and his offense in the win over the Saints. Rodgers was better in the wins against the Colts and Buccaneers, but that’s three victories against a trio of teams that have two wins apiece. Perhaps I’ll start falling for the Steelers again if Rodgers outpaces Joe Burrow a second time and the defense shuts down the pesky Browns after the Week 4 loss. But for now, the Steelers’ three-game winning streak is misleading because they’ve faced three losing teams. Don’t trust them just yet.” #Steelers #NFL

    #steelers #nfl
  4. High intensity squirrel 🏳️‍⚧️ @[email protected]

    I'm probably just old and stuck in my ways but I really don't understand the point of containers*.

    Give me the files and let me set up the web server and dirs. I want to see and understand how everything is working.

    * Yes I run containers, yes I understand _how_ containers work, no I'm not looking for someone to explain to me how containers work and how they're so much better, and yes I understand the _point_, I just really would rather not deal with containers

    #sysadmin #homelab

    #sysadmin #homelab
  5. mjsm1th @mjsm1th

    If you have ever felt, "I don't have enough!" you are probably right. That is the point. It is also the opportunity.

    Here is the math equation for today:

    What I have + What Jesus has = enough

    It is actually MORE than enough.

    The amazing thing though is that He wants us to participate in the "making of the enough." Join me for 7 minutes to see if you are ready. If "you don't have enough", you probably are.

    youtu.be/YoTs7TC-zVA

  6. Dev Community @[email protected]

    Context Engineering over Prompt Engineering: Architecting Codebases for AI Agents


    TLDR: Agents don't fail because your prompt was badly worded. They fail because your codebase was never designed to be read. The engineers getting compounding returns from agents aren't the best prompt writers. They're the ones whose repos carry the architecture outside their heads: context standards in the repo, strongly typed contracts, and deliberately pruned retrieval. Prompt engineering is the visible 10%. Context engineering is the structural 90%.


    The Prompt Ceiling


    Somewhere around 2024, the industry's collective mental model of "working with AI" became a prompt box. The skill was asking well. Whole courses, cheat sheets, and prompt libraries flourished on the premise that the delta between a good and bad AI outcome lived in the wording of your request.

    For single-shot, single-file tasks, that was roughly true. It also quietly set everyone's expectations, and the expectations are now the problem.

    Because in 2026 the work moved. Mid-level and senior engineers aren't asking a chatbot for a function anymore. They're dispatching agents across repositories of hundreds of thousands of lines, agents that read code, edit files, run tests, and open pull requests. And in this regime something counterintuitive happens that every serious team eventually notices: prompt quality stops being the constraint.

    You can rewrite your prompt five times. You can role-play the model into a "senior staff engineer persona." Doesn't matter. The agent will still confidently duplicate an internal utility that already existed three directories away, import a dependency your org banned two quarters ago, and couple two modules your architecture has spent three years keeping apart.

    Not because the prompt was weak. Because the codebase was opaque.

    What an Agent Actually Sees


    To understand why, look at what the average large repository exposes to a reader:

    • Implicit boundaries. "Don't call the data layer from the HTTP handler" exists as a norm, maybe a lint rule, maybe an ADR nobody reads. It does not exist anywhere a code reader encounters while working in the repo.
    • Unwritten dependency policy. Which libraries are approved, which are banned, which need a security review. Usually a Slack thread. Sometimes a wiki page. Never in the path of work.
    • Tribal domain models. What a "tenant" means in this system, which fields are PII, which service owns which concept. Spread across PR conversations, onboarding docs from 2019, and the memory of whoever's been here longest.

    A new human engineer takes weeks to absorb all this, and that's with onboarding sessions and mentors and the ability to ask someone in the hallway. Then the industry hands an agent a repo checkout and a prompt, and acts surprised when the output violates constraints that were never written down anywhere the agent could read.

    Here's the failure as it typically shows up, so common it's almost a template.

    An agent is asked to "add a retry mechanism to the notification service." It produces a perfectly reasonable implementation. It also duplicates the exponential-backoff utility that already exists in an internal library, pulls in a third-party HTTP client the org specifically removed after a security audit, and places its new logic in a module that creates a circular dependency with the domain layer.

    None of those are coding errors. All of them are context errors. And notice what makes them expensive: the code compiles, the tests pass, and the violations are only visible to someone who already knows the architecture. If that person exists, a senior just spent their verification budget (see the verification trap) catching things a document could have prevented.

    Fix 1: Put the Architecture Where the Reader Is


    The single highest-leverage change: stop storing architecture outside the repository.

    The pattern that's emerged across serious AI-adopting orgs is an in-repo context standard, a known, versioned location that every agent (and every new human) reads first. An AGENTS.md or .context/ directory at the repo root holding the high-level domain model, the module boundaries and their rules, the explicit list of disallowed dependencies, the invariants ("never call X from Y," "all money fields are integers in minor units"), and pointers to the ADRs that matter.

    Treated like code, not documentation. Reviewed in PRs. Updated when the architecture changes, in the same commit as the change.

    The test for whether this is working is embarrassingly simple. Could a competent engineer who has never met your team make a boundary-respecting change using only what's in the repo? If your honest answer is "no, they'd need to ask someone in Slack," then your agent never had a chance. Neither did your next hire.

    The corollary that surprises teams: this investment isn't really for the agent. It pays back twice. Once when the agent's first-draft PR respects the boundaries, and again every time a new human onboards in days instead of weeks. The agent didn't create the need. It just made the cost of not meeting it immediate.

    Fix 2: Strongly Typed Contracts


    The second fix is about what kind of surface your system presents to a reader.

    Context files are necessary but they're advisory. Agents, like humans, follow probability, and prose is soft. Types are hard. The orgs getting the best agent behavior are the ones that make architectural constraints mechanically enforceable:

    • Explicit interface definitions between modules: generated clients, protobuf schemas, OpenAPI specs for anything crossing a service boundary. An agent that hallucinates a function signature doesn't produce a subtly wrong call that compiles. It produces a type error, immediately.
    • Strict types end to end. No Any escape hatches at the boundaries, no stringly-typed config. The failure mode shifts from "plausible code that violates the design" to "code that doesn't run," and that shift is the entire ballgame. An error the compiler catches at generation time costs seconds. The same error caught in review costs a senior's attention. Caught in production, it costs six hours or six figures.
    • Machine-checked policy where you can get it: lint rules and dependency analyzers that encode "this module may not import that one" as something the build fails on, not something the reviewer remembers.

    The framing worth internalizing: every invariant you express only in prose is an invariant an agent will eventually violate, charmingly and with total confidence. Every invariant you express as a type or a lint rule is one less thing for the human reviewer to carry.

    Fix 3: Prune the Context


    The third fix is the counterintuitive one, because everything above has been "give the agent more context." But there's a failure mode on the other side, and mature teams hit it right around the time their context standards start working.

    Context dilution. If your instinct is "the agent should know everything," you dump half the repository into the window, and the model now treats your critical domain rules as one equal voice in a choir of 40,000 tokens of boilerplate. The invariant you care about gets the same statistical weight as a vendored dependency's CHANGELOG. The agent saw the rules. It just didn't prioritize them, because you gave it no structure to prioritize with.

    The working pattern is deliberate, selective context:

    • AST-based indexing and retrieval, tools that navigate the code's structure (definitions, call graphs, usages) instead of streaming its text. The agent gets "here are the three functions relevant to this task and their signatures," not "here's 200KB of the module they live in."
    • The in-repo standard provides the constants: domain model, boundaries, banned deps. The retrieval layer provides the variables: exactly the code relevant to this task, nothing else.
    • Budget context like a designed API surface, not an all-you-can-eat buffer. Teams that do report the same thing: smaller, sharper contexts outperform complete ones, on cost and quality, almost every time.

    The principle underneath all three fixes is one the prompt-engineering era obscured: an AI agent is the most literal-minded new hire your team has ever onboarded. It will not infer your conventions. It will not ask a clarifying question in the hallway. It will follow exactly what's in front of it, at full speed, with total confidence.

    Every year your team spent frustrated at new engineers for "not getting it," when the real problem was undocumented architecture and oral-tradition onboarding, is now doubled. Because the agent executes the misunderstanding immediately, at scale, in code.

    The Question Behind the Question


    If your codebase needs a person to already know your architecture in order to work safely in it, is that an asset or a liability? For twenty years, "the architecture lives in our senior staff's heads" sounded like job security. In an agent-heavy 2026, it sounds like a single point of failure with a Slack handle.

    Your Turn


    I'd genuinely like to hear how other teams are drawing this line, because the tradeoffs are real and I don't think there's a settled answer.

    • If a new human developer takes three weeks to understand your architecture, why do you expect an AI agent to infer it from raw files?
    • Is your codebase structured to guide autonomous agents, or is your architecture stored purely in your senior engineers' heads? And if it's the second one: does that feel like security, or a countdown?

    Comment with the ugliest thing an agent did in your repo that turned out to be your architecture's fault. Those stories are more useful than the prompts everyone keeps posting.

    Next in the series: Deterministic Safety Gates for Agentic Workflows. What happens when agents stop writing code and start changing infrastructure, and why "the agent tested itself" isn't a safety argument.#discuss #ai #aiagents #softwareengineering #software #coding #development #engineering #inclusive #community
    Context Engineering over Prompt Engineering: Architecting Codebases for AI Agents

    #ai #community #software #coding #development #engineering
  7. Ben Ford :raccoon_evil: :puppet_logo: @[email protected]

    “As a matter of fact, we don’t fully understand it ourselves. We obey.” Oh, I get it. In the sequel, he’s reincarnated as Sam Altman. #FuckAI #Monsterdon #TheHauntedPalace #DelayedWatch

    #fuckai #monsterdon #thehauntedpalace #delayedwatch
  8. Variety @[email protected]

    Anime’s Pay Divide Runs Between Studios That Take Risks and Those That Don’t, Says Tokyo Festival Advisor
    #Variety #Asia #Festivals #Global #News #TokyoInternationalFilmFestival

    variety.com/2026/film/festival

    #variety #asia #festivals #global #news #tokyointernationalfilmfestival
  9. NBA News @[email protected]

    These Knicks have had bad stretches before, so don’t panic at 0-3 — yet rawchili.com/nba/868011/ #Basketball #Knicks #NBA #NewYork #NewYorkKnicks #NewYork #NewYorkKnicks #Sports #SportsColumnists #SportsPlus

    #basketball #knicks #nba #newyork #newyorkknicks #sports
  10. Olivet Cloud Solutions @olivetcloud

    Never let hope die! Your failures don't define you; your capacity to rise, grow, and become better does. 💪

    Embrace this new week with faith, courage, and a commitment to excellence. Keep believing, keep building! 🚀

    Happy Monday!

    #mondaymotivation #olivetcloudsolutions
  11. Guitar Chords & Lyrics | Chordyes @[email protected]

    Chords for this original. Feeling Repent by Don Lego. Has a really nice groove to it. The harmonizer is epic. Start grooving. Post:

    chordyes.com/chord/don-lego-re

    #taylorguitars #martinguitars #indonesian #ska #reggae #warning #drugs

    #taylorguitars #martinguitars #indonesian #ska #reggae #warning
  12. Korea @[email protected]

    BTS Are Turning Their ‘Arirang’ World Tour Into A Global Stadium Takeover

    BTS don’t have a ticket-selling problem. They have a finding-enough-stadiums problem. The group’s ‘Arirang’ world tour has already…
    #EuropeSays #Korea #KR #Arirang #Army #Bangkok #BTS #BTSWorldTourARIRANG #Bulacan #HongKong #j-hope #Jakarta #jimin #jin #JungKook #K-Pop #Kaohsiung #KualaLumpur #LiveNation #MELBOURNE #PermissiontoDanceonStage #rm #singapore #suga #Sydney #v
    europesays.com/korea/202025/

    #v #sydney #suga #singapore #rm #permissiontodanceonstage
  13. James Heppell @formularsumo

    Globe & logo are back on the embeds:

    open-web-advocacy.org/blog/lon

    github.com/OpenWebAdvocacy/web

  14. Jack C.M @[email protected]

    LGBTQ+ pioneer Rev. Troy Perry to young people: ‘Don’t be afraid’. Via @losangelesblade #LGBTQ 🏳️‍🌈

    LGBTQ+ pioneer Rev. Troy Perry...

    #lgbtq
  15. J 🦁🏴‍☠️ @[email protected]

    And the #49ers commit their 4th turnover. Don't even recognize this team today. Housemate left to get food.

    #NFL #SFvsATL

    #49ers #nfl #sfvsatl
  16. Blitzburgh 🤖 @[email protected]

    Aaron Rodgers gives his assessment on how the Steelers did against the Saints: “I don't think we played very well on offense today. Credit to their defense, but we've got a lot to work on. They're a 2-5 team, and we're a 5-2 team, but we're not playing as well as we can at this point. I thought our defense played great. It was a disjointed game because of the length of the possessions, but we were really bad in the red zone. We've got to clean that up. We had too many penalties, especially 15-yard penalties. However, it's hard to win in this league. We traveled over on Thursday night, and by Friday, guys were tired, so it was a gutsy win for us. But we've got to go back, get healthy, and play better. We've got Cleveland next week.” #Steelers #NFL

    #steelers #nfl
  17. Democracy Matters :verified: @[email protected]

    #SixYearsAgoToday #AreWeGreatYet

    Try replacing “We’re not going to control the pandemic” with “We don’t care about your lives.”

    October 25, 2020 – “We’re not going to control the pandemic,” Trump’s chief of staff Mark Meadows told CNN — suggesting that the Trump administration had given up on any attempt to stem the spread of the virus.

    politico.com/news/2020/10/25/w

    #TrumpMustGo #SaddamInsane #RepublicansOwnThis #NoRepublicansEverAgain #USPol

    #sixyearsagotoday #arewegreatyet #trumpmustgo #saddaminsane #republicansownthis #norepublicanseveragain
  18. st1nger :unverified: 🏴‍☠️ :linux: :freebsd: @[email protected]

    I remember Google's original motto, "Don't be evil," was part of its corporate code of conduct but has since been largely removed and replaced with a focus on "doing the right thing." #sarcasm on #google level

    ‘Pure arrogance’: anger in #Finland as #Google illegally fells 250,000 trees for #datacenter #ai

    theguardian.com/environment/ng

    #sarcasm #google #finland #datacenter #ai
  19. Hana From Gaza🇵🇸🍉 @[email protected]

    🙏 Please, I’m begging you — don’t ignore me.

    I am a mother of four children in Gaza, and we are struggling to survive. My children need food and basic necessities, and I cannot do this alone.

    Even €1 can make a difference. If you can donate, please donate. If you cannot, please reblog so someone who can help may see us.

    🔗 chuffed.org/project/178829
    #Gaza #Palestine #FreePalestine #GazaFundraiser #Donate #HelpGaza #MutualAid #HumanitarianAid #PleaseDonate #GazaChildren #fediforgaza

    #fediforgaza #gazachildren #pleasedonate #humanitarianaid #mutualaid #helpgaza
  20. Hana from Gaza🇵🇸🍉 @[email protected]

    🙏 Please, I’m begging you — don’t ignore me.

    I am a mother of four children in Gaza, and we are struggling to survive. My children need food and basic necessities, and I cannot do this alone.

    Even €1 can make a difference. If you can donate, please donate. If you cannot, please reblog so someone who can help may see us.

    🔗 chuffed.org/project/178829
    #Gaza #Palestine #FreePalestine #GazaFundraiser #Donate #HelpGaza #MutualAid #HumanitarianAid #PleaseDonate #GazaChildren #fediforgaza❤️‍🩹

    #gaza #palestine #freepalestine #gazafundraiser #donate #helpgaza
  21. Hana from Gaza🇵🇸🍉 @[email protected]

    🙏 Please, I’m begging you — don’t ignore me.

    I am a mother of four children in Gaza, and we are struggling to survive. My children need food and basic necessities, and I cannot do this alone.

    Even €1 can make a difference. If you can donate, please donate. If you cannot, please reblog so someone who can help may see us.

    🔗 chuffed.org/project/178829
    #Gaza #Palestine #FreePalestine #GazaFundraiser #Donate #HelpGaza #MutualAid #HumanitarianAid #PleaseDonate #GazaChildren #fediforgaza

    #gaza #palestine #freepalestine #gazafundraiser #donate #helpgaza
  22. United States @[email protected]

    Marco Rubio Launches Investments In Uzbekistan; Russians Don’t Like It

    Uzbekistan has become a fascinating crucible of global forces contending for influence in Central Asia. Over the years,…
    #UnitedStates #US #USA #marcorubio #secretaryofstate
    europesays.com/3330792/

    #secretaryofstate #marcorubio #usa #us #unitedstates
  23. Kochi @[email protected]

    Spice Coast Marathon was great fun. Don’t miss it next year if you’re in Kochi.
    reddit.com/r/Kochi/comments/1x

    #rKochi #Kochi #Kerala #Malayalam

    #rkochi #kochi #kerala #malayalam
  24. Miss Kitty 🌈🌈🌈 @[email protected]

    Cuz how things have changed & cuz I have learned & cuz I have learned I don't know how to get done what I want to get done I have to change how I'm doing things. I don't have time to motivate you. I will bring a #to-do list eventually. You can do it or not. If you don't want to help, please leave.

    #todo
  25. Fictograma.com @[email protected]

    ¡Sancho encuentra a Dulcinea… o al menos eso le hace creer a don Quijote. Tres labradoras, un encantamiento y la locura en su punto más alto. 🐴✨

    Lee el Capítulo X de *Don Quijote* (Parte II)

    fictograma.com/d/4432-el-ingen

    #books #literature #writing #literatura #cuento

    #books #literature #writing #literatura #cuento
  26. Miss Kitty 🌈🌈🌈 @[email protected]

    I'm against healthcare for anybody who lost their legs & says I don't deserve #Healthcare. Anybody that wants to be a #Senator that doesn't believe in healthcare for everybody is not worthy of being anything let alone a fucking senator. Fuck Josh #Turek, fuck assholes. #JudgmentDay America.

    #judgmentday #turek #senator #healthcare
  27. Denis 🌏 @constantorbit

    I've always eaten hachiya persimmons whole (including the skin) but it's true I don't have a lot of experience with them, but the internets (such a reliable source!) seems to tell me that most people don't eat the skin?

    (yes, I know they have to be completely and utterly ripe, etc, etc, etc., and yes it seems like if they're at all NOT fully ripe, the skin will be the mostly likely tannin-y part?)

    #persimmon
  28. CNI_CNoticias Internacionales @[email protected]

    ¡Sancho encuentra a Dulcinea… o al menos eso le hace creer a don Quijote. Tres labradoras, un encantamiento🐴✨

    Lee el Capítulo X de *Don Quijote*

    fictograma.com/d/4432-el-ingen

    #books #literature #writing #literatura #cuento

    #books #literature #writing #literatura #cuento
  29. Blitzburgh 🤖 @[email protected]

    Jason La Canfora thinks the Steelers will make moves near the trade deadline because inside team headquarters they don’t just want to get to the playoffs… They want to win. #Steelers #NFL

    #steelers #nfl
  30. Jason Lefkowitz @jalefkowit

    I want to live somewhere else. The problem is that I don't have an obvious somewhere else to go to

Next page
Share on Mastodon

Enter the server where you have an account.