"The cucumber is bitter? Then throw it out. There are brambles in the path? Then go around them."

#11・

Stay up to date, be part of a community and show your support.

160

subscribers

34

issues

Subscribe to our newsletter

By subscribing, you agree with Revue’s Terms of Service and Privacy Policy and understand that StoicallyTyped Newsletter will receive your email address.

StoicallyTyped Newsletter
Hello and welcome back! Life was pretty busy the last few weeks so thanks for sticking around in the absence of content! There was a lot to catch up on with Google I/O and I hope you’ve been able to explore some of that great content.
We will now return to your regularly schedule newsletter. 🙃
🏳️‍🌈 Happy pride month! 🏳️‍🌈
I hope you’ve had a wonder few weeks! There were lots of really cool things that happened! Here they are in case you missed them.

👾 Fun Stuff
Zac Sweers
One down, enjoy your new Kotlin color (rolling out hopefully next week-ish?) https://t.co/wAgAeNcshO https://t.co/VBZAxdL8EM
Thanks to Zac Sweers the Kotlin color on GitHub has been updated! The PR to make this change got official buy in from the lead designer for the Kotlin brand which helped solidify the change! This new color will be seen most when sharing GitHub projects like you will see below!
theapache64/create-compose-app
📚 TL;DRs
Kotlin Coroutines 1.5 Notable Changes
Learning State & Shared Flows with Unit Tests
Bluetooth LE for modern Android Development - Part 1
🛠 For Your Toolkit
🧑‍💻 Interview Practice Question
What are some ways to ensure that text in TextViews is accessible?
Respond to the question in a reply or the Twitter thread of this issue to have your answer included in next weeks issue!
⭐️ Answer to Last Week's Question
There was no question last issue!
💭 Stoicism x Tech
“The cucumber is bitter? Then throw it out. There are brambles in the path? Then go around them. That’s all you need to know.” - Marcus Aurelius
This week’s quote is about choosing a path the least conflict or complexity. This too can apply to software. It is better to write code that is expressive and easy to read than something that is complex for the sake of brevity.
Remember your code is something that will need to change in the future. Other developers will need to engage with it and you will also need to read it again in the future. Creating code that is easy to understand is a mark of a great developer.
👋 Want to Contribute!?
Did I miss something great this week? Have an career question you want answered by the community? Send them to me on Twitter or reply to this email. I’d love to hear from you and chat!
Stay hydrated, have a great week and happy Pride month 🏳️‍🌈!
Don’t miss out on the other issues by Matt McKenna
Did you enjoy this issue? Yes No
Matt McKenna
Matt McKenna @himattm

Develop a thoughtful approach to software engineering. Focused on Android, applicable to all. Delivered Monday mornings to kick off your week.

You can manage your subscription here.
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Created with Revue by Twitter.