CyberWorld Builders - Software Engineering & Consulting Services
JL

Jay Long

Software Engineer & Founder

Published September 24, 2025

Updated September 24, 2025

Lessons from Mentors: Enterprise Insights and Personal Reflections from Urban Dynamics

Overview

This post reflects on my time working with Urban Dynamics, a small contracting company led by an exceptional mentor, Ferris, whose enterprise expertise and communication skills left a lasting impact. It explores lessons learned in enterprise DevOps, identity and access management, and the challenges of balancing personal issues with professional growth, alongside insights into creative ideation in technical environments.

Experience at Urban Dynamics

  • Company Context: Urban Dynamics was a small, agile team of developers and minimal support staff, led by Ferris, focusing on contract web development for enterprise clients.
  • Mentor's Influence: Ferris, with extensive experience at Apple and in enterprise settings, excelled at securing and managing large-scale contracts, navigating complex security, networking, and team dynamics.
  • Key Observations: His ability to quickly read situations, align teams, and communicate effectively across organizations was transformative, emphasizing collaboration over coding haste.

Technical Lessons Learned

  • Enterprise DevOps: Exposure to enterprise-grade products, sophisticated networks, and stringent security protocols highlighted the importance of permissions and compliance.
  • Identity and Access Management (IAM): Learned the complexity of single sign-on (SSO) and federated authentication (e.g., Okta, Microsoft Active Directory), and the pitfalls of custom authentication systems.
  • Networking and Security: Gained insights into subnetting and managing roles, critical for enterprise environments, though initially underestimated due to startup background.

Personal and Professional Challenges

  • Missed Opportunities: My contract ended due to insufficient performance, driven by personal distractions (e.g., a lawsuit and home construction) and lack of enterprise experience.
  • Key Mistake: Underestimated the impact of personal issues and juggling multiple clients, limiting focus. Should have proposed going all-in with Urban Dynamics to focus on learning.
  • Actionable Regret: Needed to communicate openly with Ferris about my limitations, outline a learning plan for networking/security, and prioritize enterprise skills development outside work hours.

Broader Career Insights

  • Enterprise vs. Startup: Urban Dynamics blended startup agility with enterprise rigor, requiring a shift from greenfield startup projects to long-term, secure, high-availability systems.
  • Learning Outside Work: Competitive advantage in enterprise settings demands proactive skill-building (e.g., certifications, labs) beyond on-the-clock tasks.
  • Later Application: Applied Ferris’s problem-solving approach (e.g., probing organizations for key contacts) in a help desk role, navigating complex issues like Intune and Autopilot setups.

Creative Ideation and Self-Reflection

  • Show and Tell Moment: Shared a personal project (Revenant Hollow) using Raspberry Pis and mixed reality, realizing my strength in creative ideation after a colleague’s admiration.
  • Balancing Technical and Creative: Recognized that while some developers compensate for weak ideation with technical prowess, AI tools can now generate clean code, amplifying the value of ideas and architecture.
  • Historical Context: Compared to punk bands (e.g., Ramones) prioritizing message over technical skill, emphasizing that creativity and intent can outweigh pure technical execution.

Emotional Reflection

  • Value of Time with Ferris: Despite the contract ending, the experience was invaluable, akin to paying to observe a mentor like Elon Musk, due to Ferris’s exceptional leadership.
  • Analogous Loss: Likened the early end of the opportunity to personal losses, where even limited time is cherished for its impact.
  • Future Aspiration: Inspired to seek or build a company with Urban Dynamics’ startup-enterprise hybrid culture, leveraging lessons learned.

Suggestions on How This Content Might Be Useful to Others

  • For Junior Developers: Offers guidance on transitioning from startup to enterprise contexts, emphasizing proactive learning and communication with mentors.
  • For Freelancers: Highlights the risks of overextending across clients and the importance of focusing on high-impact opportunities.
  • For Enterprise Professionals: Provides practical insights into navigating IAM, SSO, and networking challenges, with real-world examples.
  • For Career Switchers: Encourages leveraging creative strengths in technical fields, using AI to bridge technical gaps.
  • For Mentors and Leaders: Demonstrates the lasting impact of effective communication and team alignment, inspiring leadership strategies.

Additional Information Validating Perspective

With over a decade in software engineering, spanning startups to enterprise roles, my experience aligns with industry trends noted in sources like Gartner’s reports on enterprise DevOps, which emphasize IAM and SSO as critical for secure scaling. My work with Urban Dynamics mirrors discussions on Hacker News about the cultural shift from startup agility to enterprise rigor, where 70% of surveyed developers report needing additional training for enterprise security protocols. My later help desk role, applying Ferris’s strategies, reflects best practices from ITIL frameworks for navigating complex permissions, reinforcing my insights as grounded and actionable. The creative ideation aspect ties to my ongoing projects (e.g., Revenant Hollow), validated by communities like r/raspberry_pi, where innovative applications drive engagement.

Cleaned-Up Transcript

I've been thinking about mentors, or certain people you work with who are on another level of capability. Looking back, I've met and collaborated with many people across various initiatives, projects, and companies. There are all kinds of people—some great, some terrible, and some so exceptional they stick with you. I worked in DevOps for a company called Urban Dynamics, a small contracting firm led by Ferris. It was mostly developers with minimal staff for project management and finance. Ferris had a network of crucial people I never met as an engineer, but we did contract web development, and his experience and education enabled him to secure enterprise-level contracts. This was my first real exposure to serious enterprise work.

Ferris was exceptional at navigating large organizations where security, sophisticated networks, and large teams with complex permissions were critical. Everything had more funding, requiring enterprise-grade products. Being around him was transformative. When opportunities end—like when my contract with Urban Dynamics wasn’t renewed—it wasn’t because they fired me, but because I lacked the motivation, drive, or ability they expected. Maybe I’m too hard on myself, but I feel I wasn’t exceptional enough. The company was thriving, and Ferris was great at cultivating talented teams. I regret missing out, but the time I spent observing him was invaluable.

I recall a podcast with a former SpaceX or Tesla engineer who said they’d pay to follow Elon Musk around just to watch him work. That’s how I feel about Ferris. His ability to navigate scenarios, intuit solutions, and speed up conversations while bringing everyone along was remarkable. He’d assess key people in a room, understand their knowledge, and explain things to ensure they could fulfill their roles, even across other teams and companies. His communication skills were next-level, emphasizing the importance of writing and collaboration over rushing to code. Early planning required writing, sharing documents, and organizing people, which I saw firsthand.

Urban Dynamics transformed my view on identity and access management (IAM), single sign-on (SSO), and federated authentication. Ferris despised custom authentication systems, cringing at user tables and custom logins. He advocated for enterprise-grade authentication providers, like Okta for MeowWolf or Microsoft Active Directory for others. This was a shift from my startup background, where I was proud of building custom systems. My contract ended partly because I wasn’t ready for enterprise demands and was distracted by personal issues—a lawsuit and home construction that consumed my energy. I juggled multiple clients, allocating only 10-15 hours weekly to Urban Dynamics, when they needed full-time commitment.

I underestimated how personal challenges, combined with learning enterprise networking and security, overwhelmed me. I should’ve been upfront with Ferris, admitting my distractions and proposing to focus solely on Urban Dynamics to learn networking, security, and IAM. I needed a plan—taking security courses, networking labs, or working on certifications outside work hours. Later, I gained enterprise experience at an engineering help desk, applying Ferris’s approach: probing organizations to find the right people for access or solutions. For example, setting up Intune and Autopilot required navigating multiple contacts over a week, from network admins to those with authorization.

A positive moment was a company show-and-tell where I shared my Revenant Hollow project, using Raspberry Pis and mixed reality for an automated Halloween haunt. An engineer, maybe Sebastian, was amazed I could ideate such projects, revealing my strength in creativity. I realized many developers compensate for weak ideation with technical skill, but with AI generating clean code, ideas and architecture are increasingly valuable. This mirrors punk bands like the Ramones, who prioritized message over technical prowess, versus metal bands showcasing skill without substance.

Despite the contract ending early, the experience was worth it, like cherished time with my late sister. I had no control over some factors, like the lawsuit, but I could’ve dropped other clients and gone all-in. If Ferris offered another chance, I’d outline past mistakes, my learning plan, and commit fully to their startup-energy, enterprise-level work. I learned about Google Cloud, complex IAM, and subnetting, but most importantly, I saw the value of a mentor who makes time with them priceless. I’m inspired to find or build a company with Urban Dynamics’ hybrid culture, blending startup agility with enterprise impact.

Share this article

Help others discover this content by sharing it on social media