5 ms·

The principle the author is getting at is valid though. It should not be that hard to run tests. There should be easy escape hatches in systems to stand them up

The principle the author is getting at is valid though. It should not be that hard to run tests. There should be easy escape hatches in systems to stand them up and tear down quickly so you can check your code against a reasonable "dummy" without having to reimplement the other side in your tests, as much ad possible. As you say, Docker would be great for that, as they say they use in your linked [1]. Did you read it? I wouldn't read too much into these posts. These are days apart and read more like inner-monologue from setting up systems. My process for implementing someone would probably fare the same. You wade through the cruft, complain about some things, but it gets done in the end and it's always nice to solve the pain points later.

disruptiveink 3y ago
Fair enough – there's nothing wrong with expecting systems to be able to be ran in dev mode suitable for running locally or within test containers, and that would be my expectation as well. As you say, the inner monologue writing style of "I have this server and this thing and tried this and also I don't like this" may have led me astray as it didn't feel particularly focused, so it wasn't super clear what the complaint actually was.
- cobertos 3y ago
  Yeahh, understandable, I had to read the linked articles twice to form coherency. More time than I would have invested normally, I only did so after reading your comment xD Makes me wonder if inner-monologue type stuff is even useful to post to the internet (something ive wanted to post more off because it sucks less energy from writing motivation). Takes more effort to parse as a reader though...
jddj 3y ago
> implementing someone It does feel like this sometimes.
shadowgovt 3y ago
It's tricky. In practice, easy escape hatches tend to become ways people deploy to production with the safeties off. In the past, we would then throw up our hands and say "Well boo on them for making their system hackable; sounds like their problem." But when you factor in the damage that can be done on the internet with things like botnets, it becomes everyone's problem. So sometimes people refrain from adding the escape hatches because they intend to work in an ecosystem of "You must be at least this technically savvy to play."

disruptiveink 3y ago

Fair enough – there's nothing wrong with expecting systems to be able to be ran in dev mode suitable for running locally or within test containers, and that would be my expectation as well. As you say, the inner monologue writing style of "I have this server and this thing and tried this and also I don't like this" may have led me astray as it didn't feel particularly focused, so it wasn't super clear what the complaint actually was.

cobertos 3y ago
Yeahh, understandable, I had to read the linked articles twice to form coherency. More time than I would have invested normally, I only did so after reading your comment xD Makes me wonder if inner-monologue type stuff is even useful to post to the internet (something ive wanted to post more off because it sucks less energy from writing motivation). Takes more effort to parse as a reader though...

jddj 3y ago

> implementing someone It does feel like this sometimes.

shadowgovt 3y ago

It's tricky. In practice, easy escape hatches tend to become ways people deploy to production with the safeties off. In the past, we would then throw up our hands and say "Well boo on them for making their system hackable; sounds like their problem." But when you factor in the damage that can be done on the internet with things like botnets, it becomes everyone's problem. So sometimes people refrain from adding the escape hatches because they intend to work in an ecosystem of "You must be at least this technically savvy to play."