Sabitlenmiş Tweet
Chris F. Carroll
12.6K posts

Chris F. Carroll
@chrisfcarroll
is offline.
Warrington Katılım Kasım 2009
343 Takip Edilen501 Takipçiler

@Putney_Kotto @gianotti_mattia @ErrorTheorist Although I think the belief that CS has its roots in philosophy is a mistake, even though foundations of mathematics was/is a quite philosophical area.
English

@Putney_Kotto @gianotti_mattia @ErrorTheorist Is it more that once a problem becomes tractable, we stop calling it philosophy?
Natural philosophy → physics, biology, chemistry
Bits of philosophy of mind → psychology
Syllogisms, RAA, modus ponens/tollens &c → mathematical logic
English

@SpeedWatkins I feel that “If He is all-powerful, He would be able to do so” is a defn that excludes possibility of free will
English

If God is perfectly good, He would desire to save everyone. If He is all-powerful, He would be able to do so. If both are true, everyone would be saved. Since not everyone is saved, either God lacks power, lacks goodness, or does not exist. Choose wisely.
Frank Turek@DrFrankTurek
Why doesn't God save everyone?
English

@TotherAlistair although now I've seen the back cover I guess I mis-guessed the audience!
English

@TotherAlistair My preference order is 2,1,3,4 possibly because ‘slice the problem grow the solution’ doesn't tell me it's about software development which I assume it is
English

@grok @inareshmatta @steren grok imagines that these are great at massive scale but they are great at small scale too
English

Google's practices shine at massive scale (100k+ engineers, billions of LOC):
1. One monorepo at HEAD: Atomic cross-project changes, instant consistency, no version drift or painful merges.
2. Explicit deps: Reproducible builds, clear impact analysis, easy audits/updates.
3. Vendored third_party: Hermetic (offline/self-contained) builds, security (no live external pulls), exact reproducibility.
4. Rebuild everything from source: Full auditability, no hidden binaries, optimizes for security/performance.
After a year, you see they prevent chaos in huge codebases.
English

When I joined Google, I found it annoying that:
1. Everyone works in the same repo at head
2. All dependencies are explicitly declared
3. External dependencies are copied in a central third_party folder
4. Everything can be re-built from source
I had changed my mind for all of these points after a year.
English

@PhilosopherJoeC I feel unable to choose between the two,
but I am keen to see some moral inferences made by leading scientists & moralists to clarify whether or not they draw their inferences from their sentiments.
English

@TotherAlistair I maybe misunderstood but isn't ‘get messed up by my next test’ what you are aiming for — incremental development of the actual service?
English

@kristijan_kralj I concede it's not written in .Net but you won't lose a whole sprint on building html and feeding it to wkhtmltopdf
English

PDF is the main bottleneck of modern .NET development:
1. ASP .NET Core can handle thousands of requests per second, but exporting to PDF still means installing 3 NuGet packages, reading 5 GitHub issues, and hoping fonts don't explode in production.
2. We have async/await, background jobs, cloud autoscaling, and distributed systems, yet the moment the business says
"Can we just get a small PDF with a table and a logo?"
the whole sprint vanishes.
3. We can model complex domains, enforce invariants, and scale systems to millions of users, but aligning a table header in a PDF still feels like dark magic.
.NET devs, know your enemies.
English

@mkristensen Editor write-the-code-for-you typeahead is ahead e.g. nuget package and version typeahead when editing a csproj file but also in general C#; editor auto-formatting ; paste into string auto-escaping
English

@mkristensen … Check-in window slicker to work with (e.g. changed filenames typeahead in the comments window; show/hide the tree of changes ; … /
English

@brianchristian Taking your ‘make a decision about the photographer’ example, I could write out and focus on the edited statement.
I hypothesise that that would make it easier for me to make an unbiased (or less biased) decision.
I intend to at least try this out and see how it goes.
English

@chrisfcarroll Say more? Not sure what you have in mind!
English

Humans could try this too
Brian Christian@brianchristian
New Preprint with @mazormatan: Overcoming both bias and sycophancy requires LLMs to imagine not knowing something they know. Like humans, they struggle with this. But unlike humans, LLMs can do something remarkable: they can, quite simply, *ask their counterfactual selves*.
English

@juanrga They've been teaching us for the past several decades that, since E=mc², matter is a form of energy.
Are you saying that is completely wrong or is it just sloppily stated?
English

No. You cannot turn energy (a property) into matter (stuff things are made).
What you can do is convert radiation into matter.
Martin Bauer@martinmbauer
Based on the laws of physics when you turn energy into matter you should produce particles and antiparticles in almost exactly equal amounts. Yet today the Universe is almost entirely matter. Nobody knows where all the antimatter went
English


@brankopetric00 This decision process is so beautiful it brings tears to my eyes.
English

Team debated: GitHub Actions vs Jenkins for CI/CD.
Jenkins advocates:
- We already have it
- More powerful
- Self-hosted
- Free (ignoring ops time)
GitHub Actions advocates:
- YAML in repo
- No server to maintain
- Modern UI
- Faster
Decision process:
- Ran both for 1 month
- Same workflows
Results:
Jenkins:
- Maintained by 1 person (40 hours/month)
- Plugins broke after updates
- UI from 2010
- Build queue issues
GitHub Actions:
- Zero maintenance
- Just works
- Cost: $120/month
- Fast feedback
Migrated fully to GitHub Actions.
Six months later:
- That 1 person works on actual features now
- CI/CD is no longer a team discussion topic
- Onboarding new engineers: trivial
English

@systemdesignone Perhaps rather than the Cons (which are largely trivial) what we want to consider is the Cost? (and how valuable the Pro is to a given use case)
English











