@RogerAlsing Write good feature tests that describes the business rules, but in a manner that still makes it possible (and easy!) to refactor the code without having to change the tests.
@RogerAlsing You spend a lot more time reading (and trying to understand) code than you spend writing code, so you should put more of effort in writing readable code than into creating “smart” technical/generalized solutions to make the it quicker to write code.
@ChristinGorman Well said! Totally agree 😊 And yes, as a developer I’m prepared to take the responsibility of not asking for permission to do my job properly 😊
August 27th, join the first DDD clinic (online but interactive) event with our international panelists @EllenLippe @selketjah @gweinbach@JulienTopcu (animated by @tpierrain )
Free registrations here: https://t.co/DMRsOVCjWc
@julielerman@AnitaKvamme Hey! How was your talk yesterday? I wish I was there to see it :-) Still in Spain, though :-) Good luck tomorrow! Hope to see you soon
Ta-daa! Vi har ny nettside, oppdatert visuell profil og video og greier! 🔥
Vi er veldig fornøyde med den - hva synes dere? (hint: vi er bittelitt sårbare)
https://t.co/SyAnmIH0Rt
Finally, a book that empirically proves that adding tests improves productivity--It’s NOT a trade-off—and that quality improves business outcomes. “Accelerate” (https://t.co/nQKxpgB9cW) is essential reading. I can’t recommend it too highly. @jezhumble
Sammen med en av våre kunder, Nimbus Direct AS, gjør vi det nå enkelt å håndtere lydopptak også etter 25. mai når GDPR trer i kraft. Les mer her: Opptaks- og samtalehåndtering - https://t.co/3PQk0uywuT
Unused code slows down development. If you know that a feature/table/collection/file/resource is no longer needed then delete the code and everything that touches it. This should not be a sporadic effort but constant, ongoing activity. Keep your code lean.