This is about the OP saying "I tried programming but I gave up" post that is clearly not asking for help, but some along the lines of "i didn't like movie X" , you make them like the movie.
Also not everyone can make a living writing FOSS projects. Especially if you are not in the first world.
> This is about the OP saying "I tried programming but I gave up" post that is clearly not asking for help, but some along the lines of "i didn't like movie X" , you make them like the movie.
People usually abandon learning programming as the learning curve to some programming languages is too steep for them to climb.. Usually if they get help from a developer who knows the language then they can learn within hours more than they ever did alone.
So such encouragements are viewed as ethical in computer science if you are willing to invest the time to teach them.
> Also not everyone can make a living writing FOSS projects. Especially if you are not in the first world.
Lol who told you that? People living in a 3rd world country getting hired to work on a FLOSS projects is very common from my experience.. Mostly because they are qualified to do the job and are more economical to hire.
@FrailLeaf @LordMordred @bwk literally everyone.. There are not hard restrictions on who can be hired to work on an open-source projects.
@FrailLeaf @LordMordred @bwk like they can always change an industry.. So what's your point?
> How does a person working a job, writing absolutely horrible code change the industry?
The gross majority of people working on open-source projects write a horrible code it's by design done this way.
So again the important thing is abstracting and documenting the code preferably writing down what you are doing, how and why
@FrailLeaf @LordMordred @bwk e.g. what @lupyuen is doing with https://qoto.org/web/statuses/107793119639236951
@FrailLeaf @LordMordred @bwk Like footprinting is generally time efficient so what's the issue?
The practice of figuring out how the software works and why.
My way of doing it is by adding "WTF" comment tags all over the code as comments to things that i do not understand and then commenting out random codeblocks and changing them to see how it affects the outcome to write docs.
e.g.
fn main() {
println!("Hello, world!");
}
fn main() {
// WTF(Krey): what is this supposed to do?
println!("Hello, world!");
}
fn main() {
// WTF(Krey): what is this supposed to do?
println!("Hello, worldSSSSssss!");
}
Oh this block is the one that prints in the console!
fn main() {
// Outputs 'Hello, world!' in the console
println!("Hello, world!");
}
"Experimental Development" is what I call that. Also if you determine your code is correct, because it behaves correctly, that's precisely the same mistake. You can only understand code from the inside, not from the outside, and the best way to analyze the inside is logging. Period. Full stop. There are essentially zero exceptions to that rule.
@clay @FrailLeaf @LordMordred @bwk
If you are ever in a situation where you need to collect a
"logging data for post-analysis" then logging is just about the worst thing to use that for as it has a major impact on the efficiency of the program and you always do this once you understand the code and have established a clean room as without it your logging data will have bunch of noise in them.
Thus the case for benchmark tests preferably using criterion.
@clay @FrailLeaf @LordMordred @bwk
So you spend your time writting a logging solution and then remove it?
How is that anywhere near resource efficient?
If you are in a situation where you need to do extensive testing then someone else will most likely be in the same situation in a later date -> You implement the logging permanently on demand preferably without including it in the build binary if the programming language supports it.
