Ethan
33 posts


@_heyethan How do you feel working with railway by the way? I heard that they’re very cost effective
English

Most people think building software is about writing good code.
It isn’t.
It’s about asking uncomfortable questions early.
On almost every project I’ve worked on, the biggest risks weren’t technical.
They were:
- Unclear ownership
- Assumptions nobody challenged
- “We’ll figure it out later” decisions
- Features built before the problem was understood
Early in my career, I focused on delivery.
Ship fast. Meet deadlines. Keep clients happy.
It looked productive.
But months later, those same projects needed rewrites, workarounds, or damage control.
Not because the code was bad.
Because the thinking was rushed.
What changed for me was being willing to slow down at the start of projects.
Spending more time on:
- How this will actually be used
- Who owns what
- What happens when it breaks
- What success looks like in practice
Less excitement. More clarity.
It’s not glamorous.
But it saves years.
If you’re building something right now:
Where do you feel pressure to “just move fast” instead of thinking deeper first?
#softwaredevelopment #founders #productthinking #startups #consulting
English

I haven’t experienced an inherently broken API between them. In our setup, fragility usually comes from direct browser-to-Django calls - mainly CORS, auth, or unversioned API changes. We mitigate that by treating Django as a versioned API and using a proxy layer in Next.js where needed, which removes most of that fragility.
English

@_heyethan Thanks. How do you handle API stuff between them? According to my experience, it was fragile due to an API being broken
English

That's why I built Sendbase.
It connects to YOUR AWS account and handles the complexity for you.
AWS pricing. Zero headache.
If email costs are holding you back → getsendbase.com
English









