Octarnal Journal
Notes fromthe build.
What we have learned building and running software for other people — written down while it is still inconvenient. No launch posts, no case studies, no numbers we made up.
- Pieces
- 9
- Subjects
- 7
The archive
01
Enterprise deliveryNine decisions that settle an enterprise build
Every enterprise project that went badly went badly for a reason somebody could name on day one. The code was rarely the reason.
Shaqibul Neil · 13 October 2026 · 10 minRead02
AI and automationTen plain claims about what AI is doing to the software industry
No forecast, no chart, no number anybody made up. Ten statements we would defend in a room full of engineers.
Shaqibul Neil · 11 October 2026 · 8 minRead- 03Studio life
Life in Octarnal, written from inside it
A small studio in Dhaka where six people argue about naming things, and the argument is the point.
Shaqibul Neil · 8 October 2026 · 10 minRead 04
Growth and positioningHow a local project becomes a global one
Going global is not a market you enter. It is a set of assumptions you stop making, one at a time.
Muntahi Safwan · 4 October 2026 · 7 minRead05
PracticeWhat a discovery week should actually produce
If a discovery week ends with a deck and a warm feeling, it was a sales exercise. Here is what it should leave on the table instead.
Sagor Hossain · 29 September 2026 · 6 minRead- 06Practice
The projects we say no to, and why
Every studio has a list. Most keep it private. Here is ours, with the reasoning, because the reasoning is the useful part.
Sagor Hossain · 24 September 2026 · 6 minRead 07
Engineering craftA data model that survives year three
Schemas do not fail on launch day. They fail the first time somebody asks a question the model cannot answer without a migration.
Abdul M. Fahim · 18 September 2026 · 6 minRead08
InfrastructureMaking releases boring on purpose
A deploy should be the least interesting thing that happens on a Tuesday. Everything below exists to keep it that way.
Meraz Uddin · 12 September 2026 · 6 minRead
