I stopped my challenge several days ago. Why did I do this? Firstly, It didn't satisfy me; it felt like an obligation. The topic motivated me at the start, but it slowed down every day, and the number of problems increased. Problems are opportunities for growth, but these were so specific that I didn't learn anything new; I was just solving repetitive corner cases. I want to complete the mobile application for Dev.to, but the API seems incomplete and unreliable. Authorization is poorly implemented and available only on the web. I am disappointed with the quality of the resource.
What were the positives? I broke my previous record for streak of consecutive commits. I gained good practice in writing daily reports and improved my writing skills. I learned more about KMM development.
What did I want to achieve more of? I want more collaboration with other developers to build something together. I couldn't generate interest in my project and challenge. I stopped because I couldn't see a reason to continue just for the sake of completion.
My timeline:
Day 1. Deep breath and dive.
Day 2. Networking layer.
Day 3. Loading of articles.
Day 4. ArticleItem.
Day 5. Localization.
Day 6. Work on Sunday.
Day 7. First week.
Day 8. Enjoying coding.
Day 9. Expect/actual.
Day 10. TODOs.
Day 11. Friday evening.
Day 12. Frustration.
Day 13. Blocker
Day 14. Monday
Day 15. Reactions
Day 16. Feed
Day 17. stringWithFormat
Day 18. Comment
Day 19. 1 percent
Day 20. A bit of progress
Day 21. Pagination
Day 22. Lottie animation
Day 23. Sorting of articles
Day 24. Step by step
Day 25. Broken endpoint?
Day 26. After party
Day 27. Burnout
Day 28. Opportunity for growth
Day 29. Hard work
Day 30. Old code
Day 31. Technical debt
Day 32. API calls
Day 33. Generic response
Day 34. Response
Day 35. Coderabbit
Day 36. What is the power of Pull Request?
Day 37. Search challenge
Day 38. Search items
Day 39. A party
Day 40. Fixing UI
Day 41. Surpassed record
Day 42. Monday
Day 43. Composition
Day 44. Timestamp
Day 45. Time manipulation
Day 46. Broken pipelines
Days 47-48. Broken API
Day 49. Organization card
Day 50. GitHub Universe
Day 51. Article Screen
Day 52. Collapsing Toolbar
Day 53. Plan
Day 54. Voyager issue
Day 55. Copilot
Day 56. Collapsing logic
Day 57. Replies
Day 58. Comments screen
Day 59. Comments
Day 60. Markdown
Days 61-65. Dark theme
Day 66. Theme switcher
Day 67. Follow as in the System
Day 68-70. Theme switcher
Day 71-72. Lack of knowledge
Day 73. Working on the Library
You can find more useful content on my LinkedIn page, on X, in Medium or Mastodon.
Top comments (0)