<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: oreilly</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/oreilly.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2025-09-04T20:58:21+00:00</updated><author><name>Simon Willison</name></author><entry><title>Beyond Vibe Coding</title><link href="https://simonwillison.net/2025/Sep/4/beyond-vibe-coding/#atom-tag" rel="alternate"/><published>2025-09-04T20:58:21+00:00</published><updated>2025-09-04T20:58:21+00:00</updated><id>https://simonwillison.net/2025/Sep/4/beyond-vibe-coding/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://beyond.addy.ie/"&gt;Beyond Vibe Coding&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Back in May I wrote &lt;a href="https://simonwillison.net/2025/May/1/not-vibe-coding/"&gt;Two publishers and three authors fail to understand what “vibe coding” means&lt;/a&gt; where I called out the authors of two forthcoming books on "vibe coding" for abusing that term to refer to all forms of AI-assisted development, when &lt;a href="https://simonwillison.net/2025/Mar/19/vibe-coding/"&gt;Not all AI-assisted programming is vibe coding&lt;/a&gt; based on the &lt;a href="https://twitter.com/karpathy/status/1886192184808149383"&gt;original Karpathy definition&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;I'll be honest: I don't feel great about that post. I made an example of those two books to push my own agenda of encouraging "vibe coding" to avoid &lt;a href="https://simonwillison.net/2025/Mar/23/semantic-diffusion/"&gt;semantic diffusion&lt;/a&gt; but it felt (and feels) a bit mean.&lt;/p&gt;
&lt;p&gt;... but maybe it had an effect? I recently spotted that Addy Osmani's book "Vibe Coding: The Future of Programming" has a new title, it's now called "Beyond Vibe Coding: From Coder to AI-Era Developer".&lt;/p&gt;
&lt;p&gt;This title is &lt;strong&gt;so much better&lt;/strong&gt;. Setting aside my earlier opinions, this positioning as a book to help people go &lt;em&gt;beyond&lt;/em&gt; vibe coding and use LLMs as part of a professional engineering practice is a really great hook!&lt;/p&gt;
&lt;p&gt;From Addy's new description of the book:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Vibe coding was never meant to describe all AI-assisted coding. It's a specific approach where you don't read the AI's code before running it. There's much more to consider beyond the prototype for production systems. [...]&lt;/p&gt;
&lt;p&gt;AI-assisted engineering is a more structured approach that combines the creativity of vibe coding with the rigor of traditional engineering practices. It involves specs, rigor and emphasizes collaboration between human developers and AI tools, ensuring that the final product is not only functional but also maintainable and secure.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Amazon &lt;a href="https://www.amazon.com/Beyond-Vibe-Coding-Leveraging-AI-Assisted/dp/B0F6S5425Y"&gt;lists it&lt;/a&gt; as releasing on September 23rd. I'm looking forward to it.&lt;/p&gt;
&lt;p&gt;&lt;img alt="O'Reilly book cover: Beyond Vibe Coding: From Coder to AI-Era Developer, by Addy Osmani. Features two hummingbirds, presumably because their wings vibrate!" src="https://static.simonwillison.net/static/2025/beyond-vibe-coding.jpg" /&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/books"&gt;books&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oreilly"&gt;oreilly&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai"&gt;ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/generative-ai"&gt;generative-ai&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/llms"&gt;llms&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ai-assisted-programming"&gt;ai-assisted-programming&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/addy-osmani"&gt;addy-osmani&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/vibe-coding"&gt;vibe-coding&lt;/a&gt;&lt;/p&gt;



</summary><category term="books"/><category term="oreilly"/><category term="ai"/><category term="generative-ai"/><category term="llms"/><category term="ai-assisted-programming"/><category term="addy-osmani"/><category term="vibe-coding"/></entry><entry><title>Sharing My Location Just the Way I Like It</title><link href="https://simonwillison.net/2008/Mar/31/sharing/#atom-tag" rel="alternate"/><published>2008-03-31T20:34:22+00:00</published><updated>2008-03-31T20:34:22+00:00</updated><id>https://simonwillison.net/2008/Mar/31/sharing/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://radar.oreilly.com/archives/2008/03/sharing-my-location-just-the-w.html"&gt;Sharing My Location Just the Way I Like It&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Fire Eagle gets a great write-up from Brady Forrest over on the O’Reilly Radar.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/brady-forrest"&gt;brady-forrest&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/fireeagle"&gt;fireeagle&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/location"&gt;location&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oreilly"&gt;oreilly&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oreillyradar"&gt;oreillyradar&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/wikinear"&gt;wikinear&lt;/a&gt;&lt;/p&gt;



</summary><category term="brady-forrest"/><category term="fireeagle"/><category term="location"/><category term="oreilly"/><category term="oreillyradar"/><category term="wikinear"/></entry><entry><title>Dangers of remote Javascript</title><link href="https://simonwillison.net/2008/Jan/20/dangers/#atom-tag" rel="alternate"/><published>2008-01-20T09:49:06+00:00</published><updated>2008-01-20T09:49:06+00:00</updated><id>https://simonwillison.net/2008/Jan/20/dangers/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://radar.oreilly.com/archives/2008/01/dangers_of_remo.html"&gt;Dangers of remote Javascript&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Perl.com got hit by a JavaScript porn redirect when the domain of one of their advertisers expired and was bought by a porn company. Nat Torkington suggests keeping track of the expiration dates on any third party domains that are serving JavaScript on your site.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/domains"&gt;domains&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/javascript"&gt;javascript&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/nat-torkington"&gt;nat-torkington&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oreilly"&gt;oreilly&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/perldotcom"&gt;perldotcom&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/xss"&gt;xss&lt;/a&gt;&lt;/p&gt;



</summary><category term="domains"/><category term="javascript"/><category term="nat-torkington"/><category term="oreilly"/><category term="perldotcom"/><category term="security"/><category term="xss"/></entry><entry><title>Introduction to Neogeography</title><link href="https://simonwillison.net/2007/Jan/27/neogeography/#atom-tag" rel="alternate"/><published>2007-01-27T00:09:59+00:00</published><updated>2007-01-27T00:09:59+00:00</updated><id>https://simonwillison.net/2007/Jan/27/neogeography/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.oreilly.com/catalog/neogeography/"&gt;Introduction to Neogeography&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Having run in to Andrew Turner at last year’s EuroOSCON, this is the first O’Reilly Short Cuts PDF that I’ve been seriously tempted to buy.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://www.edparsons.com/?p=411"&gt;Ed Parsons&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/andrew-turner"&gt;andrew-turner&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/eurooscon"&gt;eurooscon&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mapping"&gt;mapping&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/neogeography"&gt;neogeography&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/oreilly"&gt;oreilly&lt;/a&gt;&lt;/p&gt;



</summary><category term="andrew-turner"/><category term="eurooscon"/><category term="mapping"/><category term="neogeography"/><category term="oreilly"/></entry><entry><title>Giving away the index</title><link href="https://simonwillison.net/2005/May/4/spotlight/#atom-tag" rel="alternate"/><published>2005-05-04T01:16:45+00:00</published><updated>2005-05-04T01:16:45+00:00</updated><id>https://simonwillison.net/2005/May/4/spotlight/#atom-tag</id><summary type="html">
    &lt;p id="p-0"&gt;My final year project is due in two weeks, and I'm going to be running on silent for most of them. I have, however, upgraded to Tiger and playing with &lt;a href="http://www.apple.com/macosx/features/spotlight/"&gt;Spotlight&lt;/a&gt; has given me plenty to think about.&lt;/p&gt;

&lt;h4&gt;Giving away the index&lt;/h4&gt;

&lt;p id="p-1"&gt;The great benefit of having an electronic version of a book you own in dead-tree format to hand is that you can search it. Publishers generally don't hand out free digital copies because, well, they want you to buy the books, not freely distribute electronic copies.&lt;/p&gt;

&lt;p id="p-2"&gt;The thing is, you don't need a digital copy of a book to be able to search it; you just need a full-text index of it (if you don't understand what this means, go and read Tim Bray's series &lt;a href="http://www.tbray.org/ongoing/When/200x/2003/07/30/OnSearchTOC"&gt;On Search&lt;/a&gt;). An index isn't enough to reconstruct the book, but it &lt;em&gt;is&lt;/em&gt; enough to answer questions like "on what pages of &lt;cite&gt;Eric Meyer on CSS&lt;/cite&gt; are float layouts discussed?"&lt;/p&gt;

&lt;p id="p-3"&gt;Imagine if technical publishers made binary full-text index files of their titles available for download, for free in some kind of open standard format. Readers could query them using Spotlight or similar technologies, and gain the ability to search the titles they own all without needing to rely on centralised, artificially limited services  such as Amazon's &lt;a href="http://www.amazon.com/exec/obidos/tg/browse/-/10197021/103-7492634-0996655"&gt;Search Inside the Book&lt;/a&gt;.&lt;/p&gt;

&lt;p id="p-4"&gt;O'Reilly, I'm &lt;a href="http://radar.oreilly.com/" title="O&amp;apos;Reilly Radar"&gt;looking at you&lt;/a&gt;.&lt;/p&gt;

&lt;h4&gt;Full-text phishing&lt;/h4&gt;

&lt;p id="p-5"&gt;On a darker note, one thing about Spotlight that has given me pause is the immense ease with which it can uncover passwords saved amongst my email. Lost password reminders, new account details, invitations to sign up for services - they're all hidden away in my mail archive. Spotlight makes it trivial to dig them back up again, and offers the APIs for applications to do so as well. Combine this with a piece of spyware / some trojan horse and you've got the ultimate vector for phishing attacks.&lt;/p&gt;

&lt;p id="p-6"&gt;This problem isn't limited to Macs either; Google and MSN's Desktop Search engines could be used for much the same purpose, and full-text search is bound to end up built in to Windows sooner or later. For the moment, the safest thing to do is either delete those pesky emails or move them to a folder that is excluded from Spotlight's index. Somehow I doubt many people will think to take such precautions.&lt;/p&gt;

&lt;p id="p-7"&gt;And with that off my chest, it's time to get back to my dissertation.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/oreilly"&gt;oreilly&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/search"&gt;search&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="oreilly"/><category term="search"/><category term="security"/></entry></feed>