170 karma · joined July 20, 2017
The same is true of humanity in aggregate. We attribute discoveries to an individual or group of researchers but to claim humans are efficient at novel research is a form of survivorship bias. We ignore the numerous researchers who failed to achieve the same discoveries.
We're not yet at a point where LLM coders will learn all your idiosyncrasies automatically, but those feedback loops are well within our technical ability. LLM's are roughly a knowledgeable but naïve junior dev; you must train them!
Hint: add that requirement to your system/app prompt and be done with it.
I think we'll find that over the next few years the first really big win will be AI tearing down the mountain of tech & documentation debt. Bringing efficiency to corporate knowledge is likely a key element to AI working within them.
Ultimately we want effective treatments but the goal of the assistant isn't to perfectly predict solutions. Rather it's to reduce the overall cost and time to a solution through automation.
> All those diagrams, when they are complete, correct and up-to-date, do convey what they are supposed to convey.
I spent a bit of time prototyping this recently. It's definitely possible. Rational Rose also had the capability to generate diagrams from code though. I don't remember how good it was at the task though. Was Rational Rose just a very bad implementation?
I find the hate in this chat strange because diagrams are incredibly useful when working through complex problems* and then conveying that information to other engineers. My experience over 20+ years is that a huge portion of engineers can't grok complex problems from code alone.
*Most of my projects are optimizing billion+ row databases, micro-service architectures, and various other scaling challenges.
Your argument is the equivalent of saying humans can't do math because they rely on calculators.
In the end what matters is whether the problem is solved, not how it is solved.
(assuming that the how has reasonable costs)
This is especially true of AI projects.
If employees were actually utilizing unlimited DTO the company would switch back to accrued PTO. I've seen this happen with an explicit claim that employees were "abusing" the generosity of the company. Said company later switched back to DTO to force employees a few years later to burn down their accrued PTO balances.
That's not a friend, that's a co-worker doing their job. There's a big difference between a friend and someone you get a long with well in a professional setting.
I've seen systems that use waste heat from central A/C to heat a swimming pool. In addition to the condenser they have a heat exchanger connected to the coolant line. Pool water is pumped through the heat exchanger and back out to the pool.
I've seen systems where heat from A/C is used to heat swimming pools. Mostly just needs an extra exchanger on the A/C coolant line that transfers the heat to the pool water. You generally run both system at the same time when it's hot out. (assuming you are fortunate enough to have a pool)
The test should never rely on rote learning (e.g. implement Dijkstra's algorithm from memory) or require a "magic" solution (e.g. Project Euler)