DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

Cover image for 10+ bonus resources from the Dev Weekly newsletter (Issue #26) πŸ“§
Vaibhav Khulbe
Vaibhav Khulbe

Posted on • Updated on

10+ bonus resources from the Dev Weekly newsletter (Issue #26) πŸ“§

Check out the bonus resources of the previous week πŸ‘€

For those who don't know what Dev Weekly is, it's a weekly developer-focussed newsletter which I've created in order to share resources which I get to other developers in order to help them.

Dev Weekly covers not only dev related links but also for UI/UX designers, comes with weekly coding challenges, some tips on life and industry, events to attend, videos and tutorials. It finishes off with a Repo of the Week. All in all, it's a newsletter which will help everyone in the industry, that's why it comes with more than 50 resources in a single issue. It can be a lot to take in for a newbie but I suggest reading 1-2 articles a day of your choice.

But wait...I collect more resources like these in a week so I've decided that those links which couldn't be added in this week's issue to be listed here. I hope you will enjoy these articles/videos. Cheers! 🍻

More GIF

Here we goooo!

Bold ones are my favourite

πŸ‘¨β€πŸ’» Miscellaneous

  1. How this self taught Software Engineer in India learned to code - No CS Degree

  2. A Less Known Attack Vector, Second Order IDOR Attacks - Noteworthy

  3. My Second Year as a Solo Developer - mtlynch.io

  4. How I’m testing in 2020 - b-list.org

  5. 3 signs you need DesignOps at your organization - Inside Design

  6. things-i-believe.md - GitHub Gist by stettix

  7. I Applied For A Job I Wasn’t Qualified For, & It Completely Changed My Career - The Financial Diet

πŸ“± Mobile App Development

  1. Flutter Essential: Bloc, Networking (REST API call), Unit Testing, Code Coverage - Flutter Community on Medium

  2. Unsafe Swift: Using Pointers and Interacting With C - raywenderlich.com

  3. Reactive state container architecture with knot - StefMa

  4. How to convince your boss to move to Flutter - Codemagic Blog

  5. Better iOS Apps with Interaction-Driven Design - Gitconnected

🌐 Web Development

  1. πŸ–Š CodePens of the week: Wheel of Dogs photo gallery by Stephen Lee, πŸ“Έ Polaroid Camera In CSS by Sarah Fossheim and Neuomorphic Checkboxes by Braydon Coyer.

  2. Optimising SVGs for the Web - CSS {In Real Life}

  3. How To Create A Headless WordPress Site On The JAMstack - Smashing Magazine

  4. HTML attributes to improve your users' two factor authentication experience - Twilio Blog

  5. Improved accessible routing in Vue.js (updated) - marcus.io

  6. Building Modern Applications with Next.js and MongoDB - MongoDB Blog

  7. Why should you use HSL color representation in CSS? - The Software House

🎨 UI/UX

  1. Website navigation design: What you need to know (plus 5 best practices) - Inside Design

  2. Why design systems fail and how to make them work in 2020 - UX Collective

  3. How to mock up UX writing - Dropbox Design

🌟 Repositories of the Week

  1. FileX by JideGuru

  2. clean-code-python by zedr

  3. gif by maxhumber

🎬 Video(s)

  1. Csaba KozΓ‘k - Annotation processing for Kotlin - Kotliners

  2. What It Takes to Stand Out as a Designer - Flux

  3. Chrome 80 - What’s New in DevTools - Google Chrome Developers

πŸ‘¨β€πŸ« Tutorial(s)

  1. Lets Upgrade React's Official TicTacToe Game with Hooks & Typescript! - Justin Kim

  2. Awesome Cursor Animation With CSS & Javascript! - Dev Ed


Sign up to get the full issue in your mailbox πŸ“§

If you're still not convinced then you can take a look at the archive page.

Thanks for reading and have a great day. See you 7 days from now. πŸ˜‰

Top comments (2)

Collapse
 
olore profile image
Brian Olore

Great list! Thank you!

Please fix the link to "things-i-believe.md - GitHub Gist by stettix"

Collapse
 
vaibhavkhulbe profile image
Vaibhav Khulbe

I'm glad you liked it. Thanks for pointing it out, I've fixed that. πŸ₯‚

Timeless DEV post...

How to write a kickass README

Arguably the single most important piece of documentation for any open source project is the README. A good README not only informs people what the project does and who it is for but also how they use and contribute to it.

If you write a README without sufficient explanation of what your project does or how people can use it then it pretty much defeats the purpose of being open source as other developers are less likely to engage with or contribute towards it.