2013|10|11|12|
2014|01|02|03|04|05|06|07|08|09|10|11|12|
2015|01|02|03|04|05|06|07|08|09|10|11|12|
2016|01|02|03|04|05|06|07|08|09|10|11|12|
2017|01|02|03|04|05|06|07|08|09|10|11|12|
2018|01|02|03|04|05|06|07|08|09|10|11|12|
2019|01|02|03|04|05|06|07|08|09|10|11|12|
2020|01|02|03|04|05|06|07|08|09|10|11|12|
2021|01|02|03|04|05|06|07|08|09|10|11|12|
2022|01|02|03|04|05|06|07|08|09|10|11|12|
2023|01|02|03|04|05|06|07|08|09|10|11|12|
2024|01|02|03|04|05|

2023-06-03 "How could I possibly know that?" [長年日記]

As a rule, your code will not work in someone else's environment -- this is common sense for code.

Virtual environments and microservices are a way to solve that problem, but they also fail to create that environment -- this is common sense in environment building.

It is common knowledge among developers that "it is tough to run code written by others on a computer.

And here comes the problem.

People who do not know this common sense will ask developers, "Why doesn't it work? How do I get it to work?" they are not afraid to ask questions.

"How could I possibly know that?"

The only way I can reply is.

Because, in my environment, the code is working.

-----

There is a dividing line between making the developer think, "I want to help you," and making the developer feel, "He's an annoying son of a bitch.

It is to describe in as much detail as possible how you have 'done everything you can to solve this problem.'

This will let the developer know how serious you are and how much pain you are in.

After that, you should be as polite as possible and add, 'Please let me know when you have time and feel up to it.

Developers who release code in good faith and for free are not obligated or responsible for solving your problems but are there to "help when they feel like it."

-----

Well, the story here is the same as the story here.