<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering on Seaway Labs</title><link>https://seawaylabs.ca/tags/engineering/</link><description>Recent content in Engineering on Seaway Labs</description><generator>Hugo</generator><language>en-ca</language><copyright>© [Seaway Labs] 2026</copyright><lastBuildDate>Tue, 18 Mar 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://seawaylabs.ca/tags/engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Why We Scope Before We Estimate</title><link>https://seawaylabs.ca/blog/why-we-scope-before-we-estimate/</link><pubDate>Tue, 18 Mar 2025 00:00:00 +0000</pubDate><guid>https://seawaylabs.ca/blog/why-we-scope-before-we-estimate/</guid><description>&lt;p&gt;Every studio has a version of this story. A client comes in with a project, the studio sends back an estimate, work begins, and somewhere around week eight the estimate is revealed to be fiction. The budget doubles. The timeline slips. Relationships fray. Sometimes the project recovers; sometimes it does not.&lt;/p&gt;</description></item><item><title>The Real Cost of a Poorly Documented Codebase</title><link>https://seawaylabs.ca/blog/the-real-cost-of-a-poorly-documented-codebase/</link><pubDate>Wed, 12 Feb 2025 00:00:00 +0000</pubDate><guid>https://seawaylabs.ca/blog/the-real-cost-of-a-poorly-documented-codebase/</guid><description>&lt;p&gt;Technical debt has a perception problem. It gets discussed as a future concern — something to address when the product is bigger, the team is larger, there is finally a quiet quarter. There is never a quiet quarter.&lt;/p&gt;
&lt;p&gt;The debt is accruing right now, in the absence of documentation, in the architectural decisions that exist only in the memory of whoever made them, in the code that has never been explained to anyone. The cost is not deferred. It is distributed invisibly across every hour your team spends working in the codebase.&lt;/p&gt;</description></item><item><title>React Native in 2025: When It Is Enough and When It Is Not</title><link>https://seawaylabs.ca/blog/react-native-when-its-enough/</link><pubDate>Tue, 07 Jan 2025 00:00:00 +0000</pubDate><guid>https://seawaylabs.ca/blog/react-native-when-its-enough/</guid><description>&lt;p&gt;The native-versus-cross-platform question gets asked at the start of almost every mobile engagement we take on. The honest answer — which is unsatisfying but correct — is that it depends. But the factors it depends on are more specific than most articles acknowledge, and the tradeoffs have shifted meaningfully over the past two years.&lt;/p&gt;</description></item></channel></rss>