<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>review on Oxymoronical</title>
    <link>https://www.oxymoronical.com/blog/tag/review/</link>
    <description>Recent content in review on Oxymoronical</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 24 May 2025 19:38:00 +0100</lastBuildDate>
    <atom:link href="https://www.oxymoronical.com/blog/tag/review/feed/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A non-fitness expert review of the Pixel Watch 3</title>
      <link>https://www.oxymoronical.com/blog/2025/05/pixel-watch-3-review/</link>
      <pubDate>Sat, 24 May 2025 19:38:00 +0100</pubDate>
      <guid>https://www.oxymoronical.com/blog/2025/05/pixel-watch-3-review/</guid>
      <description>&lt;p&gt;It&amp;rsquo;s been many years since I went to the gym regularly. I&amp;rsquo;m reasonably active, I enjoy long hikes and I try to ride my bike to the co-working space I use weekly. But weather and kids often get in the way of doing any of that and frankly the lack of exercise is starting to show. So it&amp;rsquo;s time to start hitting the gym again. And what better way to encourage me to do that than buying an expensive new gadget to help me track my progress!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tests don&#39;t replace Code Review</title>
      <link>https://www.oxymoronical.com/blog/2024/05/tests-dont-replace-code-review/</link>
      <pubDate>Wed, 01 May 2024 23:02:00 +0100</pubDate>
      <guid>https://www.oxymoronical.com/blog/2024/05/tests-dont-replace-code-review/</guid>
      <description>&lt;p&gt;I frequently see a bold claim come up in tech circles. That as a team you&amp;rsquo;re wasting time by doing code reviews. You should instead rely on automated tests to catch bugs. This surprises me because I can&amp;rsquo;t imagine anyone thinking that such a blanket statement is true. But then most of the time this is brought up in places like Twitter where nuance is impossible and engagement farming is rife. Still it got me thinking about why I think code review is important even if you have amazing tests.&lt;/p&gt;</description>
    </item>
    <item>
      <title>A review of the Canon EOS R7</title>
      <link>https://www.oxymoronical.com/blog/2023/04/a-review-of-the-canon-eos-r7/</link>
      <pubDate>Tue, 18 Apr 2023 20:42:21 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2023/04/a-review-of-the-canon-eos-r7/</guid>
      <description>&lt;p&gt;I’ve always enjoyed photography. I’ve had a Nikon D7000 for nearly 12 years and apparently I’ve taken some 80,000 shots with it. But over the past few years I’ve been taking less and less photos and finding I wasn’t enjoying it as much. I’d rarely take the camera out with me and even when I did I found I was throwing away most of the photos I took. I finally decided it was time to try something new.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New Firefox reviewers</title>
      <link>https://www.oxymoronical.com/blog/2016/06/New-Firefox-reviewers/</link>
      <pubDate>Wed, 08 Jun 2016 09:34:36 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2016/06/New-Firefox-reviewers/</guid>
      <description>&lt;p&gt;I’m delighted to announce that I’ve just made Andrew Swan (aswan on IRC) a reviewer for Firefox code. That also reminds me that I failed to announce when I did the same for Rob Helmer (rhelmer). Please inundate them with patches.&lt;/p&gt;&#xA;&lt;p&gt;There are a few key things I look for when promoting folks to reviewers, surprisingly none of them are an understanding of the full breadth of code in Firefox or Toolkit:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Linting for Mozilla JavaScript code</title>
      <link>https://www.oxymoronical.com/blog/2015/12/Linting-for-Mozilla-JavaScript-code/</link>
      <pubDate>Fri, 18 Dec 2015 11:27:07 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2015/12/Linting-for-Mozilla-JavaScript-code/</guid>
      <description>&lt;p&gt;One of the projects I’ve been really excited about recently is getting ESLint working for a lot of our JavaScript code. If you haven’t come across ESLint or linters in general before they are automated tools that scan your code and warn you about syntax errors. They can usually also be set up with a set of rules to enforce code styles and warn about potential bad practices. The devtools and Hello folks have been using eslint for a while already and Gijs asked why we weren’t doing this more generally. This struck a chord with me and a few others and so we’ve been spending some time over the past few weeks getting our in-tree support for ESLint to work more generally and fixing issues with browser and toolkit JavaScript code in particular to make them lintable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>500px isn&#39;t quite Flickr yet</title>
      <link>https://www.oxymoronical.com/blog/2013/05/500px-isnt-quite-Flickr-yet/</link>
      <pubDate>Sun, 26 May 2013 12:20:40 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2013/05/500px-isnt-quite-Flickr-yet/</guid>
      <description>&lt;p&gt;Since the &lt;a href=&#34;https://www.oxymoronical.com/blog/2013/05/Hello-new-Flickr-goodbye-social&#34;&gt;big changes to Flickr&lt;/a&gt; last week I’ve been mulling over the idea of switching to a different photo sharing site. &lt;a href=&#34;http://500px.com/&#34;&gt;500px&lt;/a&gt; had caught my eye in the past as being a very similar concept to Flickr. It has social aspects like Flickr does, maybe even more so as it supports the notion of “liking” a photo as well as making it a “favourite”. They seem to target the more professional photographer (yes &lt;a href=&#34;http://instagram.com/p/Zj1zNSGopR/#&#34;&gt;Marissa Mayer&lt;/a&gt;, there really is still such a thing) and the curated photos that show up through their main photos section shows that. Frankly it’s a little off-putting since my photos don’t even come close to that level, but the same can be said for Flickr’s similar sections so I guess it’s not that big of a deal. So I took a day or two to upload some of my photos, put 500px through its paces and see how it measures up to Flickr. I’ve built up a fairly specific workflow for my photo uploading and I’m measuring against that so what might be show-stoppers for me may not affect others.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What is an API?</title>
      <link>https://www.oxymoronical.com/blog/2012/11/What-is-an-API/</link>
      <pubDate>Fri, 23 Nov 2012 19:27:02 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2012/11/What-is-an-API/</guid>
      <description>&lt;p&gt;I recently posted in the newsgroups about a &lt;a href=&#34;https://groups.google.com/d/topic/mozilla.dev.platform/fZV-DYnqQEc/discussion&#34;&gt;concern over super-review&lt;/a&gt;. In some cases patches that seem to meet the policy aren’t getting super-reviewed. Part of the problem here is that the policy is a little ambiguous. It says that any API or pseudo-API requires super-review but depending on how you read that section it could mean any patch that changes the signature of a JS function is classed as an API. We need to be smarter than that. Here is a straw-man proposal for defining what is an API:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Managing changes is the key to a project&#39;s success</title>
      <link>https://www.oxymoronical.com/blog/2012/05/Managing-changes-is-the-key-to-a-projects-success/</link>
      <pubDate>Wed, 30 May 2012 07:43:15 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2012/05/Managing-changes-is-the-key-to-a-projects-success/</guid>
      <description>&lt;p&gt;TomTom made an &lt;a href=&#34;http://www.tomtom.com/en_gb/licensing/newsletter/201205/didyouknow/&#34;&gt;interesting claim recently&lt;/a&gt;. Their summary is “&lt;em&gt;when it comes to automotive-grade mapping, open source has some quite serious limitations, falling short on the levels of accuracy and reliability required for safe navigation&lt;/em&gt;”&lt;/p&gt;&#xA;&lt;p&gt;This is a bold claim and they talk about recent studies that back them up. Unfortunately none of them are referenced but it’s pretty clear from the text of the article that all they are doing is comparing the accuracy of TomTom maps with existing open source maps. So they’re just generalising, this doesn’t prove a limitation with the open source process itself of course, just perhaps of a particular instance of it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
