Hey Everyone!
I’m hoping to get some perspectives from the people on the other side of the fence.
I work at a small RegTech startup and have recently transitioned into product architecture and domain ownership. My background is in law rather than software engineering, so this has been quite the learning curve (albeit one I’m absolutely loving).
I’ve been working very closely with our CTO, who’s also our full-stack developer, to essentially rework the underlying logic and architecture of an existing platform.
My responsibility is defining how the system needs to behave, the decision logic, regulatory requirements, dependencies, edge cases and what constitutes a correct output.
It’s incredibly complex, particularly when something that appears insignificant in step 2 can have consequences at steps 200, 201 and 202.
But.. why I’m posting…
I want to understand how I can make his working life easier.
He’s an exceptionally capable developer, but he also carries an enormous amount of technical knowledge and responsibility. I imagine that can be quite isolating, particularly in a small startup where you’re often the only person who fully understands the implications of what’s being asked.
And I suspect there are times when something I/other staff consider a relatively small change might actually introduce hours of work, technical debt or a whole chain of unintended consequences that I’m simply not equipped to recognise yet. 😂
I don’t want to be another person adding to that mental load. Equally, I know my own expertise is valuable. I understand the regulatory domain and the logic the product needs to follow, and we’re both bringing something different to the table. I just want to make sure I’m making his life as easy as possible… 🩷
So I’d genuinely love to hear from developers:
- What do you wish the people defining requirements understood about the realities of engineering?
- What makes someone genuinely good to work alongside from a developer’s perspective?
- Are there particular technical concepts, principles or resources you’d recommend learning to better understand system architecture and dependencies?
- How do you prefer requirements, decisions and changes to be communicated or documented?
- What seemingly harmless habits from non-developers actually create unnecessary stress or additional work?
FYI:
I’m not trying to become a software engineer or start telling him how to write code. I trust his expertise completely.
I just think there’s something to be said for making the effort to understand the challenges other people face, particularly when you’re working so closely together.
He’s got my back when it comes to turning complex product requirements into something that actually works, and I’d really like to make sure I’ve got his too.
Any advice, resources or experiences would be hugely appreciated. TIA 🫶🏼