Crystal balls and clairvoyance: Future proofing in a world of inevitable change
While the future may be a mystery, you can design software to accommodate future changes. But how much future-proofing gets in the way of good design?
Plan for tradeoffs: You can’t optimize all software quality attributes
An essential part of requirements analysis is understanding which quality characteristics are the most important so that designers can address them appropriately.
Podcast 392: Do polyglots have an edge when it comes to mastering programming languages?
French, Swahili, Perl, Danish, Spanish, and C#.
Why SOLID principles are still the foundation for modern software architecture
While computing has changed a lot in the 20 years since the SOLID principles were conceived, they are still the best practices for designing software.
Code quality: a concern for businesses, bottom lines, and empathetic programmers
Code quality affects the mental state of a programmer, communication within their team, and the incentives attached to their work. Improve your code and you can improve your organizational health and competence as a whole.
Diagnose engineering process failures with data visualization
Here's three areas where data visualization can make your engineering life easier.
Using stretch work assignments to help engineers grow
Stretch work assignments are tasks or projects that are a bit beyond an engineer’s current skill or knowledge level and that allow them to improve and learn new things. When done correctly these assignments serve a dual purpose of providing learning opportunities for your engineers, while at the same time completing a project or task that will help your company.
Can InnerSource bring open source practices to closed corporate bureaucracies?
Open source won. Now, the OSS way of working is making inroads into new territories: the corporate engineering department.
The pros and cons of being a software engineer at a BIG tech company
There are benefits to being a technical lead at a less software intensive business.
Daniel Chae
Director of Content
Requirements volatility is the core problem of software engineering
It's now been more than 50 years since the first IFIP Conference on Software Engineering, and in that time there have been many different software engineering methodologies, processes, and models proposed to help software developers achieve that predictable and cost-effective process. But 50 years later, we still seem to see the same kinds of problems we always have: late delivery, unsatisfactory results, and complete project failures.
