Code Craft
Writing Readable Code in Dart
Matt Carroll of Flutter Bounty Hunters has put together this nice video containing some tips on writing readable code in Dart.
While several of these ideas may seem obvious to a seasoned Flutter developer, I came across at least one tip that I think will help improve the readability of my own code. I'd suggest checking this one out to see if something resonates with you as well.
Tips & Tricks
VSCode Extensions for Automated Testing
Andrea Bizzotto lists some helpful-looking VSCode extensions in this Twitter thread to assist in stepping-up your automated testing approach.
I know that testing coverage isn't everyone's favorite topic (it's usually more fun to implement new features than to hook up those automated tests), but tools like this which make it easier should help drive adoption -- and in turn help improve code quality across the Flutter ecosystem.
Handy git/GitHub Cheat Sheet
I'm not sure exactly why this one caught my eye, but there is something sort of elegant about Tony Herbert's simple little hand-written git/GitHub cheat sheet here.
The thing I like about Tony's notes are that they outline what a typical "day in the life" might be as you work through the various coding activities of your day.
There are some further tweaks to his process listed in the thread's comments (and these are worth checking out), but this is simple and to the point. I like it. :-)
UI Design
FlexColorScheme Tool Update
With the latest dev release V5-dev.2, Mike Rydstrom continues to knock it out of the park with the latest enhancements to his FlexColorScheme tool.
If you aren't familiar, one of the coolest features of this tool is that you can play with various color-theme palettes, and once you find something you're happy with, you can simply copy and paste the associated color theme code into your own app, then consume it from there.
Hats off to Mike for this very impressive tool!
Flutter Jobs
Any Flutter Job Openings Where You Work?
As I mentioned at the top of the newsletter, I'm rolling out this new section next week, but I need your help.
If you know of an open Flutter dev role where you work and would like it featured here, just email the details to mark[at]flutterdeveloperweekly[dot]com and I'll take it from there. (While I may look to monetize this feature at some point in the future, these listings will be free for now.)
I can't promise to publish everything I receive, but I will give careful consideration to each submission.
Note that there are a couple of qualifications the position should meet before I'll consider listing it here in the newsletter:
- The role should be Flutter-related
- The role should be associated with the actual hiring company or organization. If you're a dev shop specializing in Flutter and work for several clients simultaneously, this is fine. If you're an employment agency looking to place developers at other companies, you should look elsewhere for your job posting.
One disclaimer: As my current Flutter project winds down I'm personally ramping up the search for my own next Flutter gig, so in addition to sharing your job listing with the wider Flutter community, don't be surprised if you see a resume from yours truly come back in the mix. :-)
I've been impressed at the number of open roles for Flutter developers I've seen lately, especially when compared to a couple of years ago. I'm hoping this new feature will serve as an added means of spreading the word for some of these roles.
// From Mark
Flutter Jobs
As an intro this week, I want to announce a new section for the newsletter, which I plan to start next week: Flutter Jobs.
I'd like to use this new section each week to post a few select job openings across the Flutter community. So if you're aware of an open Flutter job where YOU work, and would like to have it featured it here, please drop me a note and let me know. (See more details in the Flutter Jobs section below.)
On to this week's newsletter... Enjoy!
Mark Winters