The networking world has long crowned the Cisco Certified Network Associate as the go‑to badge for entry‑level engineers. It distilled decades of routing, switching, and command‑line wisdom into one carefully curated blueprint. Yet the landscape that CCNA once ruled uncontested has shifted in ways that traditional command‑line study guides could not predict. Software‑defined networking, API‑driven infrastructure, and continuous‑integration pipelines have crept from proof‑of‑concept labs into production backbones. As enterprises embraced cloud transformation, the old assumption—that every change flows through a human typing configuration lines—broke down. This seismic shift birthed a new track: the Cisco DevNet Associate.
The emergence of the DevNet Associate certification represents a fundamental change in how professionals are expected to interact with network infrastructure. The automation-first mentality has become more than just a trend—it’s now a requirement in many environments where scalability and speed are paramount. The days of manual CLI configuration for hundreds of devices are giving way to repeatable, codified workflows. Instead of reactive command-based fixes, today’s engineers are expected to build proactive, automated systems capable of adjusting themselves based on data-driven triggers and business logic.
The DevNet Associate was introduced to fill this emerging skill gap. It offers a developer-centric approach to network operations, focusing on APIs, software development, network programmability, and infrastructure as code. It doesn’t discard traditional networking concepts; instead, it builds upon them by enabling engineers to manage and scale infrastructure through code, automation tools, and developer-friendly interfaces. It acknowledges that the future of networking isn’t isolated in racks and wires—it’s interwoven with application lifecycles, developer pipelines, and real-time service deployment.
What makes DevNet particularly important is its alignment with modern enterprise demands. In hybrid cloud environments, for example, resources are spun up or decommissioned dynamically based on workload needs. Doing this manually is both time-consuming and prone to errors. DevNet provides the tools and knowledge required to automate these processes using REST APIs, model-driven telemetry, and orchestration frameworks. Understanding how to leverage Cisco platforms like DNA Center, Meraki, and Webex through programmatic interfaces becomes a key skill for today’s professionals.
Moreover, DevNet Associate doesn’t just target developers—it’s crafted for infrastructure engineers ready to embrace automation. The curriculum blends foundational programming skills in Python with real-world use cases for automation and orchestration across Cisco platforms. Topics like version control with Git, CI/CD pipelines, JSON/YAML data formats, and network configuration templates are all part of the training. This hybrid learning path produces professionals who can both interpret a routing loop and write a script to detect it across an enterprise topology.
As companies shift toward intent-based networking, the demand for professionals who can implement policies programmatically and ensure alignment with business goals increases dramatically. DevNet plays a crucial role here by teaching the logic behind controller-based management systems. Engineers can now define network intent using high-level APIs, letting automation frameworks handle the low-level device configurations in real time. This empowers teams to reduce human error, respond faster to incidents, and enforce consistency across diverse environments.
The introduction of DevNet Associate has also brought a cultural evolution within IT teams. Network engineers, traditionally separated from software development teams, are now collaborating more closely with developers, DevOps specialists, and cloud architects. This collaboration requires a shared language—one rooted in APIs, code, automation, and continuous delivery. DevNet is the starting point for network engineers to speak that language fluently, breaking down silos and aligning technical capabilities with business agility.
In short, the DevNet Associate certification isn’t just a new exam on the Cisco track—it’s a signal that the rules of networking have changed. It reflects the industry’s shift toward programmability, automation, and scalable infrastructure design. As networks evolve into software-defined fabrics and cloud-native systems, professionals who adapt their skill sets to include both network fundamentals and software practices will be the ones driving future innovation. DevNet is not a replacement for CCNA but a parallel evolution that enables engineers to thrive in a programmable, dynamic, and highly interconnected digital world..
DevNet does not compete against CCNA in a winner‑takes‑all battle. Instead, it completes the picture. Where CCNA sharpens skills for troubleshooting physical links, VLANs, and routing adjacencies, DevNet unlocks the next tier: programmatic control, automation, and application‑aware networking. Imagine standing in a sprawling data center where new virtual networks spin up every hour. Manually applying ACLs becomes impossible. Scripts tied to webhooks, however, can apply consistent policies in milliseconds. That is DevNet’s domain.
Understanding why DevNet matters begins by recognizing that modern traffic flows are no longer homogenous. Microservices chatter over east‑west links, container clusters orchestrate overlay networks, and serverless functions request resources on‑demand. Traditional network teams therefore face visibility gaps unless they speak the language of APIs. DevNet Associate bridges this gap by teaching foundational programming concepts—loops, conditional logic, RESTful calls—while anchoring them to Cisco platforms. Instead of memorizing yet another show command, candidates learn to pull JSON payloads from devices, parse interface counters, and trigger configuration changes through code.
There is also a cultural dimension. DevOps practices and agile methodologies have pushed infrastructure teams to integrate with development pipelines. Release cycles shrank from quarterly to daily, sometimes hourly. A network engineer who can integrate test-driven automation gains influence across silos. DevNet Associate demonstrates competence in Python scripting, model‑driven programmability, and version‑controlled infrastructure, aligning network operations with the pace of software releases.
Another reason DevNet stands out is its relevance to security paradigms. Zero‑trust architectures demand continual identity verification and policy enforcement. Implementing that level of dynamic control through static per‑port ACLs is untenable. Instead, automation pipelines interact with identity platforms and orchestrate network edges in real time. DevNet Associate introduces DevSecOps principles, giving newcomers a framework to encode security requirements into deployment scripts, monitor compliance, and remediate drift autonomously.
None of this diminishes CCNA’s significance. Physical topology, routing protocols, and basic IP services remain the roots of any enterprise network. But focusing solely on those roots while ignoring the branches of automation and programmability risks career stagnation. Engineers who can stride across both domains—patch panel to API endpoint—will shape the next decade of network evolution.
Inside the Blueprints: How DevNet and CCNA Test Distinct Mindsets
Comparing the exam blueprints of CCNA and DevNet Associate reveals divergent priorities reflecting two phases of the same lifecycle. CCNA’s objectives revolve around network fundamentals: OSI layers, IPv6 addressing, spanning‑tree loop avoidance, and basic security controls. A candidate studies interface status messages, translates binary masks into wildcard bits, and resolves routing black holes. Success hinges on recall and manual troubleshooting logic.
DevNet Associate shifts the spotlight to abstraction. Candidates navigate device APIs instead of console prompts. They explore data serialization formats—JSON, XML, YAML—and query identity platforms over OAuth flows. A question might present a code snippet calling the Cisco Meraki Dashboard API and ask which parameter retrieves client usage statistics. The correct answer requires not just platform familiarity but also an instinct for REST verbs, query strings, and authentication tokens.
While both certifications test deep understanding of Cisco’s technologies, their fundamental philosophies diverge. CCNA focuses on configuring individual devices and resolving network faults using a command-line interface. DevNet Associate, in contrast, teaches candidates to programmatically interact with platforms, automate repetitive tasks, and integrate networks with applications. These distinctions mirror the evolution of network operations from manual oversight to scalable, automated frameworks.
CCNA teaches how to build a network. DevNet teaches how to scale and manage it using modern automation principles.
For example, in a CCNA lab environment, a candidate might manually configure OSPF, verify neighbor relationships, and troubleshoot route advertisements by inspecting interface states. In a DevNet lab, that same candidate could write a Python script using the Cisco DNA Center API to pull topology data, generate a network map, or trigger configuration changes across dozens of devices simultaneously. It’s not that one is more difficult than the other—they simply test different cognitive toolkits. CCNA demands structured memorization and situational reasoning. DevNet tests abstract thinking, code comprehension, and logical automation flows.
Another key difference lies in how each blueprint prepares candidates for collaborative roles in IT. The CCNA path equips someone to contribute as a hands-on network technician or junior engineer. These professionals are often deployed to manage cables, check connectivity, and respond to performance issues flagged by users. Their success is determined by how well they follow diagnostic steps and interpret system logs. The DevNet Associate, on the other hand, prepares individuals for roles where infrastructure becomes part of software pipelines. These professionals contribute to continuous integration workflows, provisioning labs, orchestrating service rollouts, or managing network configurations via version control systems.
These distinctions also influence the mindset each certification fosters. A CCNA candidate might grow comfortable working within the bounds of a known network topology—reacting to faults as they emerge and performing updates on a scheduled basis. A DevNet-certified professional learns to anticipate change and build mechanisms to detect, deploy, or remediate with minimal human intervention. This shift from reactive to proactive network management is increasingly essential as enterprise infrastructures expand across cloud platforms, edge locations, and global user bases.
It’s also important to consider the tools each exam encourages candidates to master. For CCNA, the command-line interface remains central. Mastery of Cisco IOS commands, syntax, and hierarchical configuration is expected. In contrast, DevNet emphasizes scripting environments, libraries, and automation platforms. Candidates spend time inside code editors, pushing requests through Postman or Python scripts, parsing API responses, and debugging infrastructure-as-code templates.
In terms of career outlook, both certifications are highly respected and serve as critical stepping stones—but they tend to attract different audiences. CCNA appeals to those who enjoy hands-on problem-solving and infrastructure design. It’s a natural choice for technicians, junior engineers, or system administrators seeking to build solid networking skills. DevNet Associate draws professionals from both operations and development backgrounds. It’s ideal for those pursuing roles in automation, software-defined networking, network engineering with a programming edge, or DevOps teams seeking infrastructure fluency.
An overlooked but vital difference lies in how the exams themselves are structured. CCNA’s test format relies heavily on scenario-based multiple-choice questions and drag-and-drop simulations of configuration steps. DevNet incorporates more code interpretation, JSON parsing, and logical deduction based on API interactions. Both require lab practice, but the form of that practice differs. CCNA labs typically revolve around router and switch setup in emulated environments. DevNet labs often leverage sandboxes that emulate Cisco platforms with live API endpoints.
Ultimately, CCNA and DevNet Associate represent complementary approaches. They are not competitors but collaborators in preparing the modern network professional. Understanding VLANs, subnets, and routing tables is just as important as being able to trigger those configurations automatically across hundreds of devices. The successful engineer of today, and especially tomorrow, is likely to need both. Whether you begin with CCNA and build toward automation or start with DevNet and later dive deeper into traditional network theory, the two certifications enrich one another.
As networks become more programmable, the boundary between infrastructure and software is fading. CCNA teaches you to understand the structure. DevNet teaches you to manipulate it at scale. Together, they create a professional who can both architect reliable systems and ensure they adapt in real time to ever-shifting operational demands.
One blueprint angle sometimes overlooked is test tooling. CCNA occasionally presents simulated CLI tasks, but DevNet challenges can embed live coding contexts. Candidates might fill in missing Python statements that parse an API payload, iterate through interface dictionaries, and post a compliance report to a collaboration room. This practicality emulates real automation workflows, where an engineer writes utility scripts on the fly.
Understanding version control is also a DevNet hallmark. Where CCNA sees configuration backups, DevNet sees Git repositories. Exam scenarios test how branches isolate feature development, how pull requests enforce code reviews, and how tags mark release snapshots. A candidate who codes an automation pipeline without committing to version control risks introducing untraceable errors in production. Cisco’s inclusion of these topics signals the end of siloed ticket‑based change management.
Furthermore, DevNet integrates secure coding considerations. Questions probe the difference between parameterized and concatenated API calls, highlighting cross‑site scripting or injection risks in automation scripts. This cross‑pollination between security and development arises because an automated misconfiguration can propagate across thousands of interfaces in seconds. Safeguards—input validation, error handling, least‑privilege tokens—must become reflexive.
Yet there is still synergy. DevNet expects fundamental network fluency; building code to adjust BGP policies requires understanding path selection and route propagation. The exam underscores this by embedding network concepts inside code challenges. For instance, a task might require updating OSPF cost metrics through NETCONF. Only a candidate who grasps OSPF’s role in path metrics can reason whether to increase or decrease the value.
At a higher level, the two certifications cultivate complementary problem‑solving lenses. CCNA instills deterministic troubleshooting: “Issue show command X, compare to baseline Y, decide remediation Z.” DevNet encourages algorithmic thinking: “Loop through interfaces, detect anomaly threshold, trigger event.” Blending deterministic and algorithmic mindsets prepares professionals for hybrid operations where scale demands code yet anomalies still call for situational reasoning.
Career Pathways: From Command‑Line Expertise to Code‑Driven Leadership
When evaluating how CCNA and DevNet trajectories unfold in the workplace, consider three converging trends: infrastructure as code, edge computing, and intent‑based networking. Each trend shifts job descriptions beyond traditional network administration.
Infrastructure as code reimagines switch configurations as versioned artifacts that software teams test, review, and deploy automatically. A CCNA‑certified engineer understands what the configuration does; a DevNet‑certified engineer builds pipelines to assure it always does what it should. In many organizations, roles titled Network Automation Engineer or Site Reliability Specialist prioritize DevNet skill sets. They still value CCNA roots for troubleshooting physical anomalies, but day‑to‑day responsibilities center on writing code that orchestrates topology, compliance, and telemetry.
Edge computing further amplifies the role of programmable infrastructure. As enterprises push applications closer to where data is generated—think factory floors, hospital rooms, or autonomous vehicle hubs—networks must adapt instantly to unpredictable demands. A traditional CCNA approach might configure each edge switch manually or rely on static templates. In contrast, DevNet frameworks enable dynamic provisioning based on telemetry inputs, application priorities, or API calls from workload orchestrators. This responsiveness demands automation fluency, system integration, and data modeling—all core tenets of DevNet training.
Intent-based networking marks yet another paradigm shift. Instead of configuring devices directly, engineers define business outcomes—such as high availability for video conferencing—and rely on centralized controllers to enforce policies across distributed environments. This model relies on abstracted control, continuous validation, and adaptive feedback loops. A CCNA-certified professional might troubleshoot a VLAN mismatch or interface error in this scenario, but a DevNet-certified practitioner might author the policy logic, create REST API scripts to query compliance states, or design telemetry flows that trigger remediation scripts when service intent deviates from reality.
What emerges is a bifurcation in networking roles—though not in opposition. The CCNA graduate often becomes the trusted operational backbone, maintaining site reliability, verifying physical topology, and jumping in when automation fails or when hardware replacement becomes necessary. Meanwhile, the DevNet practitioner operates more upstream in the pipeline—building integrations, enforcing consistency through code, and reducing manual interventions that create risk. These dual roles form a feedback loop. DevNet workflows depend on foundational CCNA knowledge, and CCNA operations increasingly benefit from DevNet-based tooling.
In hybrid cloud and multi-cloud environments, the separation between infrastructure and application is vanishing. Workloads migrate freely between on-premises data centers and cloud platforms. Here, DevNet skills provide a significant advantage. Engineers must orchestrate network paths dynamically, secure access based on identity and context, and apply policies at both infrastructure and application layers. All of this requires fluency in APIs, orchestration engines, and platform automation. CCNA knowledge remains foundational, but not sufficient in isolation for such adaptive environments.
Organizationally, teams are shifting to multidisciplinary models. A network engineer might sit next to developers, security analysts, and data scientists. Conversations often revolve around shared concerns: application performance, deployment speed, compliance assurance. In such settings, DevNet-certified professionals excel because they bridge the gap between infrastructure and software. They can code, but they also understand protocols. They can build APIs, but they also interpret routing metrics. This versatility is especially valuable in DevOps and NetDevOps teams, where cross-functional collaboration drives velocity and stability.
From a career growth perspective, these trends reshape advancement paths. A CCNA-certified technician might ascend into network design, security, or operations leadership. A DevNet-certified professional could pivot into automation architecture, cloud engineering, or platform engineering roles. The skill sets overlap but diverge in emphasis—manual configuration mastery versus programmable infrastructure fluency. Increasingly, high-impact roles blend both domains. For example, a network reliability engineer may need to troubleshoot BGP convergence while also maintaining the Ansible playbooks that enforce BGP peering rules.
In terms of professional identity, CCNA speaks to the reliability and resilience of networking’s physical and logical foundation. DevNet represents adaptability and scalability in a software-defined future. Together, they empower professionals not just to build and maintain networks, but to shape how those networks evolve. The industry no longer seeks purely reactive administrators—it demands proactive architects who understand both the wire and the code.
In summary, infrastructure as code, edge computing, and intent-based networking have changed what it means to be a network professional. CCNA and DevNet reflect two halves of a new whole: the deep domain expertise of traditional networking and the agility of software-driven operations. Mastery of both isn’t just career insurance—it’s career acceleration in a digital world that rewards adaptability, automation, and architectural thinking.
Edge computing brings compute workloads close to IoT devices, distributing micro‑data centers across campuses and remote branches. Managing thousands of edge nodes manually is impossible. DevNet‑skilled practitioners script zero‑touch provisioning, remote firmware updates, and real‑time policy pushes. Meanwhile, CCNA‑grounded technicians ensure the underlying uplinks remain solid, troubleshoot link‑flaps, and maintain power redundancy. Together they deliver resilient edge fabric.
Intent‑based networking defines desired business outcomes—like application SLAs or segment isolation—and lets controllers compute the necessary device configurations. CCNA equips engineers to verify that computed configs make sense; DevNet equips them to integrate custom intents, extend controllers via APIs, and feed external data sources (think threat feeds or IoT sensor status) into policy computations. This synergy elevates network engineering into a domain of data models and policy logic.
From a hiring standpoint, CCNA remains a baseline filter for help‑desk escalations, NOC monitoring, and campus deployments. DevNet opens doors to DevOps‑aligned teams, automation centers of excellence, and cloud networking squads. Compensation benchmarks reflect the shift: roles demanding coding aptitude often trend higher due to cross‑disciplinary scarcity.
Entrepreneurial paths also blossom. Independent consultants who script network assessments, integrate CI/CD pipelines for ACL updates, or build custom dashboards command premium fees. DevNet skills underpin such services, blending API integration with network domain insight. Yet those consultants still lean on CCNA knowledge when diagnosing underlying packet anomalies that automation reveals.
In the long run, professionals fluent in both certifications can progress into Architect positions—crafting roadmaps where programmable underlays, secure overlays, multi‑cloud fabrics, and observability pipelines converge. They speak the language of business intent to executives while also diving into JSON schemas when debugging. That bilingual expertise defines leadership in next‑generation networking.
Crafting a Dual‑Track Study Strategy for Sustainable Master
Choosing between CCNA and DevNet isn’t always binary; many aspirants pursue both in sequence or tandem. Executing that strategy demands disciplined planning to avoid burnout and maximize retention.
Begin with a structured “foundations first” sprint. Even if your end goal favors automation, understanding IP addressing, subnetting, and routing logic anchors every DevNet script. Allocate four to six weeks to master CCNA’s core: layer‑2 operations, spanning tree nuances, routing protocol basics. Use packet captures to visualize ARP exchanges, OSPF hellos, and DHCP handshakes—mental imagery that will later inform API‑query interpretation.
This foundational phase is essential not only for technical grounding but also for building confidence. Networking logic, unlike abstract software design, often follows physical principles. Seeing a MAC address propagate through a switch’s table or observing NAT translations in real time offers concrete reference points. This clarity will help when those same behaviors are abstracted behind RESTful API calls or cloud-native overlays.
After grasping the basics, shift into structured DevNet exposure. Resist the temptation to jump directly into code-heavy topics. Instead, begin with interface translation—how traditional CLI tasks map into software interactions. Explore Cisco sandbox environments where you can query device APIs for interface status, routing tables, and configuration snippets. This phase isn’t about memorizing syntax but developing fluency in how network state gets serialized into JSON, parsed in Python, and manipulated through HTTP methods.
To reinforce the material, build small lab projects. For instance, create a script that detects and logs down interfaces or automates VLAN provisioning. These bite-sized exercises cement relationships between command-line muscle memory and programmable intent. Each success compounds your understanding: you’re no longer just reading routing tables, you’re scripting them into version-controlled configurations.
Balance is key. Schedule weekly alternation between CCNA and DevNet topics. For example, Monday to Wednesday might involve troubleshooting OSPF adjacency issues in a virtual topology, while Thursday and Friday pivot to Python scripting that queries device APIs. This cyclical pattern prevents stagnation and ensures dual competency grows in sync.
As both tracks mature, convergence occurs. Consider DevNet’s emphasis on version control, CI/CD, and automated testing. A CCNA mindset still applies: what does “test” mean in a network context? Perhaps verifying that a change preserves routing reachability or doesn’t break access control policies. Your troubleshooting instincts from CCNA will shape how you build validation logic in your DevNet projects.
Eventually, test preparation becomes necessary. For CCNA, that means drilling subnetting calculations, interpreting configuration output, and resolving troubleshooting scenarios. For DevNet, it involves parsing code blocks, interpreting API documentation, and understanding OAuth workflows. Use practice exams to identify weak spots but avoid rote memorization. Each wrong answer is an opportunity to deepen conceptual clarity.
Don’t neglect rest cycles. Blending two certification journeys can easily lead to overload. Integrate “reflection days” every few weeks—review what you’ve learned, revisit difficult concepts, and restructure your plan based on emerging interests. Maybe automation intrigues you more than expected, or perhaps you’re drawn back to core networking due to its logical elegance. Adjust accordingly.
Supplement your study with documentation immersion. Read API guides as if they were protocol RFCs. Dissect network topologies as architectural blueprints. Think beyond exam objectives and explore how CCNA and DevNet knowledge intersects with cloud networking, SD-WAN, or security automation. This interdisciplinary awareness prepares you for real-world integration—not just isolated certification tasks.
Finally, approach this dual-certification path as more than a resume-builder. View it as an invitation to redefine what a network engineer can be. With CCNA, you earn the right to configure networks. With DevNet, you gain the power to design, scale, and adapt them through code. The future favors those who can combine these skill sets into a seamless, agile approach to infrastructure—engineers who configure with context and automate with awareness.
Next, transition into a “code discovery” phase. Install a lightweight Python distribution, explore Cisco’s DevNet sandbox, and write simple GET requests against device REST endpoints. Resist the urge to copy‑paste production‑grade scripts. Instead, focus on reading JSON payloads, looping through dictionary objects, and printing interface descriptions. Gradually add authentication layers—basic auth to token‑based flows—so each building block feels intuitive.
Integrate a “lab synergy” cadence: for every routing change you practice via CLI, replicate it with an API call. Configure an interface description manually; then automate the same change across five virtual routers. This side‑by‑side reinforcement cements the intellectual bridge between CCNA command sets and DevNet code logic.
Reflection rounds out retention. Maintain a digital lab journal capturing commands, code snippets, errors, and aha‑moments. Write weekly retrospectives on what concepts clicked and which remain fuzzy. This metacognitive loop uncovers hidden gaps and tracks progress, providing motivational momentum.
As exam day approaches, pivot into timed scenario drills. Simulate troubleshooting labs where a routing loop appears; resolve first via show commands, then write a script to detect such loops automatically. Alternate between CCNA‑style multiple‑choice banks and DevNet coding puzzles to exercise context switching—mirroring real‑world interruptions where an engineer toggles between console and IDE.
Finally, embrace community. Engage in forums, share lab diagrams, trade code snippets, and critique each other’s pipelines. Teaching peers forces clarity, while absorbing diverse perspectives reveals alternate solutions. Networking—both social and packet‑based—accelerates mastery.
By orchestrating foundation, code discovery, lab synergy, reflection, and timed drills, aspirants forge a dual‑track competence that resonates with future‑minded employers. Whether you deploy that competence as a script‑savvy engineer, an automation architect, or a cross‑disciplinary consultant, the journey begun with CCNA and elevated by DevNet positions you at the forefront of programmable networking’s unfolding story.
Final Words:
In today’s rapidly evolving IT landscape, the decision to pursue either the Cisco Certified Network Associate or the DevNet Associate certification should not be taken lightly. Each credential represents a unique approach to infrastructure: one grounded in traditional networking principles and the other shaped by automation, programmability, and software-defined strategies. Yet, as the boundaries between network engineering and software development continue to blur, a growing number of professionals are recognizing the value of mastering both.
The CCNA equips you with critical foundational skills—switching logic, routing decisions, IP fundamentals—that remain essential regardless of how abstracted or automated the network becomes. These skills ensure you understand what is happening behind the scenes when systems fail or behave unexpectedly. On the other hand, DevNet empowers you to automate, scale, and manage modern infrastructure with speed and precision. It provides the tools to build solutions that adapt to change without requiring manual configuration at every turn.
By choosing to study both certifications in tandem or sequence, you future-proof your career. You become not just a network specialist or a developer, but a hybrid engineer—one capable of bridging operational silos and contributing to the full lifecycle of infrastructure. That combination is rare, increasingly sought after, and deeply valuable to organizations transitioning to cloud-native, intent-based, and programmable environments.
Whichever path you begin with, stay committed to continuous learning. The world of networking is not static, and your ability to adapt, upskill, and stay curious will define your relevance more than any single exam. Whether you’re configuring VLANs by hand or orchestrating entire topologies with APIs, the most impactful professionals are those who pair technical mastery with adaptability and vision. That is the true power of integrating CCNA and DevNet in your career journey.