Search
34 results for “macf00bar”
-
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 mainSo 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 -
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 mainSo 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 -
-
@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.