When you dont know the requirements its hard to write a test. If you start implement the what you know and along the way you will probably discover new requirements. When you have a better understanding of the requirements. write the test, then I suggest to try to stash your prototype implementation and do write a new and better implementation. Inspired by Use Git tactically
I will be happy at work if
– Flexible about when and where you want to work
– Physical workspace must be quiet and have a few people from your team around and some windows where you can look at something nice
– Communication must be pull and not push pattern
– There must be time for innovation and learning
– Technical dept is not to big
I reflected on this when I read the blog on https://stackoverflow.blog/2022/03/17/new-data-what-makes-developers-happy-at-work
I have had a hard time doing copy/paste code in spock test that shares same setup logic.
The Architect Elevator — Visiting the upper floors
— Read on martinfowler.com/articles/architect-elevator.html
a blog by Jeff Atwood on programming and human factors
— Read on blog.codinghorror.com/the-ultimate-code-kata/
Using WireMock to record third party API calls you can get high quality mocks that reflect reality and are much easier to maintain
— Read on hceris.com/recording-apis-with-wiremock/
Learn what executable specifications are, where they fit in development workflows, and how HipTest can make them easier to create and execute.
— Read on cucumber.io/blog/hiptest/what-are-executable-specifications/
Using the Kafka Visualization tool you can simulate how data flows through a replicated Kafka topic, to gain a better understanding of the message processing model.
— Read on softwaremill.com/kafka-visualisation/
In this post I am going to propose a set up to run any kind of application on a developer laptop in complete isolation. It is based on packaging the …An Isolated Developer Setup with Docker