home.social

Search

34 results for “macf00bar”

  1. @macf00bar das ist ja nur, dass ich auf events so busy bin, damit ich mit niemandem reden muss ;) #schuchtern

  2. @a32 I think the interesting part here is not “are collapsible sections useful?” For some people, obviously yes.

    The problem is that #region puts a personal/editor preference into the shared source file. One person’s preferred visual grouping becomes everyone else’s diff noise, review noise, merge-conflict surface, search noise, and editor noise.

    To me, that is the wrong layer. The compiler does not care how humans want the file presented. Even most of the team disagreement here is not about semantics, but about presentation: “I want to see methods grouped/collapsed this way” vs “I want to read the file as plain code.”

    In 2026, IDEs should be much better at separating source from view. Let the repository contain a canonical representation, and let each developer locally choose their own view: virtual indentation, virtual wrapping, virtual member grouping, folding rules, maybe even “show constructors/properties/methods under visual headers” without writing those headers into the file.

    JetBrains/ReSharper’s Virtual Formatter is basically the kind of direction I mean: show code according to local formatting preferences without actually rewriting the source. I don’t think that solves regions specifically, but it proves the general idea is not absurd.

    So I don’t want to delete other people’s ability to collapse code. I want that ability to be local, configurable editor behavior, not preprocessor directives committed into shared code. Use regions when they express something genuinely structural or exceptional, sure. But using them as a substitute for an IDE view model feels like solving a UI problem by editing the data.

  3. Have a look at the latest #hanselminutes podcast by @shanselman with guest @steipete
    youtube.com/watch?v=Wm7tsiJ1nIo
    I work with multi-agent setups and LLM-driven skill pipelines daily, so #OpenClaw has been on my radar for a while. This conversation really captures both why it's exciting and why I haven't pulled the trigger on installing it yet.
    Peter built this thing for himself, on localhost, single user, full trust. Then it went viral ("stripper pole growth, not hockey stick" as his friend put it) and suddenly people who don't read docs are reverse-proxying their dashboards to the open internet. Peter openly says he kind of stopped having fun because he's now fixing security issues for people who ignore the documentation. That hits close to home for anyone maintaining developer tools.
    Scott's setup is genuinely compelling though. His agent "Tony" monitors his blood sugar, watches for his son's college acceptance letters, fetches files from remote machines via Telegram. Scott compares it to Star Trek and Peter confirms: yeah, that was the goal.
    Best story: Peter's agent got dropped into a bare Docker container with nothing installed, said "I'm sad lobster now," and then wrote its own curl implementation from raw sockets and a C compiler. Called it "lobster-curl 0.1."
    The part that got me thinking: Scott says "you're talking to yourself in the mirror." The agent has no intent of its own, you shape it through the soul file. And yet both of them clearly have a relationship with their agents that goes beyond tooling.
    I can feel the excitement. I get it. But giving an agent access to my Telegram, my files, my health data... the security-conscious part of my brain keeps pumping the brakes. Peter's own experience kind of validates both sides: it's genuinely empowering (someone at Claude Code Anonymous in Vienna helped his 60 year old dad automate a beer business with zero coding background), and genuinely risky if you don't understand what you're configuring.
    Definitely worth a listen.

  4. @bitbonk @Migueldeicaza @nuke @matkoch hell yeah! #nuke for the win. I's so glad that I convinced my team to let me migrate to nuke. I love it!

  5. @khalidabuhakmeh Man, I was this close to posting something similar. The whole transcript nails it .. the way M$ (or as I've taken to calling them, #Microslop) is force-feeding AI down users' throats like they're geese in a foie gras factory, all while hoping to monetize "engagement" to justify the obscene electricity burn.
    I never thought we'd get someone worse than Ballmer with his "Linux is a cancer" rants. But then Satya Nadella goes to Davos and essentially tells users they need to start using the AI that's been shoved on them to justify the energy Microsoft is burning on infrastructure they never asked for. The sheer audacity. "We might lose social permission to use energy if these tokens aren't improving healthcare, education..." ... as if Copilot in Notepad is somehow advancing humanity.
    Meanwhile, half a billion Windows 10 PCs are capable of upgrading to 11 but their owners refuse. Users on X responding to Microsoft's "Copilot for work" ads with "No, you heard wrong. Literally no one asked for all this AI." The Windows president having to lock replies on his agentic OS announcement after the backlash. Tools like "#Winslop" trending because people desperately want to debloat the AI cruft.
    #microsofts reading of the room has never been worse. No wonder Linux and macOS are seeing real migration waves.

  6. I just completed all 25 days of Advent of Code 2024! #AdventOfCode adventofcode.com/

    finished, and re-did it, this year with the new #file-based-app in mind and #dotnet10 and threw in some #spectreconsole to spice it up (I won't tell how long it took but at least, it was fun to play around). let's see If I got time for the 2025 version this year or it will have to wait until 2026.

  7. @bitbonk definitely an even better fit for #nuke than for aspire!

    there should be a t-shirt option out there ;-)

  8. @koopa that's why my team and I decided to use #resharper for it. the same settings file can be use in #Rider and there is a command line tool version that can also be used with the same settings file (I am tinkering to use it in a pre-commit hook).

  9. Watched yesterday the new Naked Gun with Liam Neeson as Frank Drebin’s son. The first ten minutes? I chuckled. A couple of decent gags gave me some hope. Then it slowly turned into a hostage situation and my free time was the ransom.

    Nostalgia is milked so hard the cow’s ready to sue. The humor after the opening feels like it’s been stuck in storage since the 80s and forgot to renew its passport. This isn’t a remake...it’s a museum exhibit, complete with the “Do Not Touch” sign, except here it reads: “Do Not Laugh Too Hard, You Might Remember the Original.”

    Neeson tries his best with deadpan delivery (it looks like he’s serious about doing comedy). But the movie mostly drifts along on the fumes of “Remember the old jokes? We remember them too!” If you loved the original, you might grin here and there....but mostly it serves as a reminder that comedy ages quickly and not always gracefully.

    In the end it feels like a bold experiment: take a comedy, surgically remove most of the comedy, then release it as a major studio film. If that’s supposed to be the punchline, the setup....lasting only 85 minutes....still didn’t land.

    My verdict: Cherish your fond memories of the original. If you’ve got free time on your hands, do literally anything else. Watch paint dry, organize your sock drawer, or better yet, actually rewatch the original Naked Gun. At least then, you’ll be laughing for the right reasons.

    #NakedGun #fail #milkednostalgia

  10. To be fair to nuke though, I got it to work now, I can only debug it with VsCode but not with Visual Studio, but that's a minor glitch.

    I think, with what I have now I can move on and create even more complex builds.

    #nukebuild #buildautomation #ci #azuredevops #csharp #dotnet

  11. To be fair to nuke though, I got it to work now, I can only debug it with VsCode but not with Visual Studio, but that's a minor glitch.

    I think, with what I have now I can move on and create even more complex builds.

    #nukebuild #buildautomation #ci #azuredevops #csharp #dotnet

  12. To be fair to nuke though, I got it to work now, I can only debug it with VsCode but not with Visual Studio, but that's a minor glitch.

    I think, with what I have now I can move on and create even more complex builds.

  13. To be fair to nuke though, I got it to work now, I can only debug it with VsCode but not with Visual Studio, but that's a minor glitch.

    I think, with what I have now I can move on and create even more complex builds.

    #nukebuild #buildautomation #ci #azuredevops #csharp #dotnet

  14. To be fair to nuke though, I got it to work now, I can only debug it with VsCode but not with Visual Studio, but that's a minor glitch.

    I think, with what I have now I can move on and create even more complex builds.

    #nukebuild #buildautomation #ci #azuredevops #csharp #dotnet

  15. Just to be on record:
    I honestly didn’t expect that even non-YAML code (👀 @nuke build – yeah, I’m talking to you...) would require just as many fucking never-ending commits.
    Azure DevOps has proven me wrong. (lol)

    The real pain point?
    No local test run
    No Run pipeline locally
    Zero feedback until you PR, merge, and let it rip on main

    So yeah, we’re basically testing on the main branch. In production. In 2025.
    For everything else, there’s: ¯\_(ツ)_/¯

    Also, I firmly believe that not only Carthage must be destroyed, but also:

    - CI/CD with no local feedback loop
    - “Works on my machine” excuses
    _ YAML files that silently break on pasted tabs
    - And every doc that starts with “just”

    And yes — I really thought nuke build would make things better...
    But after 24 hours of commits, checks, and trial-and-error, I’ve been proven otherwise (and I really wanted to make it work and local debugging is awesome — but it’s useless when the docs are a soggy mess and don’t reflect reality.)

    #DevOps #AzureDevOps #YAML #NukeBuild #CI #CICD #MainBranchDrivenDevelopment
    #WorksOnMyMachine #AgileStruggles #ModernDev #CarthagoDelendaEst #DevHumor
    #BuildFail #DebuggingHell #LocalIsNotProd #SoftwareEngineering #DotNet #DevLife

  16. Just to be on record:
    I honestly didn’t expect that even non-YAML code (👀 @nuke build – yeah, I’m talking to you...) would require just as many fucking never-ending commits.
    Azure DevOps has proven me wrong. (lol)

    The real pain point?
    No local test run
    No Run pipeline locally
    Zero feedback until you PR, merge, and let it rip on main

    So yeah, we’re basically testing on the main branch. In production. In 2025.
    For everything else, there’s: ¯\_(ツ)_/¯

    Also, I firmly believe that not only Carthage must be destroyed, but also:

    - CI/CD with no local feedback loop
    - “Works on my machine” excuses
    _ YAML files that silently break on pasted tabs
    - And every doc that starts with “just”

    And yes — I really thought nuke build would make things better...
    But after 24 hours of commits, checks, and trial-and-error, I’ve been proven otherwise (and I really wanted to make it work and local debugging is awesome — but it’s useless when the docs are a soggy mess and don’t reflect reality.)

    #DevOps #AzureDevOps #YAML #NukeBuild #CI #CICD #MainBranchDrivenDevelopment
    #WorksOnMyMachine #AgileStruggles #ModernDev #CarthagoDelendaEst #DevHumor
    #BuildFail #DebuggingHell #LocalIsNotProd #SoftwareEngineering #DotNet #DevLife

  17. Just to be on record:
    I honestly didn’t expect that even non-YAML code (👀 @nuke build – yeah, I’m talking to you...) would require just as many fucking never-ending commits.
    Azure DevOps has proven me wrong. (lol)

    The real pain point?
    No local test run
    No Run pipeline locally
    Zero feedback until you PR, merge, and let it rip on main

    So yeah, we’re basically testing on the main branch. In production. In 2025.
    For everything else, there’s: ¯\_(ツ)_/¯

    Also, I firmly believe that not only Carthage must be destroyed, but also:

    - CI/CD with no local feedback loop
    - “Works on my machine” excuses
    _ YAML files that silently break on pasted tabs
    - And every doc that starts with “just”

    And yes — I really thought nuke build would make things better...
    But after 24 hours of commits, checks, and trial-and-error, I’ve been proven otherwise (and I really wanted to make it work and local debugging is awesome — but it’s useless when the docs are a soggy mess and don’t reflect reality.)



  18. Just to be on record:
    I honestly didn’t expect that even non-YAML code (👀 @nuke build – yeah, I’m talking to you...) would require just as many fucking never-ending commits.
    Azure DevOps has proven me wrong. (lol)

    The real pain point?
    No local test run
    No Run pipeline locally
    Zero feedback until you PR, merge, and let it rip on main

    So yeah, we’re basically testing on the main branch. In production. In 2025.
    For everything else, there’s: ¯\_(ツ)_/¯

    Also, I firmly believe that not only Carthage must be destroyed, but also:

    - CI/CD with no local feedback loop
    - “Works on my machine” excuses
    _ YAML files that silently break on pasted tabs
    - And every doc that starts with “just”

    And yes — I really thought nuke build would make things better...
    But after 24 hours of commits, checks, and trial-and-error, I’ve been proven otherwise (and I really wanted to make it work and local debugging is awesome — but it’s useless when the docs are a soggy mess and don’t reflect reality.)

    #DevOps #AzureDevOps #YAML #NukeBuild #CI #CICD #MainBranchDrivenDevelopment
    #WorksOnMyMachine #AgileStruggles #ModernDev #CarthagoDelendaEst #DevHumor
    #BuildFail #DebuggingHell #LocalIsNotProd #SoftwareEngineering #DotNet #DevLife

  19. Just to be on record:
    I honestly didn’t expect that even non-YAML code (👀 @nuke build – yeah, I’m talking to you...) would require just as many fucking never-ending commits.
    Azure DevOps has proven me wrong. (lol)

    The real pain point?
    No local test run
    No Run pipeline locally
    Zero feedback until you PR, merge, and let it rip on main

    So yeah, we’re basically testing on the main branch. In production. In 2025.
    For everything else, there’s: ¯\_(ツ)_/¯

    Also, I firmly believe that not only Carthage must be destroyed, but also:

    - CI/CD with no local feedback loop
    - “Works on my machine” excuses
    _ YAML files that silently break on pasted tabs
    - And every doc that starts with “just”

    And yes — I really thought nuke build would make things better...
    But after 24 hours of commits, checks, and trial-and-error, I’ve been proven otherwise (and I really wanted to make it work and local debugging is awesome — but it’s useless when the docs are a soggy mess and don’t reflect reality.)

    #DevOps #AzureDevOps #YAML #NukeBuild #CI #CICD #MainBranchDrivenDevelopment
    #WorksOnMyMachine #AgileStruggles #ModernDev #CarthagoDelendaEst #DevHumor
    #BuildFail #DebuggingHell #LocalIsNotProd #SoftwareEngineering #DotNet #DevLife

  20. I hate vendor lock-in. Why the fuck can't I decide which "app store" I want or which source I do download my apps from. What the actual fuck! #amazon #firetablet and/or #appleIOS (which in my opinion reads I Owe you Several apologies)

  21. I hate vendor lock-in. Why the fuck can't I decide which "app store" I want or which source I do download my apps from. What the actual fuck! #amazon #firetablet and/or #appleIOS (which in my opinion reads I Owe you Several apologies)

  22. I hate vendor lock-in. Why the fuck can't I decide which "app store" I want or which source I do download my apps from. What the actual fuck! and/or (which in my opinion reads I Owe you Several apologies)

  23. I hate vendor lock-in. Why the fuck can't I decide which "app store" I want or which source I do download my apps from. What the actual fuck! #amazon #firetablet and/or #appleIOS (which in my opinion reads I Owe you Several apologies)

  24. CW: Spoilers for advent of code Day 3, Puzzle 2

    #AdventOfCode2023
    Finished Day 3, P2 and can't say how much I love doing it with C# and #LinqPad

  25. Just watched @danclarke showing #LinqPad and I'm glad to see people discovering this great productivity tool. I'm using and supporting it from version 1.0 and use it daily.

    @danclarke mentioned in one of his blog posts about #LinqPad, that you would need symbolic links in you "scripts" folder and showed how to do that on the command line. I can highly recommend a neat little tool #LinkShellExtension (schinagl.priv.at/nt/hardlinksh) to get that functionality in your right mouse menu on windows explorer

  26. @leyrer habe schon Mal gehört von dieser Praxis. Es soll diese Menschen geben, die diesen Content dann auch noch vor Publikum präsentieren und Interaktion mit #MannerSchnitten belohnen 😉