Understanding the Basics: What to Focus on When Starting Out

TechCrushHQ avatar
TechCrush.pro
@TechCrushHQSep 29, 2026

The Spaces brought together practitioners to guide beginners on how to start and stay on course in tech. The host framed the session around avoiding shiny-object syndrome, trusting the process, and prioritizing implementation over perpetual learning. Polenity (software developer) shared a transition from history to software, emphasizing sticking to a stack (JavaScript), building and shipping projects, and leveraging LinkedIn visibility. Dixon (ethical hacking/Linux background) underscored OS, networking, and scripting fundamentals before tools, and warned against chasing every new tool or rushing to be job-ready. Tega Virji (SOC analyst) stressed roadmaps, community, LinkedIn/X presence, accountability partners, and patience about timelines. Patrick (product management/recruitment) advocated building products tied to business value, mastering logic and system design, and understanding market expectations, including the value of strong quantitative foundations. Practical do’s and don’ts included: pick a niche, focus on fundamentals, build consistently, share progress publicly, use AI as an assistant, and avoid comparing timelines. The discussion concluded with learning habits—breaking goals into modules, daily practice, and progress tracking—so beginners can navigate varied paths while sharing core principles.

Onboarding Webinar: Starting in Tech — Fundamentals, Focus, and Real‑World Advice

Session context and objectives

  • Format: Roundtable Twitter Space/webinar for newcomers to tech (follow‑on to a prior onboarding session on mindset/structure).
  • Aim: Demystify how to start in tech; highlight do’s/don’ts; what to focus on first; how to build fundamentals; how to learn effectively; and how to turn learning into opportunities.
  • Core message from the Host: Trust the process; journeys differ and take time; implementation separates passive learners from people who progress; avoid shiny‑object syndrome; cut out noise; pick a path and stick with it while solving real problems.

Participants

  • Host/Moderator (name not stated): Facilitated the discussion and framed the themes (mindset, focus, do’s/don’ts, real‑life scenarios).
  • Olamide (Software Developer; studied History; full‑stack; IT personnel/manager experience): Transitioned into software via HTML/CSS/JS; heavy project building; freelance‑focused.
  • Michael (“Dixon”) (Founder, State Academy; Ethical Hacking/Cybersecurity; Linux background): Computer Science background; moved from web/mobile dev into Linux, then ethical hacking; strong emphasis on fundamentals.
  • Tega Virji (Cybersecurity Analyst; SOC experience across industries): Electrical Information Engineering background; CyberGirls alum; strong on OS/networking fundamentals; active mentor/tutor.
  • Patrick (Product Manager, Drive Technology; Technical Recruiter in blockchain): Engineering and business blend; product thinking; building and selling; international recruiting perspective.

Mindset and orientation: what matters at the start

  • Trust the process and your own pace: People progress at different speeds; mastery comes with time, practice, and mistakes.
  • Implementation over passive consumption: Build things as you learn; reflect, adjust, and keep shipping.
  • Avoid shiny‑object syndrome: Don’t jump between tracks/tools based on hype; choose a path and focus.
  • Problem‑solving posture: Tech is about solving real problems; lean into challenges rather than avoiding them.

How they got started: paths, challenges, turning points

Olamide (Software Developer)

  • Timeline: Interest in late 2019; first HTML “Hello, world” in Jan 2020; intense 9‑month COVID era learning via Microverse (daily stand‑ups, sprints, rigorous projects).
  • Projects and tools: Replicated existing projects/designs to master tools (VS Code, GitHub, Figma). Built continuously and uploaded to GitHub.
  • Early freelancing: First significant gig arrived in 2022 via LinkedIn; client amplified his work publicly, driving inbound requests. Initially handled diverse domains (web3, health, education), which created client/product fit friction.
  • Key challenge: Lack of niche created inconsistency and conflicting expectations across industries. Solution: Specialize—picked a JavaScript‑centric stack (JS/React/Next.js/Node). Learns other tech (e.g., Flutter, Swift) only when product needs demand, keeping JS as the core.
  • Work style: Favours freelance over 9–5; also stepped into IT personnel roles, learned on the job, and broadened practical problem‑solving capability.
  • Growth methods: Consistent tutorial strategy (1–2 reliable sources, not scattered videos), public progress on LinkedIn, tackling real client problems (even small/low‑pay initially) to build experience and credibility.

Michael (“Dixon”) (Ethical Hacking/Cybersecurity)

  • Timeline: Started 2014 in Computer Science; did web and Flutter; internship at Linux Nigeria (UI, Ibadan) pivoted him to Linux and ethical hacking.
  • Course correction: Initially chased tools (influenced by media) without fundamentals; realized limitations and restarted from the ground up.
  • Fundamentals built: Computer hardware/OS concepts; Windows and Linux fundamentals (commands, users/permissions, services, package management, SSH, shell scripting, filesystems); networking (OSI, TCP/IP, ports/protocols, DNS, IP/subnetting, routing, firewalls, NAT); web apps and HTTP; databases/SQL; programming/scripting (Bash, Python, C++).
  • Practice stance: Use Kali in a VM, not replacing the host OS; learn reconnaissance/enumeration; be fluent with standard tools (Nmap, Wireshark, Burp Suite, Gobuster, Nikto); learn to build tools where useful.
  • Real‑world impact: Traced an account abuse case; performed external assessments for clients and delivered scans, reports, and remediation.
  • Guidance: Don’t try to learn everything; avoid tool‑chasing (e.g., fixation on “Pegasus”); don’t compare yourself to veterans; prioritise skills over certificates; expect a multi‑year runway.

Tega Virji (Cybersecurity)

  • Background: Electrical Information Engineering; exposure to programming and a university cybersecurity course (sparked interest).
  • Early dabbling: Tried web dev (stopped at CSS) and data analysis (Excel/Power BI) without depth; recognized lack of focus.
  • Break‑in: CyberGirls Fellowship—built strong foundations in OS (Windows/Linux) and networking; pursued CCNA; embraced a long‑term view (set realistic timelines rather than expecting a job in 3 months).
  • Community & visibility: Uses LinkedIn and X to connect locally (Nigeria) and globally; values a healthy, curated feed; advocates public learning (e.g., “100 days of cybersecurity”).
  • Advice: Pick a field and adopt a roadmap with accountability; don’t skip fundamentals; don’t pressure yourself—contexts differ (CS grads vs non‑tech backgrounds). Be consistent and share progress.

Patrick (Product Management/Recruiting)

  • Early years: Learned Java, .NET, open source, and design; shifted to the business side—building applications and selling them.
  • Discipline: Learn a technology → build an application → find users willing to pay. This pressure for real users fosters quality and problem‑solution fit.
  • Product/engineering blend: Strong on system logic; can assemble junior teams and guide execution through clear logic/design rather than just code syntax.
  • COVID‑era pivot: Became a technical recruiter for a blockchain company; assessed full‑stack, blockchain, and niche roles for US/EU markets; learned how international hiring weighs backgrounds.
  • Recruiting insight: Pick one area and build tangible outcomes; don’t make money the sole initial driver—offer value, even free or low‑paid, to build proof. Over time, rates grow with trust and capability.
  • Education alignment: Quantitative/tech academic foundations matter for some international roles. Illustrative story: physics grad at a top local university lacked cryptography depth; manager discounted due to absent academic research ecosystem. Takeaway—when possible, align education with your tech goals, especially for specialized international niches. Regardless, demonstrable, relevant skills and solid fundamentals remain crucial.

Cross‑track fundamentals: what beginners should actually learn first

  • Computing and OS basics: How computers work; RAM/storage distinction; processes/services; filesystems; permissions; command line usage (Windows CMD/PowerShell, Linux shell).
  • Networking: OSI/TCP‑IP models; ports/protocols; DNS; IP addressing and subnetting; routing; firewalls; NAT.
  • Web and data basics: HTTP/HTTPS; how websites/web apps work end‑to‑end; databases and SQL fundamentals.
  • Programming/scripting: Pick a language aligned with your track (e.g., JavaScript for web/app; Python/Bash for security/automation). Learn by building.
  • Tooling and environments: Use VMs for experimentation (e.g., Kali on VM); version control (Git/GitHub); editors/IDEs (VS Code); design tools (Figma) for interface work.
  • Problem‑solving and logic: The hardest part is solution logic; design systems that solve real problems—code is an implementation detail.

Track‑specific focus highlights

  • Software development (Olamide):

    • Choose a primary stack and stick with it (e.g., JavaScript: React/Next.js/Node). Avoid serially switching stacks by chasing job postings.
    • Use AI as an assistant, not a crutch—understand what you’re doing.
    • Build projects continuously; copy/replicate good projects to master tools and patterns.
    • Niche down to stabilize expectations and deepen expertise.

  • Cybersecurity (Dixon, Tega):

    • Master OS, networking, and security fundamentals before tools; practice on VMs.
    • Learn reconnaissance and standard toolchains (Nmap, Wireshark, Burp, Gobuster, Nikto), but don’t chase “magic” tools.
    • Pick up scripting (Bash/Python) to automate and build.
    • Keep a roadmap; get community/accountability; adopt a long‑term horizon.

  • Product/business (Patrick):

    • Build for real problems and find paying users; validate willingness to pay.
    • Translate business logic into engineering execution; clarity of logic trumps code syntax.
    • For international specialization (e.g., cryptography), aligned academic foundations can be an advantage; otherwise, demonstrate deep, relevant skills.

Do’s and Don’ts for beginners

  • Do

    • Pick a track, define a roadmap, and focus; be consistent (daily or near‑daily learning).
    • Implement as you learn: build real projects; practice over passive watching.
    • Share your journey publicly (LinkedIn/X), showcase progress, and engage communities.
    • Use accountability mechanisms (study partners, sprints, calendars/stand‑ups).
    • Learn fundamentals first (OS, networking, web basics, SQL, scripting) before advanced tools.
    • Start small with real users/clients—even low‑paid/free work builds proof and confidence.
    • Embrace tough problems and debugging; persistence compounds skill.

  • Don’t

    • Chase trends/tools/certificates without fundamentals.
    • Compare yourself to seasoned professionals; avoid unrealistic “job in 3 months” expectations.
    • Spread yourself thin across multiple tracks and stacks at once.
    • Treat AI or tools as replacements for understanding.
    • Ignore regional context—network locally and tailor your roadmap to your market while keeping global standards in view.

Learning habits that accelerate progress

  • Tega Virji

    • Break learning into modules with weekly targets; keep goals specific and trackable.
    • Use a study partner and fixed study windows; debrief briefly to reinforce learning and stay accountable.

  • Dixon (Michael)

    • Learn every day; build something rather than just watch tutorials.
    • Don’t fear difficult problems—step away, return, and debug systematically.

  • Olamide

    • Use structured calendars/stand‑ups (kept from academy experience) to plan and reflect.
    • Limit tutorial sources for coherence; post progress on LinkedIn to document growth and attract opportunities.
    • Seek real‑world challenges (small gigs, new responsibilities) to drive skill growth.

Tools, platforms, and resources mentioned

  • Core tools: VS Code, GitHub, Figma; VMs for Kali Linux.
  • Security toolchain: Nmap, Wireshark, Burp Suite, Gobuster, Nikto.
  • Social platforms: LinkedIn (optimize profile; post progress), X/Twitter (curate a healthy feed for your field).
  • Programs/communities: Microverse (structured online learning), CyberGirls Fellowship (foundational cybersecurity pathway), Linux Nigeria (Linux training environment).

Career and recruiting insights

  • Show, don’t tell: Portfolios, public progress, and shipped projects matter more than certificates alone.
  • Market exposure: COVID‑era opened global hiring; international roles often scrutinize educational alignment and depth in specialized domains. Where formal alignment isn’t present, demonstrable skill and real outcomes become even more critical.
  • Pricing and progression: Starting with small stipends or free value can lead to trust, better gigs, and higher rates over time.

Key takeaways and next steps

  • Start with fundamentals, pick a focus, and commit to steady implementation.
  • Build projects from day one; replicate to learn tools, then design your own solutions.
  • Publish your learning and outcomes; invest in community and accountability.
  • Use AI to accelerate, not substitute, understanding.
  • Expect a multi‑year journey; avoid shortcuts and comparison traps.
  • For specialized international paths, align education where possible—or backfill with deep, verifiable skill.

Closing note from the Host

  • Reinforced that journeys differ but share common patterns: focus, fundamentals, implementation, and persistence. More webinars will follow to deepen these themes and support learners across tracks.