Github has made it easy for millions of developers to publicize their projects so they can attract users and collaborators. But these developers often find themselves spending hundreds of hours building a project, only to push it to GitHub and earn a mere one or two stars. This is an amazing write up by Abhinav Suri on the recipe of creating the perfect open source GitHub repository.
Andrey Azimov had an itch he needed to scratch: When is the best time to surf every day. He learned how to code, built a web app and then launched it in 2 months! Go read his story, inspiring stuff!
A good read from the Professor Beekums blog, arguing that software developers with sysadmin experience can write better code. Since the context is really important when building software, developers need to understand the environment where their code will be running or they may not build it properly.
Over-engineering can be the enemy of shipping! Join RDX as he writes on how to avoid falling in the trap. Many articles say Dont over-engineer but don’t say why or how. Here are 10 clear examples.
This article focuses on demystifying some of the trendy topics in today's software development workflows. Written by Suzie Prince, she explains the basics of CI/CD/DevOps to product managers and business folks involved in software companies.
Some CD anti-patterns arise not from an existing behavior, but by trying to actually implement the practices without understanding their goals first. We want to go faster and have faster-delivering products. To do so we should also be able to go faster and faster in adapting our pipeline to support that goal.
A good post by Pier-Luc Brault with insights from working for 2 years as a backend developer. He writes on how modern backend development should be more about architecture than writing code and that front-end should dictate the API design, not the other way around.