Tome.gg Library
Tome.gg
  • Tome.gg Library
  • Onboarding
    • Self-directed learning
      • Junior Software Engineer
      • Mid- to Senior-level Software Engineer
    • Accelerated learning
      • Junior Software Engineer
      • Mid- to Senior-level Software Engineer
  • Fundamentals
    • Reading, Writing, Discourse
  • Contexts
    • Overview
    • Problems
      • How do I manage a change in levels of formality on my apprenticeship?
      • Monolith vs. Microservice
      • Office Bullies
      • On Developing Motivation
      • Building Confidence
      • All Work and No Play
      • Handling disappointment and frustration
    • Scenarios
      • Offering Guidance Without Context
      • Code Review Disagreements
      • Misunderstandings and Unreliable Communications
      • Unrealistic Deadlines
      • Conflicting Coding Practices
      • Receiving Feedback on Performance Reviews
      • Bias in Task Distribution
      • Disagreements Over Tech Stack Choices
      • Dispute Over Feature Priority
      • Exclusion from Important Meetings
      • Lack of Recognition for Work
      • Dealing with Unconstructive Criticism
      • Resolving Conflict Over Deadline Disputes
      • Overcoming Conflict over Technical Debt
      • Addressing Discrimination or Harassment
      • Documentation Disputes
      • Managing Remote Work Discrepancies
      • Navigating Design Disagreements
      • Handling Security Concerns
      • Addressing Culture Fit Problems
      • Resolving Intellectual Property Disputes
  • Resources
    • Roadmap
  • EXTRAS
    • Frequently Asked Questions
      • Is Tome.gg coaching and mentoring for me?
      • Tome.gg Overview
    • Roadmap
    • Contributing Guidelines
    • Privacy Policy
Powered by GitBook
On this page

Was this helpful?

  1. Onboarding
  2. Accelerated learning

Junior Software Engineer

PreviousAccelerated learningNextMid- to Senior-level Software Engineer

Last updated 1 year ago

Was this helpful?

At this point, it is assumed that you have followed the fundamentals of Reading, Writing, Discourse.

To accelerate yourself as a junior software engineer, you should pour in time to practice the following:

  • Typing speed - You don't need to practice with a typing game. You already do coding and programming for a living- just focus on building and programming faster and faster.

  • Keyboard shortcuts - At some point, your improvement in your typing speed will slowly plateau, in which case you should now begin to think carefully about how you interface with your computer. What are common actions that you frequently do? (e.g. using the or ).

  • Learning quickly and sharing your notes - This is a two-pronged challenge. Not only do you have to learn very rapidly, you need to consume content and critically analyze topics as well as synthesize ideas into simpler concepts when you explain it to your colleagues, both technical and non-technical. This is the sandbox of polishing your communication skills.

  • Read documentation voraciously and try it for yourself - As a software engineer, you need to develop the confidence and discipline of always referring to the available documentation to verify how a tool, package, or system works and verifying usual cases and edge-cases to check whether it behaves as you expect. This is what it means to "speak the computer's language" and to be fluent in it.

    • Documentation is often outdated and broken. Learning how a machine behaves (and practicing the skill of theorizing why a system works or not is what senior-level software engineers do).

  • Participate in hackathons or create one - These can be public events, or you can just run a hackathon for yourself on your own. The important thing is to relentlessly pursue the solving of a certain problem. This is the sandbox for your discipline and focus. Can you push yourself hard to deliver results when you need to? In that sense, it is also a sandbox for confidence and emotional resilience.

Command Palette on VS Code
navigating your inbox in Gmail