It turns out, focusing on “the fundamentals” first is a great way to never get started at all.
The Myth of the Leave-Averse Software Engineer: Why Balance Matters
In the dimly lit coding cave, a brilliant software engineer had unlocked the secrets to a groundbreaking algorithm. Little did they know, their discovery held the power to change the digital world forever. But as whispers of their breakthrough spread, a shadowy figure emerged, determined to seize the code’s potential at any cost.
Rollback and Roll-Forward Plans vs. CI/CD Workflows
When it comes to software development, rollback/roll-forward plans and CI/CD workflows are common methodologies and workflows that teams adopt to ensure effective development practices.
Rollback vs. Roll-Forward Plans in Software Engineering: Which is the Better Approach?
In software engineering, there are two main approaches to handling changes and updates to a system: rollback and roll-forward plans. Both approaches have their own advantages and disadvantages, and the choice between them largely depends on the specific needs and requirements of a project.
Forget What You Know: The Importance of Being Open to New Ideas in Software Development
Learn and relearn: one of the keys to staying relevant and successful in the fast-paced world of software development
How regular breaks can help you write better code
Here’s a surprise (yet obvious) trick on how you can write better code without doing a thing – literally
Writing Helpful Technical Documentation
Learn how to write helpful documentation that not only helps other members of your team understand your code, but also serves as a valuable resource for future reference and maintenance.
What to do with unfinished side projects
So you are a developer? Yes? And you have dozens of unfinished projects? What do you do with all your unfinished side projects?
Working With A Legacy Codebase: Why Rewriting From Scratch Doesn’t Work
What to do if you need to change code that’s impossible to maintain, without making it worse? Explore working with legacy code and why rewriting may bad for you.
How to be a Terrible Developer in 10 Simple Steps
A sarcasm Step 1 Whatever issue you face, make sure to always blame others and make them responsible for it. It’s generally never your fault, so refuse to consider any …