Go Goroutines → Concurrent Systems Go Gin/Fiber → High-Performance APIs Go GORM/sqlx → Database Access Go HTMX → Full-Stack Web Apps Go WebAssembly → Browser Apps Go Wails/Fyne → Desktop Apps Go Ebiten/OpenGL → Games & Graphics Go TinyGo → Embedded & IoT Go Docker/Kubernetes → Cloud-Native Systems Go Apache Arrow → Analytics & Data Processing one language performance simplicity concurrency full-stack and people still say "go is only for backend"

今でも実行時にデータベースに問い合わせたり（dbflute）、DBのエンジン丸抱えで展開したり（sqlcやsqlx）はあるんですが、特化している分確実な反面、複数DB対応や柔軟性に問題がありまして。 そこをLLMのpowerでカバーするwプロジェクトになっております。

I have very strict rules (in claude.md) about how Errors for the Rust Result type work. Errors must *always* be naked enums and free from prose. They must never propagate. e.g if you call a function and it returns an error enum, you must map it to your own error enum before returning to your caller - even if they incidentally end up being the same. Claude just cannot understand this. Always trying to return things like Sqlx::Error or Foo(Bar) enum variants. Already fixed over 1200 violations and not even half way.

Hey Andras, I’m exploring a related direction with rustwing, but focused on the backend side. It generates Axum SQLx backends with auth, resources, services, repos, migrations, OpenAPI docs, client generation, workers, and LLM hooks wired in. Would love your thoughts: github.com/creativebash/rust…

The stack, for the nerds: Rust Leptos SSR Axum PostgreSQL Why Rust for a data site? Honestly, I wanted to learn it. Also: single binary, zero runtime surprises, compile-time DB query correctness via sqlx. cargo-leptos handles the full-stack build.

An AI just opened a 1,700-line PR on my repo. Rust, 37 tests, two pre-existing bugs fixed. It took 30 minutes. Here's what happened. I asked Fable 5 (@AnthropicAI's new model) to add a CLI to Tabularis, my open source database GUI. Went to make coffee, came back to a draft PR. The stuff I expected: the commands themselves. `tabularis query <connection>` drops you into a proper SQL shell. History, multi-line statements, \use to jump between databases, table/json/csv output. The stuff I did NOT expect: It dug through the codebase first and realized our MCP server already knew how to resolve connections without the GUI (keychain, ssh tunnels, plugin drivers). So instead of writing all that twice, it pulled the logic into a shared module and made the MCP server use it too. That's the refactor I would have done. It found two real bugs that were already there. Keychain logs printing to stdout, which would have corrupted any piped csv output. And a panic in headless mode because sqlx drivers were never installed. Then it ran its own shell against a live MySQL db to check the output, and fixed what it didn't like. Thirty minutes. I've spent longer naming a variable. It's a draft PR and I'm reviewing every line before anything ships. But the fact that the review is even worth doing is what gets me. Two years ago this was autocomplete. Real demo in the video. PR in the first comment 👇

Rust Roadmap: From Zero to Production (2026) Most people learn Rust the wrong way. They get stuck in the ownership model and never reach production level. Here’s the exact path I recommend: Phase 1: Fundamentals (3 weeks) Ownership, Borrowing, Lifetimes, Structs, Enums, Error Handling Phase 2: Core Concepts (3 weeks) Traits, Generics, Smart Pointers, Iterators, Testing Phase 3: Async & Concurrency (4 weeks) Tokio, async/await, channels, shared state Phase 4: Real Projects - REST API with Axum SQLx PostgreSQL - Async Background Job Processor (Tokio Redis) Phase 5: Production Ready Observability, Error handling, Graceful shutdown, Docker CI/CD Phase 6: Advanced gRPC, High-performance systems, Unsafe Rust, WebAssembly Rust has a steep curve in the beginning, but once you get past it, you become extremely valuable. Stop watching tutorials after the fundamentals. Start building real projects early. Save this roadmap. Which phase are you currently in? Drop it below 👇

Rust Tokio Axum sqlx Cranelift ... = Hot Dev: An open source language and platform for backend and AI workflows. github.com/hot-dev/hot

예쓰. 안그래도 러스트가 제 추구방향이랑 많이 일치해서 주력으로 쓸 예정입니다. SQLx 라이브러리는 처음 알았네요. 좋은정보 감사합니다.

データ準備からエクスポートした SQLX ファイルが pipe syntax なのは確かにびっくりだ #dataformjp

バックフィルの原子性のために type: operations の sqlx でトランザクションを貼るパターン。やったことなかったけど良さそう。 #dataformjp

Go net/http → Backend Engineer Go Chi → API Engineer Go Fiber → High-Performance API Engineer Go GORM → Database Engineer Go sqlx → Backend Engineer (PostgreSQL/MySQL) Go Templ → Full-Stack Web Engineer Go HTMX → Modern Web Backend Engineer Go Wails → Desktop App Developer Go Fyne → Cross-Platform UI Engineer Go Docker → DevOps Engineer Go Kubernetes → Platform Engineer Go Temporal → Workflow Engineer Go NATS → Distributed Systems Engineer Go gRPC → Microservices Engineer Go Connect → API Platform Engineer Go CGO → Systems Programmer Go TinyGo → Embedded/IoT Engineer one language…a dozen infrastructure careers, and people still ask "where's the enterprise?"🦫

Go Gin → Backend Engineer Go Echo → API Engineer Go gRPC → Systems Backend Engineer Go GORM → Database Engineer Go sqlx → High Performance Backend Engineer Go WebAssembly → Web Performance Engineer Go Wails → Desktop App Developer Go Fyne → Native UI Engineer Go Ebiten → Game Developer Go TinyGo → Embedded Systems Engineer Go Kubernetes → Cloud Native Engineer one language…multiple elite engineering paths 🫡

Rust Tokio → Backend Engineer Rust Actix → API Engineer Rust Axum → Systems Backend Engineer Rust Diesel → Database Engineer Rust SQLx → Async Backend Engineer Rust WebAssembly → Web Performance Engineer Rust Yew → Frontend/WASM Engineer Rust Tauri → Desktop App Developer Rust egui → Native UI Engineer Rust Bevy → Game Developer Rust wgpu → Graphics Engineer Rust Embedded Rust → Embedded Systems Engineer Rust Linux Kernel → Systems Programmer one language…multiple elite engineering paths 🫡

Rust backend development does not have to start from a blank page. With Rustwing, you can scaffold an Axum SQLx app fast, make changes, run it, and open the generated OpenAPI docs in Swagger UI or ReDoc. Routes, structure, and docs are there early, so you can start building faster. #rustlang #buildinpublic

what about sqlx, it is getting traction

I’ve built apps with PHP, Python, JavaScript and TypeScript for years. Over time, I kept running into the same backend pattern: - auth - CRUD - services - repositories - migrations - workers - API docs - clients Different language, same boilerplate. When I came into rust, I found Axum, I really liked how minimal it was. Excellent foundation, no heavy magic. So I started building Rustwing around one idea: What if Axum stayed Axum, but the repetitive application layer could be generated? Not hidden. Not locked away. Just ordinary Rust files your app owns. That’s the project I’ve been building. Rustwing is still early, but it can already generate production-shaped Rust backends with Axum SQLx: scoped resources, workers, LLM integration hooks, OpenAPI docs, and more. I’ll be sharing the journey here calmly over the next few weeks: what works, what doesn’t, and what I’m learning while trying to make Rust feel practical for building real SaaS and AI backends. Repo: github.com/creativebash/rust… #rustlang #buildinpublic

【ソフトウェアエンジニア募集】 売上超成長中の美容業界向けSaaSのエンジニアを募集しています。 弊社では美容業界向けに、 ・AI ・予約 ・顧客管理 ・物流 など複数のサービスを開発・運営しています。 現在、 ・500法人以上導入 ・前期黒字 ・MRR成長中 という状況で、開発チームを強化しています。 技術スタックは、 ・TypeScript / React / Next.js ・Rust / Axum / SQLx ・Swift / SwiftUI ・PostgreSQL が中心です。 エンジニア組織は私を含めて5名（正社員・業務委託含む） これまでは新機能開発が中心でしたが、ユーザー数の増加に伴い、 ・パフォーマンススケーリング ・インフラコスト最適化 ・セキュリティ強化 といった課題にも本格的に取り組むフェーズに入っています。 フロントエンド、バックエンド、インフラといった職種の境界にこだわらず、 「技術で事業課題を解決したい」 という方を探しています。 ・フルリモート（出社も可） ・フレックス ・MacBook貸与 ・Claude Teamプラン会社負担 詳細はプロフィールの求人リンクをご覧ください！

Here is my architectural design spec ADR so you can write code like me ! This is my flavor of ice cream. rust sqlx postgres vite react zustand github.com/ethereumdegen/arc…