An individual lesson in tech meetings, group society, and reading between the lines
At some time in your programmer trip, you’ll hear it:
“You can select the modern technology you choose.”
It sounds encouraging– also interesting. It feels like a ballot of self-confidence in your abilities and your judgment. That’s specifically just how I really felt during a work application not long ago.
The interview was going well. I was vibing with the employer, the project appeared interesting, and they offered me what seemed like creative control: freedom to choose the stack and tools I ‘d be using. Naturally, I was thrilled. I chose django-ninja — a lightweight, modern internet structure that brings the clearness of FastAPI right into the Django world. It’s fast, uses Pydantic for validation, includes integrated OpenAPI assistance, and is optimal for constructing tidy, maintainable APIs rapidly.
I presented my thinking plainly:
- The job didn’t call for the heavyweight equipment of DRF.
- django-ninja would certainly help deliver faster.
- It was getting energy in the area.
- It lined up with the principles of modern Python advancement.
I was showing initiative and technical maturation. I anticipated conversation, perhaps even pushback– however not what followed.
A few days later on, I was told they were “going in a different instructions.” After digging deeper, the fact appeared: the technological team wasn’t aboard with django-ninja. They favored Django REST Framework (DRF) , which was “battle-tested” and “currently acquainted” to the team. My option of a more recent device, in spite of its preliminary openness, had actually made me a threat, not a possession.
Which’s when the realisation struck me:
When somebody informs you, “you can choose,” constantly make clear: is it actual liberty, or is it a concealed test with one right response?
This experience wasn’t just about picking the incorrect device (I didn’t– django-ninja is strong). It was about misaligned expectations The group had actually currently picked DRF in their hearts; they simply hadn’t told me. And I made the error of presuming that “tech freedom” in a working with context suggested true autonomy, when it was a type of vetting– a catch spruced up as empowerment.
The Takeaways
This experience showed me more than simply tech pile national politics. Below are the lessons I’m taking onward– and sharing with you:
1 “Flexibility to choose” requires borders.
Following time I’m informed I can pick the devices, I’ll ask:
“Are there any kind of devices or stacks the group currently chooses or expects?”
Don’t assume blank-slate liberty unless it’s plainly spelled out.
2 Culture fit matters greater than glossy devices.
Even the best device is worthless in a group that doesn’t acquire into it. Technology decisions should be shared decisions. Introducing something new ways bringing people with you– not charging ahead alone.
3 New ≠ bad, yet comfort zones are genuine.
django-ninja is an outstanding device. However teams familiar with DRF might not prepare to proceed– and that’s okay. It’s not a representation on your ability or judgment if they’re not all set for adjustment.
Final Idea
I share this story not out of bitterness, however since I recognize several developers will encounter a similar scenario. You’ll believe you’re being rewarded for assuming outside package– when actually, package was never open to begin with.
So right here’s my suggestions:
Select your devices carefully, yet select your groups much more intelligently.
You do not need simply consent to develop– you need placement to expand.
Thanks for analysis. And if you belong to a group that states “you can pick”,– suggest it. Or be straightforward regarding your constraints. It saves everybody time and irritation.