WeSearch

The Road to KiwiEngine — Why I Stopped Thinking in Frameworks

·2 min read · 0 reactions · 0 comments · 26 views
#softwareengineering#webdev#architecture
The Road to KiwiEngine — Why I Stopped Thinking in Frameworks
TL;DR · WeSearch summary

Drew Marshall discusses his shift in thinking about software development, moving away from traditional frameworks towards a more modular and composable approach. He emphasizes the importance of designing systems based on contracts and predictable behavior rather than being locked into specific frameworks. This change in perspective has led to the development of KiwiEngine and the CitrusWorx ecosystem, which he plans to document publicly.

Key facts
About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

Original article
DEV.to (Top)
Read full at DEV.to (Top) →
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherDEV.to (Top)
Canonical URLhttps://dev.to/stinklewinks/the-road-to-kiwiengine-why-i-stopped-thinking-in-frameworks-34co
Publication timeWed, 27 May 2026 15:30:00 +0000
Retrieval time2026-05-27T15:38:01.782Z
Last seen2026-05-27T15:38:01.782Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterbLyVg-Knt8KS
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 832808) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Drew Marshall Posted on May 27 The Road to KiwiEngine — Why I Stopped Thinking in Frameworks #buildinpublic #webdev #architecture #softwareengineering Over the last few years, I kept running into the same problem while building projects: Every tool solved its own problem well, but the overall system kept getting more chaotic. Frontend frameworks handled UI. Backend frameworks handled APIs. Cloud platforms handled deployment. CMS platforms handled content.

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)