Strong type systems, memory safety, automatic memory management and so on have had zero effect on software quality, because all the extra slack was consumed by new features instead
From experience, these make a significant difference in medium to large teams, where juniors / newcomers feel more confident working a codebase without the fear that they’ll trigger a chain reaction of load-bearing tech debt bugs.
-
-
I think that's the responsibility of testing
-
Every project I’ve worked on with extensive automated unit tests blew up gloriously when we needed to make a large architectural change. Types, in contrast, showed us exactly what needed to be updated. There may be unit tests that wouldn’t do that, but I haven’t seen it.
- Još 4 druga odgovora
Novi razgovor -
-
-
I guess the lesson here is to pick the best tool for the job. Smaller teams need tools that are inclined towards faster development iteration. Bigger teams need tools for maintenance. That’s where Objc vs Swift fit
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.