This repository was archived by the owner on Aug 14, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 15
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #7 from Jan-Stepien/main
docs: one size doesnt fit all architecture talk
- Loading branch information
Showing
2 changed files
with
46 additions
and
56 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
{ | ||
"cSpell.words": [ | ||
"Stępień" | ||
] | ||
} |
97 changes: 41 additions & 56 deletions
97
...ne_size_doesnt_fit_all_tailoring_flutter_architectures_for_team_and_business_success.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,57 +1,42 @@ | ||
{ | ||
"speakers": [ | ||
{ | ||
"name": "Jan Stępień", | ||
"bio": "About", | ||
"companyName": "", | ||
"companyUrl": "", | ||
"githubUrlOrHandle": "", | ||
"xUrlOrHandle": "", | ||
"linkedinUrlOrHandle": "", | ||
"webUrl": "" | ||
} | ||
], | ||
"title": "One Size Doesn't Fit All: Tailoring Flutter Architectures for Team and Business Success", | ||
"description": "In the fast-paced world of startups, idealism often needs to adapt.\r\nJoining a small team, I faced the challenge of balancing long-term architecture with immediate business needs.\r\nWe embraced a pragmatic approach, prioritizing features while gradually refactoring when possible.\r\nThis meant shared responsibility for testing and maintaining code. While not ideal, it fostered flexibility and helped us create a \"good enough\" workflow for our unique environment.\r\nThis experience taught me the importance of tailoring development strategies to team strengths and project realities.\r\n\r\nI would like to share with you the takeaways for the project and key concepts that you should be aware of when scheduling long term, large scale refactor of the app.", | ||
"videoUrl": "", | ||
"resources": [ | ||
{ | ||
"label": "Slides/Blog/...", | ||
"url": "" | ||
} | ||
], | ||
"recommendations": [ | ||
{ | ||
"tool": "", | ||
"url": "", | ||
"comment": "" | ||
} | ||
], | ||
"level": "Introductory and overview/Intermediate/Advanced/Expert", | ||
"topics": [ | ||
"Accessibility", | ||
"Animations", | ||
"Application Architecture - Navigation", | ||
"Custom Painting - Render Objects - Rendering", | ||
"Dart 3 Language Features", | ||
"Dart on the server", | ||
"Enterprise - Tech Leadership", | ||
"Firebase & Flutter", | ||
"Flutter Multiplatform (Desktop, Web, Embedded, etc)", | ||
"Flutter Widgets & Layouts", | ||
"Game Development", | ||
"Networking (GraphQl, APIs, etc.)", | ||
"Package & Plugin Development", | ||
"Security", | ||
"State Management", | ||
"Testing", | ||
"Third Party Libraries" | ||
], | ||
"day": "Wednesday", | ||
"time": "2:35 PM", | ||
"startsAt": "2024-07-03T12:35:00.000Z", | ||
"endsAt": "2024-07-03T13:15:00.000Z", | ||
"room": "Flutter Forest", | ||
"format": "Session" | ||
} | ||
|
||
"speakers": [ | ||
{ | ||
"name": "Jan Stępień", | ||
"bio": "About", | ||
"companyName": "OneRoof", | ||
"companyUrl": "https://www.oneroofapp.com/", | ||
"githubUrlOrHandle": "https://github.com/Jan-Stepien", | ||
"xUrlOrHandle": "", | ||
"linkedinUrlOrHandle": "https://www.linkedin.com/in/jan-stepien-developer/", | ||
"webUrl": "" | ||
} | ||
], | ||
"title": "One Size Doesn't Fit All: Tailoring Flutter Architectures for Team and Business Success", | ||
"description": "In the fast-paced world of startups, idealism often needs to adapt.\r\nJoining a small team, I faced the challenge of balancing long-term architecture with immediate business needs.\r\nWe embraced a pragmatic approach, prioritizing features while gradually refactoring when possible.\r\nThis meant shared responsibility for testing and maintaining code. While not ideal, it fostered flexibility and helped us create a \"good enough\" workflow for our unique environment.\r\nThis experience taught me the importance of tailoring development strategies to team strengths and project realities.\r\n\r\nI would like to share with you the takeaways for the project and key concepts that you should be aware of when scheduling long term, large scale refactor of the app.", | ||
"videoUrl": "", | ||
"resources": [ | ||
{ | ||
"label": "Slides", | ||
"url": "https://github.com/Jan-Stepien/fluttercon-architecture-presentation/tree/main" | ||
} | ||
], | ||
"recommendations": [ | ||
{ | ||
"tool": "", | ||
"url": "", | ||
"comment": "" | ||
} | ||
], | ||
"level": "Introductory and overview/Intermediate/Advanced/Expert", | ||
"topics": [ | ||
"Application Architecture - Navigation", | ||
"Enterprise - Tech Leadership", | ||
"State Management" | ||
], | ||
"day": "Wednesday", | ||
"time": "2:35 PM", | ||
"startsAt": "2024-07-03T12:35:00.000Z", | ||
"endsAt": "2024-07-03T13:15:00.000Z", | ||
"room": "Flutter Forest", | ||
"format": "Session" | ||
} |