Blog
  • devcrisis
  • ๐Ÿ”ฎSoftware atoms
    • Validating code Architecture with dependency cruiser
    • Actionable ways to use ChatGPT
    • Most courses aren't worth it
    • SQLite isโค๏ธ
    • Stabilizing Tests without fixing them
    • Interviews should copy Advent of Code
    • Rust is nice
    • Agile fatigue is rising
    • Documentation is needed after all
    • The Direction of the JS ecosystem is good
    • Zero configuration == <3
    • Make small pull requests
    • Good practices fade out
    • Rushing !== unmaintainable
    • Commit message readability
    • Universal Practices
    • More functions == good
    • Mocking Private Functionality
    • Lines of code != feature count
    • Different Software - Different Quality
    • junior2mid
    • Book alternatives
    • Courses
    • Type Driven Development
    • Latest and Greatest
    • Real Developers
    • 10x Developer
    • Books for beginners 1
    • Parkinson's Law
    • nest-cli architecture is nice
    • Incremental Feature Delivery
    • Self Healing Software
      • Typed Configuration
  • ๐Ÿ’กMemos
    • 2022 Holiday code report
    • Complexity
    • Software Development Fundamentals
  • ๐Ÿงฑfoundation
    • Junior2Mid
    • Books and resources for new developers
    • ๐Ÿ”๏ธNow
Powered by GitBook
On this page
  1. Software atoms

Book alternatives

๐Ÿ›‘ You don't need books to learn new technologies!

When I was starting out in ~2011 books were a huge part of how new technologies were learned.

๐Ÿ“š They contained useful tips, down to earth explanations and many, many examples.

These books had their fair share of problems - old versions of the language/framework, outdated coding practices, etc.

Nowadays I am very happy that developers no longer need to rely on books.

๐Ÿ“˜ If you are a complete beginner, you can find hours long free tutorials on YouTube that can get you started with a technology. The community is thriving and you will always find something up to date.

๐Ÿ“— After the basics are done you can mostly rely on the official documentation. Look for beginner sections and example projects. Documentation has really improved over the last years.

โค๏ธ By using the official docs you are not only removing issues with outdated versions and practices, but you are also learning to navigate docs faster which is an invaluable skill on its own.

As with anything technical - don't forget to practice, practice, practice - experiment with everything you read.

๐Ÿ’ก Don't get me wrong - you should still read a lot of books. Books about principles like Clean Code and The Pragmatic Programmer. Books about architectures, different styles of programming. And ofcourse, the few in-depth technological books that really dive deep like Rust for Rustaceans.

Previousjunior2midNextCourses

Last updated 2 years ago

๐Ÿ”ฎ