Learn more about computerscience with this collection
The differences between Web 2.0 and Web 3.0
The future of the internet
Understanding the potential of Web 3.0
Leaving technical debt unaddressed can result in several issues for your organisation, such as higher total cost of ownership, slower time to market, reduced agility because of a poorly designed architecture, and poor security.
Make sure to have a process that makes it easy to share knowledge with team members and resolve technical debt continuously.
14
48 reads
MORE IDEAS ON THIS
Design debt often occurs in highly competitive markets or startups where speed to market often is the highest priority.
When delivering new features quickly, you're not thinking about the structure of features or the architecture of your codebase. It often gets neglected, making it increasi...
14
62 reads
A retrospective meeting addresses what went well and what didn’t. It’s an open stage to share feedback without placing blame. It would be best if you focused on improvement.
Benefit: You can use retrospective meetings to share updates about the code. Engineers can show what...
14
41 reads
Tracking technical debt in the editor allows engineers to:
Benefit: Developers already spend most of...
14
31 reads
14
34 reads
Code debt is about writing bad code and not fixing this in time. For instance, a developer wants to quickly merge code without writing sufficient tests or adhering to code standards.
Many organizations use automation tools such as pre-commit hooks with code linting to verify code quality. W...
14
55 reads
Technical debt refers to a rushed development process or a lack of shared knowledge among team members. However, in many cases, technical debt is inevitable and is part of a normal software development process.
The negative impact of technical debt on businesses is massive....
14
139 reads
Imagine two software engineers have worked on a new feature. They own all knowledge about this specific feature. However, other software engineers in your team don't have this knowledge. When they have to work on this feature or have to do an implementation that makes use of this feature, they wo...
14
82 reads
A refactoring week allows your team to resolve open bugs, evaluate the current architecture, and prepare the architecture for the upcoming product features.
Benefit: A refactoring week gives the needed breathing room for developers to evaluate and reflect on the code befor...
14
50 reads
Track metrics related to different types of tech debt.
14
40 reads
CURATED FROM
Read & Learn
20x Faster
without
deepstash
with
deepstash
with
deepstash
Access to 200,000+ ideas
—
Access to the mobile app
—
Unlimited idea saving & library
—
—
Unlimited history
—
—
Unlimited listening to ideas
—
—
Downloading & offline access
—
—
Personalized recommendations
—
—
Supercharge your mind with one idea per day
Enter your email and spend 1 minute every day to learn something new.
I agree to receive email updates