First Day at Endoo: New Beginnings and Odoo Adventures
First Day at Endoo: New Beginnings and Odoo Adventures
February 16th, 2026 - 9:00 AM. I walked into the Endoo office for the first time as an intern, a mix of excitement and nervous energy. Today marks the start of my 14-week internship journey at Endoo by Endare, and as I sit here reflecting on my first day, I can already tell this is going to be an incredible learning experience.
About Endoo and Endare
Before diving into my first day, let me introduce the company.
Endare is a digital innovation company that helps businesses transform through technology. They specialize in creating custom software solutions, digital products, and strategic consulting.
Endoo is Endare's dedicated Odoo division—a team of specialists focused on implementing, customizing, and optimizing Odoo ERP solutions for businesses. For those unfamiliar, Odoo is a comprehensive open-source business management platform that covers everything from CRM and sales to inventory, accounting, and HR.
What makes Endoo special is their deep expertise in the Odoo ecosystem combined with a pragmatic, business-first approach. They don't just deploy software—they help companies rethink their workflows and processes.
The Project: Visual Manuals for Odoo
During my first morning, I got a brief introduction to the project I'll be working on for the next 14 weeks: a visual manuals module for Odoo.
The problem: Many companies use an external SaaS platform to create visual step-by-step instructions with images and videos. It's great for training employees or documenting processes, but it's expensive and completely disconnected from their other business systems.
The solution I'll be building: A native Odoo module that replaces this external platform entirely, bringing all that functionality directly into the Odoo environment. This means seamless integration with sales, products, inventory—everything.
Why this matters: Instead of paying for yet another external tool, companies can manage their instructional content right alongside their other business data. Plus, as a student, I get to build something real that will actually be used by clients.
I won't lie—hearing about the scope of this project was both exciting and slightly intimidating. But that's what internships are for, right?
Morning: Setup and Onboarding
My first morning was all about getting up to speed.
1. Team Introduction
I was welcomed by the team and immediately invited to join the daily standup at 9:30 AM. Standups are a core part of the Agile workflow here—every morning, the Odoo team gathers (virtually or in-person) to share:
- What they worked on yesterday
- What they're working on today
- Any blockers or questions
It was a bit surreal to be sitting in on a real development team's standup. Everyone was friendly, and I appreciated that they took the time to introduce me and explain what they were working on.
2. Getting the Tools Ready
The rest of the morning was dedicated to setting up my development environment. Here's what I configured:
Development Tools:
- Claude Code - AI-powered coding assistant (this was new to me, and I'm excited to see how it helps)
- PyCharm - Python IDE (I'd used VS Code before, but they recommended PyCharm for Python/Odoo work)
- GitKraken - Git GUI (makes working with branches and PRs much easier visually)
Odoo-Specific Setup:
- Odoo.sh account - Endoo's cloud hosting platform for Odoo instances
- SSH access to staging servers - So I can deploy and test my code
- Access to the Endoo knowledge base - Internal documentation and best practices
The Challenge: About halfway through setup, I hit a bug with SSH connections to Odoo.sh. After some troubleshooting (and a quick question to a colleague), I got it working. First bug of the internship: conquered. ✅
3. Odoo Crash Course
Once my environment was ready, I received a practical exercise to get familiar with the Odoo framework. The goal was simple: build a basic Odoo module with models, views, and some business logic.
I worked through:
- Models - Defining database structure with Python classes
- Views - Creating forms and lists in XML
- Security - Setting up access rules
- Basic business logic - Constraints and computed fields
By late afternoon, I had a working prototype (well, mostly working—frontend still needed some polish). For someone who hadn't touched Odoo before today, I was pretty happy with the progress.
Afternoon: Documentation Deep Dive
The latter part of my day was spent reading through documentation:
Odoo Official Docs:
- Framework architecture
- ORM (Object-Relational Mapping) basics
- QWeb templating engine
- Module structure and conventions
Endoo Internal Docs:
- Coding standards and best practices
- Git workflow (feature branches, pull requests, code reviews)
- Deployment process to staging and production
- How they structure projects and collaborate with clients
Odoo.sh Platform:
- How to manage branches
- Database management
- Logs and debugging tools
Reading documentation isn't the most exciting part of development, but it's essential. I'd rather spend a day learning conventions now than waste weeks doing things the wrong way.
First Impressions
As I wrap up this first day, here are my initial thoughts:
What Went Well ✅
1. The Team is Welcoming
Everyone I met today was friendly, approachable, and genuinely interested in helping me succeed. No "you're just an intern" vibes—I felt like part of the team from day one.
2. Clear Expectations
I know exactly what I'm building, why it matters, and what success looks like. Having a clear project scope from the start is huge.
3. Real-World Experience
This isn't a toy project or a made-up scenario. I'm building something that will be deployed to actual clients. That's both motivating and a little nerve-wracking.
4. Modern Tooling
The development setup here is top-notch. Claude for AI assistance, PyCharm for Python, GitKraken for version control, Odoo.sh for hosting—everything feels professional and well thought out.
What's Challenging 🤔
1. Odoo is Big
The Odoo framework is massive. There are hundreds of modules, thousands of classes, and countless conventions to learn. I know I'll only scratch the surface in 14 weeks, but that's okay.
2. Python Refresher Needed
I learned Python in school, but it's been a while. I'll need to brush up on object-oriented programming, decorators, and Python-specific patterns.
3. Working Solo (Mostly)
This is a solo project, which means I'll have a lot of autonomy—but also a lot of responsibility. I'll need to be proactive about asking for help when I'm stuck.
What's Next?
Looking ahead to the rest of week 1:
Tomorrow (Tuesday):
- Continue the Odoo practical exercise
- Start drafting requirements for the project
- More documentation and tutorials
Rest of the Week:
- Complete initial requirements analysis
- Create user stories and acceptance criteria
- Set up a project roadmap
- Possibly start on the "Hello World" ticket (basic module skeleton)
There's also a team building event on Thursday, which I'm looking forward to. It'll be a good chance to get to know everyone outside of work mode.
Reflections
Starting an internship is always a mix of emotions. You're excited to learn, eager to prove yourself, but also aware of how much you don't know yet.
What I appreciate most about today is that Endoo didn't throw me into the deep end. They gave me time to:
- Set up properly
- Learn the tools
- Understand the project
- Ask questions
That thoughtful onboarding makes all the difference.
I'm walking away from day one feeling optimistic. The project is challenging but doable. The team is supportive. The tech stack is interesting.
Let's see where the next 14 weeks take me.
Day 1 Stats:
- Hours: 9:00 AM - 5:30 PM (8.5 hours)
- Coffee consumed: 3 cups ☕
- Lines of code written: ~200 (practice module)
- New tools learned: 5 (Claude, PyCharm, GitKraken, Odoo.sh, Odoo framework)
- SSH bugs encountered: 1
- SSH bugs fixed: 1 ✅
Follow along as I document my internship journey. Next up: diving into requirements analysis and starting to build the visual manuals module.