About the service
I am a backend developer who consciously specializes in server-side Dart rather than turning to it out of necessity. Many know Dart as a language for mobile apps in Flutter, but I am interested in its other side, the server side. I design and run HTTP services and REST APIs on shelf-style middleware and frameworks like Serverpod: I set up routing, authentication, request validation, structured logging, and graceful shutdown. I care about what the user doesn't see but always feels: predictable response latency, sensible error codes, connection pools to Postgres or another store, and code a colleague can read six months later without a guide. Beyond web services, I work a lot with tools for developers. I write console applications with proper argument parsing, subcommands, colored output, and meaningful exit codes so they work well in scripts and CI pipelines. I actively use Dart's build system and code generation: source_gen and build_runner turn annotations and schemas into type-safe serialization, client stubs, and boilerplate code that otherwise quickly becomes stale with manual edits. When a project needs a small internal daemon, migration runner, data importer, or service linking systems together, Dart lets me ship something compact, statically typed, and easy to build into one self-contained executable.
To set boundaries: I am not the one hired for pixel-perfect mobile screens, and I do not propose rewriting everything in Node or Go. If your backend is already in Dart or you want one team and one language on client and server, I will make the server side solid. I write tests, document endpoints, and hand over something you can actually run and maintain.
— REST and HTTP API on shelf and Serverpod-level frameworks
— Console utilities, daemons, and automation for CI
— Code generation via build_runner and source_gen
— Working with databases, migrations, and connection pooling (Postgres and others)
— Authentication, request validation, logging, and error handling
— Building Dart into a single native executable
To set boundaries: I am not the one hired for pixel-perfect mobile screens, and I do not propose rewriting everything in Node or Go. If your backend is already in Dart or you want one team and one language on client and server, I will make the server side solid. I write tests, document endpoints, and hand over something you can actually run and maintain.
— REST and HTTP API on shelf and Serverpod-level frameworks
— Console utilities, daemons, and automation for CI
— Code generation via build_runner and source_gen
— Working with databases, migrations, and connection pooling (Postgres and others)
— Authentication, request validation, logging, and error handling
— Building Dart into a single native executable
