--- title: "Cool site: Software Reality" url: "https://osherove.com/blog/2003/9/19/cool-site-software-reality.md" canonical: "https://osherove.com/blog/2003/9/19/cool-site-software-reality.html" published: "2003-09-19T20:32:00" updated: "2003-09-19T20:32:00" tags: ["Cool sites"] author: "Roy Osherove" description: "An innocent link in Benjamin's blog lead me to this very nice site about software development. It contains a lot of articles about lots of stuff, most with a touch of satire in them, but it all seems like its a very…" usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)." license: "https://creativecommons.org/licenses/by/4.0/" --- # Cool site: Software Reality By Roy Osherove September 19, 2003 In [Cool sites](https://osherove.com/blog/category/cool-sites) **Historical article** · Originally published September 19, 2003; technical details may be outdated. An innocent link in [Benjamin's blog](http://benjaminm.net/PermaLink.aspx?guid=c470f292-78cf-4555-94ce-0af22f8398b1) lead me to [this very nice site](http://www.softwarereality.com/) about software development. It contains a lot of articles about lots of stuff, most with a touch of satire in them, but it all seems like its a very good read. The reason **I** like the site is because it seems to have lots of articles about XP and agile development, book reviews and so on. It's also one of the few places so far where I have seen a look at XP practices with a grain of salt, and bothers to give some good reasons for it. Not everything is hunky Dorry about it, according to them, and I always like to hear a second opinion. In fact, the “this sucks and here's why” opinions are usually the the ones you learn the most from.  For example, when I plan to buy a book at [Amazon](https://osherove.com/blog/2003/9/19/www.amazon.com), I always look for reviews that gave the book bad ratings. Why? Because if I can't find anything **there** that I think is viable, and there are enough good reviews for the book, there's a good chance the book might be what it's cover pretends to be. Mad readers are the best way to know if a book sucks. The same goes for other areas. If a company wants to know if it has any problems or possible ways to improve and do better, it should talk directly to those who say it has problems or those who will never buy from it.. If a practice it discouraged by parts of the community, a big **why** is a must from those that are in charge of this practice. Usually, you get to learn something new in the process, or at least discover a new way to look at things. ## More in Cool sites [All posts in Cool sites](https://osherove.com/blog/category/cool-sites) - Oct 5, 2003 ### [Good JavaScript reference and help](https://osherove.com/blog/2003/10/5/good-javascript-reference-and-help.html) - Sep 25, 2003 ### [AmazReplacer - Convert Amazon's URL into your referrer URL automatically](https://osherove.com/blog/2003/9/25/amazreplacer-convert-amazons-url-into-your-referrer-url-auto.html) - Sep 17, 2003 ### [Feeds of interest](https://osherove.com/blog/2003/9/17/feeds-of-interest.html) - Sep 11, 2003 ### [Geeky lectures - part III](https://osherove.com/blog/2003/9/11/geeky-lectures-part-iii.html) --- ## About the author **Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: https://x.com/royosherove - LinkedIn: https://www.linkedin.com/in/osherove/ ### Contact - Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7 ### License Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/