Nehranis
@nehranis.bsky.social
Software Developer, Drummer.
Blog: dev.nehranis.de
Blog: dev.nehranis.de
"More important than the percentage of lines covered is human judgment over the actual lines of code (and behaviors) that aren’t being covered (analyzing the gaps in testing) and whether this risk is acceptable or not." (Google Testing Blog, Code Coverage Best Practices)
February 9, 2025 at 7:15 AM
"More important than the percentage of lines covered is human judgment over the actual lines of code (and behaviors) that aren’t being covered (analyzing the gaps in testing) and whether this risk is acceptable or not." (Google Testing Blog, Code Coverage Best Practices)
"The first term of what I’ve dubbed “Constantine’s Equivalence,” then, is that the cost of software is approximately equal to the cost of changing it." (Kent Beck, Tidy First?)
January 30, 2025 at 8:42 AM
"The first term of what I’ve dubbed “Constantine’s Equivalence,” then, is that the cost of software is approximately equal to the cost of changing it." (Kent Beck, Tidy First?)
"If we disagree in principle and we can discuss our principles, then we have a chance to agree on what to do sooner. We also have a chance to learn from each other." (Kent Beck, Tidy First?)
January 28, 2025 at 9:41 AM
"If we disagree in principle and we can discuss our principles, then we have a chance to agree on what to do sooner. We also have a chance to learn from each other." (Kent Beck, Tidy First?)
"Now, there are times to tidy first for sure. When: cost(tidying) cost(behavior change after tidying) < cost(behavior change without tidying) then absolutely tidy first." (Kent Beck, Tidy First?)
January 28, 2025 at 9:39 AM
"Now, there are times to tidy first for sure. When: cost(tidying) cost(behavior change after tidying) < cost(behavior change without tidying) then absolutely tidy first." (Kent Beck, Tidy First?)
"Nothing is more dangerous than an idea if it's the only one you have." (Andrew Hunt, David Thomas, The Pragmatic Programmer)
January 27, 2025 at 8:05 PM
"Nothing is more dangerous than an idea if it's the only one you have." (Andrew Hunt, David Thomas, The Pragmatic Programmer)
"Tidy first when: It will pay off immediately, either in improved comprehension or in cheaper behavior changes. You know what to tidy and how." (Kent Beck, Tidy First?)
January 23, 2025 at 9:12 AM
"Tidy first when: It will pay off immediately, either in improved comprehension or in cheaper behavior changes. You know what to tidy and how." (Kent Beck, Tidy First?)
"What does this mean for software design? Software design is preparation for change; change of behavior." (Kent Beck, Tidy First?)
January 21, 2025 at 9:53 AM
"What does this mean for software design? Software design is preparation for change; change of behavior." (Kent Beck, Tidy First?)
"When starting out, however, keep a new system on the more monolithic side; getting service boundaries wrong can be costly, so waiting for things to stabilize as you get to grips with a new domain is sensible." (Sam Newman, Building Microservices)
January 19, 2025 at 9:32 AM
"When starting out, however, keep a new system on the more monolithic side; getting service boundaries wrong can be costly, so waiting for things to stabilize as you get to grips with a new domain is sensible." (Sam Newman, Building Microservices)
"You might ask, “But what if we need it later?” That’s what version control is for." (Kent Beck, Tidy First?)
January 10, 2025 at 8:23 AM
"You might ask, “But what if we need it later?” That’s what version control is for." (Kent Beck, Tidy First?)
"When you find you have to add a feature to a program, and the program's code is not structured in a convenient way to add the feature, first refactor the program to make it easy to add the feature, then add the feature." (M. Fowler, John Brant, Kent Beck, William Opdyke, Don Roberts, Refactoring)
December 30, 2024 at 12:18 PM
"When you find you have to add a feature to a program, and the program's code is not structured in a convenient way to add the feature, first refactor the program to make it easy to add the feature, then add the feature." (M. Fowler, John Brant, Kent Beck, William Opdyke, Don Roberts, Refactoring)
"A unit test class should at least **test the *public* interface of the class**." (Ham Vocke, The Practical Test Pyramid)
December 30, 2024 at 12:17 PM
"A unit test class should at least **test the *public* interface of the class**." (Ham Vocke, The Practical Test Pyramid)
"“Whenever I have to think to understand what the code is doing, I ask myself if I can refactor the code to make that understanding more immediately apparent.”" (Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts, and Erich Gamma, Refactoring)
December 29, 2024 at 10:02 AM
"“Whenever I have to think to understand what the code is doing, I ask myself if I can refactor the code to make that understanding more immediately apparent.”" (Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts, and Erich Gamma, Refactoring)
Wrote a short blog post about Kotlin Numbers: dev.nehranis.de/posts/kotlin...
Kotlin Fundamentals - Numbers
Welcome to my Blog. Here I write about dev topics.
dev.nehranis.de
December 28, 2024 at 1:53 PM
Wrote a short blog post about Kotlin Numbers: dev.nehranis.de/posts/kotlin...
"Treat the service interfaces that your microservice exposes like a user interface. Use outside-in thinking to shape the interface design in partnership with the people who will call your service." (Sam Newman, Monolith to Microservices)
December 26, 2024 at 8:36 AM
"Treat the service interfaces that your microservice exposes like a user interface. Use outside-in thinking to shape the interface design in partnership with the people who will call your service." (Sam Newman, Monolith to Microservices)
"It is an open research question whether code coverage alone reduces defects, but our experience shows that efforts in increasing code coverage can often lead to culture changes in engineering excellence that in the long run reduce defects." (Google Testing Blog, Code Coverage Best Practices)
December 22, 2024 at 11:22 AM
"It is an open research question whether code coverage alone reduces defects, but our experience shows that efforts in increasing code coverage can often lead to culture changes in engineering excellence that in the long run reduce defects." (Google Testing Blog, Code Coverage Best Practices)
"Thus, our architects need to shift their thinking away from creating the perfect end product, and instead focus on helping create a framework in which the right systems can emerge, and continue to grow as we learn more." (Sam Newman, Building Microservices)
December 20, 2024 at 2:58 PM
"Thus, our architects need to shift their thinking away from creating the perfect end product, and instead focus on helping create a framework in which the right systems can emerge, and continue to grow as we learn more." (Sam Newman, Building Microservices)
"Work in smaller steps. That’s the tidying way. Big design changes too hard and scary? Take smaller steps. No, smaller. Still scary? No? Good." (Kent Beck, Tidy First?)
December 18, 2024 at 8:27 AM
"Work in smaller steps. That’s the tidying way. Big design changes too hard and scary? Take smaller steps. No, smaller. Still scary? No? Good." (Kent Beck, Tidy First?)
"Don't blame someone or something else, or make up an excuse. Don't blame all the problems on a vendor, a programming language, management, or your coworkers. Any and all of these may play a role, but it is up to you to provide solutions, not excuses." (A. Hunt, D. Thomas, The Pragmatic Programmer)
December 15, 2024 at 2:52 PM
"Don't blame someone or something else, or make up an excuse. Don't blame all the problems on a vendor, a programming language, management, or your coworkers. Any and all of these may play a role, but it is up to you to provide solutions, not excuses." (A. Hunt, D. Thomas, The Pragmatic Programmer)
"Instead of excuses, provide options. Don't say it can't be done; explain what can be done to salvage the situation." (Andrew Hunt, David Thomas, The Pragmatic Programmer)
December 15, 2024 at 2:51 PM
"Instead of excuses, provide options. Don't say it can't be done; explain what can be done to salvage the situation." (Andrew Hunt, David Thomas, The Pragmatic Programmer)
"“Complex applications combine different types of problems, so picking the right language for each job may be more productive than trying to fit all aspects into a single language.”" (Pramod J. Sadalage and Martin Fowler, NoSQL Distilled)
December 14, 2024 at 7:38 AM
"“Complex applications combine different types of problems, so picking the right language for each job may be more productive than trying to fit all aspects into a single language.”" (Pramod J. Sadalage and Martin Fowler, NoSQL Distilled)
"All communication between the services themselves are via network calls, to enforce separation between the services and avoid the perils of tight coupling." (Sam Newman, Building Microservices)
December 14, 2024 at 7:36 AM
"All communication between the services themselves are via network calls, to enforce separation between the services and avoid the perils of tight coupling." (Sam Newman, Building Microservices)
"So you should instead think of microservices as a specific approach for SOA in the same way that XP or Scrum are specific approaches for Agile software development." (Sam Newman, Building Microservices)
December 10, 2024 at 7:26 AM
"So you should instead think of microservices as a specific approach for SOA in the same way that XP or Scrum are specific approaches for Agile software development." (Sam Newman, Building Microservices)
"What sorts of things might you choose to investigate with a prototype? Anything that carries risk. Anything that hasn't been tried before, or that is absolutely critical to the final system. Anything unproven, experimental, or doubtful. Anything you aren't comfortable with." Pragmatic Programmer
December 8, 2024 at 8:34 AM
"What sorts of things might you choose to investigate with a prototype? Anything that carries risk. Anything that hasn't been tried before, or that is absolutely critical to the final system. Anything unproven, experimental, or doubtful. Anything you aren't comfortable with." Pragmatic Programmer
"Domain-driven design calls for a model that doesn’t just aid early analysis but is the very foundation of the design." (Eric Evans, Domain-Driven Design)
December 7, 2024 at 12:08 PM
"Domain-driven design calls for a model that doesn’t just aid early analysis but is the very foundation of the design." (Eric Evans, Domain-Driven Design)