This is pretty neat: ChatGPT Work and GPT-6 Astra (I used "Max") can take an address and produce a 5K/10K circular running route starting from that address, using OSM data
This is pretty neat: ChatGPT Work and GPT-6 Astra (I used "Max") can take an address and produce a 5K/10K circular running route starting from that address, using OSM data
So it's strange because it's also perhaps the major software release that I've worked on the least in terms of lines of code. I have the least number of personally hand-chiseled lines of code in Quattro than I've had in any major release I've ever done. And yet, I am insanely proud of what we've accomplished.
Such, indeed fragile, peace not only puts an end to today’s carnage, but leaves open a possibility of eventual long-term solution between Russia and Ukraine.
New: emulate a GitHub App in a few lines of TypeScript Generated App keys, installation auth and stateful repository APIs Develop locally, test in CI or give sandboxed agents their own isolated GitHub environment
So this one will not be coding-related, but coding from scratch is actually a very, very useful technique because it really helps you understand how something is implemented.
I'm so incredibly tired of seeing low-effort AI-designed web pages. I basically bounce off any new product immediately when I see it (never get a chance to judge the product itself). Lots of thin lines, glowy styles, inconsistent fonts, lots of monospace.
Like that just does not seem like the ideal artifact. We should be able to store them somewhere. We should be able to have architecture diagrams that we can review and discuss that generate that code to spec.
Facts and Fallacies of Software Engineering by Robert L. Glass. In essence, this is a book about an industry that refuses to learn. That was true 25 years ago when this book was published, and it's probably twice as true today. (Just think about all the AI adoption metrics being rolled out — back to productivity mistaken for lines of code produced, only more elaborate. And expensive). What I like about this book is that Glass doesn't present anything new. Quite the opposite, actually. Rather, it's about research lessons that we all should know, but tend to forget. Ever had to do an estimate, or plan according to a requirements spec? Or maybe you thought that enough eyeballs make all bugs shallow? Then this book is for you. A great work by a fantastic author.
I think there's a difference between being able to write lines of code in a particular language like Python or C++ and understanding how code, computer systems, products work. And I don't think the latter is going away.
I still see a craft excellence that's really important in the disciplines that I don't think is going away anytime soon. Even if there's fluidity or blurring of the work across the functional lines.
it's more important to invest in trains that can get more riders than just the railfans; taking a line from 0% to 5% modal split is less important than taking it from 20% to 40%
Riders diverted from other lines still benefit from the project, especially in a case like QueensLink, where the diverted riders would enjoy an improvement in trip time to Midtown of about 10-15 minutes each way.
If this were $200 I'd complain, but not for $25. For that, it's a neat little box that maybe more people could contribute to, to make it the most handy way to jack in from a crash cart.
The demand for inference is growing. So, like I don't think it's linearly growing. I think it might even be exponentially growing. But we haven't made our production of GPUs grow exponentially. That's like kind of a linear process. So as those lines intersect, there's going to be uh tightening.
But right now I think it's sitting somewhere between half million and five million lines of code, somewhere in there. Probably more on the half million side right now and with the next drop of an Anthropic model, we're probably going to see it jump up to a few million lines.
We can have a breakthrough in our agent architecture on Monday implemented on Tuesday and have it deployed with hundreds of our customers on Wednesday and directly see the impact of of that work.
There's a point in which all of your choices add up. And I typically find that right around 5 to 10,000 lines of code. The choices you've made either weigh you down or kind of free you up.
Archeology, in this regard, is the worst enemy of this. So we put these names on cultures, we talk about how they evolve from one to another, we draw these lines where there aren’t any.
I often read advice along the lines of “if you want to help a project send PRs” and I never understood it. Reviewing and iterating or pushing back on PRs is work! Often more than writing the code itself.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.