Escape from Tutorial Hell

on YouTube ↗26m

" summary

Concrete checklist: pick platforms, frameworks and APIs then break the project into chunks (server, database, users/products/orders) and further into folders and one-task files such as an orders/payments/<payment_method>.py; use git, linters, a notes file and a snippets manager; prefer long descriptive names and functions shorter than a screen (300 lines is the Swift limit mentioned); use AI like GitHub Copilot and Cursor to iterate (CSS for trolls.net took ~3 hours of prompts) but follow the rule only ask AI to write code you could write yourself.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 1:03Non-Python speaker at Python conf
3. 2:55Tutorial hell problem
4. 3:58Project design before coding
5. 6:46Project structure for maintainability
6. 11:58Git for source control
7. 12:23Reading docs effectively
8. 14:52Saving code snippets
9. 15:37AI to escape tutorial hell
10. 21:38Summary
11. 22:43Q&A

" related talks

• 01h 03mHow To Do Kick-Ass Software DevelopmentSven Peters · JavaDay 2013
• 27mThe Journey Over the Intermediate GapSara Packman · PyCon 2018
• 30mMaintaining Sanity and CodeBogo Giertler · iOS Conference SG 2015
• 19mJourney into the Deep World of Web DevelopmentAndrew Kim · PyConline AU 2020
• 29mLeveling Up from Planning to ProductionThomas Countz · RailsConf 2022
• 48mEnding Keynote: 7 Principles of Productive Software DevelopersSebastian Daschner · Voxxed Days Cluj-Napoca 2019
• 15mLearning Tips Every Developer Should KnowCeora Ford · DevOpsDays Portland, OR 2021
• 01h 00mBuilding better developersRowan Merewood · SunshinePHP 2014