you need to test your application? be happy you used an application context that you can redirect to your functional test service. what if some use cases require you use s3 to retrieve the different words? thank god you used interfaces and beans for the implementation. what if requirements change and you need a new upper bound? well it's good that you have that wrapped into configuration so you don't need to restart the service to pick up the change.
reality is the battlefield
- she/they (pl)
- breadthcharge.net/
the first line goes in Cohost embeds
🐥 I am not embroiled in any legal battle
🐦 other than battles that are legal 🎮
I speak to the universe and it speaks back, in it's own way.
mastodon
email: contact at breadthcharge dot net
I live on the northeast coast of the US.
'non-functional programmer'. 'far left'.
conceptual midwife.
https://cohost.org/NireBryce/post/4929459-here-s-my-five-minut
If you can see the "show contact info" dropdown below, I follow you. If you want me to, ask and I'll think about it.
You must log in to comment.
in reply to @hayley's post:
Look at that subtle configuration injection, oh god. It even does cqrs...
Meanwhile in gamedev:
"that many print calls seems expensive, can we bake the fizzbuzz instead?"