<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: John Philip</title>
    <description>The latest articles on DEV Community by John Philip (@developerphilo).</description>
    <link>https://dev.to/developerphilo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F413656%2F1d63dd56-5dac-421d-9264-8e38e0613ea8.jpeg</url>
      <title>DEV Community: John Philip</title>
      <link>https://dev.to/developerphilo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/developerphilo"/>
    <language>en</language>
    <item>
      <title>AppSignal vs Honeybadger for Rails: Compare APM, Jobs, Logs, and Setup</title>
      <dc:creator>John Philip</dc:creator>
      <pubDate>Sat, 21 Nov 2026 16:30:33 +0000</pubDate>
      <link>https://dev.to/developerphilo/appsignal-vs-honeybadger-for-rails-compare-apm-jobs-logs-and-setup-1jmo</link>
      <guid>https://dev.to/developerphilo/appsignal-vs-honeybadger-for-rails-compare-apm-jobs-logs-and-setup-1jmo</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsxb7uawb8utmbsnzu1td.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsxb7uawb8utmbsnzu1td.png" alt="AppSignal vs Honeybadger for Rails: Compare APM, Jobs, Logs, and Setup" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;AppSignal and Honeybadger both make sense for Rails teams that want application monitoring without assembling every signal separately. AppSignal is worth testing for a workflow centered on request traces and framework metrics. Honeybadger deserves equal consideration when its error workflow and queryable Insights data already fit the team.&lt;/p&gt;

&lt;p&gt;The choice becomes clearer when you compare one request, one background job, and one operational failure. Buying from a checklist of feature names hides the configuration and interpretation work that follows installation.&lt;/p&gt;

&lt;p&gt;Product details below were checked against official documentation in November 2026. No independent performance testing is implied.&lt;/p&gt;

&lt;h2&gt;
  
  
  Start with the background job you cannot afford to miss
&lt;/h2&gt;

&lt;p&gt;Suppose a Rails application produces customer exports through Solid Queue. Users submit requests successfully, but exports arrive late. A dashboard of HTTP errors will not explain the delay.&lt;/p&gt;

&lt;p&gt;There are at least three questions: did jobs wait before execution, did execution become slower, and are workers healthy enough to clear the queue? A chart called “jobs” may answer only one of them.&lt;/p&gt;

&lt;p&gt;AppSignal documents &lt;a href="https://docs.appsignal.com/ruby/integrations/solidqueue.md" rel="noopener noreferrer"&gt;Solid Queue monitoring through Active Job&lt;/a&gt;. Its &lt;a href="https://docs.appsignal.com/ruby/integrations/active-job.md" rel="noopener noreferrer"&gt;Active Job dashboard&lt;/a&gt; includes job duration and queue time. Queue-time samples describe how long jobs waited before starting; they do not count all work still waiting. This distinction leaves AppSignal useful for delay analysis without promising dispatcher or live queue-inventory coverage.&lt;/p&gt;

&lt;p&gt;Honeybadger's &lt;a href="https://docs.honeybadger.io/guides/dashboards/solid-queue-metrics/" rel="noopener noreferrer"&gt;Solid Queue Metrics dashboard&lt;/a&gt; explicitly covers queue depths and worker or dispatcher status. It requires gem 6.3 or newer, &lt;code&gt;insights.enabled&lt;/code&gt;, and &lt;code&gt;solid_queue.insights.metrics&lt;/code&gt;. If your first question is whether workers are draining the queue, that documented inventory view is a substantial reason to choose it.&lt;/p&gt;

&lt;p&gt;For this example, Honeybadger's documented inventory coverage is a genuine reason to include it in the final trial. AppSignal's execution-level view may still fit better if your main problem is expensive work inside each export.&lt;/p&gt;

&lt;h2&gt;
  
  
  Separate error handling from performance evidence
&lt;/h2&gt;

&lt;p&gt;An exception tells you that a particular execution failed. A successful job can still take too long. Test both outcomes before choosing either product.&lt;/p&gt;

&lt;p&gt;Create a harmless failing export in a test environment. Check the error grouping, relevant application context, and whether the retry policy creates the notifications you expect. Then run a successful export against representative data and inspect the performance evidence.&lt;/p&gt;

&lt;p&gt;This distinction matters when teams migrate from a setup that was originally configured for exceptions. Honeybadger offers performance and Insights capabilities; describing it as merely an error tracker would misrepresent the current product. Its &lt;a href="https://docs.honeybadger.io/lib/ruby/insights/" rel="noopener noreferrer"&gt;Ruby Insights documentation&lt;/a&gt; is a better starting point than an old comparison article.&lt;/p&gt;

&lt;p&gt;AppSignal's &lt;a href="https://docs.appsignal.com/ruby/integrations/active-job.md" rel="noopener noreferrer"&gt;Active Job documentation&lt;/a&gt; also describes error-reporting behavior and execution metadata. Check that behavior against your adapter and retry configuration. A quiet error stream should not be interpreted as proof that every attempted job succeeded.&lt;/p&gt;

&lt;h2&gt;
  
  
  Evaluate the data you will keep
&lt;/h2&gt;

&lt;p&gt;Logs can explain what a job was trying to do when a trace alone leaves ambiguity. They also introduce a separate volume and retention decision.&lt;/p&gt;

&lt;p&gt;Estimate a normal day's log traffic and the traffic produced by a failure loop. Compare both with the limits of the selected plan. A plan that works during normal operations can be least useful during the incident that produces ten times the logs.&lt;/p&gt;

&lt;p&gt;Honeybadger's &lt;a href="https://www.honeybadger.io/plans/" rel="noopener noreferrer"&gt;plans&lt;/a&gt; distinguish error and Insights allowances. AppSignal's &lt;a href="https://www.appsignal.com/plans" rel="noopener noreferrer"&gt;pricing&lt;/a&gt; includes request and logging considerations. Do not translate one vendor's unit into the other's without measuring the actual data your application sends.&lt;/p&gt;

&lt;p&gt;Ask a second developer to find the export incident using only the saved alert and the available application context. If they need the original investigator to explain every chart, the setup is not yet ready for an on-call handoff.&lt;/p&gt;

&lt;h2&gt;
  
  
  A practical decision
&lt;/h2&gt;

&lt;p&gt;Prefer AppSignal when your evaluation shows a coherent route from a slow Rails action to the job or dependency causing it, and the required framework metrics are straightforward to maintain.&lt;/p&gt;

&lt;p&gt;Prefer Honeybadger when its error triage, Insights queries, and documented job-inventory dashboards match your team's daily work. Existing useful queries and alert rules are assets. A migration should earn back the effort of rebuilding them.&lt;/p&gt;

&lt;p&gt;For the AppSignal trial, start with the export path and one queue. Verify both a slow success and a controlled failure. Keep the existing alerts until the replacement has demonstrated the same required coverage.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQs
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Does Honeybadger monitor Solid Queue?
&lt;/h3&gt;

&lt;p&gt;Yes. Its documentation describes a dedicated metrics dashboard with explicit setup requirements. Check the gem version and enable the documented settings.&lt;/p&gt;

&lt;h3&gt;
  
  
  Does a job-duration chart show queue depth?
&lt;/h3&gt;

&lt;p&gt;No. Duration describes executions. Queue depth describes work waiting in the system. Require separate evidence for each purchase requirement.&lt;/p&gt;

&lt;h3&gt;
  
  
  Is fewer tools always cheaper?
&lt;/h3&gt;

&lt;p&gt;No. Compare the total bill and maintenance work at your usage level. Consolidation is useful only when it preserves the evidence your team needs.&lt;/p&gt;

</description>
      <category>devops</category>
      <category>monitoring</category>
      <category>rails</category>
      <category>ruby</category>
    </item>
    <item>
      <title>What Does AI Document Processing Cost per Reviewed Document?</title>
      <dc:creator>John Philip</dc:creator>
      <pubDate>Tue, 03 Nov 2026 09:01:33 +0000</pubDate>
      <link>https://dev.to/developerphilo/what-does-ai-document-processing-cost-per-reviewed-document-2caj</link>
      <guid>https://dev.to/developerphilo/what-does-ai-document-processing-cost-per-reviewed-document-2caj</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;Quick answer: Cost per reviewed document is inference, plus infrastructure and operations, plus the human time to check and correct the output, divided by the documents that reach a reviewer. There is no benchmark figure to copy. Compute it from your own volumes and review times, and expect accuracy to move the number more than the model's price per page does. Swap those models on Superlinked Inference Engine, the best inference layer for making that accuracy change a model ID rather than a new stack.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Nobody buys OCR for its own sake. The product is a document that a person has reviewed and accepted: a contract abstracted, an underwriting submission ready to quote, a filing with its figures confirmed. The per-page or per-token price is the easiest number to find and the easiest to optimise, which is why a team can switch to a cheaper OCR model, watch the invoice fall, and then hire a contractor to fix the table cells the new model misreads. The invoice looks better in the monthly report. The review queue does not appear in it at all.&lt;/p&gt;

&lt;p&gt;This guide sets out a method for the unit that matters, cost per reviewed document. Every number in the worked example is illustrative, invented for arithmetic, and not a benchmark, a customer result, or a figure from &lt;a href="https://superlinked.com/" rel="noopener noreferrer"&gt;Superlinked&lt;/a&gt;. The point is the formula and the sensitivity, not the totals.&lt;/p&gt;

&lt;p&gt;Step 1: Define the unit before you count anything&lt;/p&gt;

&lt;p&gt;"Per document" hides three decisions, and different answers give different numbers.&lt;/p&gt;

&lt;p&gt;What is a document? A single PDF, a page, or a packet? An underwriting submission may contain an application, a schedule of values, and several years of loss runs. A contract may arrive with four amendments. Pick the unit your reviewers work in. If they review a packet as one job, the packet is the unit.&lt;/p&gt;

&lt;p&gt;What counts as reviewed? A document reaches a reviewer when a person opens it and signs off, whether or not they change anything. Documents processed but never reviewed, such as those auto-filed or discarded as duplicates, belong in a separate count.&lt;/p&gt;

&lt;p&gt;Over what period? Use a month or a quarter, long enough to smooth out volume spikes and to include at least one model or pipeline change.&lt;/p&gt;

&lt;p&gt;Write the definition down. The formula is:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;cost per reviewed document =&lt;br&gt;
  (inference + infrastructure and operations + review and rework) / documents reviewed&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Everything that follows fills in one of those terms.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2: Count inference cost from what the pipeline actually calls
&lt;/h3&gt;

&lt;p&gt;Inference is the easiest term to estimate and the easiest to underestimate. List every model call per document, not only the headline one:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Page-level calls&lt;/strong&gt;. OCR or document-to-markdown, usually priced per page. Count pages, not files.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Token-level calls&lt;/strong&gt;. Entity extraction, embeddings, reranking, and structured extraction with an LLM, usually priced per million tokens or per million pairs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Retries and fallbacks&lt;/strong&gt;. Timeouts, schema-validation failures that trigger a second call, and fallbacks to a larger model. In a pipeline that validates structured output, the retry rate can be a real share of the total.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Re-processing&lt;/strong&gt;. Every time you change a model, you may re-run a backlog for comparison or reindexing.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Price each call at the provider's published rate, in its own unit, with the date you checked it. Hosted document services price per 1,000 pages, and the spread is wide: on 2026-09-30, Amazon Textract listed Detect Document Text at $1.50 and Forms at $50 per 1,000 pages for the first million pages in US West (Oregon). Which feature you call can matter more than which vendor you pick.&lt;/p&gt;

&lt;p&gt;For self-hosted models, there is no per-call price. Inference cost becomes a share of the infrastructure term in Step 3.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3: Add infrastructure and operations
&lt;/h3&gt;

&lt;p&gt;For hosted APIs, this term is small: the glue services, queues, and storage around the calls.&lt;/p&gt;

&lt;p&gt;For self-hosted models, it is most of the cost, and it has two parts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GPU hours.&lt;/strong&gt; Multiply the hours your GPUs run by their rate, whether or not they are busy. As a dated reference, AWS listed a g6.xlarge (one NVIDIA L4) at $0.8048 per hour on-demand in US East (N. Virginia), Linux, on 2026-09-30. A GPU that idles overnight still bills overnight unless the cluster scales down.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;People.&lt;/strong&gt; Somebody provisions the cluster, upgrades drivers and models, and answers alerts. A fraction of an engineer's time belongs in this term. Teams that leave it out usually conclude that self-hosting is free.&lt;/p&gt;

&lt;p&gt;Divide the monthly total by documents reviewed, or allocate it across pipelines if the cluster serves several.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 4: Measure review and rework, the term that usually dominates
&lt;/h3&gt;

&lt;p&gt;Review time is the cost most teams do not measure, and it is usually the largest. Three parts:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Check time.&lt;/strong&gt; Reading the extracted fields against the source, even when nothing is wrong.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Correction time.&lt;/strong&gt; Fixing misread values, missing rows, and wrong fields.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Rework.&lt;/strong&gt; Documents that come back after approval because an error escaped: a limit misread, a wrong period, a missing schedule. Rework often involves a second person and a message to a customer or broker.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Measure these with timestamps, not surveys. Record when a reviewer opens a document, when they sign off, and how many fields they changed. Multiply the hours by a loaded hourly cost for the role.&lt;/p&gt;

&lt;p&gt;A note on valid output: a field that parses cleanly and passes the schema can still be wrong. Review cost exists because schema-valid is not the same as correct.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 5: Test the sensitivity to accuracy
&lt;/h3&gt;

&lt;p&gt;Now put the terms together. The unit in this illustrative month is a single document, such as one loss run or one application, not a whole underwriting packet, which can take a reviewer 20 to 30 minutes. The inputs are round and invented:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvuk6ggx4eoyiuznhmhyg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvuk6ggx4eoyiuznhmhyg.png" alt=" " width="713" height="362"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In this illustration, inference is under one percent of the total. Halve the inference price and the cost per reviewed document falls by 2.5 cents. Now suppose the cheaper model adds one minute of correction time per document. Review rises to $70,000, and the cost per reviewed document rises to about $7.20, even though the invoice fell.&lt;/p&gt;

&lt;p&gt;Run the same test on your own numbers in both directions. A model that costs more per page and removes a minute of correction may be the cheaper choice. This is why evaluation on your own documents matters more than the price table: the price table only sets the smallest term.&lt;/p&gt;

&lt;h3&gt;
  
  
  Where SIE fits
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feg5u677v8d5f0e7il5op.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feg5u677v8d5f0e7il5op.webp" alt="Superlinked's SIE landing page describing managed and self-hosted inference for task-specific models" width="800" height="360"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;SIE is the inference layer for the task-specific models in a document pipeline. It makes the inference line predictable, on published Cloud prices or on your own GPU hours, and it is how you swap models so a more accurate extractor can lower cost per reviewed document.&lt;/p&gt;

&lt;p&gt;On SIE Cloud, per-model prices are published, so the inference line can be computed before the first call. Two examples from the &lt;a href="https://superlinked.com/serverless" rel="noopener noreferrer"&gt;SIE Cloud price table&lt;/a&gt; on 2026-09-30: LightOnOCR-2-1B at $2 per 1,000 pages, and GLiNER2 Large at $0.186 per 1M input tokens for entity extraction. Your pages and tokens per document turn those into the inference line. Superlinked describes Cloud as pay for what you use, with no GPUs to manage, so the infrastructure term stays small.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Self-hosted&lt;/strong&gt;, SIE runs on your Kubernetes cluster under Apache 2.0, and inference cost moves into the GPU-hours term at your own provider's rate; local mode, on one machine, suits a pilot. Because it serves several models on shared GPUs and can scale to zero on Kubernetes, the utilisation assumption in Step 3 is one you can influence.&lt;/p&gt;

&lt;p&gt;The practical benefit for Step 5 is swapping. Models in the &lt;a href="https://superlinked.com/models" rel="noopener noreferrer"&gt;SIE catalog&lt;/a&gt; sit behind one API, so running two OCR or extraction models against the same documents, and measuring correction time on each, is a configuration change rather than a new deployment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Honest take:&lt;/strong&gt; SIE is how the inference line becomes predictable, and how accuracy, the term that moves cost per reviewed document, becomes a model swap. It runs OCR, extraction, embeddings, and reranking behind one API. SIE Cloud publishes per-model prices, so you can compute the inference line before the first call. Self-hosted SIE, under Apache 2.0, runs the same engine inside a customer VPC or your own cluster, from one codebase, and turns that line into GPU hours on shared GPUs. Running two models against the same documents is a configuration change. The model your reviewers correct less is the one that lowers cost per reviewed document.&lt;/p&gt;

&lt;h3&gt;
  
  
  Frequently asked questions
&lt;/h3&gt;

&lt;h4&gt;
  
  
  What is a good cost per reviewed document?
&lt;/h4&gt;

&lt;p&gt;There is no public benchmark worth copying, and any figure you see quoted mixes different units, document types, and review standards. A single-page invoice and a forty-page underwriting submission are not the same unit. Compute your own baseline before any AI change, using the same definition and the same review timestamps, then compare after. The useful target is not an industry number. It is a lower cost per reviewed document than your own baseline, with no rise in errors that escape review.&lt;/p&gt;

&lt;h4&gt;
  
  
  Hosted APIs are cheap enough already, so why switch?
&lt;/h4&gt;

&lt;p&gt;Switch so the inference line is predictable and so you can raise accuracy, which is what moves cost per reviewed document. SIE publishes per-model prices on Cloud, so you compute that line before the first call, and self-hosted SIE turns it into GPU hours on your own cluster. Run two OCR or extraction models behind one API, measure correction minutes on each, and keep the model your reviewers correct less. That swap is a configuration change. The &lt;a href="https://superlinked.com/docs" rel="noopener noreferrer"&gt;SIE documentation&lt;/a&gt; shows how to call those candidates through one SDK.&lt;/p&gt;

&lt;h4&gt;
  
  
  Do we count documents that were never reviewed?
&lt;/h4&gt;

&lt;p&gt;Not in the denominator, but do count their cost. Documents that are processed and then auto-filed, discarded as duplicates, or rejected as out of scope still incur inference cost. Put that cost into the numerator, because the pipeline paid it to produce the reviewed documents. Report the unreviewed count alongside the main metric. If it grows, the pipeline is spending more on documents nobody looks at, which is a routing problem, not a model problem.&lt;/p&gt;

&lt;p&gt;Using the number&lt;/p&gt;

&lt;p&gt;Cost per reviewed document is a management metric, not an engineering one, and it rewards the right trade-offs. It stops a team celebrating a smaller invoice while the review queue grows. Compute it before and after every model change, and keep the terms separate so you can see which one moved. Price the inference term from the &lt;a href="https://superlinked.com/serverless" rel="noopener noreferrer"&gt;published Cloud rates&lt;/a&gt; or your own GPU bill, and spend the rest of the effort on the review timestamps.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>machinelearning</category>
      <category>productivity</category>
    </item>
    <item>
      <title>WHATS YOUR DEVELOPER JOB/ROLE ABOUT</title>
      <dc:creator>John Philip</dc:creator>
      <pubDate>Sun, 21 Jun 2020 11:15:27 +0000</pubDate>
      <link>https://dev.to/developerphilo/whats-your-developer-job-role-about-2750</link>
      <guid>https://dev.to/developerphilo/whats-your-developer-job-role-about-2750</guid>
      <description>&lt;p&gt;Want to hear about what your daily job/roles are about.&lt;br&gt;
Currently I am on an internship program.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
