"exactly, I would have liked the grisp of the interesting part of it"
And that is all, no interesting excerpt, I was able to get source code of the entire page myself :) You are writing an article/tutorial. This kind of work should be in, this was my initial feedback.
I'm not sure how to read your comment as everything in the script seems to be a comment? Probably format messed up.
What it usually fails at (maybe 4 can do it, I only use 3.5) is that the output should have one line per line-number, so nothing like 9-15 but 9,10,11,12 etc. I made this very explicit, I gave also examples on how the output should look like. Nothing helped.
Also, I explicitly set it should work under macOS but there were many syntax errors or uses of grep that are incompatible with macOS. So maybe part of it would have worked with linux, not sure. If you can maybe reformat, I could check
So what is the USP of this one against the others?
I tried my simple favorite one where all of these tools fail (prompt has more details): Write a script that converts git-diff output to a file that can be easily grepped by filename and linenumber.
Never works. And I point then to the errors to clarify in quite a few iterations. Will never be fixed. I did not find any tool that can do that.
The answer from this tool is just the same garbage than with ChatGPT. Not better, not worse, same shit.
I get that this is really interesting and I surely enjoyed the read... But has it really any practical implications?
I mean, in a sense, there are so many mathematical riddles...
Anyways, I'm fine to ignore this question. Very nice!
Testing hugely via expensive integration tests or E2E is needed no matter which software you have. And you could easily fall into doing that for microservice architectures. However, a common way is rather having contract tests. Google Fowler's article for it
What puzzles me at such websites is that they cannot manage to briefly describe WHAT they actually do. Without previous information about it, you have no clue to figure out what they are for (I googled it, Github says a bit more, but the website? No clue for that, even in documentation)
What such articles lack is that they assume anyone could do anything, but that's just not true.
To become a really well-paid, influential developer (IC called here, I think), you need to be smart, so that others that are also smart acknowledge you as a very skilled developer. Plus, it's probably not enough to be very smart (which in itself most people are not), but you need some level of politics that is always necessary.
For managers, it's also not a default that promotion will just come with years being somewhere, just untrue.
I would say, although depressing, some people in the industry just don't have it to be successful enough in anything to feel great at their job and there is not always a way to change this. I would never fingerpoint to anyone and say "he cannot make it", I would probably not even recognise that person (apart from myself) but I would say they take up a great portion, unfortunately.
Today's environment enforces performance. Those who cannot perform, will have a hard time...