What I did:
I feel so exhausted. I don't feel like I'm making a progress; I just deal with an endless series of errors and problems. It feels like additional responsibility without any enjoyment. Sometimes, I think it would be easier to stick to just what I do at work. Why do I always need to learn something new and improve my skills? I haven't answered on this question yet. Sorry for this kind of progress report, which sounds more like self-reflection.
Over the last two days, I tried to extract the logic for theme switching into a separate KMM library. I used the KMM Library Wizard for this, but instead of publishing directly to Maven, I tried to publish to Jitpack. It doesn't work properly, and the article with a detailed explanation of publishing is quite outdated because repository was updated in the past years, but the article wasn't. So, I want to solve it, but I realize I have a lack in my knowledge. Here's my favorite expression: it is a good point for growth.
What I will do:
- Update README file with description of project.
- Fix comment element
- Implementation of WebView to display stub content
- Theme configuration for Lottie animation
- Create public collection of API calls in Postman
If you want to join the project, just leave a comment here, or write a message in LinkedIn.
What help I'm looking for:
Designer (create design of application in Figma)
Android/KMM developer
Any other help related to the project.
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
You can find more useful content on my LinkedIn page, on X, in Medium or Mastodon.
See you tomorrow.
Top comments (0)