I think 383toast is talking about your landing page design which has very strong AI-generated design vibes (blue-green gradients, rounded rectangles with a colored border on the left...)
There are a bunch of skills you can find online to improve on this if you want to keep designing with Claude, and the latest generation of models are better (Fable/GPT5.6).
Dashdoc is a SaaS Transport Management System for road freight. We help carriers and shippers run transport operations on one shared platform.
We’re hiring a product-minded engineer to help us expand in Belgium and the Netherlands. Local specifics: e-CMR mandates, digital waste regulations, Dutch/Flemish accounting standards, regional carrier workflows often block deals or deployments. Your job is to find those blockers and turn them into shipped product.
You’ll work directly with customers, sales, CSMs, and product. You’ll be able to spend time with carriers in Belgium and the Netherlands, watch users use the product, read contracts/regulations, then spec, build, deploy, and measure the features yourself.
Stack: React, React Native, Python/Django, Django REST Framework, PostgreSQL, Google Cloud. We use Shape Up, ship continuously, and use AI coding tools like Claude Code, Cursor, and Codex.
Good fit if you speak Dutch fluently, write clearly in English, like owning ambiguous product problems end-to-end, care about simple UX and clean code, and enjoy deleting code as much as adding it.
I may have misremembered but I thought I had read somewhere that recent models by OpenAI and Anthropic tend to produce reasoning that is not always understandable for humans. But you're right that it's not the case for Deepseek so maybe I'm hallucinating ;)
Or maybe it was an article or a tweet about researchers trying really hard to steer the model to think in English otherwise interpretability / safety becomes a lot harder?
I believe that most reasoning models actually think in their own "language" which is not really understandable by humans. The thinking traces that are shown in the UI are actually summaries generated by a smaller model in plain english (or user language). Sometimes this leaks through and you see some chinese/japanese characters in e.g. Claude's reasoning.
Great timing as I'm exploring the space to get rid of Cursor in our stack.
For local dev everyone is switching to Claude Code or Codex.
The state of the art for cloud agents in my opinion right now is Cursor. But their pricing model per-user doesn't make sense when what I want is to enable anyone in the company to fix things in the product.
2 things not immediately clear from your homepage:
- do you support full computer use? Again Cursor is the best I've tried there
- what kind of triggers do you support? We have in particular one automation built with cursor to auto approve PRs that are low-risk. It triggers on a specific comment on a PR
Finally some advice from a user's pov: you need to invest a lot in the onboarding experience. I tried Devin today and it couldn't get it to work after one hour of fiddling. How do you store the repo's setup scripts? Cursor cloud is pretty opaque and annoying to configure on that side.
Anyway I'll try it!
I'm currently in that hellish process too... I don't know how to get out of it. Did you know that your employees will be forbidden from downloading from the App store once you launched that migration? It's a nightmare
Dashdoc is a fast-growing transport management platform for the road freight transportation industry.
We're hiring a Lead Software Engineer to work on our Invoicing domain. Small 3-person (including you) team, great impact on tens of thousands of people using the tool all day everyday, great colleagues, international context, access to good tools (Cursor, Claude Code).
I don't understand why pytest's collection is so slow.
On our test suite (big django app) it takes about 15s to collect tests. So much that we added a util using ripgrep to find the file and pass it as an argument to pytest when using `pytest -k <testname>`.
https://cosmith.fr
Feel free to contact me at [email protected].